GreptimeTeam/greptimedb

Supports profile signal for OLTP

Open

#6,760 opened on Aug 18, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (495 forks)github user discovery
C-featurehelp wanted

Repository metrics

Stars
 (6,332 stars)
PR merge metrics
 (PR metrics pending)

Description

What problem does the new feature solve?

GreptimeDB already supports OLTP metrics, logs, and traces.

Profiles were introduced as an experimental signal type in OTLP v1.3.0.

https://opentelemetry.io/blog/2024/state-profiling/

We should add support for profiles to make GreptimeDB fully support OLTP.

What does the feature do?

Supports profile signal for OLTP

Implementation challenges

  • Investigate the OLTP profiling signal and finalize a plan for converting it into GreptimeDB table schemas.
  • Explore visualization solutions.

No response

Contributor guide

Research direction
Investigate the OpenTelemetry profiling signal specification and design a mapping to GreptimeDB table schemas. Start by reading the OTLP profile signal documentation and reviewing existing implementations.
Tech stack
rust
Domain
backendobservabilitydatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustgRPCProtobuf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40