Operations | Monitoring | ITSM | DevOps | Cloud

When your IT systems are nearing capacity, you need to make decisions to expand provision, and many of those decisions will revolve around the choices you make to scale up vs scale out. For many the decision is intrinsically linked to their choice of platform and whether they are looking at cloud based, hybrid infrastructure or on-premises led strategies.

As a developer working with Linux systems, containers, or Kubernetes, it's crucial to understand process termination signals, particularly SIGKILL and SIGTERM. This comprehensive guide will explore these signals, their differences, and their implications in various environments. We'll delve into best practices, common scenarios, and advanced considerations to help you manage process termination effectively in your applications.

We are excited to share that our Early Warning Signals feature, previously in beta, is now fully available to all StatusGator users on all plans. This long-awaited feature ensures you never miss a beat and keeps you informed of outages before a provider publicly acknowledges them on their status page. Since its beta launch, this feature has successfully detected multiple service outages before they were officially acknowledged by each provider.

In today’s complex cloud-native environments, observability is key to maintaining performance, reliability, and scalability. However, different teams often need to focus on different aspects of the system. Developers might be more interested in error rates and response times, while operations teams must monitor system health and resource utilization. Lumigo now supports multiple dashboards, so you can provide each team with the information they need precisely how they need it.

In the first part of this series, we saw that even if you just use AppSignal’s default application monitoring, you can get a lot of information about how your Phoenix application is running. Even so, there are many ways in which a Phoenix application may exhibit performance issues, such as slow database queries, poorly engineered LiveView components, views that are too heavy, or non-optimized assets.

In recent years, we’ve significantly advanced how we think about and use topology within AIOps and Observability solutions from Broadcom, while solidly building on our innovative domain tools. We’re eager to share these innovations, advancements, and benefits for IT operations. In this blog post, we level-set on the topic of topology, clarify several important concepts, and discuss the decisive role topology plays in delivering powerful capabilities for AIOps and Observability from Broadcom.

The Java Virtual Machine (JVM) is an important part of the Java programming language, allowing applications to run on any device with the JVM, regardless of the hardware and operating system. It interprets Java bytecode and manages memory, garbage collection, and performance optimization to ensure smooth execution and scalability. Effective JVM monitoring is critical for performance and stability. This is where OpenTelemetry comes into play.