fix(docs): DataSink CR example
#58
Merged
Conversation
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
Co-authored-by: Jordan Raychev <[email protected]>
|
@mirzakopic You can approve this one so we can merge it. |
maximiliantech
changed the title
DataSink CR example
maximiliantech
approved these changes
Jun 27, 2025
There was a problem hiding this comment.
Thanks @jpraychev for your contribution! 🤝 Much appreciated 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it:
This pull request updates the
README.mdfile to reflect changes in the configuration for connecting to the Dynatrace metrics API. The most notable changes include the removal of certain fields related to the connection protocol and security settings, as well as updating the endpoint URL.Updates to Dynatrace connection configuration:
README.md: Changed the endpoint URL fromhttps://your-tenant.live.dynatrace.com/api/v2/metrics/ingesttohttps://your-tenant.live.dynatrace.com/api/v2/otlp/v1/metrics. This reflects a shift to the OpenTelemetry Protocol (OTLP) for metrics ingestion.README.md: Removed theprotocolfield and theinsecureSkipVerifyfield. These fields are no longer relevant with the updated endpoint configuration.Which issue(s) this PR fixes:
Fixes #32
Special notes for your reviewer:
Release note: