Logging with Context
Loggly customers are a vocal bunch – and I love it! My job gets much easier when I have so many chances to interact with customers with face to face meetings, emails, survey responses, and even tweets. All these touchpoints help guide the Loggly team as we work to make the world’s most popular cloud-based log management service even better. Here are some of the latest changes that you asked for, we listened to, and we delivered on.
As of this week, we have deployed a new email template for our alerts. With this template, every alert you receive will include even more insight into the condition that triggered it:
You also have the option to receive a sample of some of the events that triggered the alert. These are included in-line as part of the alert notification, so you can get a sense of what specific events triggered the alert even before you log into the Loggly console.
Armed with this information, you’ll be able to react smarter and bring the right resources to each potential problem.
One of our customer’s favorites features (and also a big competitive differentiator for us) is how Loggly automatically parses a wide range of log types. Automated parsing speeds up your searches and also gives you a better way to navigate and explore your data without depending on complex searches.
Whenever you expand any specific log event (to see it in ‘parsed mode’) you will now see two additional pieces of information::
With so much diversity in the applications, platforms, and devices customers want to send us data from, it’s always a priority for us to keep making our source setup as streamlined as possible. The most recent updates include:
We’re always looking for more input. Please do reach out at pm+feedback@loggly.com or DM @loggly on Twitter.
Hector Angulo
Share Your Thoughts