Operations | Monitoring | ITSM | DevOps | Cloud

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.

When it comes to business, data is everything. Whether it’s sales, supply, marketing, or your I.T. systems, every day is a constant stream of decisions to be made. To make the right decisions, you need enough knowledge. To have enough knowledge, you need the right data. What’s the best way to collect all this data? In the information age, there’s so much data out there, all the time.

Among developers, alerts have a bad rep. But outside the coding environment, alerts can signify positive developments. For example, a microwave just alerted me that my burrito is ready to eat. Sentry’s new Metric Alerts is the microwave to the frozen burrito that is your code.

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.

When making purchasing decisions, organizations must consider a vendor’s product pricing, promised benefits and level of customer service. Thorough vendor evaluation tends to result in successful investments, allowing organizations to reap the benefits of their newly acquired products without buyer’s remorse. Unfortunately, some buyers dismiss the importance of personal information security and how the vendor promises to protect user data.

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.

June was the month where many of us stretched our legs, glad to be out of quarantine — and then immediately went back inside due to fears of a second wave. “One step forward, one step back,” offers an adequate summary of life in a pandemic. It’s also a sentiment that applies to the ongoing challenge in mitigating glitches and outages.

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.