Story
Orsted Extends Elastic Search AI Across Incident Response
Orsted, a utilities organization in Denmark, uses Elastic Search AI from Elastic to support incident response for on-call engineers.
When log investigation outgrew homegrown tracking, Orsted brought in Elastic.
“In Denmark, on-call engineers already knew where log investigation 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 | Log investigation can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for log investigation |
| Capability | Incident response stays visible to adjacent teams through Elastic Search AI |
Story
Orsted did not need another dashboard that nobody opened. It needed incident response to move. In Denmark, on-call engineers already knew where log investigation went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.
Elastic Search AI 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 incident response, which is why on-call engineers live in it rather than exporting from it once a quarter.
Orsted can show how log investigation is handled today. That is the value: a repeatable way to run incident response on software the rest of the industry already recognizes.