question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Source information is not available in signalfx

See original GitHub issue

Current reporter for SignalFx does not send information about “source”, that is by default equal to hostname.

SFX team’s dropwizard reporter sends this information as dedicated dimension, appended to every data point: https://github.com/signalfx/signalfx-java/blob/master/signalfx-codahale/src/main/java/com/signalfx/codahale/reporter/AggregateMetricSenderSessionWrapper.java#L195

Micrometer implementation sets source field in dataPoint, but looks like it does not work as expected, because there is no dimension with a value having this info.

Expected result:

  1. It is possible to enable behavior that all reported data point has additional dimension with value equal to source() property.
  2. It is also should be allowed to define tag name with sf_ prefix so that reported data can keep compatibility with already existing data (some legacy examples for signal fx used sf_source for this info)

I’m fine if this behavior would be optional and enabled by special config parameter, e.g. management.metrics.export.signalfx.reportSource

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:1
  • Comments:11 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
zeldigascommented, Oct 21, 2019

Yes, I’ll send PR this week

0reactions
rajanigkcommented, Aug 1, 2022

we used the splunk-otel-javaagent and are able to push metrics and filter it based on sf_service. When we push metrics using spring-boot and the micrometer-signalfx-registry library as per the springboot documentation at https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#actuator.metrics.export.signalfx, not able to filter the metrics based on the application. So thought the source dimension is for that filtering. I tried with spring-boot 2.7.2 which pulls the 1.9.2 version of micrometer-registry-signalfx the source is not coming to metric so that i could filter the metric based on it. If there is any other way to filter the metric to differentiate between different applications, please do let me know.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Service, host_name, process_id, runtime information is not ...
Service, host_name, process_id, runtime information is not available in signalfx when using micrometer for pushing custom metrics.
Read more >
Troubleshoot detectors in Splunk Observability Cloud
To access a detector, navigate to Alerts then Detectors from the Alerts menu, or by selecting Open Detector from an alert pop-out window....
Read more >
Splunk Infrastructure Monitoring (Formerly SignalFX)
If you don't see the Data Sources link in your side menu, it means that your current user does not have the Admin...
Read more >
claranet/detectors/signalfx | smart-agent_docker Submodule
module "signalfx-detectors-smart-agent-docker" { source ... receiver not based on an existing Smart Agent monitor is not available from old agent so related ...
Read more >
The new Splunk Infrastructure Monitoring plugin ... - Grafana
In order to configure your data source, you need your realm name and your SignalFx access token. Your realm can be found as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found