Zabbix template: HTTP route mean by OpenTelemetry, version 1.3.2
For Zabbix 8.0 with the APM data source configured.

1. Data collection > Templates > Import: choose http-route-mean.json (the JSON, not this ZIP).
2. Link "HTTP route mean by OpenTelemetry" to one host per application.
3. On that host, set the macro {$APM.SERVICE.NAME} to the application's OTEL_SERVICE_NAME.
4. Monitoring > Hosts: in the host's row click Dashboards (dashboard "HTTP"). It is a host dashboard that comes
   with the template; the Dashboards menu does not list it.

The application must export the stable HTTP server metrics every 60 seconds: the histograms
http.server.request.duration (seconds), http.server.request.body.size and http.server.response.body.size
with DELTA temporality, and http.server.active_requests. OpenTelemetry zero-code instrumentation for
FastAPI does, with OTEL_SEMCONV_STABILITY_OPT_IN=http.

Per application: requests, responses by status class, HTTP 429, error rate, mean and slowest request, bytes
in and out, requests in flight, reporting instances. Per API (HTTP method + route, created by discovery):
mean and slowest request, requests, error responses, mean response size. Means and maxima are per minute;
they are not percentiles.

Triggers: HTTP 5xx responses, HTTP 429 responses ({$APM.HTTP.429.WARN}, default 1), no application instance
reported for 5 minutes, and the APM query returned no result for 5 minutes.

Changes in 1.3.2: after a failed query, the items that store no value in a quiet minute (mean and slowest
request, error rate, mean response size) no longer stay "Not supported". Importing 1.3.2 over 1.3.1 updates
the template in place and keeps the existing items and their history; an API's items pick the change up at
its next request.

Changes in 1.3.1: the trigger "No application instance reported for 5 minutes". It fires after five polls
without a reporting instance; a restarted application reports again only after its first request.

Changes in 1.3.0: the per-application items, four more items per API (slowest request, requests, error
responses, mean response size), the HTTP 5xx and HTTP 429 triggers, and the dashboard's Overview and API pages.
