Na, I know that is what you mean. I’m saying that shouldn’t be the case. I think because of the influence this will likely have on how Elixir users instrument their projects it should push for doing things the “proper” way from the beginning, where you use a tracing library for creating spans (not through telemetry events) and telemetry events for annotating them.
tristan
Rebar3 Core Team
Ludwik
Hey, I’ve just implemented InfluxDB reporter for Telemetry:
https://github.com/ludwikbukowski/telemetry_influxdb
7
darkmarmot
I’ve been reading through the Telemetry docs and am confused about the unique handler-ids.
If I have matching event names in different libraries that use telemetry, would these be invoked across different handler-ids since the execute function doesn’t seem to include a handler-id?
I guess I don’t understand the point of the handler-id if it isn’t being used to discriminate between events? Is it just to provide a unique name in an ets table?
Any info would be appreciated, thanks!
0
josevalim
Creator of Elixir
The name is only so you can remove your own callback/handler later if you want to and for error reporting. It has no relation to the events. You can even use a random name if you want to.
3
