LogDNA integrates with your PagerDuty instance to help trigger incidents based on log data coming in from your ingestion sources. This allows your teams to quickly understand when there are issues with your application, and where in the logs you can investigate to understand root cause. To help further accelerate your team’s ability to understand the state of your applications, we are introducing the ability to automatically resolve those PagerDuty Incidents directly from LogDNA.

Developers of any skill set find it frustrating when we don’t have access to the information we need. We want easy and complete access to application logs so that we can troubleshoot application problems. Quickly resolving issues requires a complete picture of what’s going on. Using the wrong tools limits our ability to determine what’s wrong, slowing the repair process.

Generating and collecting logs is one thing. Generating and collecting actionable logs can be quite another. That's a problem because logs that are not actionable – meaning they can be easily used to derive valuable insights or resolve issues – are not very valuable. If you don't generate actionable logs, you might as well not log at all. Fortunately, ensuring that you generate useful logs is not tricky. Keep reading for seven tips on making your logs actionable and valuable.

Developers must have access to the information that they need. Accessing this information, however, can be time-consuming. With the wrong tools or workflow, it’s frustrating and challenging to filter logs by source. Tags are an easy solution from LogDNA that helps developers get a more granular view of what’s going on in our services.

I’m Tim, a Product Design Manager at LogDNA and a massive coffee and magic enthusiast. My team is responsible for creating a beautiful and easy-to-navigate user interface so that you can easily access, and gain value from, your logs. We’ve been working on making our product more accessible and are about to roll out some subtle changes.