Oh, that’s much better, thank you.
dimitarvp
mudasobwa
Creator of Cure
Do it 
Just add the package, update a compiler list, declare any function with deft/2 instead of def/2 and see what happens
0
mudasobwa
Creator of Cure
bglusman
derekbrown
This is pretty cool, @mudasobwa! Thanks for sharing.
Thoughts on the decorator pattern for something like this?
@decorator telemetria # the decorator could be anything. t, track, emit, report, etc.
def my_function() do
my code |> my other code
end
It’s a pattern I use regularly and makes code pretty easy-to-read. Spandex uses it too.
2
mudasobwa
Creator of Cure
mudasobwa
Creator of Cure
Thanks!
I thought about allowing to declare telemetry aspects through module attributes, but I frankly don’t see any reason to include decorators in the library itself. Whether one wants to use a decorator, or any other implementation of AOP, t/2 is already there, exported, and nothing can prevent from doing somewhat like
@decorator telemetria()
def my_fun, do: my_code
with a decorator delegating to t/2. SRP
OTOH, maybe you are right and I should think about optional support when decorators are already used in the target application.
0
mudasobwa
Creator of Cure
UPD
0.5.0—- [ENH] annotation
@telemetria trueas a synonym todeft/2 - [FIX] polling is off by default
- [ENH] annotation
0.4.0—- [ENH] default polling of system / vm states for free
- [ENH] starting in phases ensuring proper instrumenter setup
0.3.0—- [ENH] no need for any config in any environment
- [BUG] proper handling of guards in compiler, correct event names
The module attribute @telemetria accepts true only ATM, but it will be extended to accept additional context, levels and specific handler.
1
mudasobwa
Creator of Cure
mudasobwa
Creator of Cure
It’s been a while. Three features and several bugfixes:
0.14.0—- [ENH] Allow
if: runtime_functionin@telemetriaattribute in the form&Mod.fun/1,
which will receive the result and emit the telemetry event if it returnstrue
- [ENH] Allow
0.13.0—- [ENH] Allow
if: compile_time_booleanin@telemetriaattribute
- [ENH] Allow
0.12.0—- [ENH] Allow
[transform: [args: M.f/1, result: {M, :f}]]coercers in@telemetriaattribute
- [ENH] Allow
The above means @telemetria hooks can be optional both in compile time (purged from the resulting code) and runtime (no event if the condition is not met.)
@telemetria level: :info, if: Application.compile_env(:foo, :bar, true)
def foo, do: 42
1