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.

In this article, we’ll learn about the Elasticsearch flattened datatype which was introduced in order to better handle documents that contain a large or unknown number of fields. The lesson examples were formed within the context of a centralized logging solution, but the same principles generally apply. By default, Elasticsearch maps fields contained in documents automatically as they’re ingested.

One of the most common dashboards for metric visualization and alerting is, of course, Grafana. In addition to logs, we use metrics to ensure the stability and operational observability of our product. This document will describe some basic Grafana operations you can perform with the Coralogix-Grafana integration. We will use a generic Coralogix Grafana dashboard that has statistics and information based on logs. It was built to be portable across accounts.