The latest News and Information on DevOps, CI/CD, Automation and related technologies.
An incident can take many forms. It can look like a small issue that locks a few customers out of their accounts or a huge catastrophe that brings down your entire product for a full day. How you respond to the incident should vary based on the impact of the incident. And that’s where severity comes into play. Defined severity levels are crucial to any good incident management program.
We eat lots of our own dog food at MetricFire, monitoring our services with a dedicated cluster running the same software. This has worked out really well for us over the years: as our own customer, we quickly spot issues in our various ingestion, storage, and rendering services. It also drives the service status transparency our customers love. Our customers include large multinational coffee brewers, game companies, and other data science/SaaS companies.
Monitoring indoor air quality with Airthings and Netdata. Understanding and measuring common contaminants and pollutants reduces your risk of air quality health concerns.
Business organizations that want to save money and be competitive take into consideration the time costs associated with investments in new technologies. Will the efficiency gains translate to a rapid return on investment? Will users embrace the change and be more productive? Or will those investments be a hassle to employees and result in time-wasting workarounds and a fallback to inefficient, manual processes?
