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

Provide fine grained mechanism for instrumenting a subset of workloads #2057

Open
ddelnano opened this issue Dec 9, 2024 · 0 comments
Open
Labels
area/datacollector Issues related to Stirling (datacollector) kind/feature New feature or request

Comments

@ddelnano
Copy link
Member

ddelnano commented Dec 9, 2024

Pixie's instrumentation works at the kernel level since it uses eBPF. This means that all workloads on the machine are instrumented and is generally seen as beneficial since it reduces blind spots. However, there are times where it could be beneficial to scope instrumentation more tightly and to specific workloads. The end user that requested this is interested in lowering the PEM's overhead. In these cases, they want to trace workloads by selecting specific containers, pods or pods in certain namespaces.

Describe the solution you'd like
This end user would like to have runtime toggles that can do the following:

  • Specify which containers, pods or pods from specific namespaces should be traced
  • Change which protocols are traced
    • Pixie currently allows enabling/disabling protocols via deploy time configuration, but it's not possible to change this at runtime
@ddelnano ddelnano added kind/feature New feature or request area/datacollector Issues related to Stirling (datacollector) labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/datacollector Issues related to Stirling (datacollector) kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant