LogicMonitor is an agentless monitoring solution. What we really mean by “agentless” is that we don’t require an agent on every monitored server (physical or virtual). One LogicMonitor Collector - a lightweight application that takes just seconds to install - can monitor hundreds or even thousands of devices, including servers, virtual machines, network switches, storage systems, cloud resources, containers, and more.

Google has effectively made the discipline of site reliability engineering (SRE) a DevOps best practice by publishing two decades’ worth of lessons in keeping alive the most scalable apps on the planet. As more organizations make the shift (or “transformation,” as it were) to becoming IT organizations, the demand for reliability increases substantially for customer-facing services.

Access Gartner’s exclusive research report to find out how AIOps—when used together with APM—plays a pivotal role in driving better business outcomes.

Once a year, PagerDuty’s SREs get together for a three-day, in-person offsite. With the team spread across three time zones in the U.S. and Canada, encompassing two offices and three remote members, face time is rare and valuable. We use our offsites for thoughtful discussions on team health, long-term project roadmap planning, refining and updating our team’s mission, and to simply spend time together as a team.

We read with interest a recent article from CloudBees published in The New Stack: How Culture Will Make or Break Cloud Native DevOps and have seen some highly differing views on where the adoption of DevOps is. The Cloudbees article starts by saying that “Software delivery cycles are becoming faster thanks to DevOps-backed continuous integration/continuous delivery (CI/CD) as production pipelines are increasingly ported to scale with microservices on cloud-native environments.”

Apache ActiveMQ is message-oriented middleware (MOM), a category of software that sends messages between applications. Using standards-based, asynchronous communication, ActiveMQ allows loose coupling of the elements in an IT environment, which is often foundational to enterprise messaging and distributed applications.

In Part 1 of this series, we looked at how ActiveMQ works, and the key metrics you can monitor to ensure proper performance of your messaging infrastructure. In this post, we’ll show you some of the tools that you can use to collect ActiveMQ metrics. This includes tools that ship with ActiveMQ, and some other tools that make use of Java Management Extensions (JMX) to monitor ActiveMQ brokers and destinations.

As you operate and scale ActiveMQ, comprehensive monitoring will enable you to rapidly identify any bottlenecks and maintain the flow of data through your applications. Earlier in this series, we introduced some key ActiveMQ metrics to watch, and looked at some tools you can use to monitor ActiveMQ.