Technologies/Prefect/prefect.server.api.requests
PrefectPrefectMetric

prefect.server.api.requests

Total API requests
Dimensions:None
Available on:PrometheusPrometheus (1)
Interface Metrics (1)
PrometheusPrometheus
Total number of API requests to the Prefect server
Dimensions:None
Sources
prefect_server_api_requests_totaldocs.prefect.io

Technical Annotations (16)

Configuration Parameters (3)
PREFECT_CLIENT_RETRY_EXTRA_CODESrecommended: 500,421
Enables retry logic for HTTP 500 responses to prevent worker crashes
PREFECT_API_KEY
Must be current API key from Prefect Cloud; stored in profiles.toml
PREFECT_API_URL
Prefect Cloud endpoint URL; stored in profiles.toml
Error Signatures (5)
500 Internal Server Errorhttp status
prefect.exceptions.PrefectHTTPStatusErrorexception
unhandled errors in a TaskGroupexception
401 unauthorizedhttp status
401http status
CLI Commands (2)
prefect cloud loginremediation
flow.run()remediation
Technical References (6)
read_deploymentcomponent_submit_runcomponent_check_flow_runcomponentprofiles.tomlfile path.prefectfile pathPrefect Cloud APIcomponent
Related Insights (5)
Worker exits unexpectedly when API server returns HTTP 500critical
▸
API server overload at high scale causes HTTP 500 errorswarning
▸
Stale API key in profiles.toml causes 401 unauthorized errorswarning
▸
Prefect Cloud free tier rate limits cause request failureswarning
▸
API outage prevents task state confirmation and flow completionwarning
▸