ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Guide to selecting the right Dynatrace OneAgent mode on Kubernetes: full‑stack DaemonSet, application‑only injection, or infrastructure‑only, with a comparison table, trade‑offs, and a step‑by‑step full‑stack deployment example.
Learn how to tag your Dynatrace hosts with key/value pairs at agent startup, verify them in the UI and API, and avoid common pitfalls like reserved names and length limits.
Learn how to deploy Dynatrace OneAgent on Linux for automated full-stack monitoring, from host metrics to automatic runtime instrumentation without code changes.
Learn how to architect Dynatrace OneAgent and ActiveGate deployments to achieve full-stack observability while maintaining security boundaries and resource stability.
Deploy the Dynatrace OneAgent as a DaemonSet so every node runs the agent, enabling automatic instrumentation of Java processes without code changes. One DaemonSet, a secret for the API token, and DT_TENANT is the minimal design.
Automate full-stack OneAgent injection on Kubernetes using the Dynatrace Operator: create the secret, install via Helm, define a DynaKube CR, annotate namespaces, and verify metrics, traces, and logs flow to your tenant.
Learn how Dynatrace OneAgent automatically discovers services and builds real‑time dependency maps, with a concrete Java Spring Boot + PostgreSQL example and practical limits to consider.
Error context The OneAgent health log emits the warning "Timezone conversion failed, falling back to UTC" when the host’s IANA time‑zone database is missing or outdated. This causes the agent to treat all host timestamps as UTC, shifting metric timestamps relative to local time. Goal: Ensure that metric timestamps remain accurate despite a missing or outdate
dynatrace
kubernetes
linux