{
  "id": 20317426,
  "title": "Crossplane Dynatrace: observability as code driven from Kubernetes",
  "url": "https://urgent.news/2026/11/16/crossplane-dynatrace-observability-as-code-driven-from-kubernetes",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T19:30:13.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/spanobserver/crossplane-dynatrace-observability-as-code-driven-from-kubernetes-15bb"
  },
  "original_language": "en",
  "account": "The Crossplane Dynattrace platform enables observability configurations to be defined as Kubernetes objects, similar to other configurations, using a controller that maintains them in line. This article explores the question of when Dynatrace should be controlled within the Kubernetes cluster. The solution addresses the problem of keeping configurations consistent, rather than creating them. Kubernetes operators enable this by continuously comparing actual and desired states and remedying any discrepancies. By describing observability configurations as Kubernetes objects, teams can integrate alerting profiles and dashboards into their existing GitOps processes, allowing for code reviews and version control. Crossplane achieves this by generating Kubernetes objects from Terraform schemas using the Upjet framework, which produces CRDs, controllers, and example manifests. The Dynatrace provider relies on the dynatrace-oss/dynatrace Terraform provider, with authentication provided through an API token with specific scopes. The process involves setting up the Terraform provider, generating CRDs, applying them, and creating a secret with the API credentials. The controller can then synchronize objects, such as dashboards, ensuring they are always up-to-date. By using Crossplane Dynatrace, teams can maintain consistent observability configurations without manual intervention, improving operational efficiency and reducing the risk of drift.",
  "summary": "Your platform team already runs clusters through Kubernetes manifests, yet Dynatrace alerting profiles and dashboards still get edited by hand in the UI. Configuration drifts and nobody can say who changed what. Crossplane Dynatrace answers one operational decision: describe observability configuration like any other Kubernetes object, and let a controller keep it in line. This article does not…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}