Telemetry

Zilla captures telemetry data in metrics and events. The data can then be accessed outside of Zilla by configuring exporters to chose how and where to see the telemetry data. You can see logs and metrics with the Telemetry Intro example.

telemetry:
  metrics:
    - http.duration
  exporters:
    stdout_logs_exporter:
      type: stdout

Metrics

Metrics are separated by protocol where the stream metrics relate to Zilla's internal message handler. The other protocols have common metrics you would expect to find. The zilla metrics command can be used to see the raw metrics that Zilla has collected.

Events

Events in Zilla signal important activities and collect relevant information along with them. Primarily they are useful when troubleshooting common issues like model validation or failed secure access, but they provide more observability with the HTTP access information. The easiest way to see logged events in Zilla is to add the stdout exporter to your zilla.yaml config.

Exporters

Exporters will determine how the collected telemetry data is exposed. The Prometheus exporter Zilla will expose any configured metrics via the standard /metrics endpoint that is by prometheus to collect metrics. The stdout exporter will simply log all Events to the host stdout and can be collected by any log aggregator. The OpenTelemetry Protocol exporter can push both logs and metrics telemetry data to the specified.