Alljob events share the same details about the job that was executed. In addition, failed jobsprovide the error type, the error itself, and the stacktrace. The following chart shows whichmetadata you can expect for each event:
All the Oban plugins emit telemetry events under the [:oban, :plugin, *] pattern (where * iseither :init, :start, :stop, or :exception). You can filter out for plugin events bylooking into the metadata of the event and checking the value of :plugin. The :plugin fieldis the plugin module that emitted the event. For example, to get Oban.Plugins.Cron specificevents, you can filter for telemetry events with a metadata key/value of plugin: Oban.Plugins.Cron.
A default log handler that emits structured JSON is provided, see attach_default_logger/0 forusage. Otherwise, if you would prefer more control over logging or would like to instrumentevents you can write your own handler.
3a8082e126