Dynatrace just laid out its AI observability playbook at KubeCon. Here’s why it matters for developers.

A new AI model goes live for a small group of users. Some of them start seeing errors. The build is the same for everyone, so checking the deployment history gets you only so far. Which users got the new model? What else was happening in the application when the errors began? And can you turn off the feature before the incident channel fills up with theories? That’s the kind of investigation Sean O’Dell , who leads developer experiences at Dynatrace , wants to make easier. In a conversation with The New Stack’s Frederic Lardinois at KubeCon + CloudNativeCon in Salt Lake City, O’Dell explained...

Source: The New Stack

← Back to News