![]() That includes Twitter conventions like and chat platform integration (although VictorOps has taken this concept further with that allows you to ping an entire team in your chat). Communicationĭuring the entire incident lifecycle, VictorOps provides extensive communication tools to ensure your team can work together. From there they can ack or re-route the issue to one or more teams, while also having the ability to filter the Incident Pane by items that are paging them, paging team’s they’re on, or all paging events. Members of your DevOps team can see the Incident Pane, which is a distilled view of the critical alarms in their system. The timeline shows all alerts coming off of your system, who’s being paged, and conversation occurring pertaining to problem identification and resolution. Think of the timeline as the main point of focus in the VictorOps platform. The timeline is also multi-threaded, which means that you can leverage the timeline to gain situational awareness of other alarms from your systems that may be contributing to the issue, rather than only surfacing limited information relevant to a single alert. This timeline is accessible from desktop and mobile devices, allowing you to help solve issues in and outside of the office. You can view a detailed overview of the Transmogrifier here.Īfter filtering through your alerts and notifying the developers on-call, the VictorOps timeline is there to help you see the full scope of the incident as it unfolds. This feature allows alerts to be escalated when certain conditions are met, annotated with documentation and/or developer specific notes, and much more. The Transmogrifier is a recently launched VictorOps feature that works to greatly increase the value that an average alert can provide. Users can be paged regarding incoming alerts via push notifications, SMS, email, and phone, all at specific and predetermined intervals. Once VictorOps comes across an alert you’ve defined as critical, it begins the paging process in exactly the manner you’ve set up, itself open to plenty of customization and user specific settings. That being said, the first thing that VictorOps helps you achieve in the incident lifecycle is ensuring the right people are alerted for issues within their problem domain through advanced routing.Īdvanced routing allows you to programmatically alert on-call team members to issues that need attention. Sending your alerts to VictorOps Filtering through AlertsĪlerts come through all the time, and while some do contain important information, many can be irrelevant and unhelpful. With that in mind, let’s take a look at how VictorOps helps you work through the incident lifecycle to help you solve the problem faster. ![]() Each incident has a lifecycle of it’s own, from when the alert comes in to holding a post-mortem when it’s over. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |