Operations | Monitoring | ITSM | DevOps | Cloud

Believe it or not, we are in the middle of one of the biggest cloud repatriation movements of the past decade. More than ever, companies are rushing to find infrastructure solutions that better suit their needs. Over the past decade, hyperscalers have dominated the market, generating trust and, in some cases, overconfidence in software development. Drawn in by promises of reliability, ease of use, and ultimate flexibility, teams turned to providers like AWS, GCP, and Azure.

Ever wrapped up an incident, thought 'Phew, glad that’s over,' only to feel your stomach drop when you see the dreaded "Incident Debrief" on your calendar? We've all been there. Incident debriefs don't need to feel like sitting through your least favorite school subject. They can (and should!) actually be engaging and useful. At incident.io, we've found a simple, repeatable, and blameless framework.

Atlassian recently announced they’ll be shutting down Opsgenie, their popular on-call alerting tool. After June 4, 2025, no new Opsgenie accounts will be created, and by April 5, 2027, the service will shut down completely. Users don’t seem happy about it. If you’re currently using Opsgenie, this news is significant. A key part of your incident response process is disappearing, and Atlassian suggests moving to their other products, like Jira Service Management or Compass.

Colonial Pipeline was shut down for six days after finding itself at the center of a cybersecurity threat. During the May 2021 incident, States declared emergencies, gas prices soared to a six-year high, fuel shortages hit Southeast America, and panic buying almost threatened national fuel security. As per The New York Times report, the attack was traced to DarkSide, a Russian-speaking ransomware group that used a stolen VPN password to breach Colonial’s systems.

Logging in Node.js might not be the most exciting part of development, but it’s one of the most important. Whether you're troubleshooting bugs or keeping track of how your app is running, good logs make life easier. Let’s break down how to set up logging the right way.

Have you ever opened your Kubernetes dashboard and wondered why your app seems to slow down? As containers multiply rapidly, keeping track of CPU usage becomes a must. Let’s break it down by focusing on one key metric: container_cpu_usage_seconds_total.

Ever felt like you're missing crucial insights into your Java applications? The OpenTelemetry Java Agent changes that game completely. This comprehensive guide takes you beyond the basics, showing you not just how to implement it, but how to master it for maximum observability.

Businesses today rely on multiple cloud services to manage their operations. Whether it's hosted services like AWS, customer relationship tools like Salesforce, or marketing platforms like HubSpot, these services play a crucial role in day-to-day business functions. However, businesses can suffer significant disruptions when a third-party service experiences downtime. A single outage in a critical service can halt operations, causing frustration for both employees and customers.

We are thrilled to announce the public preview of our new feature: Static Data for PostgreSQL Database using Flyway. This feature is designed to enhance your database management experience by allowing you to manage static data alongside your schema seamlessly for versioning and deploying your database changes.

We’re excited to announce that users can opt-in/out of preview features that are under development directly in Flyway Desktop. There are currently three preview features that will be in the next major version of Flyway Desktop; a new connection dialog with options to provision databases, a full schema model view, and support for static data in PostgreSQL databases.