Operations | Monitoring | ITSM | DevOps | Cloud

PagerDuty sat down with J. Paul Reed, a Senior Applied Resilience Engineer at Netflix, for an Ask Me Anything (AMA) to discuss best practices around postmortems. Reed is a prominent speaker and advocate of DevOps and operations complexity, and has over 15 years of experience in release engineering. His background in tech, along with his previous work at companies like Mozilla and VMware, give him a unique perspective into the inner workings of innovative organizations.

We are going through an incredibly difficult time of uncertainty, lockdowns, cutbacks, and even fear. Taking this time to optimize and rethink the way we do business is essential in ensuring we get back on track and return even stronger than before. Most of us have been working from home for months now and, in some cases, there is no end in sight. How are you and your operations holding up? Are you able to work, maintain, and control your infrastructure?

In our latest two-part series blog, Gigi Sayfan, author of “Mastering Kubernetes”, discusses managing complex infrastructure on AWS with an eye towards SLOs (service level objectives). Though there are many ways to discuss the management of infrastructure, in this two-part series, he covers SLOs for AWS, Observability on AWS, Quotas Limits, and Optimizing cost on AWS and in the second part, he uses the lens of Kubernetes to compare and contrast compute infrastructure on AWS with Kubernetes.

Our July update brings new features to the email and webhook API’s. You can now close alerts in SIGNL4 when the issue was resolved in your backend system.

We are delighted to announce our new PagerDuty integration for Salesforce Cloud. This integration empowers Customer Service, Engineering, and IT teams to proactively resolve customer issues in real time by improving communication and collaboration.

Here at FireHydrant we are always looking for ways to improve and simplify incident management, today we’re happy to announce a set of changes to the incident and retrospective pages to further simplify the incident command center. To make it easier to stay up to date on the status of your incident, we have made the incident timeline permanently viewable on your Incident Command Center. You can adjust the width of your timeline to ensure you can see the most important information at all times.

In an effort to make it even easier to open incidents, FireHydrant will now let you open an incident from Slack in a single click. When an alert is ingested into FireHydrant a message will post to a channel of your choosing to open an incident. When the incident is opened it will pull in all the data from the PagerDuty alert and configure your incident with that data. Now you can go from an alert firing in PagerDuty to an open FireHydrant incident with all of your automated process in under 5 seconds.

Communication is one of the hardest things to do well while responding to incidents. At FireHydrant, we’ve focused on helping people communicate well within their teams when responding to incidents, and also after the fact during post-incident reviews. But what about communicating with your customers? During an incident, your customers want to know that you’re aware of the problem and are working to mitigate or resolve it.

Flowmon has recently joined Fortinet’s Open Fabric Ecosystem by integrating with FortiGate and FortiSIEM. This cooperation brings automated system for threat detection and response, blocking security risks in their infancy, and giving time to administrators to carry out forensics.