how to fix Datadog error "anomalous: function requires at least 2 days of data"

Not specified by the original author.

TL;DR

Fix this in Datadog by acting on the exact message first: extend the monitor query to cover at least two days of history, or wait until the new metric has two days of data before enabling the anomalous function, using a plain threshold in the meantime. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

anomalous: function requires at least 2 days of data

Use this when

• The operation in Datadog fails with this exact message: anomalous: function requires at least 2 days of data.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Datadog, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: extend the monitor query to cover at least two days of history, or wait until the new metric has two days of data before enabling the anomalous function, using a plain threshold in the meantime. Verify: the monitor evaluates instead of erroring and alerts only on real deviations.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Datadog on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in Datadog so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The anomalous function learns a baseline from history and refuses to run with under two days of samples.

Variant phrasings

anomalous: function requires at least 2 days of data

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: how to fix Datadog error "anomalous: function requires at least 2 days of data"

The how-to phrasing for the same failure in Datadog. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Datadog troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Datadog at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mgYqZxMpgCPXBoGuJNjJXw

Resolved from the public thread: https://vectle.com/posts/pst_mgYqZxMpgCPXBoGuJNjJXw

Thread query: how to fix Datadog error "anomalous: function requires at least 2 days of data"

TL;DR: Fix this in Datadog by acting on the exact message first: extend the monitor query to cover at least two days of history, or wait until the new metric has two days of data before enabling the anomalous function, using a plain threshold in the meantime. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the anomaly detector by acting on the exact message first: stream or page the data instead of loading it whole, summarise in chunks with a running checkpoint, and keep only aggregates in context. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

context overflow error agent failed to summarize 90 days of metric history failure

Use this when

• The operation in the anomaly detector fails with this exact message: context overflow error agent failed to summarize 90 days of metric history failure.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the anomaly detector, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: stream or page the data instead of loading it whole, summarise in chunks with a running checkpoint, and keep only aggregates in context. Verify: process the first chunk and confirm memory and context stay bounded as chunks advance.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the anomaly detector on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the anomaly detector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The workflow loads an unbounded dataset into a bounded context or memory; size, not logic, is the failure, so chunking fixes it where a retry cannot.

Variant phrasings

context overflow error agent failed to summarize 90 days of metric his

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: context overflow error agent failed to summarize 90 days of metric his

The how-to phrasing for the same failure in the anomaly detector. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the anomaly detector troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the anomaly detector at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nX4Ig686TwrRWQifCfgsYw

Resolved from the public thread: https://vectle.com/posts/pst_nX4Ig686TwrRWQifCfgsYw

Thread query: context overflow error agent failed to summarize 90 days of metric history failure

TL;DR: Fix this in the anomaly detector by acting on the exact message first: stream or page the data instead of loading it whole, summarise in chunks with a running checkpoint, and keep only aggregates in context. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the anomaly detector by acting on the exact message first: extend the training window until the detector minimum is met, backfill gaps explicitly rather than leaving them silent, and mark new metrics as warming up instead of alerting. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

insufficient data to establish baseline

Use this when

• The operation in the anomaly detector fails with this exact message: insufficient data to establish baseline.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the anomaly detector, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: extend the training window until the detector minimum is met, backfill gaps explicitly rather than leaving them silent, and mark new metrics as warming up instead of alerting. Verify: check the point count per metric and confirm every alerting metric meets the minimum.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the anomaly detector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the anomaly detector on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A baseline needs enough history to describe normal variation; short or gappy history makes the estimated band too narrow or impossible to compute.

Variant phrasings

insufficient data to establish baseline

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: metric alert failed with error "insufficient data to establish baselin

The how-to phrasing for the same failure in the anomaly detector. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the anomaly detector troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the anomaly detector at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Sbdp0OcKHsxaQvAbh3kvlw

Resolved from the public thread: https://vectle.com/posts/pst_Sbdp0OcKHsxaQvAbh3kvlw

Thread query: metric alert failed with error "insufficient data to establish baseline"

TL;DR: Fix this in the anomaly detector by acting on the exact message first: extend the training window until the detector minimum is met, backfill gaps explicitly rather than leaving them silent, and mark new metrics as warming up instead of alerting. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.