Function Autoscaler Observability
The Function Autoscaler emits structured logs, Prometheus metrics, and
OpenTelemetry spans. The chart exposes its Prometheus exporter through the
function-autoscaler service on the metrics port, which defaults to 41338.
The shared stack’s default monitors do not include this service. Add a monitor
or scrape target for it to collect these metrics.
These service metrics describe the autoscaler itself. They are separate from the function metrics that the autoscaler reads from VictoriaMetrics or an external backend.
Metric reference
Tracing
The function autoscaler emits OpenTelemetry spans for outbound calls to the timeseries database and the NVCF API, with the OTLP endpoint and span filter configurable under server.tracing.
Logging
The function autoscaler writes structured logs to stdout. Set log filter directives in the server.envfilter_directive configuration field. The format follows the tracing_subscriber env filter syntax (Rust ecosystem standard):
The same syntax applies to server.tracing.logging_envfilter_directive if you separate logging and tracing filters.
Useful target prefixes:
See also
- Function Autoscaler Operations for common symptoms tied to these metrics and log lines.
- Architecture for the components that emit each signal.
- Configure Autoscaling for setting per-function scaling bounds and policy via the NVCF API.