Add integration for tailsamplingprocessor

[gregkalapos]

Adding a content pack to visualize metrics from the tailbasedprocessor OTel Collector component.

Metrics are based on the upstream docs here.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Screenshots

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[gregkalapos]

I'd like some input on this: Problem is that this dataset is present as soon as internal telemetry in an OTel collector config is turned on, but there is no guarantee that the tailsamplingprocessor is present.

This means, with this potentially we'd install this integration even if the data we visualize here is not present.

Options I see:

• either proceed as is (and then potentially the integration is installed even if there is no data to visualize)
• we try to find something that identifies data from tailsamping processor (so far, I don't see anything obvious)
• drop this part and there is no auto discovery (this'd be sad :( )

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b0979d5

History

• 💔 Build #41319 failed ade5b75
• 💔 Build #41316 failed 27c6b53

cc @gregkalapos

[gregkalapos]

Closing this over #18527