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

Add missing processors to metrics pipeline #399

Merged
merged 4 commits into from
Mar 9, 2022

Conversation

tongpu
Copy link
Contributor

@tongpu tongpu commented Mar 7, 2022

We've seen that some labels that are present on logs are not present on metrics, add the k8sattributes and resource/add_environment processors to the metrics pipeline fixes this issue.

@tongpu tongpu requested review from a team as code owners March 7, 2022 08:45
@dmitryax
Copy link
Contributor

dmitryax commented Mar 7, 2022

@tongpu which backend do send the metrics to?

The processors are omitted in the metrics pipeline on purpose.

  • All the k8s related metrics coming kubeletstats, k8scluster and receiver_creator (with k8s observer) receivers already have the k8s attributes, so there is no need in additional processor. Metrics coming from hostmetrics receiver cannot be enriched with k8s attributes because they are out of k8s context.

  • deployment.environment attribute as a concept in Observability Cloud is only applicable to traces and logs. Correlation with metrics is happening in signalfx exporter which is looking at traces coming through it. If you want this attribute on metrics in Splunk Platform backend, please add the condition so it's added only if splunk-otel-collector.platformMetricsEnabled.

@tongpu
Copy link
Contributor Author

tongpu commented Mar 8, 2022

which backend do send the metrics to?

We're sending everything to Splunk.

The processors are omitted in the metrics pipeline on purpose.

I already thought so, mostly opened the PR to get your feedback on this.

  • All the k8s related metrics coming kubeletstats, k8scluster and receiver_creator (with k8s observer) receivers already have the k8s attributes, so there is no need in additional processor. Metrics coming from hostmetrics receiver cannot be enriched with k8s attributes because they are out of k8s context.

I'm going to look further into that with our Splunk team.

  • deployment.environment attribute as a concept in Observability Cloud is only applicable to traces and logs. Correlation with metrics is happening in signalfx exporter which is looking at traces coming through it. If you want this attribute on metrics in Splunk Platform backend, please add the condition so it's added only if splunk-otel-collector.platformMetricsEnabled.

So it would be okay if I limit this PR to add the environment processor when splunkPlatform.metricsEnabled is true?

@tongpu tongpu force-pushed the bug/metrics_processors branch from 4bf71a0 to 1809628 Compare March 8, 2022 15:29
CHANGELOG.md Outdated Show resolved Hide resolved
@dmitryax
Copy link
Contributor

dmitryax commented Mar 8, 2022

We're sending everything to Splunk.

I was asking which Splunk destination, Splunk Observability or Splunk Platform? :)

So it would be okay if I limit this PR to add the environment processor when splunkPlatform.metricsEnabled is true?

Yes, it should be ok

@tongpu
Copy link
Contributor Author

tongpu commented Mar 8, 2022

We're sending everything to Splunk.

I was asking which Splunk destination, Splunk Observability or Splunk Platform? :)

Currently Splunk Platform, but we're going to set up a PoC with Splunk Observability in the future.

Co-authored-by: Dmitrii Anoshin <[email protected]>
@tongpu tongpu requested a review from dmitryax March 8, 2022 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants