If you’re a software developer, then you understand how vital application logging is in software development and a critical part of logging is something called logging levels. Log entries generally contain essential information—such as a timestamp, a message, and sometimes additional stuff like an exception’s stack trace. Those pieces of information are useful because they allow someone reading the log entry to understand how the application behaved in production.
The brand new Monitive platform is almost ready to be seen by the world, but just like any software development project, minor issues always surface that tend to push a release date back further and further. There’s always copy to be adjusted, links to be added, an icon that would improve clarity. Maybe a box is missing or the color of a button needs to change.
For our tech-minded readers, we strongly recommend you read the suggested articles in the US-CERT notification for detailed examples of how the hijacking takes place, for the rest of you, we’ve put together a summary of how the multifaceted attacks work.
A project post mortem is a lethal-sounding term that seeks to answer the question: did this project work? Was it worth the investment and the time, and if it wasn’t can you learn from it? As the term implies, the project must be “no more” or “ceased to be” or “bereft of life.” Creating this document requires a time investment, and it’s tempting to just move onto the next project.
In 2018, we launched many improvements to the Raygun Platform, including the biggest ever addition to Raygun: Application Performance Monitoring (APM). For this article, we wanted to surface our favorite releases from 2018, just in case you missed them.
Opsgenie Actions enable you to automate manual, repetitive tasks so that your resources are freed up to concentrate on higher-value work. This blog post is the second in a series of use cases in which we discuss how Opsgenie works with various third-party automation platforms to automate these traditionally manual tasks—right from the Opsgenie console or mobile app— to reduce interruptions for your on-call responders, and ultimately help your bottom line.
Kafka and the ELK Stack — usually these two are part of the same architectural solution, Kafka acting as a buffer in front of Logstash to ensure resiliency. This article explores a different combination — using the ELK Stack to collect and analyze Kafka logs. As explained in a previous post, Kafka plays a key role in our architecture. As such, we’ve constructed a monitoring system to ensure data is flowing through the pipelines as expected.
We get it — errors suck. And you don’t want to spend too much of your time fixing them, dealing with them, investigating them, etc. In our Workflow blog post series, we’ll help you optimize your, well, workflow, from crash to resolution. To quote “the second-most frequently quoted writer in The Oxford Dictionary of Quotations after Shakespeare,” Alexander Pope, “to err is human.” There will always be errors, even in code written by the best developers.
