Per API, per server, per cluster
Calls, errors and p95 latency for every API and every server. Histograms merge across servers, so the p95 of the cluster is right.
Operations
Monitoring
Calls, errors and latency of every API, the health of every server, and alerts when something drifts.
API Maker counts every call after its response and writes one rollup a minute per process, with the vitals of the process. The analytics dashboard shows calls, errors and p95 per API and per server, built-in rules turn the health verdict to degraded or critical, and more dashboards cover the servers, Redis and your data model.
See it live
Step through it, slow it down, or open the full canvas.
api-maker/features/monitoringLive- Calls
- 0this minute
- Writes
- 1per minute, per process
- p95
- 150ms
- Health
- HEALTHYverdict
Every call counted, after its response. The worker answers first, then adds the call to counters in memory: calls, errors and a latency histogram per API. No database, no Redis on the way.
How it works
Every call counted, after its response.
The worker answers first, then adds the call to counters in memory: calls, errors and a latency histogram per API. No database, no Redis on the way.
One write a minute per process.
Every 60 seconds the counters go out in a single bulk write as 1 minute rollups, kept 30 days, with memory, heap, CPU and event loop vitals.
Calls, errors and p95, per API and server.
Histograms merge across servers, so the p95 of the whole cluster is right. Logs can be off: the dashboards do not depend on them.
Built-in rules, one health verdict.
Error rate over 5 %, p95 over 2000 ms, memory, disk, heap, event loop lag, DB pool, sandbox queue, nodes down: each firing rule turns the verdict to DEGRADED or CRITICAL.
Servers, Redis and your data model.
The nodes dashboard shows workers, memory, platform and DB connections. The Redis dashboard edits keys and TTLs. The ER diagram draws your instances and tables.
What you get
Vitals of every process
Memory, heap, CPU and event loop lag of each process, stored with the minute rollups.
Rules you do not have to write
Error rate over 5 %, p95 over 2000 ms, memory or disk over 85 %, heap over 90 %, event loop lag over 200 ms, a full DB pool, a sandbox queue or a node down turn the verdict to degraded or critical.
Server nodes
The nodes dashboard lists the servers and workers of the cluster with their memory, platform and database connections.
Redis dashboard
Browse the keys of Redis, read and edit values, and change their TTL.
ER diagram
See your instances, tables and the relations of their schemas as a diagram.
An example
A slow API after a release
After a deployment, the verdict turns degraded: the p95 of one API went past 2000 ms. The dashboard shows which server and since when, and the log explorer, sorted by duration, shows the slow calls themselves.
Good to know
- Counters are kept in memory and written once a minute, so the last minute of a process that crashes can be missing.
Questions
Does monitoring slow down the APIs?
No. A call is counted after its response, in memory, and each process writes one bulk update a minute.
Where are the metrics stored?
In the log database of API Maker (or its main database when there is no log database), as minute rollups and vitals that expire after 30 days.
Learn more
Documentation