New project under OpenCenus organisation:
tracelog by @ferd (known as author of Learn You Some Erlang, Erlang in Anger and * Property-Based Testing with Proper, Erlang, and Elixir) which allows you to trace your application by using new Erlang’s logger module and metadata assigned to log messages.
Package not yet released on Hex.
Few updates:
tracelog 0.1.0 have landed on Hex, we encourage you to test this outopencensus_telemetry 0.1.0 have been released, it provides seamless integration between Telemetry 0.3.0 and additionally supports Telemetry.Metrics via oc_telemetry:track/1oc_datadog 0.2.0 (name will probably change in future to opencensus_datadog instead) released with fix that now allows user to define views with exporter-independent naming and exporter will normalise it to the format used by the DogStatsD (non alphanumeric characters will be replaced with . (dot))Future work:
I have started work on zPages for Erlang, which will be separate application that will provide development dashboard with look into current traces and metrics. The plan is to provide similar features to the (now abandoned) wobserver on top of OpenCenus library.
The tracing quickstart has been updated to include Elixir code examples OpenCensus
Plus a reporter for the opencensus agent has been published: GitHub - opencensus-beam/opencensus_service: Library for reporting spans and metrics to OpenCensus Service over grpc · GitHub
Using the agent gives you zPages, support for more trace backends and a collector with intelligent sampling.
Can you guys that write the libraries and wrappers give us here a quick breakdown on which does what? I scanned this thread several times and I am still confused.
I’d like to experiment with metrics and tracing in a hobby project so I’m interested in:
How to use a BEAM library that can register events emitted from both Erlang and Elixir code under the umbrella of the same project.
How to install that in an Elixir Mix project, exactly.
How to emit metrics events.
How to emit tracing events.
How to store those events.
How to query those events, with nice graphs, drill-downs and all the statistics goodies (a la Prometheus or the ELK stack).
Bonus points: some explanations on which Hex dependencies are just interfaces, which are implementations, which comply to which standard etc.
Apologies if this is too noob a question but somewhere along the messages here I got lost trying to understand how to achieve the basics – coming from the standpoint of a guy who never used any metric/tracing events when working with Elixir.
That is a lot to cover and we plan to eventually. For now the best I can do is the quickstarts for OpenCensus. The trace guide has Elixir examples included OpenCensus while the metric one only has Erlang, but simple enough to convert to Elixir OpenCensus
As OpenCensus and OpenTracing are merged into OpenTelemetry - I’m wondering Erlang/Elixir library is in the scope of the first-class there.
The official post itself does not list Erlang in the list: https://medium.com/opentracing/a-roadmap-to-convergence-b074e5815289
But the linked roadmap image includes Erlang: https://storage.googleapis.com/open-source-software/OpenConsensus%20Roadmap.jpg
Being ready by early September is likely. We’ve been in a bit of a holding pattern until the new spec and java implementation are near completion (July 6th).
