| commit | 26d5225a142057b6eb04cff9ba86173a6682b626 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Mon Feb 07 15:57:54 2022 +0100 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue Feb 08 13:00:46 2022 +0000 |
| tree | 8b5d8b35d0cd629d467b1e01200c2f12a950a588 | |
| parent | cc078df2124306799c66786833746999259ea792 [diff] |
m/p/supervisor: implement sub-loggers This permits logging from a runnable into a logtree sub-DN that is not backed by an actualy child runnable. For example, 'root.foo' can request a SubLogger with name 'bar' to emit logs into 'root.foo.bar'. This is in preparation for logging RPC calls within supervised runnables, but can also come in handy in other situations where we'd like to log to separete 'topics' within a single runnable. This breaks 1:1 correspondence between logtree DNs and supervisor DNs. An alternative would be to introduce extra 'tags'/'topics' eg root.foo:bar, but that would require encoding extra logic to the logtree. However, that would perhaps allow us to introduce higher cardinality child loggers, with a logger per RPC. We'll have to consider this at some later point. Let's see where this takes us, there's a chance we'll roll this back if it's too confusing from an UX point of view. Change-Id: Ibdee5c2b400bb8fce76b0a4f781914748793db0e Reviewed-on: https://review.monogon.dev/c/monogon/+/536 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 //...