IT professionals are now adapting to a remote environment and learning to manage a distributed, homebound workforce. From a technical standpoint, the process of setting up a remote workforce is well-known. For this blog post let’s dive into one step of the process, which is arguably the most important, user experience monitoring.

Security Information Monitoring or Security Event Monitoring is part of Security Information Management. Yes, I acknowledge they are flashy names and that even experts have their differences about concept and scope. Here in Pandora FMS, flexibility is part of our name, so, hereby, I will abbreviate it as Security Monitoring. As you can see, it is short and manageable!

Here is an overview of the features & fixes we released over the last ~2 months.

Software development and delivery is an ever-changing landscape. Writing software was once an art form all its own, where you could write and deploy machine code with singleness of purpose and no concern for things like connecting to other computers. But as the world and the variety of systems that software supports became more complex, so did the ecosystem supporting software development.

In Part 1 of this blog series, we took a look at how we could use Elastic Stack machine learning to train a supervised classification model to detect malicious domains. In this second part, we will see how we can use the model we trained to enrich network data with classifications at ingest time. This will be useful for anyone who wants to detect potential DGA activity in their packetbeat data.

In today’s digital world, every transaction is logged to give businesses endless amounts of functional data, and there is near-universal agreement that data insights will be integral to the success of businesses in the future. There is undoubtedly a need for a more data literate workforce.

Monitoring requires a multi-faceted approach if DevOps teams want end-to-end visibility and deep insight into issues. This is especially true in the case of modern microservices applications, which are essentially collections of distributed services that talk to each other over a service mesh. With monolithic applications, requests can be tracked easily from the client to the server and back, but with modern applications, every request passes through numerous services before completion.

ROS, Ripple and reflections – In this month’s edition of The State of Robotics, we’ll tell you about the recently discovered Ripple vulnerability, the latest and greatest in robots reflecting nature, and a dash of news from the ROS universe.

In our series of blog posts based on Automated Containerization, here is another quick read on why Enterprises should invest in containerization of applications instead of Lift-and-Shift approach. Legacy applications can be slow and expensive to maintain. If you use the Lift-and-Shift approach to migrate applications to cloud is relatively inexpensive, but ongoing operating costs can be exactly the opposite. The contention is that applications perform and evolve relative to their environments.

Our July update brings new features to the email and webhook API’s. You can now close alerts in SIGNL4 when the issue was resolved in your backend system.