If you are a developer, a systems administrator, you work in the information technology sector or you are simply a technology enthusiast who has ever deployed some type of application, surely you will have faced the same problem we all ran into. If you are thinking of dependencies, bingo!
A couple of weeks ago I had the great pleasure of hosting CJ Silverio, Principal Engineer, and Ben Gardella, Manger of Infrastructure from Eaze for a clue- and cackling-filled webcast interview.
Tools. As engineers we all love great tools that help our teams work productively, resolve problems faster, be better. But tools can tend to grow in number, require additional maintenance, and most importantly, create silos. Each team has certain responsibilities and is constantly searching for tools that can address specific requirements in the best possible way.
Observability without AIOps is just noise.
In recent months, the major cloud and tech players have been unfurling their latest products and strategies to win enterprise dollars. One trend that’s catching fire is hybrid infrastructure management: the need to support a mix of on-premises, private cloud, and public cloud resources.
Any system connected to the Internet is vulnerable to malicious attacks and breaches. If it’s online, there’s someone out there trying to break into it and do something bad with it (usually stealing data). Plain and simple. To protect your most valuable assets, you need bulletproof security measures, a skilled SecOps team, robust investigation tools, and reliable prevention/mitigation strategies.
Cybersecurity is a hot topic. With high profile breaches making headlines on almost a monthly basis, combined with a far more restrictive regulatory environment, the need to responsibly protect your customers’ data has never been felt more keenly. It is estimated that a business is subjected to a ransomware attack every 14 seconds, predicted to drop to eleven seconds by 2021.
Before the need for log correlation, there was a time not so long ago when reading software application logs was simple. Your application would output log files in sequential order, and you’d read through them. In the event of a bug, software outage, or security incident, you could easily parse what happened and when. It was a tedious process, but it was simple.
Systemd is an initialization program that manages processes on Linux systems. It was designed to improve the performance of its predecessors by creating a dependency tree of system components, initializing them only when needed, and using as much parallelization as possible. With systemd becoming ubiquitous in Linux distributions, it’s crucial that you monitor the health and performance of both systemd and the components that it manages.
