Metrics Anomaly Detector

[rexagod]

Enhancement Description

• One-line enhancement description (can be used as a release note): The Metrics Anomaly Detector enables detecting anomalies in time series data.
• Kubernetes Enhancement Proposal: KEP-4231: Metrics Anomaly Detector #4232
• Primary contact (assignee): @logicalhan, @rexagod
• Responsible SIGs: SIG Instrumentation
• Enhancement target (which target equals to which milestone):
  • Alpha release target: TBD.

• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4231: Metrics Anomaly Detector #4232
  • Code (k/k) update PR(s): N/A yet (requires a sub-repo)
  • Docs (k/website) update PR(s): WIP

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[rexagod]

/sig instrumentation

[dashpole]

@rexagod Is this planned for 1.30?

If it is, we need to add the 1.30 milestone, and the lead-opted-in label

[rexagod]

I believe we'll sit this one out, at least for v1.30, since this needs a bit more polishing.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[logicalhan]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mengjiao-liu]

/remove-lifecycle stale