Software services are at the heart of modern business in the digital age. Just look at the apps on your smartphone. Shopping, banking, streaming, gaming, reading, messaging, ridesharing, scheduling, searching — you name it. Society runs on software services. The industry has exploded to meet demands, and people have many choices on where to spend their money and attention. Businesses must compete to attract and retain customers who can switch services with the swipe of a thumb.

As Elasticsearch users are pushing the limits of how much data they can store on an Elasticsearch node, they sometimes run out of heap memory before running out of disk space. This is a frustrating problem for these users, as fitting as much data per node as possible is often important to reduce costs. But why does Elasticsearch need heap memory to store data? Why doesn't it only need disk space?

Let’s be honest. No one wakes up in the morning thinking of reasons to contact customer support. It’s tedious, onerous, and can eat into your evening Netflix time. Thankfully, most brands realize that customer experiences drive brand loyalty and repeat purchases.

Binary classification aims to separate elements of a given dataset into two groups on the basis of some learned classification rule. It has extensive applications from security analytics, fraud detection, malware identification, and much more. Being a supervised machine learning method, binary classification relies on the presence of labeled training data that can be used as examples from which a model can learn what separates the classes.

If you want to skip ahead to see the MITRE ATT&CK eval round 2 results visualized in an easy-to-configure Kibana dashboard, check it out here.

To achieve unified observability, we need to gather all of the logs, metrics, and application traces from an environment. Storing them in a single datastore drastically increases our visibility, allowing us to monitor other distributed environments as well. In this blog, we will walk through one way to set up observability of your Kubernetes environment using the Elastic Stack — giving your team insight into the metrics and performance of your deployment.

Six months ago we celebrated the joining of forces between Endgame and Elastic under the banner of Elastic Security and announced the elimination of per endpoint pricing. Simultaneously, while the newest members of Elastic Security were getting acquainted with the Elastic SIEM team, a few of our analysts were locked away in an office at MITRE HQ for round 2 of MITRE’s APT emulation.

As COVID-19 continues to make clear, being adaptable and resilient when the world changes can help a business stay alive. At Elastic, we know from experience that being distributed helps build a strong company that can scale and adapt as new challenges arise. In the spirit of open source and our relationship with the Elastic community, we’ve been offering tips and tricks on our blog and on social media about how to work effectively while remote.

A classic problem that every backend developer has faced during their work is testing an application that uses a database. A perfectly valid solution is to use the real database for testing your application, but you would be doing an integration test, while you want a unit test. There are many ways to solve this problem. You could create the database with docker, or use an in-memory compatible one, but if you are writing unit tests that can be easily parallelized this will become quite uncomfortable.

We are offering a variety of on-demand Elastic training courses for free — featuring 11 titles that span observability, security, and Elastic Stack administration. If you haven’t tried one of our self-paced courses yet, now is the perfect time to find out why so many people have shifted their learning preference from in-class to online. Our on-demand courses provide the same immersive learning experience found in the classroom, but delivered in a convenient, remote environment.