Allma has brought everything related to real time incident collaboration directly into Slack for a team. The primary way of interacting with Allma is through slash commands, and buttons. Here we're seeing a list of full commands and there are two commands that we can take from anywhere in our Slack workspace, and that's the ability to declare a new incident, and the ability to list out incident history over time, which shows all active and all inactive prior incidents, and then a set of commands that can be taken from explicitly within an active incident channel.
Let's go ahead and list out incident history and you'll see that Allma spins up an incident specific channel for every event to keep a workspace clean and to provide a dedicated space for problem solving for teams. Allma also integrates with alerting tools like Pagerduty. We've just seen a high 500 error rate Pagerduty alarm. So let's say we're responding to that alert and declare an incident from anywhere in the workspace. It brings up a modal, where we can talk about what's going on.
If there's any customer impact we've put it right in here, and we've brought all of our active PagerDuty alerts straight into Slack so that we usually see an alert, and link it, and bind it to an incident. And the other thing we'll see here is the ability to show severity levels of a service right in the modal to mitigate context switching for teams and guiding teams through best practice, Allma has embedded severity levels directly into the tool, they're fully optional, and fully configurable so a team can configure severity levels with their own definitions based on your organization.
I'll go ahead and declare the incident and a few things will happen. First Allma spins up that incident specific channel. But before we jump in, I want to show you that we're acknowledging and silencing the PagerDuty alert for your team, so that it doesn't distract you during an incident. And then the final thing worth pointing out is Allma has built a communication system into our Slack app that enables a team to define pieces of data and events that they'd like pushed out across their workspace to various channels during an incident, so the team can say for example that every time an incidents declared, I want my engineering and Customer Success channels and maybe my product channels to be automatically notified of this incident. We enable granular conditions so you can specify that maybe you just want highest priority incidents to be sent to your executive channel and all incidents to go to other channels.
So here we're seeing an incident update, having been pushed into the engineering channel and we always include a link to the channel with the impact of the incident so a team can easily jump in.
We're now in the incident channel. We're seeing that Allma is maintaining the data trail within the channel topic, and so this is consistently updated and serves as a single source of truth for teams. Also, every time an individual joins the Allma incident channel, they'll receive a status update, a summary of what's happened so far, so that they don't have to scroll back through the many messages and threads already happening. It's only visible to them so won't clog up the rest of the channel with noise, you can call that command at any time with /allma status.
Another thing worth pointing out is the concept of role management here. Allma built best practices, straight into the tool inclusive of role management. Again it's fully optional and fully configurable so teams can configure corresponding roles and definitions to their unique processes. I'll go ahead and select the role of incident commander. Allma will follow with two pieces of configurable and optional content, a prerequisite, as well as an embedded role checklist to serve as a friendly reminder for folks on their corresponding responsibilities for each role.
You can link out to run books and play books here as well as well as any external documentation that you have. You can interact throughout with buttons and you're able to change and assign roles throughout an incident, especially key for knowledge handoffs.
Allma also built the concept of timeline directly into the slack app so that at any time, we can add a note to the timeline and say we've been investigating recent deploys and we found one. We've hooked this up to our communication system such that any channel to pre configured to receive updates around timeline. You can always, in the moment decide just to add it to the timeline and not broadcast it out. In this case I'm going to broadcast it to everyone because we have a path forward and eta. This note will be dropped into the incident channel, It will appear in the timeline right here with the timestamp and it'll be pushed out across my workspace to the channels that I wanted it to go to. We can also edit the incident at any moment, if we figure out customer impact changes, we can change the state. And as soon as we save the incident channel is now updated with the topic with the correct status, it's pushed out as an update to any channels that have been pre prescribed to receive so at any moment too.
You can easily add messages straight to the timeline with a click of a button. In this case, I'm not going to broadcast it out. You may have more alerts come in that are related. We're seeing a new alert come in straight into this incident channel, and that's because Allma has intercepted the alert and dropped it right into the channel for us so that we can easily get context on to what's happening in our pager duty and bind any related alerts. Here we have a latency alarm its the same API is an error rate so I'll go ahead and bind it and we'll have that same behavior of acknowledging and silencing that alert for the team so it's not distracting.
You can also page people into an incident at any moment and easily get the right person in, you can page a service, you can page a user, it's actually overrides of humans pager duty escalation policy, as long as that person has a Slack account and a PagerDuty account, and every time on the page some someone we include a link to the incident channel and context so they can easily jump in on their phone.
When an incident is over you can run /allma resolve. We can add any resolution notes, Letting people know the rollback was successful. And when we push it out. We'll see the channel topic updates with the resolution. Allma auto resolves the active pager duty alerts and pushes out updates across your workspace channel based on your specific configuration. Allma will automatically archive this incident channel on your behalf seven days after inactivity to keep your workspace clean.
Let's check out our web app, the Allma web application stores full incident history for teams so they have one place with all of their incidents. We have easy criteria for filtering here and working and navigating through these incidents.
So this is the incident that we've been working on together. And we can see that we include an overview of the incident with key times between states. And then we've also generated a full timeline for teams, based on the events that we've learned, via Slack and PagerDuty. We've put the full chat transcripts next to the timeline so that a team can easily see them side by side and make edits to curate the timeline for your post incident review. You can easily add messages through the timeline, and it will swap them right in to their corresponding position, as well as make edits and add events to the timeline. Finally, Allma provides a list of all of the collaborators throughout an incident with their corresponding role so you can easily get a sense of who's been involved in incidents the role they've taken, how much time they're spending, and make necessary team design decisions accordingly. Allma does have an API, so you can feel free to send these metrics to your data warehouse or internal analytics systems.