Channels ▼
RSS

Tools

DevOps Log Data Intelligence Is Not Stupid


Are DevOps tools getting closer to developers and able to add real value? That's the question that arises when we look across the batch of products currently emanating from firms like Logentries, with its log management and analytics service.

The software enables "entire DevOps teams" to enrich their machine log data with real-time annotations, shareable performance dashboards, and instant group notifications.

The firm says that development and operations teams need deep, log-level visibility and root-cause analysis that can only be achieved by log files. Logentries believes in maintaining all of the information in one secure, centralized location and says that valuable log data must be accessible across the entire team. Team-based annotations allow users to see team member comments, share expertise, and maintain context with the new team-based view of system activity and log events; and identify and resolve issues together in real-time.

There are also shareable dashboards to publish log data visualizations and trends across the DevOps team, and across the organization, to create one single data source for system and application performance.

An Open API allows developers to build with out-of-the-box integration and use existing toolsets and system integrations, including HipChat, PagerDuty, and Campfire, says Andrew Burton, CEO, Logentries.

"The Logentries service features a pre-processing engine that collects and analyzes log files in real-time to offer immediate alerting, visualizations, and tailing of the data. There is no complex query language required, making searching the data easy and intuitive with click-through navigation," he said.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video