Configuration¶
All configuration is done through environment variables. This page is the canonical list. Every how-to guide links here rather than repeating these values.
Health server¶
PLONE_OBSERVABILITY_HEALTH_HOSTBind address for the health probe server. Default:
0.0.0.0.PLONE_OBSERVABILITY_HEALTH_PORTPort for the health probe server. Default:
8081. Set to0to disable the health server.
Metrics¶
PLONE_OBSERVABILITY_METRICS_ALLOWLISTComma-separated CIDRs allowed to access
@@metrics. Default: empty, which allows all IP addresses.PLONE_OBSERVABILITY_TRUSTED_PROXIESComma-separated CIDRs of trusted reverse proxies, used to resolve the client address from
X-Forwarded-For. Default:127.0.0.1,::1.PLONE_OBSERVABILITY_METRICS_CACHE_TTLSeconds to cache the expensive-to-collect metrics: the content catalog counts and the database-wide ZODB gauges (
plone_zodb_object_count,plone_zodb_db_size_bytes). On Postgres-backed storage those two are full-table queries, so caching keeps@@metricsfast. Default:60.PLONE_OBSERVABILITY_ZODB_ACTIVITY_MONITORInstall a minimal ZODB activity monitor for the load and store counters. Set to
0to disable. Default:1.
OpenTelemetry tracing¶
These variables apply only when the opentelemetry extra is installed.
The standard OTEL_* variables are honored directly; the table below lists them for convenience alongside the package-specific overrides.
OTEL_EXPORTER_OTLP_ENDPOINTOTLP collector endpoint. Setting it enables tracing.
OTEL_SERVICE_NAMEService name reported on emitted spans.
OTEL_TRACES_SAMPLERSampling strategy.
OTEL_PYTHON_WSGI_EXCLUDED_URLSComma-separated regexes of paths to never trace, matched as a substring search against the path. Falls back to
OTEL_PYTHON_EXCLUDED_URLS.PLONE_OBSERVABILITY_OTEL_ENABLEDMaster on/off override. Accepts
1or0.PLONE_OBSERVABILITY_OTEL_EXCLUDE_DEFAULTSDefault-exclude the package’s own
@@metricsscrape from tracing. Accepts1or0. Default:1.PLONE_OBSERVABILITY_OTEL_USER_IDInclude
enduser.idon spans. This is personally identifiable information; it is off by default.
See also
About health probes explains why the health server runs on a separate port, and How to install plone.observability shows how to wire the WSGI filters that activate metrics and tracing.