This first post in our Microsoft + OverOps blog series breaks down how to enhance your troubleshooting process with our Microsoft Teams integration.
At OverOps, we like to work the way you work. Whatever tools you use, wherever you are in the DevOps lifecycle, we’ll meet you there – and bring our deep, code-level visibility along with us.
When it comes to integrating with the modern DevOps life cycle, it should come as no surprise that Microsoft tools are on our radar. Their suite of software delivery offerings covers the entire pipeline from development to alerting, and they are used by some of the world’s largest enterprise engineering organizations.
In this series of posts, we’ll share more about our two new Microsoft integrations and how OverOps can help you maximize your existing investments.
OverOps + Microsoft Teams
Efficient communication is a hallmark of efficient incident resolution, and critical to minimizing MTTI and MTTR. That’s why many of our customers rely on tools like Microsoft Teams for fast messaging and collaboration. By integrating with OverOps, Teams users can instantly view critical events and the context needed to resolve them, helping to streamline the error resolution process.
- Identify & alert on critical events in real-time. OverOps analyzes code at runtime to detect new, critical and increasing errors – even those missed by logs – and immediately alerts you via Microsoft Teams.
- View complete error context for fast resolution. OverOps Teams alerts include error snapshots with critical context about new issues, and a single click into OverOps allows you to see the complete source code, variables, DEBUG logs and environment state behind any error or slowdown.
- Intelligently route context to the right developer at the right time. Using OverOps support for git blame, you can automatically route issues to the developer who last modified the code via Teams and ensure the correct person is equipped with all the context needed to reproduce and resolve the error.
The Microsoft Teams integration for OverOps is simple to set up, and once configured, enables you to view all events detected by OverOps directly within your preferred Teams channel. Users can instantly see the event type, name and environment, as well as a link to the root cause screen in OverOps. Moreover, you can specify the filtering set (called “views” in OverOps) to receive only specific types of events.
The message includes the call stack, as well as the server, VM and deployment in which the error occurred. Get to the OverOps root cause analysis screen in one click directly from the message so you can further investigate the variable values for fast resolution.
You can find step-by-step guidance on how to configure your OverOps-Microsoft Teams integration here. And be sure to keep an eye out for our next post in the series where we’ll breakdown other Microsoft tools we support throughout your pipeline.