Logs have been around for a while, not quite as long as the wheel, but not far off. Here at Logentries, we have the mantra of evolve don’t revolve (as in don’t sit around spinning your wheels getting nowhere). We are taking this concept and looking to evolve the way you work with and think about your log data.
Gone are the old days, where you only used logs to find exceptions. A new day has dawned, and the future is here, the future is Logentries (a bit cheesy I know, but I do think we are going to revolutionize the way you utilize logs).
Over the last 6 months, we have made giant strides to add features and functionality to the core Logentries product, we have endeavored to ensure we don’t just add more buttons and new (but similar features), but instead help deliver our customer-base a more powerful and rounded tool than ever before.
Over the last 6 months, we have been focused on delivering a specific set of features focused on the following areas:
- More powerful agents and libraries (Server metrics)
- Increased Library coverage (new Mobile devices)
- Working with multiple log streams in unison (powerful aggregation tools)
- Providing tools to extract computed data from your logs (Saved queries and Functions)
- Enabling easy-to-use visualizations (instant visualizations and dashboards)
- Export metrics to 3rd party service (JSON export)
- More powerful alerting (inactivity and anomaly detection)
- Teams and sharing information (annotations)
These improvements in functionality now give the user more power to use their logs as data than ever before.
A way of using Logentries and logs, which was not possible 6 months ago:
So as an example, a user could be logging all the key events from their mobile and web clients to Logentries; extracting visualizations and metrics from these logs to gain insight into how their users are engaging with their application, all in real time.
Have their logs from tens to hundreds of servers streaming into Logentries and have visualizations built on key metrics from the application level or server level built on a log or a combined log level.
Have all of these views and visualizations on a single dashboard view to give them an instant view on application usage and associated impact on their servers/systems in real time.
Be able to quickly and easily drill down from the visualizations to the individual log events to identify issues and resolutions.
Have these KVP’s metrics exported in JSON format to a 3rd party dashboard to enable the combining of data from multiple sources.
Have powerful alerts set up identifying inactivity of a server or if anomalies are noticed in a specific log, such as if average response time had increased on a server by X% over last week.
Be able to select the logs that they are currently interested in, and have them combined into a single log view, have this in a live tail mode to see the incoming log events in real-time, and then filter to only show events what contain specific information to enable easy identification of issues.
And all of this new functionality and much more has been delivered in the last 6 months. (Check out our product timeline)
When you consider how much we have added to the product, and you consider we were only getting started, imagine how much we are going to improve over the next 6 months…
We really are re-inventing the