Story
Elastic
NianticElastic at Niantic: Application Health
Niantic, a communication services organization in the United States, uses Kibana from Elastic to support production support for SREs and developers.
Kibana sits in the daily path at Niantic, especially for SREs and developers.
“In the United States, SREs and developers already knew where application health went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.”
“Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Named workflow replaces ad hoc routing for application health |
| Capability | Production support stays visible to adjacent teams through Kibana |
| Capability | SREs and developers work from the same Kibana record for application health |
Story
Niantic did not need another dashboard that nobody opened. It needed production support to move. In the United States, SREs and developers already knew where application health went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.
Kibana from Elastic is now in that path. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. The company treats it as production tooling for production support, which is why SREs and developers live in it rather than exporting from it once a quarter.
Niantic can show how application health is handled today. That is the value: a repeatable way to run production support on software the rest of the industry already recognizes.
