|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Laravel Newrelic||174||28||1||3 years ago||19||February 06, 2019||18||PHP|
|Laravel NewRelic ServiceProvider|
|Signalfx Agent||115||23||a month ago||85||April 23, 2021||18||apache-2.0||Go|
|The SignalFx Smart Agent|
|Performance Observer||54||5 months ago||3||October 19, 2020||1||apache-2.0||TypeScript|
|Generic interface for PerformanceObserver API.|
|React Spy||33||1||4 years ago||23||January 23, 2019||1||TypeScript|
|A set of utilities for collecting UX-analytics of your React-application (ex: clicks, shows, errors and etc.)|
|Memory Pressure||9||4 months ago||Go|
|Linux memory pressure evaluation discovery toolkit|
|Go Observer||8||263||206||6 years ago||1||June 22, 2017||apache-2.0||Go|
|an Observer API for OpenTracing-Go Tracers|
|Opentelemetry Metric Dotnet||7||3 months ago||1||apache-2.0||C#|
|Dynatrace OpenTelemetry Metrics Exporter for .NET|
|Bluekiri Diagnostics Prometheus||6||5 years ago||3||mit||C#|
|Exposes Diagnostic Source events as prometheus metrics using prometheus-net underneath|
|Masstransit.prometheus||5||4||4 years ago||408||July 15, 2022||apache-2.0||C#|
|Collect the necessary MassTransit metrics for Prometheus|
|Visdomobserver||4||5 years ago||mit||Jupyter Notebook|
|A sacred RunObserver which uses visdom to plot metrics and artifacts|
OTObserver can be used to watch the span events like StartSpan(), SetOperationName(), SetTag() and Finish(). A need for observers arose when information (metrics) more than just the latency information was required for the spans, in the distributed tracers. But, there can be a lot of metrics in different domains and adding such metrics to any one (client) tracer breaks cross-platform compatibility. There are various ways to avoid such issues, however, an observer pattern is cleaner and provides loose coupling between the packages exporting metrics (on span events) and the tracer.
This information can be in the form of hardware metrics, RPC metrics, useful metrics exported out of the kernel or other metrics, profiled for a span. These additional metrics can help us in getting better Root-cause analysis. With that being said, its not just for calculation of metrics, it can be used for anything which needs watching the span events.
otobserver package provides an API to watch span's events and define
callbacks for these events. This API would be a functional option to a
tracer constructor that passes an Observer. 3rd party packages (who want to
watch the span events) should actually implement this observer API.
To do that, first fetch the package using go get :
go get -v github.com/opentracing-contrib/go-observer
and say :
and then, define the required span event callbacks. These registered callbacks would then be called on span events if an observer is created. Tracer may allow registering multiple observers. Have a look at the jaeger's observer.
With the required setup implemented in the backend tracers, packages watching the span events need to implement the observer api defining what they need to do for the observed span events.
An observer registered with this api, can observe for the following four span events :
StartSpan() SetOperationName() SetTag() Finish()
As noble as our thoughts might be in fetching additional metrics (other than latency) for a span using an observer, there are some overhead costs. Not all observers need to observe all the span events, in which case, we may have to keep some callback functions empty. In effect, we will still call these functions, and that will incur unnecessary overhead. To know more about this and other tradeoffs, see this discussion.