Find the function that's burning your CPU
A flame graph answers what logs and traces can't: which function is actually on the CPU, or holding memory, right now. KloudMate samples your services continuously and turns those samples into a flame graph down to the line.
Traces tell you which service is slow, not why.
A trace stops at the service boundary. Profiling goes inside it and samples the running code, so instead of guessing which function is expensive you see it, ranked by how much CPU or memory it actually used.
What teams can do with Profiling
Sample running services continuously, find the hotspot down to the line, and prove whether a deploy made things better or worse.
Continuous, always-on profiles
Services are sampled continuously at low overhead, so the flame graph for any moment is already there when you need it, no debugger to attach and no build to ship.
Profile CPU, memory, and goroutines
Not just CPU. Profile allocated and in-use memory, object counts, and goroutines too, each as its own flame graph, whatever your SDK collects.
Compare before and after a deploy
The difference view sets two time windows side by side and colors what grew and what shrank, so you can answer "did that change make it worse?" in seconds.
Slice by service and label
Break a service's profiles down by the attributes your SDK attaches, region, pod, or version, to isolate the one instance that's hot.
From a slow service to the line to fix
Start wide across every service, narrow to the one that's hot, then open its flame graph and read the hotspot straight off the widest frame.
Send profiles
Add a Pyroscope-compatible SDK, or send through the KloudMate Agent so it attaches the labels that help with root cause.
Scan every service
See every reporting service and its peak at a glance, so you start with the outlier instead of profiling all of them.
Open the flame graph
The widest frame is the biggest consumer. Zoom into it to reach the specific function and line responsible.
Confirm the fix
After you ship, use the difference view to check the hotspot shrank instead of moving somewhere else.
Find the hot service at a glance
Don't guess which service to profile. Every service sending profiles shows its peak and a trend on one screen, so the outlier jumps out before you open a flame graph.
- Switch profile type, CPU, memory, objects, or goroutines, and see who's hottest
- Peak and a live trend on every card, so a spike stands out immediately
- Click straight through to that service's flame graph, already filtered to the type
Spot a regression right after a deploy
Set a before window and an after window, and KloudMate colors what changed: red where a frame grew, green where it shrank. A new hotspot is impossible to miss.
- Read a regression straight off the graph, no diffing stack traces by hand
- Grown frames turn red, shrunk frames green, so the change jumps out
- Catch a fix that just moved the cost somewhere else instead of removing it
Send profiles from any language you run
KloudMate speaks the Pyroscope ingest protocol and the OpenTelemetry Profiles signal, so any Pyroscope-compatible SDK works. Send through the KloudMate Agent and it attaches the resource labels that make root cause faster.
- Go, Java, Python, Node.js, Ruby, .NET, and Rust, each with a dedicated setup guide
- Ingest over the Pyroscope protocol or OpenTelemetry Profiles, via the agent or straight to the endpoint
- Correlate a hotspot here with the trace that triggered it, and let Assistant investigate the top functions
Ask KloudMate Assistant to read the flame graph for you
Assistant investigates a flame graph's top functions, so you get the hotspot and a direction to fix it without reading every frame yourself.
- Summarize Name the function taking the most CPU or memory
- Compare Say what a deploy changed between two windows
- Guide Point to the trace or line behind the hotspot
Related Features
Keep the rest of the workflow close by so teams can move between detection, investigation, and response without losing context.
APM & Distributed Tracing
Trace requests across services, inspect dependencies, and move from latency symptoms to request-level evidence.
Learn moreKloudMate Assistant
Use natural language to correlate telemetry, summarize incidents, and guide the next investigation step.
Learn moreDatabase Monitoring
Track query latency, workload shape, and downstream impact alongside traces and service health.
Learn moreInfrastructure Monitoring
Monitor hosts, Kubernetes, Prometheus, and cloud resources with linked application context.
Learn moreGet started
From telemetry to root cause,
in one platform.
Connect your OpenTelemetry pipeline, AWS integrations, or eBPF agent. Distributed tracing, log management, alerting, and AI-assisted investigation: unified, with predictable pricing.