Fastify-native plugin
Instrument Fastify 4–5 through lifecycle hooks designed for the framework request model.
Fastify API monitoring
Know which customers a Fastify issue actually affects.
Add customer context to Fastify errors, slow routes and release regressions with native hooks and bounded asynchronous delivery.
Fastify 4–5Native lifecycle hooksBounded queueNo payload capture
Customer-aware observability
Fastify monitoring that explains who is affected.
Preserve Fastify's performance model while connecting route-level operational signals to the accounts and integrations your team supports.
Customer-aware errors
Connect failed requests and stable error codes to the authenticated accounts that encounter them.
Normalized route analytics
Compare latency and reliability by route template rather than high-cardinality raw URLs.
Non-blocking capture
Append events to a bounded queue while batching and network delivery stay outside the response path.
Automatic shutdown flush
Use the Fastify close lifecycle to deliver pending events within a fixed timeout.
No payload capture
Exclude bodies, credentials, cookies, query values, email addresses and client IP addresses.
Setup
From requests to customer impact.
Keep your current logging and tracing stack. Add the customer context that generic infrastructure monitoring cannot provide.
- 1
Install the Fastify plugin
Add the framework adapter and shared Apirelio core package from npm.
- 2
Register customer resolution
Provide the ingestion key and map the authenticated request to a stable customer ID.
- 3
Verify an API route
Send a request and inspect customer-level reliability, latency and release impact.
Questions
Frequently asked questions.
How do I monitor a Fastify API by customer?+
Register the Apirelio Fastify plugin after authentication and provide a resolver that maps each request to the authenticated customer and consuming application.
Will Fastify monitoring block API responses?+
No. Capture uses a bounded in-memory queue, while batching, retry and network delivery run outside the observed customer response path.
Does the plugin use native Fastify hooks?+
Yes. It records timing, framework errors, final status and the resolved route through the Fastify request lifecycle and flushes during shutdown.
Are Fastify request payloads stored?+
No. Request bodies, response bodies, credentials, cookies and query strings are excluded from Apirelio telemetry.
Start with the requests you already serve
Know who is affected before the support ticket arrives.
Connect API reliability to customer impact with a privacy-safe event model and framework-native setup.