PostHog / PostHog/posthog

No data status for alerts

Open
#26,902 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/alerts team/product-analytics team/query-performance
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Describe the solution you'd like

It'd be nice to have a "no data" status instead of "errored" - if I have an alert based on a sparse metric. In posthog right now, 0 data metrics appears to be "errored" and I have no control over what happens in the scenario (whether or not there's an email to anyone, etc)

Describe alternatives you've considered

Additional context

Debug info

No response

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

The issue names no files, tests, or entry points. Start by reviewing how sparse metrics are currently classified as errored and how alert notifications are controlled. Done means supporting a distinct no-data status and defining whether notifications occur in that scenario.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.