timescale / timescale/rsigma

Forecast-band anomaly enrichment example (TimesFM)

Open
#331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement
Dominant language
Rust
Stars
142
Forks
16
Avg merge
1h 19m
Merged PRs (30d)
18

Description

Summary

Ship a runnable example where an out-of-band TimesFM producer emits per-rule quantile bands loaded as a dynamic source, and a lookup enricher annotates firings with expected bands.

Motivation

Operators want a glass-box 'is this louder than usual' signal without putting ML in the hot path. Composing shipped enrichment and dynamic sources keeps the daemon a cache lookup.

Proposed approach

  • Python producer with file/prometheus/custom series adapters.
  • Daemon loads bands via dynamic source; enrich_rule_forecast lookup recipe.
  • example under examples/forecast-anomaly/ plus guide docs.

Out of scope

  • Core-engine ML models.
  • Synthesizing alerts with no rule firing.

Tasks

  • Example producer + golden band table
  • sources/enrichers recipes
  • Guide page and enricher catalogue entry

References

  • Post-evaluation enrichment
  • Detached dynamic sources
  • Per-rule match metrics

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the existing examples and recipes for post-evaluation enrichment and detached dynamic sources, then create the proposed example under examples/forecast-anomaly/. The work is complete when the producer and golden band table, source and enricher recipes, guide page, and enricher catalogue entry are all runnable and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
prometheus, python
Domain
backend, data, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.