They say knowledge is power and today, there is no greater source of knowledge than data. It is well documented that businesses produce a vast amount of data whether it be in manufacturing, IT, UX, Marketing, Sales or Finance. Collectively, all of this data can provide you with business intelligence, enabling you to optimize decisions, improve collaboration, and increase overall performance.

Alerts are a core part of monitoring systems. Using alerts keeps you aware of changes within your infrastructure and applications, helping you identify and respond to issues faster. Log management solutions like LogDNA provide an ideal environment for configuring alerts, since it allows you to create detailed alerts based on your log data. Rather than manually search for problems, you can use alerts to scan your log data in real-time and receive immediate notifications on potential problems.

One of the unintended side-effects of the public cloud is the enablement of a platform-agnostic cloud architecture. This means that it’s now easier than ever to mix offerings from multiple vendors (cloud vendors in this case) to form a single application or service-based solution. There is one gotcha, however: log management.

Many of our users are responsible for monitoring logs to detect sudden changes in volume or to control the budget. To help you with this goal, we’re excited to announce new enhancements to our usage dashboard.

As Elasticsearch is gradually becoming the standard for textual data indexing (specifically log data) more companies struggle to scale their ELK stack. We decided to pick up the glove and create a series of posts to help you tackle the most common Elasticsearch performance and functional issues. This post will help you in understanding and solving one of the most frustrating Elasticsearch issues – Mapping exceptions.