Elastic

Overview

Elastic is the company behind Elasticsearch, a distributed search and analytics engine, along with the broader Elastic Stack (formerly ELK Stack) comprising Kibana, Logstash, and Beats. Elastic's products are primarily infrastructure tools used by developers and operations teams for full-text search, log aggregation, application performance monitoring (APM), and security information and event management (SIEM).

Unlike most vendors in a consent management context, Elastic does not typically inject visitor-facing scripts into third-party websites. Its tools operate on the backend — indexing data, processing logs, and powering search functionality behind the scenes. When Elastic does appear on a website, it is usually powering a site search feature or collecting server-side application telemetry.

What This Script Does

Elastic's presence on a website can take several forms depending on the implementation:

• Site search: Elastic App Search or Elasticsearch may power a website's search functionality. Search queries are sent to an Elastic endpoint, and results are returned and rendered. The search queries themselves constitute user input that is processed by Elastic infrastructure.
• Real User Monitoring (RUM): Elastic APM's RUM agent can be deployed as a client-side script that captures page load performance, JavaScript errors, and user interaction timing. This script collects performance metrics and sends them to an Elastic APM server.
• Backend analytics: Elastic Beats agents and Logstash pipelines collect server-side logs and metrics. These never execute in the visitor's browser but may process data derived from visitor activity (e.g., access logs containing IP addresses).
• Kibana dashboards: Occasionally embedded as iframes for public-facing dashboards, though this is uncommon on consumer-facing sites.

When the RUM agent is present, it collects page URLs, timing data, browser metadata, and error information. It does not typically set cookies or track users across sessions unless explicitly configured to do so.

Consent & Compliance

Elastic's compliance profile depends entirely on which components are deployed client-side. Backend-only deployments (Elasticsearch powering search, server-side log processing) do not interact with the visitor's browser and fall outside the scope of ePrivacy consent requirements.

If the Elastic RUM agent is deployed client-side, it accesses the visitor's browser environment to collect performance telemetry. Under a strict reading of the ePrivacy Directive, this constitutes accessing information on the user's terminal equipment. However, performance monitoring is often considered a legitimate interest when it directly supports the quality of the service the visitor is using.

Site search functionality powered by Elastic processes user-initiated queries and is typically classified as a service explicitly requested by the user, exempting it from prior consent requirements.

Should You Block This Without Consent?

No. In most deployments, Elastic operates as backend infrastructure or powers user-requested search functionality, neither of which requires consent. If the RUM agent is deployed client-side for performance monitoring, it serves a functional purpose and does not track users for marketing.