Operations | Monitoring | ITSM | DevOps | Cloud

In our world of distributed systems, state changes to your infrastructure often take some time to propagate. With a few exceptions (for example, feature flags), single point in time changes are rare. Deploys, outages, database migrations, failovers, stress tests; none of these things are instantaneous – all have some duration during which the system is changing.

Getting the right information at the right time can be a difficult task in large corporate IT infrastructures. Whether you are dealing with a security issue or an operational outage, the right data is key to prevent further breakdowns. With central log management, security analysts or IT operators have a single place to access server log data. But what happens if the one log file that is urgently needed is not collected by the system?

The AWS marketplace gives users access to a large variety of SaaS and API products that can be easily found, subscribed to and used. One of the biggest advantages for users is the ability to benefit from an easier procurement and payment process — users can use their existing paying terms with AWS, and unify billing across all the AWS services they are consuming, including those offered in the marketplace. Logz.io is now available on the AWS SaaS Marketplace.

Earlier this year, we showed you how to monitor Amazon Web Services Elastic Load Balancer (AWS ELB) with Cloudwatch. This piece is a follow up to that, and will focus on Classic Load Balancers.

This week’s roundup highlights videos from Monitorama, making your own Grafana Plugins, NetApp’s fully open source monitoring stack and more.