-
Notifications
You must be signed in to change notification settings - Fork 140
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Groundwork for OTel instrumentation in operator (#2272)
* Basic OTel infrastructure for metrics and traces to ingest directly into DT cluster, sample metric and spans. * Move OTel basic setup stuff to utils. Add simple auto instrumentation. * Use Noop implementation of OTel if no OTel config secret is provided. * Start OTel collection with auto-instrumentation also in operator and CSI driver. * Introduce a few OTel helpers that make calls resilient when OTel can't be properly started. * fixup! Basic OTel infrastructure for metrics and traces to ingest directly into DT cluster, sample metric and spans. * Fix typo Co-authored-by: Albian Krasniqi <[email protected]> * Add noop tracer installment log. Co-authored-by: Albian Krasniqi <[email protected]> * fixup! Basic OTel infrastructure for metrics and traces to ingest directly into DT cluster, sample metric and spans. --------- Co-authored-by: Albian Krasniqi <[email protected]>
- Loading branch information
1 parent
a23c825
commit 42326a1
Showing
30 changed files
with
711 additions
and
28 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# How to setup OpenTelementry | ||
|
||
Dynatrace operator, CSI driver and webhook are instrumented using OpenTelemetry. To enable this instrumentation and ingest collected | ||
metrics and traces into your tenant follow this guide. | ||
|
||
## Create an access token with the following scopes | ||
|
||
- openTelemetryTrace.ingest | ||
- metrics.ingest | ||
- logs.ingest | ||
|
||
## Create OpenTelementry configuration secret | ||
|
||
```yaml | ||
apiVersion: v1 | ||
kind: Secret | ||
type: Opaque | ||
metadata: | ||
name: dynatrace-operator-otel-config | ||
namespace: dynatrace | ||
data: | ||
endpoint: base64(<uuid>.dev.dyntracelabs.com) | ||
apiToken: base64(<apiToken>) | ||
``` | ||
*Note:* | ||
- as indicated the values have to be base64 encoded (as usually with K8S) | ||
- obey to the name | ||
- make sure it is created in the same namespace as the webhook |
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
Oops, something went wrong.