Operations | Monitoring | ITSM | DevOps | Cloud

Not too long ago, you would have needed development experience to oversee the delivery of scalable and reliable software. But with the rise of low-code and no-code tools, that requirement is now obsolete. What used to be hours of coding has turned into a few minutes of dragging and dropping.

A comprehensive definition of SREs and Site Reliability Engineering, including what SREs do and what makes SREs different from other roles.

In the SIGNL4 web portal you can manually export historic alert reports as.csv files. In some cases it might be useful to export alert data programmatically. For example you can forward all alerts including specific parameters to InfluxDB and show the alert history in Grafana to recognize peaks, trends and abnormalities over time. You can even use AIOps to recognize certain trends automatically. By using the SIGNL4 REST API it is possible to export alert data automatically.

GigaOm’s latest Radar for AIOps solutions has just been released and it makes for compelling reading for anyone trying to maximize organizational performance in our digital world. Particularly if you’re down with DevOps.

What do IT security, production monitoring and technical field service have in common? In all scenarios there is need to notify the right people immediately in the event of technical malfunctions, urgent maintenance requests or emergencies to resolve the incident quickly and efficiently.

A few days ago I received an inquiry about a scripting problem from one of our longtime partners, to be exact our DCP Marc Handel from IT unlimited AG. In the exchange with Marc I realized that his idea to use the Enterprise Alert Scripting Host, the Windows Task Scheduler and CheckMK to realize a roundtrip monitoring could be interesting for the whole community. Especially for all our CheckMK customers.

One of the tools we use internally at Squadcast for SLO and Error Budget tracking is now open-source. In keeping up with the SRE ideology of automating as many ops tasks as possible, we built this SLO Tracker. We made this open-source so that the SRE community can also use it too. Looking forward to get your feedback, suggestions and patches :)

Although conversation about observability often ignores SREs, SREs have a central role to play in observability success.

Site reliability engineers (SREs) are involved in scaling systems and making them reliable and efficient for organizations. But SREs often fail to build system resiliency when they do not have the right tools at their disposal. In this post, we’ll uncover five leading tools that SREs can use to drive the reliability and stability of computing systems. It also examines how SREs can use the tools to improve operations tasks and infrastructure processes.

Coming to this article you may be in two learning mindsets. You’re curious about building a service catalog and want to know some of the basics. Or you’re curious about FireHydrant’s philosophy around this growing space.