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: support OpenTelemetry Protocol (OTLP) #312

Closed
connec opened this issue Feb 24, 2023 · 8 comments · Fixed by #657
Closed

feature: support OpenTelemetry Protocol (OTLP) #312

connec opened this issue Feb 24, 2023 · 8 comments · Fixed by #657
Assignees
Labels
enhancement New feature or request

Comments

@connec
Copy link

connec commented Feb 24, 2023

I'm very interested in using parseable as it looks like a great answer to bloated/closed logging services, but I'm also keen to adopt OTLP for my projects in the hope that they could then be integrated seamlessly into different environments with different logging services (including, tragically, bloated/closed ones).

Is support for the OpenTelemetry Protocol (OTLP, specification) on the roadmap at all? Would there be appetite to discuss it/merge a PR introducing it?

@nitisht
Copy link
Member

nitisht commented Feb 25, 2023

hi @connec thank you for the issue. We’re interested in OTEL support. I am curious what would it entail from Parseable server perspective, AFAICS a client can send OTLP logs and we can ingest that (since Parseable is schema free).

Happy to discuss here or on our Slack.

@nitisht nitisht added the question Further information is requested label Feb 25, 2023
@connec
Copy link
Author

connec commented Feb 25, 2023

You may well be right that JSON over HTTP is already supported! I'm a bit of a neophyte in this area, but it looks like JSON over HTTP is still "experimental" in the OTLP spec, and that grpc/protobuf over HTTP are the stable options, so I assumed a dedicated endpoint would be needed.

I'd understand if you'd rather keep the interface to JSON/HTTP, and I can instead look at the exporter I'm using and adding JSON/http support there.

@nitisht
Copy link
Member

nitisht commented Feb 26, 2023

it looks like JSON over HTTP is still "experimental" in the OTLP spec, and that grpc/protobuf over HTTP are the stable options

ah, I missed the experimental part. It makes sense for Parseable to have grpc support for ingestion. Would you be interested in a contributing dedicated endpoint for grpc?

@nitisht nitisht added enhancement New feature or request and removed question Further information is requested labels Apr 20, 2023
@nitisht nitisht changed the title feature request: support OpenTelemetry Protocol (OTLP) feature: support OpenTelemetry Protocol (OTLP) Apr 20, 2023
@shubhwip
Copy link

Hi @nitisht I would like to contribute to this feature.

@nitisht
Copy link
Member

nitisht commented Apr 25, 2023

Hey @shubhwip thanks for the offer. Would you join our slack at https://launchpass.com/parseable and we can discuss further?

@nitisht nitisht added this to the Release 0.5.1 milestone May 24, 2023
@trueleo trueleo mentioned this issue Jun 18, 2023
3 tasks
@nitisht nitisht modified the milestones: Release 0.5.1, Release 0.5.2 Jun 25, 2023
@nitisht nitisht removed this from the Release 0.6.2 milestone Sep 8, 2023
@masenocturnal
Copy link

I'm also looking at this and would love to be part of the conversation. I've done a lot of work in generating optimal parquet from otlp payloads

@masenocturnal
Copy link

The oltp collector also has a branch which uses apache arrow over the wire.

@nitisht
Copy link
Member

nitisht commented Jan 10, 2024

The oltp collector also has a branch which uses apache arrow over the wire.

Thanks @masenocturnal this is an interesting idea. we'll prioritise this issue again. This had fallen through the cracks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment