DEVOPSdigest

VictorOps announced a new Slack integration that will allow VictorOps customers to conduct remediation more quickly and directly within Slack while still enabling the VictorOps platform to act as a single source of record.

“Today’s DevOps teams want to be able to use the chat platform of their choice when it comes to incident management - and most of the time, they choose Slack,” said Joni Klippert, VP of Product, VictorOps. “But the problem is a lot of information is being lost in the process of switching back and forth between VictorOps and the Slack channel. That lost data doesn’t make it onto the ticket and isn’t incorporated into post mortem reports. This new integration will help to streamline the firefighting process and provide our customers with easier access to the tools they want to use to get the job done.”

The full integration will be delivered in three phases, the first of which will focus on allowing customers to interact with VictorOps incidents within Slack. Other key feature of phase one include:

- Native Slack App: VictorOps will now be a native Slack app that admins can download and easily install from either the Slack app store or from within the VictorOps platform.

- User Mapping/Linking: VictorOps links the user accounts in each system so users can operate out of either platform and the VictorOps platform will still track all actions to ensure managers have accurate statistics and information for each incident.

- Action Buttons: Users can manage VictorOps incidents from within Slack, acknowledging and resolving incidents with a button, which results in quicker response times.

- Full Payload: VictorOps provides more information to the end user by enabling them to see the full incident payload from within Slack.

- Two-way integration: Captures all channel activities.

“As our user base evolves, we want to be able to accommodate them as much as possible to make being on-call suck less,” added Klippert. “This particular integration is focused more on the needs and preferences of the developer community in an effort to support further collaboration among DevOps teams. In phase two of the integration, we hope to continue to foster this with additional features.”