20 April 2017 Engineering

Tuning Go Apps with Metricbeat

By Giuseppe ValenteMedcl Zeng

The Elastic Stack can be leveraged to monitor Go applications to analyze memory usage, performing long-term monitoring, tuning and capturing diagnostics.

engineering Created with Sketch.

20 April 2017 Engineering

The future of Log4j input in Logstash

By Jordan Sissel

This post describes a security issue with Log4j input in Logstash. This input is deprecated and will be removed in the future.

19 April 2017 Engineering

GeoIP in the Elastic Stack

By Mark Walkom

Discover what browsers access your site. See where your end users are logging in from. Put your IP addresses or hostnames to work with geoip filtering.

19 April 2017 User Stories

Stretching the Elastic Stack to Fit the (Very Large and Complicat...

By Emily Mosher

How Merck is using Elasticsearch to tame a rich, but wild jungle of genetic data and getting it to perform tricks — like predicting disease causes.

19 April 2017 Engineering

Componentizing the Kibana UI, Part 2: Writing JavaScript with Rea...

By CJ Cenizal

React complements our componentization process perfectly! We've used React to encapsulate complexity, and reduce CSS and markup to mere implementation details.

18 April 2017 News

Hosted Elasticsearch Services Roundup: Elastic Cloud and Amazon E...

By Haley EshaghTyler Hannan

What's the difference between Elastic Cloud, Amazon's Elasticsearch Service, and vanilla Elasticsearch on AWS? Let us explain.

13 April 2017 Engineering

New Kibana Visualizations: Heatmap and Point Series

By Peter Pišljar

Our journey of adding new visualizations to Kibana started with Tag Cloud. But we did not stop there. In 5.2 we introduced Heatmap visualization, and in 5.4...

11 April 2017 Engineering

Operational Analytics with Elasticsearch at Elastic{ON} 2017 - Pa...

By Dale McDiarmidAsawari Samant

A 3 part series on Operational Analytics: Exploring attendee engagement at Elastic{ON} using the Elastic Stack.

11 April 2017 Engineering

Multi data path bug in Elasticsearch 5.3.0

By Clinton Gormley

If you use a custom data path with Elasticsearch 5.3.0, you may be subject to a bug which could cause data loss unless properly handled.