Using Dynatrace to Detect Problems in Logs#
Support Policy
This is a demo project created by the Developer Relations team at Dynatrace, showcasing integrations with open source technologies.
Support is provided via GitHub issues only. The materials provided in this repository are offered "as-is" without any warranties, express or implied. Use them at your own risk.
View the Code
The code for this repository is hosted on GitHub. Click the "View Code on GitHub" link above.
In this hands-on demo, you will send logs from the OpenTelemetry demo application to Dynatrace.
You will artificially create a problem in the application which Dynatrace DAVIS will detect and thus raise a problem report based on the Observability data.
The logs include span and trace IDs meaning you will be easily able to drill between signal types to see logs in the context of the distributed trace and vice versa.
Tip
Right click and "open image in new tab" to see large image
How is the problem created?#
You will release a new feature into production. For demo purposes, this new feature intentionally introduces failure into the system.
First you will inform Dynatrace that a change is incoming. This will be done by sending a CUSTOM_CONFIGURATION event to Dynatrace.
Then the feature will be enabled by toggling a feature flag.
After a few moments, the error will occur. The ERROR logs flowing into Dynatrace will trigger the problem.
This demo uses the OpenTelemetry demo application and the Dynatrace OpenTelemetry collector distribution (why might I want to use the Dynatrace OTEL Collector?).
Logical Flow#
Compatibility#
| Deployment | Tutorial Compatible |
|---|---|
| Dynatrace Managed | ❌ |
| Dynatrace SaaS | ✔️ |