sibyl
sibyl copied to clipboard
Vetspire
Easy, ergonomic telemetry & observability for Elixir applications.
When using `@decorate trace()`, warnings for underscored arguments are emitted, however these arguments are not being used in the function itself: ```elixir # ... @decorate trace() def index(conn, _params) do...
This PR implements a new `Sibyl.Experimental` module which aims to replace the usage of the `decorator` library we're currently using to avoid some of the pitfalls of said library. See...
It would be very useful to be able to attach arbitrary metadata which gets passed into all our handlers when attached, for custom metadata overrides such as setting a custom...
See TODO linked in `Sibyl.Dynamic` module for more info, but in short: Right now, dynamic tracing traces all specified functions via one single process. This is fine for simple traces,...
Allow setting of custom event names in our `@decorate trace()` and `@decorate_all trace()` decorators.
It would be convenient to be able to provide a simple plug that checks an incoming HTTP request for a particular (maybe configurable) header that contains metadata that we add...
Code in Elixir is compiled asynchronously. Therefore, loading all modules in compile times is not possible (because most modules are not even compiled yet), so some invocation of `emit` macro...
```elixir defmodule :my_module do use Sybil end ``` Is a valid code
It would be useful to allow `Sibyl.Experimental` to allow users to automatically trace any function like macro such as `test`/3` ```elixir use Sibyl.Experimental, trace_all: [def: 2, defp: 2, test: 3]...
Primary use case is @decorate_all. Functions, starting with `_` won't be traced