The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
It’s common sense. When a logstorm hits, you don’t want to be left scrambling to find the one engineer from each team in your organization that actually understands the logging system – then spending even more time mapping the logging format of each team with the formats of every other team, all before you can begin to respond to the incident at hand. It’s a model that simply won’t scale.
StatusGator status pages are a unique way to consolidate the status of all of your vendors on a single page. Reduce support ticket volume by publishing your status page to your team or users. Now you can publish a message to the top of your status page for even more effective communication. Use this space for maintenance notifications, highlighting critical outages, or explaining your page to your users.
StatusGator is a status page aggregator: We bring together the status of all of your vendors into a single status page you can share with your team. Now, you can override the status of any service on your page to reflect exactly what you want it to. There are two opposite use cases for this feature: When a service is experiencing an outage and it’s not reflected on their status page. Or when an outage posted on their page is not affecting you and your team.
Industry analysts do primary research and two of the best, IDC and EMA (Enterprise Management Associates), have recently published some great insights for enterprises in 3 areas.
This is Part 1 of a two-part series on Blameless Postmortems. Today, we'll discuss why blameless postmortems are so important and their implications for your team; the second part will go into detail on how to set them up as a process and make them successful. Somebody wise may have once told you that how we handle adversity shows our character. Being able to acknowledge and admit mistakes is the first step towards learning - it's a key part of success both in personal relationships and in large companies.
Operational resilience remains the top priority for those in financial services. From the U.S. Federal Reserve's study into "Sound Practices to Strengthen Operational Resilience" and "Principles of Operational Resilience" from the Basel Committee to the Bank of England's upcoming rule changes for financial organizations in the UK, the intent is to create financial services institutions that are geared towards managing digital disruption. The goal is that financial service businesses can continue providing mission-critical services in the event of disruptions such as IT glitches, outages, and cyber-attacks.
Together with you, our fabulous community, Netdata is changing the way the world thinks of high fidelity monitoring – and we are gaining momentum. Our chief troublemaker and CEO, Costa Tsaousis, is the pioneer and architect of this revolution that’s brewing in the monitoring and troubleshooting space. Watch him explain the Netdata way of troubleshooting.
On March 30th, 2022, rumors began to swirl around a GitHub commit from a researcher containing proof of concept (POC) exploit code. The exploit targeted a zero-day in the Spring Core module of the Spring Framework, and was quickly confirmed against specific versions of Spring Core with JDK 9 and above. Anything running Tomcat is most at risk given the POC was based on Tomcat apps. This threat posture will evolve over time as new vectors and payloads are discovered and distributed.
