Skip to content
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
merged 1 commit into from
Sep 1, 2024

Conversation

basti1302
Copy link
Member

@basti1302 basti1302 commented Aug 22, 2024

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.

api/dash0monitoring/v1alpha1/dash0monitoring_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/dash0monitoring_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/dash0monitoring_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/dash0monitoring_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/dash0monitoring_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/operator_types.go Outdated Show resolved Hide resolved
api/dash0monitoring/v1alpha1/operator_types.go Outdated Show resolved Hide resolved
config/crd/bases/operator.dash0.com_dash0monitorings.yaml Outdated Show resolved Hide resolved
config/rbac/role.yaml Show resolved Hide resolved
@basti1302 basti1302 marked this pull request as ready for review August 22, 2024 14:47
PROJECT Outdated Show resolved Hide resolved
internal/dash0/controller/self_monitoring_util.go Outdated Show resolved Hide resolved
@basti1302
Copy link
Member Author

Please also take a look at the Sonar issues.

image

@basti1302 basti1302 force-pushed the self-monitoring branch 9 times, most recently from c008a0d to 03729f0 Compare September 1, 2024 10:32
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.
Copy link

sonarcloud bot commented Sep 1, 2024

@basti1302 basti1302 enabled auto-merge (rebase) September 1, 2024 10:46
@basti1302 basti1302 changed the title feat: Self-monitoring feat(self-monitoring): add support for self-monitoring Sep 1, 2024
@basti1302 basti1302 merged commit 0a3e04e into main Sep 1, 2024
6 checks passed
@basti1302 basti1302 deleted the self-monitoring branch September 1, 2024 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants