iovisor / iovisor/kubectl-trace

Ability to obtain flame graphs

Open
#73 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.2k
Forks
176
PR merge metrics
No merged PRs in 30d

Description

Since [flame graph](https://github.com/brendangregg/flamegraph) supports [bpftrace](https://github.com/iovisor/bpftrace) I propose to create a new feature making users of kubectl-trace able to obtain flame graphs.

Not sure yet whether such feature should be implemented from a flag or from a new command.

We'll investigate further cc @fntlnz.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file, test, or entry point is named. Start by reviewing how kubectl-trace currently exposes commands and flags, then examine the linked bpftrace and flame graph projects. Done means users can obtain flame graphs through a defined kubectl-trace interface.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.