Operations | Monitoring | ITSM | DevOps | Cloud

Speedily minimizing the negative impact of an information security incident is a fundamental element of information security management. The risks — loss of credibility in the eyes of users and other stakeholders, loss of business revenue and critical data, potential regulatory penalties — can significantly jeopardize your organization’s mission and objectives.

Everyone needs observability. If you have a service that users rely on, you need to know if it’s working for your users. Heartbeat monitoring (Also called Synthetic Monitoring) should be a way to truly know how well our site is performing for users.

This blog explores a possible approach to collecting and formatting OpenShift Container Platform logs and audit logs with Red Hat OpenShift Logging Operator. We recommend using Elastic® Agent for the best possible experience! We will also show how to format the logs to Elastic Common Schema (ECS) for the best experience viewing, searching, and visualizing your logs. All examples in this blog are based on OpenShift 4.14.

How much of the data you collect is actually getting analyzed? Most organizations are focused on trying not to drown in the seas of data generated daily. A small subset gets analyzed, but the rest usually gets dumped into a bucket or blob storage. “Oh, we’ll get back to it,” thinks every well-intentioned analyst as they watch data streams get sent away, never to be seen again.

With a limitless load of questions on IT automation and the industry’s biggest trends, Resolve’s “Ask Me Anything (AMA)” session went about tackling them in an all-new way. We threw out the preparation, we threw out the scripts, and we asked our community to submit the questions that matter most to them and their organizations. Part of our leadership team took the hot seat and provided answers in real time, sans dress rehearsal.