Operations | Monitoring | ITSM | DevOps | Cloud

Being able to visualize the logs from your infrastructure is crucial - both for identifying potential issues and identifying opportunities for improving performance and utilization. However, when it comes to SCOM and Azure, monitoring can be a bit confusing. That is why, we at SquaredUp, have made it our mission to help you make sense of all the data being collected with beautiful visualizations and dashboards that can be shared with the rest of your organization and displayed on wallboard monitors.

It’s one thing to build a Kubernetes log management strategy that only needs to support Kubernetes. But most organizations don’t have that luxury. They have log management practices already in place for other types of platforms or infrastructure, and they need to extend them to support Kubernetes. How can you do that in an efficient way? Keep reading for tips on integrating Kubernetes logging data into your existing log management workflow without rebuilding from the ground up.

The lines Between IT and OT are blurring. With IT and Operational Technology (OT) systems converging, ensuring the security of devices, applications, physical locations and networks has never been more difficult or more important. There is a growing recognition by security professionals that they have a readiness and visibility problem in plain sight.

Kubernetes (or “K8s”) is an open-source container orchestration tool developed by Google. In this tutorial, we will be leveraging the power of Kubernetes to look at how we can overcome some of the operational challenges of working with the Elastic Stack.

We are pleased to announce the general availability of Elastic 7.9. This release brings a broad set of new capabilities to our Elastic Enterprise Search, Observability, and Security solutions, which are built on the Elastic Stack — Elasticsearch, Kibana, Logstash, and Beats.

I have recently been heads-down working on a large Splunk Cloud PoV (20+ TB / day), and the customer asked if Splunk supported their forwarding technology called Vector. I had never heard of Vector, so I took a note to do further research. I couldn’t find anyone else at Splunk who had seen this technology before, so I embarked on a little research project. What I discovered surprised me—Vector is actually fairly powerful, and cool!

One question I get asked frequently is “how can I get deeper insight and audit correlation searches running inside my environment?” The first step in understanding our correlation searches, is creating a baseline of what is expected and identify what is currently enabled and running today. Content Management inside Splunk Enterprise Security is a quick way to filter on what is enabled (and it’s built into the UI and works out of the box).

The stats overview page that we launched in June was very well received. We have followed up on this and developed a similar idea for downtime logs. This went live on Friday and shows downtime records for all your monitors in one place.