Today, we’re launching a major upgrade that will improve the way yourteam manages application errors, with more error states, error assignments,severity labels and a “my incidents” overview. Your team’s communication around incidents will improve significantly.You’ll know exactly how severe an error is, who’s responsible, and howyou handled this error historically.
Hi! 👋 Colin, the creator of StatusGator, here with big news. TL;DR We just rolled out a massive update (with 7+ new features) and redesigned the entire website. One thing we often heard from people seeing StatusGator for the first time is that it had a rather outdated look. Landing on our website, many people got the impression StatusGator was created 10 years ago and forgotten about.
Serverless event-driven architectures are composed of AWS Lambda functions that regularly interact with databases, APIs, message queues, and other resources to facilitate complex workflows and functionalities. It is therefore crucial to monitor every component of your stack to ensure your applications perform optimally at scale. But traditionally, telemetry data for AWS resources has lived in silos, making it difficult to quickly get the context you need to debug issues.
18 months later, organizations around the globe are slowly but surely starting to welcome their employees back to the office – or at least thinking about it. But this is not a “back to normal” kind of thing. Most will recognize that something’s different this time around. Firstly, there is no clear one-size-fits-all return-to-office strategy.
The Java Persistence API (JPA) is used in most Java applications to interact with a relational database. One of its most popular implementations is the Hibernate ORM, because it uses object-relational mapping to abstract database interactions and makes implementing simple CRUD operations very simple. But this abstraction also has its downsides. Hibernate uses a lot of internal optimizations and hides all database interactions behind its API.
The OpsRamp Monitor is back, capturing the latest buzz around what’s trending in the world of ITOps and related technology. It’s been a busy month!
Is GitOps changing observability as we know it? GitOps has been the buzz word in the DevOps space for several years. GitOps, to those that are not familiar, is an operational methodology for DevOps that leverages a continuous deployment approach with Git as the single source of ‘truth’ for declarative control over both infrastructure and applications.
Excellent new features have arrived in Loki v2.3.0. Bug fixes too. And performance increases on top of that. While we have been quiet, we have been very busy!
During the execution of a PHP application, it is possible for it to generate a wide range of warnings and errors. For developers seeking to troubleshoot a misbehaving application, being able to observe these errors is critical. Developers, on the other hand, frequently encounter difficulties when attempting to display errors from their PHP applications. Instead, their applications simply stop working.
In Part 1 of this series, we looked at the key EFS metrics you should monitor, and in Part 2 we showed you how you can use tools from AWS and Linux to collect and alert on EFS metrics and logs. Monitoring EFS in isolation, however, can lead to visibility gaps as you try to understand the full context of your application’s health and performance.
