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.”
It’s time for change – my first insight from GartnerIO, 2018. During my flight to Vegas I remembered that this was probably my 15th visit to a conference in Vegas (but who can really count…after a few, it all starts to blur together). What I do remember though is that, in each of these conferences, there was one very shiny buzzword. The reason I remember this so well is because, while everyone agreed on what the buzzword was, there was no consensus on what that word meant!
You asked and we delivered; you and other customers requested a solution that would integrate alert management into Datto’s Autotask PSA capabilities. We at OnPage are excited to announce that this MSP solution is now a reality.
Today is the day: Sensu Go is now in General Availability (GA)! Sensu Go features human-centered design by making it easier to use Sensu; we went from operations having to do the heavy lifting to creating a user-centric, self-service, and highly scalable product.
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.
