-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(self-monitoring): add support for self-monitoring #109
Merged
Conversation
This file contains 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
basti1302
commented
Aug 22, 2024
basti1302
commented
Aug 22, 2024
basti1302
force-pushed
the
self-monitoring
branch
9 times, most recently
from
September 1, 2024 10:32
c008a0d
to
03729f0
Compare
This commit lays the foundation for self-monitoring: 1. Add a cluster-scoped Dash0OperatorConfiguration CRD, which contains a default endpoint and authorization setting, which will be used for self-monitoring. 2. When self-monitoring is enabled in the Dash0OperatorConfiguration resource, the controller deployment and the collector daemonset are extended with environment variables like OTEL_EXPORTER_OTLP_ENDPOINT etc., based on the operator configuration resource export settings. 3. On removal of the Dash0OperatorConfiguration resource, the same environment variables are removed from the controller deployment and collector daemonset. 4. Add metrics and tracing to the filelogoffsetsynch container via the Go OTel SDK. Other collector containers and the operator controller process will be extended with the Go OTel SDK in a later iteration. 5. Add a new end-to-end test for self-monitoring telemetry.
basti1302
force-pushed
the
self-monitoring
branch
from
September 1, 2024 10:45
03729f0
to
7b0a885
Compare
Quality Gate passedIssues Measures |
basti1302
changed the title
feat: Self-monitoring
feat(self-monitoring): add support for self-monitoring
Sep 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit lays the foundation for self-monitoring:
default endpoint and authorization setting, which will be used for
self-monitoring.
resource, the controller deployment and the collector daemonset are
extended with environment variables like OTEL_EXPORTER_OTLP_ENDPOINT
etc., based on the operator configuration resource export settings.
environment variables are removed from the controller deployment and
collector daemonset.
Go OTel SDK. Other collector containers and the operator controller
process will be extended with the Go OTel SDK in a later iteration.