-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Switch SAPM receiver to internal data model #186
Switch SAPM receiver to internal data model #186
Conversation
@tigrannajaryan please take a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please post before/after perf test results once we have both receiver and exporter merged.
Performance degraded because we introduced OTLP translation additionally to OC. Once exporter is migrated it should be improved. Test results: Before:
After:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@dmitryax makes sense. Let's see where we land after migrating the exporter. It will be useful to compare "before" results from this PR to "after" results when exporter is also migrated. |
* Implement factory and config for sampling processor (head-based) * Change Config name
* Fix defaultoutput * Implement PR feedback
…ightreceiver. (open-telemetry#186) * Add Elastic Fabric Adapter (EFA) metric collection to awscontainerinsightreceiver. The new component scrapes hardware counters from /sys/class/infiniband on disk. The layout of that directory is: /sys/class/infiniband/<device name> └── ports └── 1 └── hw_counters ├── rdma_read_bytes ├── rdma_write_bytes ├── rdma_write_recv_bytes ├── rx_bytes ├── rx_drops └── tx_bytes These are cumulative counters and so they are converted to deltas before sending down the pipeline. We sum up data from all ports. The device data is joined with data from the kubelet podresources API which tells us which container a given device is assigned to. The metrics are reported at container, pod, and node levels. This commit also refactors some metric decoration code from cadvisor to a common localnode decorator, intended to be used by any awscontainerinsightreceiver component that gathers metrics from the local node (as oppoosed to e.g. the k8s control plane scraper). This is because we want to share the logic of populating PodName, Kubernetes labels, etc. I also renamed RawContainerInsightsMetric to CIMetricImpl for brevity.
No description provided.