Operations | Monitoring | ITSM | DevOps | Cloud

Our Golang Stack in 2025

In our Go projects, we rely on a consistent and battle-tested stack of libraries that help us build reliable, maintainable, and scalable systems. We started using Go in our stack many years ago (before Go v1) and therefore many of our choices have changed over the years. Here in this post, I wanted to share some of the libraries we use regularly to power our Go apps.

How to Use an SLA Uptime Calculator to Understand Service Availability

TL;DR A Service Level Agreement (SLA) defines the required uptime for a service. An SLA uptime calculator helps convert uptime percentages into actual allowed downtime across different timeframes. This guide explains how these calculators work, why uptime matters, and how to monitor performance to meet SLA targets.

OpenTelemetry for Go: measuring the overhead

Everything comes at a cost — and observability is no exception. When we add metrics, logging, or distributed tracing to our applications, it helps us understand what’s going on with performance and key UX metrics like success rate and latency. But what’s the cost? I’m not talking about the price of observability tools here, I mean the instrumentation overhead.

Navigating the Growing Challenge of CVEs in Cybersecurity #shorts

Navigating the Growing Challenge of CVEs in Cybersecurity Assets and known CVEs increase annually, complicating the work of security teams. Accumulating old CVEs and overwhelming data from vulnerability scans make compliance difficult. Security teams produce detailed reports for IT teams to address. While regular OS updates can fix many CVEs, delays create backlogs. Improved reporting in the Linux kernel enhances visibility but adds to the number of CVEs, highlighting the need to manage data effectively to tackle vulnerabilities.

Everything You Need to Know About Event Logs

Your code passes locally, CI is green, and the deploy goes through. Then production throws a 500, and the trace isn’t helpful. And here, event logs help. A log captures timestamped records of what the app did HTTP requests, DB queries, cache misses, retries, failures. These entries give you enough context to debug without reproducing the issue locally. Especially when dealing with distributed systems, logs are often the only consistent source of truth.

E4: Streamlining critical ITSM practices with no-code/low-code automations in ServiceDesk Plus Cloud

In the fourth episode, learn how to automate critical ITSM practices from end to end with no-code automations and low-code components. We will go over how to configure business rules, SLAs, and other essential automations that let you manipulate data within ServiceDesk Plus Cloud.

E4: Streamlining critical ITSM practices with no-code and low-code automations in ServiceDesk Plus

In the fourth episode, earn how to automate critical ITSM practices from end to end with no-code automations and low-code components. We will go over how to configure business rules, SLAs, and other essential automations that let you manipulate data within ServiceDesk Plus.