PostHog / PostHog/posthog

Feature request: Profiling backend server application (tracing, spans, flame graphs)

Open
#37,477 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Is your feature request related to a problem?

I would like to profile the performance of my nodejs backend application. For this I need to be able to trace when functions have been called and when they returned.

Describe the solution you'd like

Maybe by adding explicit posthog.captureSpanStart and posthog.captureSpanEnd calls to my code, that can be used to generate flame graphs from. But something more automagical that can be enabled once for my whole code base would be even better.

Describe alternatives you've considered

Sentry: https://docs.sentry.io/product/explore/profiling/flame-charts-graphs/

Additional context

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.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

The issue names no repository files, tests, or entry points. Start by scoping how PostHog's Node.js backend application support could expose function tracing, spans, and flame graphs, using the linked Sentry profiling page as the stated comparison. Done should be a decided implementation scope rather than the current open-ended request.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
backend, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.