opentelemetry-specificatio
signoz
Our great sponsors
opentelemetry-specificatio | signoz | |
---|---|---|
7 | 310 | |
- | 16,886 | |
- | 3.2% | |
- | 9.9 | |
- | 7 days ago | |
TypeScript | ||
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opentelemetry-specificatio
-
Migrating to OpenTelemetry
Sure, happy to provide more specifics!
Our main issue was the lack of a synchronous gauge. The officially supported asynchronous API of registering a callback function to report a gauge metric is very different from how we were doing things before, and would have required lots of refactoring of our code. Instead, we wrote a wrapper that exposes a synchronous-like API: https://gist.github.com/yolken-airplane/027867b753840f7d15d6....
It seems like this is a common feature request across many of the SDKs, and it's in the process of being fixed in some of them (https://github.com/open-telemetry/opentelemetry-specificatio...)? I'm not sure what the plans are for the golang SDK specifically.
Another, more minor issue, is the lack of support for "constant" attributes that are applied to all metrics. We use these to identify the app, among other use cases, so we added wrappers around the various "Add", "Record", "Observe", etc. calls that automatically add these. (It's totally possible that this is supported and I missed it, in which case please let me know!).
Overall, the SDK was generally well-written and well-documented, we just needed some extra work to make the interfaces more similar to the ones were were using before.
-
OpenTelemetry in 2023
Two problems with OpenTelemetry:
1. It doesn't know what the hell it is. Is it a semantic standard? Is a protocol? It is a facade? What layer of abstraction does it provide? Answer: All of the above! All the things! All the layers!
2. No one from OpenTelemetry has actually tried instrumenting a library. And if they have, they haven't the first suggestion on how instrumenters should actually use metrics, traces, and logs. Do you write to all three? To one? I asked this question two years ago, not a single response. [1]
[1] https://github.com/open-telemetry/opentelemetry-specificatio...
-
Go standard library: structured, leveled logging
That's why you have otel logging: https://github.com/open-telemetry/opentelemetry-specificatio...
-
Monarch: Google’s Planet-Scale In-Memory Time Series Database
There are a large amount of subtle tradeoffs around the bucketing scheme (log, vs. log-linear, base) and memory layout (sparse, dense, chunked) the amount of configurability in the histogram space (circllhist, DDSketch, HDRHistogram, ...). A good overview is this discussion here:
https://github.com/open-telemetry/opentelemetry-specificatio...
As for the circllhist: There are no knobs to turn. It uses base 10 and two decimal digits of precision. In the last 8 years I have not seen a single use-case in the operational domain where this was not appropriate.
-
OpenTelemetry
A good place to look at is the milestones on GitHub: https://github.com/open-telemetry/opentelemetry-specificatio...
Logging is still experimental in the spec. Metrics API is feature freeze and the protocol is stable, so it's more on language SDKs to stabilize their implementations. This is a focus for several of them right now.
signoz
-
Show HN: OneUptime – open-source Datadog Alternative
You should also check out SigNoz [1], we are an open-core alternative to DataDog - based natively on OpenTelemetry. We also have a cloud product if you don't want to host yourself
[1] https://signoz.io
-
Indexing one petabyte of logs per day with Quickwit
You might want to have a look at SigNoz [1] as well. We have also published some perf benchmark wrt Elastic & Loki [2] and have some cool features like logs pipeline for manipulating logs before ingestion
[1] https://github.com/signoz/signoz
- Open-Source Observability – SigNoz
-
Tools used by the top 1% of Platform Engineers and their Commercial Open Source Alternatives
Check Signoz's repo on GitHub
-
Show HN: Quickwit – OSS Alternative to Elasticsearch, Splunk, Datadog
SigNoz maintainer here.
We also have traces, metrics and logs in a single application which makes correlation across them much easier. From what I can understand from Quickwit website, they use Grafana and Jaeger for UI.
Here'e our github repo if you want to check it out. https://github.com/signoz/signoz
-
Sentry new TOS to use data to train AI with no opt-out
Using user's private with no opt-out option is unethical.
If anyone is looking self-hosted for alternatives then they should try SigNoz: https://github.com/SigNoz/signoz
-
Top 11 New Relic Alternatives & Competitors
SigNoz is a great New Relic alternative that is open-source and provides three signals in a single pane of glass. You can monitor logs, metrics, and traces and correlate signals for better insights into application performance.
-
Share your DevOps setups
If anyone wants to check the project, here's our github repo - https://github.com/signoz/signoz
-
Amazon EKS Monitoring with OpenTelemetry [Step By Step Guide]
You need a backend to which you can send the collected data for monitoring and visualization. SigNoz is an OpenTelemetry-native APM that is well-suited for visualizing OpenTelemetry data.
-
Spring Boot Monitoring with Open-Source Tools
Once the data is collected, it needs to be sent to a backend. That’s where SigNoz comes into the picture. SigNoz is an open-source OpenTelemetry-native APM that provides logs, metrics and traces under a single pane of glass.
What are some alternatives?
skywalking - APM, Application Performance Monitoring System
SLF4J - Simple Logging Facade for Java
prometheus - The Prometheus monitoring system and time series database.
opentelemetry-specification - Specifications for OpenTelemetry
uptrace - Open source APM: OpenTelemetry traces, metrics, and logs
semantic-conventions - Defines standards for generating consistent, accessible telemetry across a variety of domains
jaeger - CNCF Jaeger, a Distributed Tracing Platform
zipkin-api - Zipkin's language independent model and HTTP Api Definitions
zipkin - Zipkin is a distributed tracing system
jvm-serializers - Benchmark comparing serialization libraries on the JVM
Sentry - Developer-first error tracking and performance monitoring