Imagine you could empower your team to create incidents in PagerDuty or Datadog, message service details to Slack, and trigger jobs in GitHub, GitLab, or Jenkins directly from OpsLevel, without having to build anything from scratch? 

If unblocking your developers so they can build and ship products faster is top of mind, you’re going to want to pay attention: you can now choose from six ready-made Actions and empower developer self-service today. 

We took some of the most common operational tasks, and built templated Actions that get you 90% of the way there—just finish some basic configuration and you’re all set to unblock your teams. Developer self-service has never been easier.

A recap on Actions in OpsLevel

Back in January, we launched Actions in the OpsLevel internal developer portal. The goal? Enable developer self-service. 

The trend of developer self-service was born out of classic engineering team tension: 

• SRE and security teams want to ensure security and reliability standards are being met
• Developers want to build and ship code faster without bottlenecks

Platform engineering teams were created to empower devs to move faster without sacrificing standards, but to truly unblock development velocity, they need to empower developer self-service without sacrificing standards. Cue: Actions. 

By implementing Actions with standards baked-in, developers can take on common operational tasks themselves, risk-free, to do things like: 

• Create a new S3 bucket
• Resize infrastructure
• Provision a new Kafka topic
• Send a structured Slack message
• Trigger an incident
• Open or merge a PR

And the list goes on. With the whole goal being to make everyone’s life easier, we got to thinking about how we could make the initial setup of these Actions even easier for OpsLevel Admins. 

Get started right away with templated Actions

We decided to start by templating Actions. We built a library of six common operational tasks to remove bottlenecks and streamline the developer experience for nearly every engineering team: 

For operational teams, the burden of setting up these workflows is reduced to minutes instead of days, and product developers can leverage these Actions with a few clicks exactly when they need to. Best part? They’re used repeatedly over time, reducing the operational costs for the entire team.

We’ve started with six templates but will be adding to our library over time to make sure we’re unblocking the most impactful tasks. 

Making self-service a priority

The introduction of Action templates supports our larger focus of empowering developer self-service, alongside a few other key updates to OpsLevel: 

Self-service hub

All OpsLevel users will see a new Self-service category at the very top of their main navigation. This is where you can find all implemented Actions and Service templates—in one central hub. Admins will also have access to manage Actions and create or import new Service templates. 

Global actions

You asked, we listened: Actions no longer have to be tied to a specific service. Are you looking to:

• Raise a generic MIM incident across services?
• Provision a generic resource that would exist outside of a service?
• Request escalated access to logging across services in order to troubleshoot an issue?

You can now create global actions, to unblock operational tasks that aren’t service-oriented. 

Team assignment

Last but not least, you can now choose to make an Action available to one or more teams, in addition to Admins and the team who owns the service. If a few extra folks need permissions, just toggle their access on. 

Hit the ground running

Ready to give templated Actions a go? Log into your account and navigate to Self-service, or read our docs to set things up. Not an OpsLevel user yet? Sign up for a free trial to see how our IDP can free up your teams, and budget, for higher impact work.