elastic / elastic/observability-migration-platform
[Datadog] "Sparse Data" Fill Logic
Open
asset:alerts
capabilities
phase:6
source:datadog
workstream:asset-coverage
- Dominant language
- Python
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 23
Description
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.
```json
{
"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 }
}
}
```
Contributor guide
Assessment
This issue has not been assessed yet.