Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow users to select which process to enable trace-profiling #458

Open
dxsup opened this issue Feb 23, 2023 · 0 comments
Open

Allow users to select which process to enable trace-profiling #458

dxsup opened this issue Feb 23, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@dxsup
Copy link
Member

dxsup commented Feb 23, 2023

Is your feature request related to a problem? Please describe.

Now when users enable trace-profiling, all the processes on the host are profiled. The motivation to allow users to select which process to enable trace-profiling is:

  • Users only care about part of the processes and don't want to affect others.
  • More processes, more events, and more resources are consumed.

Describe the solution you'd like

To implement the feature, the following modifications should be made:

  • Users can see the processes on the host when enabling trace-profiling from the front end and can select some of them.
  • Collector provides an API that accepts PID or container ID or other identification to enable trace-profiling.
  • The drivers can classify which processes are profiled.
@dxsup dxsup added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant