Operations | Monitoring | ITSM | DevOps | Cloud

Coroot is excited to feature an editorial from the open source observability database GreptimeDB as an Open Source Spotlight. We hope to improve the work of our global community of SREs and DevOps professionals by sharing exciting projects like GreptimeDB, which make innovation accessible for everyone through the freedom of open source.

Freshdesk is a popular incident management system known for its ease of use, robust ticketing system, and powerful automation capabilities as part of the Freshworks suite of tools. While Freshdesk comes with native reporting and dashboards, they can be limited in terms of customization and data correlation across different sources. Additionally, building complex visualizations in Freshdesk often requires more advanced knowledge of their reporting tools. This is where SquaredUp comes in!

“We want developers to break things – just not for the customers. If all our tests are green, I get nervous that we’re not testing deep enough.” Naga Santhosh Reddy Vootukuri, Principal Software Eng. Manager, Microsoft Azure SQL Naga Santhosh, Sunny to most, leads a team that ships changes to Azure SQL databases worldwide. Those deployments must be fast, frequent, and invisible to customers. That kind of reliability doesn’t come from playing it safe during development.

“You fixed a bug in QA — great! But did that fix go into version control and get tested and deployed everywhere? If not, you just created drift, and more problems down the line.” Peter Kruis, Microsoft SQL Engineer at Monin Fixing a bug in the environment where it appears feels like progress, but without a proper process, it creates fragility everywhere else.

Finding yourself migrating and weighing the options when it comes to moving your entire Apache Kafka setup to a new cloud? This blog will point you to a solution to efficiently migrate your workloads to an Aiven for Apache Kafka cluster circumventing the headache that usually comes with cloud migration.

Unity has a reputation for handing out surprises: the play-mode freeze just after a hot-reload, the sudden sea of pink materials, or the stack trace that politely reminds you your transform was null all along. Rather than letting those moments derail the rest of your sprint, this post rounds up four of the most common runtime offenders, and shows you exactly how to trigger, spot, and fix each one.

The observability market is changing rapidly. The days of simply collecting logs, metrics, and traces are giving way to something bigger: delivering actionable intelligence that actually connects IT operations with business goals. Organizations don’t just want to know what’s happening anymore; they need to understand why it’s happening, what actions to take, and whether their systems can respond independently.

We’ve all had that “uh-oh” moment. You press Enter and your blood runs cold, as you realize you just deleted something critical. For engineering teams, this type of disaster takes many forms. For example, maybe you used a DELETE statement without a WHERE clause to delete a row in a database, and accidentally deleted all of them instead. To protect you from the accidental deletion of critical resources in Grafana Cloud, we’re introducing a feature called deletion protection.

Mobile applications offer increased flexibility to both users and developers. Users can access content on a wide range of devices, operating systems, and network types, while developers can leverage touch screens and orientation-based layouts to create more responsive features. However, all of these factors create new testing challenges. To ensure a good user experience (UX), developers have to test their apps across many device models and platforms, which can become costly and time-consuming.

Asynchronous communication patterns are commonly used in distributed systems, especially in those that rely on events or messages to coordinate activity. Rather than responding to direct API calls like in a traditional request-response architecture, services in an asynchronous system produce, route, or consume events and messages independently.