In order to answer this question, it is best to first explain what is IBM MQ and the benefits that it can bring to a business. IBM MQ (Messaging and Queuing) is a messaging system that enables applications running on different computers to communicate quickly with each other in real-time. This is achieved by exchanging messages using queues, and processed as and when computing resources and internet bandwidth allow. IBM MQ has been designed to provide high availability and reliability and can be used in a variety of different environments, including cloud computing.
This is Part 2 of a two-part series on Blameless Postmortems. The previous article went into why blameless postmortems are so effective; this second part goes into detail on how to build your own postmortem process and kick it into overdrive. Read Part 1 here. So you've read our first installment and recognized the value of the blameless postmortem for efficiency, culture, and output. Now you're ready to get off the blame train and kickstart a blameless postmortem process of your own. Where to begin?
Changes in the way organizations consume technology are reflected in the growth of the software-as-a-service (SaaS) market.
As we previously discussed in the Automating Your Cloud Security Posture Management (CSPM) Response blog post, CSPM is a vital component in any environment leveraging cloud services. Whether you are using a single cloud or are in a multi-cloud scenario, the complexity of these cloud platforms is constantly expanding. Staying on top of new changes in policies and functionality to ensure that you are maintaining a secure environment is daunting - and almost impossible to do without automation. No one has the resources to spend on maintaining a large team of cloud specialists who just audit everything that is in use.
We are all moving towards a digital workplace - or a hybrid work scenario. Whatever be the case, you can expect end-users to call and complain about a poor WiFi experience. That's because network monitoring needs to be done from their standpoint, not from the enterprise end. And without the correct WiFi observability data, it's challenging to narrow down the root cause of the problem affecting remote employees. And those problems - poor WiFi performance leading to poor digital experience - can be pervasive and persistent.
Prometheus has emerged as the de-facto open source standard for monitoring Kubernetes implementations. In this tutorial, Kristijan Mitevski shows how infrastructure monitoring can be done using kube-prometheus operator. The blog also covers how the Prometheus Alertmanager cluster can be used to route alerts to Slack using webhooks. In this tutorial by Squadcast, you will learn how to install and configure infrastructure monitoring for your Kubernetes cluster using the kube-prometheus operator, displaying metrics with Grafana, and configuring alerting with Alertmanager.