| commit | fb0fb6db2a30038fecea4500ffd4281ad510c1d3 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Fri Feb 18 12:11:28 2022 +0100 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Mon Feb 21 11:58:32 2022 +0000 |
| tree | 2d2e9a9457da5c50af1a30aa258e9c5d58ba8d15 | |
| parent | d9775a656cb709133407507b1e3a94793dd0ea49 [diff] |
m/n/c/rpc: implement Span/Trace This is a first pass at implementing basic support for Dapper/OpenTracing/OpenTelemetry-style tracing within Metropolis RPCs. More precisely, this implements an API to expose an RPC-local Span to RPC handlers (unary and streaming). These Spans are currently backed by a logtree logger, and aren't processed further (ie. there's no support for child spans and carrying span information over the wire when performing remote calls from an active Span). However, this allows us to at least start emitting Span Events and use them for debugging purposes. Since we don't yet have OpenTelemetry in our GOPATH, we reimplement a minimum subset of the Span type that should still be compatible with real OpenTelemetry types. Once OpenTelemetry lands in our GOPATH (by way of it landing in k8s, for example), we'll move over to using the real type instead. Then, we can also begin integrating with OpenTelemetry proper, ie. start sending traces over to collectors, start injecting/extracing span information over gRPC, etc. Another change on top of this one actually uses the Trace(ctx) functionality within the curator - this is just the library implementation. Change-Id: I85506303538aacc137a28828ab39ccfd9ff72924 Reviewed-on: https://review.monogon.dev/c/monogon/+/541 Reviewed-by: Leopold Schabel <leo@nexantic.com>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...