A better view on status: improving ESI health monitoring
Hi all,
Today we're announcing improvements to how ESI reports its health status. The health status route is migrating from /status.json to /meta/status and the Status Dashboard gets a fresh new look.
Update health status
The current /status.json route is running on older infrastructure and can’t access information about newly introduced routes like corporation projects. Additionally, the “red” / ”yellow” / ”green” status indicators aren’t very descriptive.
To address these issues, we are migrating the health status to a new, more robust backend. The updated status values will be as follows:
OK: (old “green”) This route is currently operational and available.
Degraded: (old “yellow”) This route is currently degraded and may be slow to respond.
Down: (old “red”) This route is currently experiencing issues and may not be available.
Recovering: (new) This route is recovering from an outage.
In practical terms, "degraded" means we're seeing a few 5XX responses per second - the route is still working, but not at full capacity. "Down" means most of the traffic is returning 5XX responses - the route is experiencing significant issues and may not be usable.
Along with these changes, the Status Dashboard has been updated to reflect the new route and status indicators. The updated route is now listed under “Meta” in the OpenAPI specs and API Explorer.
If you're currently using /status.json, you should migrate to the new /meta/status endpoint. The old endpoint will remain available for a few months to allow time to update your applications.
Cheers,
Your friendly developers of the EVE Status Indicator (working title)