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

FEATURE: New reporter for OpenTelemetry #188

Open
secustor opened this issue Oct 13, 2023 · 3 comments
Open

FEATURE: New reporter for OpenTelemetry #188

secustor opened this issue Oct 13, 2023 · 3 comments

Comments

@secustor
Copy link

Looking at the definition of BuildStep it looks like there is everything to create traces in the OTEL format.

This would allow to send build profiling data to nearly any Observability tooling.

Based on the short peak into the code base this should need only a new reporter.

TBD:

  • should only an export to a file be supported or direct push to a compatible endpoint too?
@secustor secustor changed the title FEATURE: New reporter for OpenTelemetry json files FEATURE: New reporter for OpenTelemetry Oct 13, 2023
@BalestraPatrick
Copy link
Collaborator

That's an interesting idea. I never personally used OpenTelemetry before, but it sounds like this should be a nice feature to introduce. Would you send to OpenTelemetry the parsed file from the machine after parsing it with XCLogParser?

@secustor
Copy link
Author

The simplest implementation would to start with integrating https://github.com/open-telemetry/opentelemetry-swift
which would push the traces to a compatible backend directly.
That could be OSS tools like Jaeger or Grafana Tempo on the one side or SaaS sytems like Datadog

@bok-
Copy link

bok- commented Oct 26, 2023

I'd recommend https://github.com/apple/swift-distributed-tracing over the opentelemetry-swift port as that's where the Swift on Server ecosystem is moving.

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

No branches or pull requests

3 participants