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

[receiver/splunkhec] support trace signal #35953

Closed
antonjim-te opened this issue Oct 23, 2024 · 8 comments
Closed

[receiver/splunkhec] support trace signal #35953

antonjim-te opened this issue Oct 23, 2024 · 8 comments

Comments

@antonjim-te
Copy link

Component(s)

receiver/splunkhec

Is your feature request related to a problem? Please describe.

The https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/splunkhecexporter supports traces but not the receiver. And it is a requirement for us.

Describe the solution you'd like

[receiver/splunkhec] support trace signal

Describe alternatives you've considered

No response

Additional context

No response

@antonjim-te antonjim-te added enhancement New feature or request needs triage New item requiring triage labels Oct 23, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme
Copy link
Contributor

atoulme commented Oct 23, 2024

How would that look like? Please show an example of trace as a HEC event.

@pellared
Copy link
Member

And it is a requirement for us.

Why do you actually need it? Why cannot you simply send traces using OTLP or any other protocol?

@atoulme atoulme added waiting for author and removed needs triage New item requiring triage labels Oct 25, 2024
@vutnguye-te
Copy link

And it is a requirement for us.

Why do you actually need it? Why cannot you simply send traces using OTLP or any other protocol?

@pellared Our otel-collector pipeline supports exporting traces to SplunkHec. For our integration test, we plan to use a SplunkHec trace receiver to verify that data is being exported accurately.

@atoulme
Copy link
Contributor

atoulme commented Nov 2, 2024

I see, you want to validate trace exports via a splunkhecreceiver. We support traces in the splunkhecexporter by marshaling them to JSON and making the event field of the HEC event. You want to read that event field and unmarshal the trace from it, correct?

@vutnguye-te
Copy link

Yes, we need to validate trace exports via a splunkhecreceiver. I am not sure how json marshalling can help us. Can you please elaborate a bit more? Thanks.

Copy link
Contributor

github-actions bot commented Jan 6, 2025

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 6, 2025
Copy link
Contributor

github-actions bot commented Mar 7, 2025

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants