The Artifact Firewall emits metrics and traces over OpenTelemetry, under the instrumentation scope artifact-firewall, as its otel section configures. A firewall run on its own and integrated with a Virtual Registry sets up no OpenTelemetry and emits neither.
Bundled with the Virtual Registry, the firewall has no telemetry configuration of its own: it reuses the Supervisor’s providers, set up from its otel section, and its telemetry arrives alongside Varnish and Supervisor telemetry carrying the same service.name.
Firewall metrics leave by whichever route otel.metrics.exporter selects, pushed over OTLP or served on the Prometheus scrape endpoint.
The audit log is a separate stream with its own destination setting.
Package evaluation:
| Metric | Type | Description |
|---|---|---|
firewall_requests_total |
counter | Package evaluations: on an /api/eval call, while filtering a manifest, and on a download refused before the firewall fetches it, not counted before Artifact Firewall 0.9.0. Attributes: package_type, action, rule_id, mode. |
firewall_manifests_total |
counter | Manifest transformations. Attributes: package_type, status, mode. status is ok, error, or report_only for a manifest left alone because of the firewall mode. |
firewall_manifest_duration_seconds |
histogram | Time spent transforming a manifest. Attribute: package_type. |
firewall_proxy_duration_seconds |
histogram | Total proxy request duration. Attribute: package_type. |
firewall_audit_entries_total |
counter | Audit log entries. Attribute: result, which is written, or failed for an entry lost to a write error. A failed entry is logged and the request is served anyway. With audit_log_output: otel an entry counts as written once it is handed to the OpenTelemetry pipeline. Nothing is counted while audit logging is off. |
Rulesets and their cache:
| Metric | Type | Description |
|---|---|---|
firewall_rules_loaded |
gauge | Rules currently loaded. |
firewall_rulesets_loaded |
gauge | Rulesets currently loaded. |
firewall_ruleset_reloads_total |
counter | Reload attempts. Attribute: status, success or failure. |
firewall_storage_used_bytes |
gauge | Bytes used by the ruleset cache directory, sampled every 10 seconds. Only reported when storage.size is set. |
firewall_storage_declared_bytes |
gauge | The declared budget from storage.size, or 0 when it is not set. |
Publish-time lookups, made to place a package inside or outside its quarantine window:
| Metric | Type | Description |
|---|---|---|
firewall_maven_solr_requests_total |
counter | Solr API calls for Maven publish times. Attribute: outcome. |
firewall_maven_head_requests_total |
counter | HEAD requests against upstream POM URLs, the fallback when Solr answers nothing. Attribute: outcome. |
firewall_pypi_publish_time_requests_total |
counter | PyPI JSON API calls for publish times on the HTML simple index. Attribute: outcome. |
HTTP:
| Metric | Type | Description |
|---|---|---|
http_requests_total |
counter | All HTTP requests. Attributes: method, route, status. |
http_errors_total |
counter | Responses with a 5xx status. Attributes: method, route, status. |
http_request_duration_seconds |
histogram | Request duration. Attributes: method, route. |
The route attribute is normalised to one of /api/rulesets, /api/update, /api/eval, /api/mode, or /. Registry traffic falls into the / bucket, since package paths are unbounded. To count proxied traffic, filter on route="/".
The /healthz and /readyz probes are answered before these metrics are taken, so they are not counted, and they start no span.
Tracing is off until otel.tracing is enabled with an endpoint. Bundled with the Virtual Registry, it is the Supervisor’s otel.tracing, which needs the vmod-otel license addon.
Per request the firewall emits:
GET /api/eval.firewall.proxy, covering the proxied request.firewall.transform_manifest, covering manifest evaluation and rewriting.firewall.evaluate on an /api/eval call, carrying the decision as firewall.purl, firewall.rule_id, firewall.ruleset_id, firewall.action, firewall.enforced_action and firewall.mode. Before Artifact Firewall 0.7.0 firewall.enforced_action was named firewall.effective_action.An inbound W3C traceparent header is honored and propagated to the origin, so a build system that traces its own dependency fetches sees them continue through the firewall.