DEVOPSdigest

Loggly announced a new integration with GitHub.

Available with Loggly 3.0, a unified log analysis and monitoring solution designed for companies building modern software applications running in the cloud and serverless architectures, the GitHub integration delivers one-click access to source code from within the Loggly interface.

“GitHub has become an integral part of the DevOps toolchain in many enterprises and is used by millions of developers,” said Manoj Chaudhary, CTO at Loggly. “We’re excited to be the first log analysis company to integrate with GitHub. This integration is another way that Loggly 3.0 simplifies and accelerates the process of moving from error identification to resolution.”

"Loggly offers a powerful and effective way of connecting log analysis with source code,” said Jared Jones, Business Development Manager at GitHub. “The integration with GitHub strengthens the tie of operational troubleshooting and software development. The developer community will benefit from the GitHub integration, making it faster and easier for developers to deliver quality software."

The new integration enables Loggly users to match an exception to the exact file and line that generated that exception within source code managed in GitHub. The integration requires no additional instrumentation. Regardless of whether the user investigating the exception wrote the source code or not, he or she can find the right code with just one click.

In addition, users can:

- Quickly view all recent commits on the relevant source code files, since recent changes are often the sources of exceptions.

- Create an issue in GitHub directly from within Loggly or add a comment to an existing issue so that no bugs fall through the cracks.

Summary of Benefits:

- Shorter mean time to resolution (MTTR) through a tighter connection between exceptions and the source code that generated them.

- Better teamwork since Loggly users can quickly identify the right people to bring into an issue and efficiently initiate the tracking process in GitHub.

- Better auditing of regressions by connecting logs to change history.

- Less risk of leaving costly bugs untracked.