The Stack Infra team at Elastic uses many services to provide downloads for projects like Elasticsearch and Kibana to our users. One of these services is Fastly, which helps us optimize delivery to regions around the world. Keeping an eye on the performance and behavior of our CDN is important to ensure we're operating at the level we expect.
At STRABAG, we are using Elastic Cloud Enterprise (ECE) for two main use cases within our on-premises web applications. One to power different kinds of search and a second for operations where we ship more than 25,000 log entries per minute to Elastic from our load balancers. The ECE platform runs in an air-gapped environment, and we would still like to be able to use our corporate logins for the ECE platform.
At Elastic, we love data. It’s the backbone of what we do: search. And that data takes many forms. A knowledge base article showing how to reset your cable box — data. Logs from your network — data. IP addresses accessing your secure network — data. A video tutorial on how adults can use TikTok — data. The list goes on. But behind each piece of data is a story. And a person. Or a customer.
This post is the second in our series on system metrics where we cover: In the previous post, we went through some built-in tools and methods for identifying key metrics and values on your systems. In this post, we'll provide a tutorial on how to use Metricbeat to consolidate metrics, store and analyze them in the long term, and discuss some of the benefits of a centralized metric store.
We hosted our first ever virtual Elastic{ON} Gov Summit with one primary goal: recreate the collaboration and community-building we normally enjoy at our in-person Gov Summit in a new, virtual format. And we were humbled to be able to do just that. The event gathered more than 2,000 registered attendees from across government agencies and partners to collaborate while so many of us were social distancing across the nation.
While Google G Suite is an indispensable productivity and collaboration tool for modern businesses, all too frequently content tends to pile up in the far corners of Google Drive, making content search and discovery difficult. Spending valuable time sifting and searching through tens of thousands of documents to find the right one has become all too common, and most workers spend several hours per week searching for information.
Elasticsearch has a lot of strengths (speed, scale, relevance), but one of its most important strengths is its flexibility to be added to existing environments without the need for any sort of architectural overhaul. If you are a sysadmin (dev, sec, ops, etc.), you know just how appealing this is. So many legacy systems remain in place not because they are perfect, but because replacing them would cost time and money that you don't have.
This post is the first in a three-part series on how to effectively monitor the hosts and systems in your ecosystem, and we're starting with the one you use most: your personal computer. Metrics are a key part of observability, providing insight into the usage of your systems, allowing you to optimize for efficiency and plan for growth. Let's take a look at the different metrics you should be monitoring.
When you perform a search in Elasticsearch, results are ordered so that documents which are relevant to your query are ranked highly. However, results that may be considered relevant for one application may be considered less relevant for another application. Because Elasticsearch is super flexible, it can be fine-tuned to provide the most relevant search results for your specific use case(s).
Application performance monitoring (APM) and logging both provide critical insight into your ecosystem. When paired together with context, they can provide vital clues on how to resolve problems with your applications. As the log data you analyze becomes more complex, navigating to the relevant pieces can be tricky using traditional tools. With Elastic Observability (powered by the Elastic Stack), correlating logs with APM is as simple as a few clicks in Kibana.
