Skip to content

Conversation

@robsunday
Copy link
Contributor

@robsunday robsunday commented Jan 20, 2026

Common Splunk profiling declarative config contains setting for snapshot selection_probability that is needed by SnapshotVolumePropagator.
This is current format introduced with this PR:

# Required for callgraphs
propagator:
  composite:
    - tracecontext:
    - baggage:
    - splunk_snapshot_volume:
distribution:
  splunk:
    profiling:
      callgraphs:
        selection_probability: 0.123
        sampling_interval: 5

Unfortunately, there is one issue with this solution.
Convention established by declarative config recommends putting the component's config under the component's node in YAML. With this convention it should look like as follows:

# Required for callgraphs
propagator:
  composite:
    - tracecontext:
    - baggage:
    - splunk_snapshot_volume:
       selection_probability: 0.123
distribution:
  splunk:
    profiling:
      callgraphs:
        sampling_interval: 5

It is incompatible with common Splunk distribution config idea, but I think that common config has a great value for the users.

@robsunday robsunday requested review from a team as code owners January 20, 2026 11:52
@robsunday
Copy link
Contributor Author

I'd really suggest rethinking if automatic adding splunk_snapshot_volume propagator in model customizer wouldn't make sense. Without this propagator the call graphs will not work anyway. So why force user to add one more line in YAML? This would also somehow hide this inconsistency, I mentioned in the description.

@laurit
Copy link
Collaborator

laurit commented Jan 21, 2026

I'd really suggest rethinking if automatic adding splunk_snapshot_volume propagator in model customizer wouldn't make sense. Without this propagator the call graphs will not work anyway. So why force user to add one more line in YAML? This would also somehow hide this inconsistency, I mentioned in the description.

I totally agree with this, users should not need to manually configure splunk_snapshot_volume propagator. Requiring it is just going to create confusion and extra support requests because it is easy to miss.

@robsunday robsunday merged commit 3b047b2 into signalfx:main Jan 21, 2026
28 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jan 21, 2026
@robsunday robsunday deleted the fbc-snapshot-volume-propagator-config branch January 21, 2026 17:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants