Include OpenLIT to OpenTelemetry Vendors

[patcher9]

In this PR, I have added OpenLIT as a OTEL Vendors as we provide LLM Observability to our end users. I have linked out to our Repository as the source. I have included the entry in the alphabetical order in the list.

Please let me know if you have any suggestions, Thanks!

[svrnm]

@patcher9 taking a look at what OpenLIT is, it looks to me that it should be listed with "integrations" not with "vendors"

[svrnm]

@patcher9 also, are you involved in the LLM Semantic Conventions SIG already?

[patcher9]

@patcher9 taking a look at what OpenLIT is, it looks to me that it should be listed with "integrations" not with "vendors"

Yeah I was a bit confused for sure. But I figured our SDK is what I was gonna add in "Integrations", But since our UI is providing dashboards which are powered by Otel data (can be any OTEL trace that is sent), Vendors made sense for the UI front.

Its quite similar to Traceloop which is listed in vendors in this list already

@patcher9 also, are you involved in the LLM Semantic Conventions SIG already?

Not involved fully involved yet, Though we follow the semantics that were merged recently as we have been following the progress for a while now

[svrnm]

@patcher9 taking a look at what OpenLIT is, it looks to me that it should be listed with "integrations" not with "vendors"

Yeah I was a bit confused for sure. But I figured our SDK is what I was gonna add in "Integrations", But since our UI is providing dashboards which are powered by Otel data (can be any OTEL trace that is sent), Vendors made sense for the UI front.

Its quite similar to Traceloop which is listed in vendors in this list already

Ah, I missed the UI part then somehow, then you're at the right place. In that case the url should point to the documentation where your backend supports OTLP ingestion.

@patcher9 also, are you involved in the LLM Semantic Conventions SIG already?

Not involved fully involved yet, Though we follow the semantics that were merged recently as we have been following the progress for a while now

👍

[patcher9]

Ah, I missed the UI part then somehow, then you're at the right place. In that case the url should point to the documentation where your backend supports OTLP ingestion.

My bad, Lemme clear it a bit on how it works
OpenLIT SDK -> Otel Collector -> Clickhouse exporter -> Clickhouse(data stored) -> OpenLIT(Pulls data from Clickhouse for Visualizations, Similar to SigNoz listed in Vednors)

And now since we only work on OTEL (Actual ingestion being via collector), Linking out to the root of the repo made more sense. Based on the flow and as I saw SigNoz and traceloop directly link out to their website, I felt Repo root might be better to use

[svrnm]

Ah, I missed the UI part then somehow, then you're at the right place. In that case the url should point to the documentation where your backend supports OTLP ingestion.

My bad, Lemme clear it a bit on how it works OpenLIT SDK -> Otel Collector -> Clickhouse exporter -> Clickhouse(data stored) -> OpenLIT(Pulls data from Clickhouse for Visualizations, Similar to SigNoz listed in Vednors)

Then your solution is not supporting native OTLP. Please annotate that in your entry correctly. Note that our page currently states that the vendor list only contains vendors with native OTLP support, so we might consider splitting the list out in those with native and those without native support.

And now since we only work on OTEL (Actual ingestion being via collector), Linking out to the root of the repo made more sense. Based on the flow and as I saw SigNoz and traceloop directly link out to their website, I felt Repo root might be better to use

We need to follow up with them then, because they should also point to the right documentation.

[patcher9]

Cool, Updated the native OTLP to false. Since OpenLIT is OSS only we need a seperate Clickhouse to store OTEL data which is similar to saying Grafana storing Otel traces in Tempo tbh.

Does it work now? with repo link. It does say at the heading itself OpenTelemetry-native with insctructions on ingesting data via our otel library. It feels technically the same thing as me creating a website page and writing it opentelemetry tbh. Lemme know, Wanna get this closed soon before our Demo day. Thanks!

[svrnm]

To make it short, our vendors page does not reflect the reality of what backends do and can do anymore. It needs some rework, but that's none of your concerns (except you are open to help with that:-)), please add the link to your docs and then I'll merge in the PR

[patcher9]

@svrnm Updated the link to point to our docs
and yeah happy to help with any rework on the vendors page.

[svrnm]

/fix:refcache

[opentelemetrybot]

You triggered fix:refcache action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/8922156839

[svrnm]

@svrnm Updated the link to point to our docs and yeah happy to help with any rework on the vendors page.

Appreciated, I will raise an issue and tag you there as well (maybe we have one already so I might reuse that one, need to check)

[patcher9]

Hey @svrnm one question

I missed to add the distribution: true. This should be true correct since the SDK does give Auto Instrumentation for various LLM and VectorDBs?

Also Can I add the SDK to the Integrations page, Seems like a good fit?

Just wanted to confirm on these two before I make another PR
Thanks!

[svrnm]

I missed to add the distribution: true. This should be true correct since the SDK does give Auto Instrumentation for various LLM and VectorDBs?

Distributions is not used anymore, since we have a dedicated page for them: https://opentelemetry.io/ecosystem/distributions/

Also Can I add the SDK to the Integrations page, Seems like a good fit?

It's either a distribution or an integration. Spreading it out across all the pages is not something we should do as it decreases the value of each page. I think your SDK is best described as a distribution.