Opentelemetry implementation and monitoring/observability updates #1453
Draft
the2hill wants to merge 24 commits intorackerlabs:mainfrom
Draft
Opentelemetry implementation and monitoring/observability updates #1453the2hill wants to merge 24 commits intorackerlabs:mainfrom
the2hill wants to merge 24 commits intorackerlabs:mainfrom
Conversation
the2hill
changed the title
the2hill
force-pushed
the
otelimpl1
branch
2 times, most recently
from
2071857 to
9250d01
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR implements opentelemetry as a metrics, logging and tracing ecosystem. This PR touches the entirety of the monitoring and observability stack. The goal was to consolidate the related monitoring and observability tooling in to a more manageable and clean directory and namespacing structure. This means that services/applications like Loki, Grafana, Prometheus(and its related tooling) have all been placed within the monitoring directory structure as well as migrated from various namespaces to a sinigle 'monitoring' namespace. That means that this pr won't directly work against current deployments.
In order to properly structure things a destructive tear down of the components is required. Loki, Prometheus(and any exporters), Grafana(and its database) needs to be completely uninstalled, including the PVC's. Metrics, and local logging will be lost during the migration process. Once all the components are removed a fresh install will bring everything back up functioning under the 'monitoring' namespace. Follow the docs that are part of this PR for more information.