Skip to content

Identify auto-collected metrics (no tracing overlap) #1462

@dingsdax

Description

@dingsdax

We want to define a set of lightweight metrics that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that do NOT overlap with Tracing. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples:

  • Node.js runtime metrics (e.g., event loop delay, heap usage)
  • Prisma-related metrics in Next.js
  • Mobile CPU / memory usage to help surface potential ANRs or app hangs

Candidate Metrics (add more below)

❓ in Native it is a bit harder to just 'hook into' metrics, so these might require active polling (which is maybe not what we want). Still, we could conceivably collect these values periodically (and the Gaming-specific ones might be hook-able).

  • Thread/Concurrency Metrics
  • Memory Metrics
  • Gaming-Specific Metrics (TODO move into new issues in sentry-unreal/sentry-unity/sentry-godot
  • Console-Specific Metrics (TODO move into new issues in console repos)

(please also add ideas, questions or examples in comments)

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions