The typical DevOps on-call engineer is responding to alerts, triaging based on service impact, troubleshooting high priority incidents, and taking action to remediate issues. Automation tools like AWS Systems Manager can be a big help in reducing some of the more repetitive work and allowing engineers to focus on the most important tasks.
It’s an exciting time here at Opsgenie. We recently joined the Atlassian family, updated our logo, released new pricing, and now we’re headed to AWS re:Invent 2018! So much has changed since last year’s event and we can’t wait to talk about it in person.
It's official and you're the first to know – Opsgenie is the newest member of the Atlassian family! Our commitment to you has always been that we'll provide the world's best alerting and incident management solution, coupled with outstanding customer service. That doesn't change. But we're excited to bring you even more – a fresh new logo, new plans, and much lower pricing.
Language used across the high technology ecosystem is dynamic to say the least. Nowhere else can you find a mixture of technical jargon seamlessly intertwined with references from science fiction, mythology, pop-culture, literature, and more. While this makes conversations heard across technical environments colorful and engaging, it also makes communications allegorical and metaphorical— opening them to variable interpretation.
Emails are one of the most popular notification methods of Opsgenie when reaching out to your users. Now, you can create Email Templates which represent your company’s style and streamline communication processes! Email Templates are available for the emails sent out for Mass Notifications and Stakeholder Notifications, and you can customize of the content of the emails depending on your needs.
Announcing the following integrations: BMC Remedy OnDemand
The transition to Agile development and continuous deployment has resulted in the DevOps movement to break down organizational walls. While there are many benefits to this approach, some best practices of traditional IT Service Management (ITSM) have been lost in the transition. Which ITSM processes and controls are still relevant and how can you adapt them to the new agile world?
