Operations | Monitoring | ITSM | DevOps | Cloud

Incident management is a practice that seeks to resolve business-impacting events in the most efficient manner possible. But not every problem that arises requires an incident response, and it’s crucial that teams know the difference between a problem and an incident. Responding to problems may be part of daily routines, or small ad hoc projects that don’t require more than one resource or a significant time commitment.

More often than not, as developers, when we get a report that a large customer is hitting 502 errors, there's a flurry of activity. What's wrong? Is something deeply broken? So you start digging through AWS logs to see what you can find, but it's hard to reproduce. Sometimes, there's no clear answer, and you move on without any resolution. What if I told you it doesn't have to be this way?

It’s been twenty years since the corporate scandals of Enron, WorldCom, and Tyco. The collapse of these giant corporations ruined the lives of the employees who tirelessly worked for leaders who let greed dictate their decision-making. Laws have been implemented since then to help reduce the risk of another Enron, but laws won’t stop all instances of poor leadership. Poor tone at the top increases vulnerabilities, employee non-compliance, and job dissatisfaction.

The new Sqlyze data source plugin (in beta) allows you to connect your Grafana instance to all your favorite SQL databases, many NoSQL databases, and many other non-SQL data sources — from document databases, to ERP systems, to even Slack. You don’t have to know the native query syntax for these data sources; you can just use SQL. The Sqlyze plugin uses ODBC at its core. Hundreds of ODBC drivers are available for various databases/data sources.

Everybody is used to dealing with the bugs on their smartphone and other technology devices In their homes that have been an issue for years. The fact that they may never be resolved is just one of those things that we’ve decided to accept. At Cribl, we approach this situation differently — we’re not okay with bugs of any size.

Without logs, or a good understanding of them, debugging an application or looking through an error stack trace can be challenging. Luckily, Flask logging can change the way you understand debugging and how you interact with logs produced by the application. The Flask logging module gives you a way to record errors over different severity levels. A default logging module is included in the Python standard library, and it provides both simple and advanced logging functions.