set up opentelemetry metrics for new infra (and now) #2999
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
datadog is the target system for logs & metrics in the new infra. We're already running the datadog agent locally on the server to ship our logs, so we can also start using it for metrics. I already activated the OTLP endpoint, and also enabled the process & nginx monitoring. I'll be able to setup & test in more detail when I have the necessary permissions.
This way we can have both systems running side by side for some time, and compare.
In our codebase I chose not the "native" datadog libraries, but opentelemetry as standard solution. Hopefully this will lead to us never having to refactor any more, only choose new exporters.
After I validated everything and created the necessary dashboards in datadog, we can drop the whole prometheus logic & integration.
Some detail notes:
recent_*metrics, I'm thinking about either dropping them completely (after the initial learning they brought, I didn't see much additional value), or perhaps using datadog log-based metrics for them, where datadog generates metrics by parsing logs.