Membrane.Telemetry (Membrane Core v0.7.0) View Source

Defines basic telemetry event types used by Membrane's Core. Membrane uses Telemetry Package for instrumentation and does not store or save any measurements by itself.

It is user's responsibility to use some sort of metrics reporter that will be attached to :telemetry package to consume and process generated measurements.

Instrumentation

Membrane.Telemetry publishes functions that return described below event names.

The following events are published by Membrane's Core with following measurement types and metadata:

  • [:membrane, :metric, :value] - used to report metrics, such as input buffer's size inside functions, incoming events and received caps.

  • [:membrane, :link, :new] - to report new link connection being initialized in pipeline.

The measurements are reported only when application using Membrane Core specifies following in compile-time config file:

config :membrane_core,
  enable_telemetry: true

Link to this section Summary

Types

  • component_path - element's or bin's path
  • metric - metric's name
  • value - metric's value
  • parent_path - process path of link's parent
  • from - from element name
  • to - to element name
  • pad_from - from's pad name
  • pad_to - to's pad name

Link to this section Types

Specs

event_name_t() :: [atom(), ...]
Link to this type

metric_event_value_t()

View Source

Specs

metric_event_value_t() :: %{
  component_path: String.t(),
  metric: String.t(),
  value: integer()
}
  • component_path - element's or bin's path
  • metric - metric's name
  • value - metric's value

Link to this section Functions

Specs

metric_event_name() :: event_name_t()