c60fcebc12
Summary: `ObservabilityContext` is a structure that helps logging facilities within Mononoke to make logging decisions. Specifically, the upcoming `DynamicLoggingDrain` and already existing `MononokeScubaSampleBuilder` will have this structure as a component and decide whether a particular logging statement (slog or scuba) should go ahead. Internally, `ObservabilityContext` is a wrapper around data received from a [configerator endpoint](https://www.internalfb.com/intern/configerator/edit/?path=scm%2Fmononoke%2Fobservability%2Fobservability_config.cconf). This diff makes a few unobvious decisions about how this is organized. My goals were: 1. to have production (i.e. reading from configerator), static (i.e. emulating current prod behavior) and test variants of `ObservabilityContext` 1. to avoid having consumers know which of these variants are used 1. to avoid making all consumers of `ObservabilityContext` necessarily generic 1. to avoid using dynamic dispatch of `ObservabilityContext`'s methods Points 3 and 4 mean that `ObservabilityContext` cannot be a trait. `enum` is a common solution in such cases. However, if `ObservabilityContext` is an `enum`, consumers will know which variant they are using (because `enum` variants are public). So the solution is to use a private enum wrapped in a struct. Reviewed By: mitrandir77 Differential Revision: D25287759 fbshipit-source-id: da034c71570137e8a8fb7749b1e4ad43be482f66 |
||
---|---|---|
.. | ||
benchmark | ||
blobimport_lib | ||
blobrepo | ||
blobrepo_utils | ||
blobstore | ||
blobstore_sync_queue | ||
bonsai_git_mapping | ||
bonsai_globalrev_mapping | ||
bonsai_hg_mapping | ||
bookmarks | ||
bulkops | ||
cache_warmup | ||
changesets | ||
cmdlib | ||
cmds | ||
commit_rewriting | ||
common | ||
derived_data | ||
edenapi_server | ||
fastreplay | ||
filenodes | ||
filestore | ||
git | ||
gotham_ext | ||
hgcli | ||
hgproto | ||
hook_tailer | ||
hooks | ||
lfs_import_lib | ||
lfs_protocol | ||
lfs_server | ||
load_limiter | ||
manifest | ||
mercurial | ||
metaconfig | ||
microwave | ||
mononoke_api | ||
mononoke_hg_sync_job | ||
mononoke_types | ||
mutable_counters | ||
newfilenodes | ||
observability | ||
permission_checker | ||
phases | ||
pushrebase | ||
reachabilityindex | ||
regenerate_hg_filenodes | ||
repo_client | ||
repo_import | ||
revset | ||
scs_server | ||
segmented_changelog | ||
server | ||
sshrelay | ||
tests | ||
time_window_counter | ||
tunables | ||
unbundle_replay | ||
walker | ||
Cargo.toml | ||
README.md |
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build
. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future