Skip to content

[Datadog] "Sparse Data" Fill Logic #3

Description

@a03nikki

In Datadog, .fill(zero) or .fill(last) is handled at the query level. Elastic's bucket_script or gap_policy behaves differently. If you are comparing two sparse metrics using division, the logic often breaks during migration.

{
  "name": "Error Rate with Sparse Data Handling",
  "type": "query alert",
  "query": "avg(last_5m):default_zero(sum:api.errors{*} / sum:api.requests{*}) > 0.05",
  "message": "High error rate detected. Note: default_zero used to prevent null-pointer logic. {{value}}",
  "options": {
    "thresholds": { "critical": 0.05 }
  }
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    asset:alertsAlert, monitor, and rule migration assetscapabilitiesNew translator capability — new panel type, query construct, or Kibana featurephase:6Phase 6 - Full-stack assetssource:datadogDatadog source migrationworkstream:asset-coverageNon-dashboard assets and broader migration coverage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions