Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes (K8s) is the most popular container orchestration platform today. But it can also be quite complex. To overcome this management challenge, you can deploy your Kubernetes containers using the Google Kubernetes Engine, which is a fully managed service. Yet, to get the most from GKE, you still need to follow best practices. The following tips and best practices for monitoring GKE clusters will help you get started.

When it comes to network management, there are two challenges that are ever-present; ensuring optimal network performance and maintaining uninterrupted network connectivity. Network admins are the unsung heroes, diligently managing the digital highways that connect the modern world. To maintain the delicate balance between seamless user experience and network reliability, two crucial practices come to the forefront: Network Load Testing and Load Balancing.

We've made major improvements to maintenance window notifications with flexible options that adapt to your communication strategy. Now you have three notification options for every maintenance window: You'll also see how many subscribers will be notified with a detailed breakdown of subscriber counts by channel type (Email, Slack, Teams, etc.), giving you complete visibility into your communication reach before sending.

When using Percepio TraceRecorder, kernel objects like queues, semaphores and mutexes are named using their address by default. This can be a bit hard to follow for complex traces. However, it is quite easy to set more descriptive custom names for your RTOS kernel objects. This by calling the “SetName” functions (or macros) found in the TraceRecorder API, for example: The first argument is the pointer to the object (i.e. the object address).

After four years. Hundreds of meetings and conversations. Countless forms and paperwork submissions… …We’ve done it. SquaredUp is finally, officially B Corp certified We can now say that we are part of a unique global movement – and we couldn’t be more proud, excited, and motivated for our journey ahead.

In Kubernetes environments, cost is rarely just about spend. It’s about performance, node utilization, workload behavior, and how all of those align with your team’s operational goals. Komodor’s approach to cost optimization has an operational advantage due to its deep visibility into your entire Kubernetes estate. Imagine the potential for cost optimization when you have complete visibility into every aspect of your Kubernetes operations.

As infrastructure grows in complexity, the demand for intelligent, autonomous operations is no longer optional. AIOps tools help IT organizations sift through data noise and detect what matters. But insights alone don’t close the loop. Without automation, even the most accurate prediction still relies on humans to triage, decide, and resolve. This is the gap intelligent automation fills.

We’ve just rolled out a helpful new setting to give you tighter control over how uptime is measured: Redirect URL Validation.

The era of scattered monitoring tools and fragmented operational visibility is over. As hybrid and multi-cloud environments have become the norm rather than the exception, traditional observability approaches—siloed metrics, isolated logs, and disconnected traces—can no longer keep pace with the complexity of modern IT infrastructure. Organizations today need more than just monitoring.

Modern applications demand strong observability to ensure performance, reliability, and quick troubleshooting. Two powerful open-source tools, OpenTelemetry and Fluent Bit play key roles in this space. While OpenTelemetry offers a full-stack framework for collecting metrics, logs, and traces, Fluent Bit specializes in fast, lightweight log forwarding.