newrelic / newrelic/newrelic-pixie-integration
Provide the ability to include/exclude pods and services by annotation, label, or namespace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Customers may only want to send data for specific pods or namespaces in a K8s cluster. Currently, there is not a way to filter exclude certain data from being sent to NR. There will be scenarios where customers do not want to send data from both New Relic APM agents already running in the cluster and Pixie.
Desired Behavior
Provide a filtering option within the integration config.
Possible Solution
Annotation or label-based exclusion.
Additional context
When running New Relic agents and Pixie in the same cluster, certain metrics will be collected twice for the same services causing increased ingest and potential confusion in the UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the integration configuration and Kubernetes collection path, then determine how annotations, labels, and namespaces can be represented as filters. Done means customers can include or exclude the specified Kubernetes data and avoid duplicate metrics from Pixie and New Relic agents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100