Story
Elastic
JDHow JD Runs Incident Response on Elastic Observability
JD, a consumer discretionary organization in China, uses Elastic Observability from Elastic to support incident response for on-call engineers.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in incident response sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Elastic Observability is the governed place on-call engineers use for incident response |
| Capability | New joiners can see how incident response actually runs |
Story
Consumer Discretionary work at JD spans more than one site, even when headquarters sits in China. Log investigation was splitting across regional habits. On-call engineers asked for a shared way to run incident response without freezing local judgment.
Elastic (Elastic Observability) is what they standardized on. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. JD uses it as the system of record for log investigation, with on-call engineers as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
