Story
Elastic
DexcomDexcom Standardizes Log Investigation on Elastic
Dexcom, a health care organization in the United States, uses Elastic Observability from Elastic to support incident response for on-call engineers.
Value results
| Category | Value result |
|---|---|
| Capability | Incident response stays visible to adjacent teams through Elastic Observability |
| Capability | On-call engineers work from the same Elastic Observability record for log investigation |
| Capability | Log investigation can be reviewed without waiting on a personal export |
Story
Dexcom is based in the United States and runs health care operations at a scale where log investigation cannot live in side channels. On-call engineers were reconciling competing copies of the same work, which slowed incident response and hid who owned the next step.
The company runs incident response on Elastic, with Elastic Observability as the product on-call engineers actually open. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. For Dexcom, that means on-call engineers can open one workflow, see log investigation, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for log investigation.
