PostHog / PostHog/posthog

Workflows metrics series chart improvements

Open
#44,578 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature/messaging feature/workflows
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Bug Description

There are a few improvements worth making to the metrics series chart for workflows.

  1. Explain what each series is
  2. Make each series human readable (billable_invocation is readable but we can present it nicely)
  3. Option to disable specific series in the chart. In some instances it is possible that one series could be much greater than others, making it difficult to read the chart for the other metrics. Being able to disable certain series metrics could alleviate that issue when a user encounters it.

Additional context

Debug info
- [x] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

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 locating the workflows metrics series chart in the frontend and reviewing how its current series labels and rendering are assembled. Done means each series is explained and human-readable, and users can disable individual series so larger values do not obscure the others.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
data, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.