Skip to content

Compatibility

Compatibility depends on the exact platform release, Elastic version, enabled components, integrations, and client software used by the deployment.

Do not choose client or integration versions based only on the documentation publication date.

What to check

Component Check
Managed platform Confirm the platform release associated with the deployment
Elasticsearch Confirm the exact Elasticsearch version
Kibana Confirm compatibility with the deployed Elasticsearch version
Fleet Server Confirm compatibility with the deployed Elastic Stack
Elastic Agent Confirm the Agent version is supported by the deployed Fleet and Elasticsearch versions
Fleet integrations Confirm the integration package is supported by the deployed Elastic version
OpenTelemetry Collector Confirm Collector, receiver, processor, exporter, and OTLP compatibility
OpenTelemetry SDKs Confirm application SDK and instrumentation compatibility
Logstash Confirm Logstash and plugin compatibility with the deployed Elasticsearch version
Elastic connectors Confirm connector availability, version, and license requirements
Elastic license Confirm required features are included in the active license
Azure region and plan Confirm the Marketplace plan and required Azure services are supported in the selected region

Elasticsearch

You can identify the Elasticsearch version using an authenticated request to GET / or from an appropriate Kibana view.

When using language clients, Beats or legacy collectors, Logstash, integrations, or plugins, follow Elastic's compatibility guidance for the deployed version.

Avoid upgrading clients or ingestion components independently without first confirming compatibility.

Elastic Agent and Fleet

Fleet Server, Elastic Agent, and integration packages have their own compatibility requirements.

Before deploying or upgrading an Agent:

  1. confirm the deployed Elastic Stack version;
  2. confirm the supported Elastic Agent version;
  3. confirm required integration packages are available;
  4. test representative telemetry after the change.

Do not assume the newest Elastic Agent is automatically appropriate for an older deployment.

OpenTelemetry Collector

OpenTelemetry Collector compatibility includes more than the Collector version itself.

Check:

  • Collector distribution;
  • receivers;
  • processors;
  • exporters;
  • extensions;
  • OTLP protocol support;
  • authentication;
  • TLS;
  • semantic-convention behavior.

If the Collector sends telemetry to Elastic, confirm the configuration is supported by the deployed Elastic version.

OpenTelemetry SDKs and instrumentation

Application instrumentation can evolve independently of the backend.

Before upgrading an OpenTelemetry SDK or instrumentation library, consider:

  • semantic-convention changes;
  • resource attributes;
  • metric-name changes;
  • histogram behavior;
  • trace propagation;
  • log signal support.

Changes in instrumentation can change the fields and datasets visible in Elasticsearch even when the platform itself has not changed.

Fleet integrations

Fleet integration packages can have minimum Elastic or Kibana version requirements.

An integration visible in upstream Elastic documentation might not be available in every deployed platform version.

Use the integrations available in the deployed Fleet environment as the authoritative starting point.

For new observability onboarding, prefer supported OpenTelemetry-native integrations where available.

Logstash

When Logstash is used, check compatibility for:

  • Logstash version;
  • Elasticsearch output;
  • input and filter plugins;
  • pipeline syntax;
  • authentication and TLS behavior.

Do not upgrade individual Logstash plugins without understanding their compatibility with the managed platform.

Elastic connectors

Connector availability can depend on:

  • Elasticsearch version;
  • Kibana version;
  • connector version;
  • Elastic license;
  • external service compatibility.

Confirm these requirements before building a production workflow around a connector.

Elastic license

Some Elastic capabilities depend on the active license.

Before enabling a feature, confirm that the deployed license includes it.

iVedha can assist with:

  • license requirements;
  • license installation;
  • procurement;
  • renewal;
  • available licensing options.

See manage the Elastic license.

Before making a compatibility-sensitive change

Confirm:

  1. the current platform and Elastic versions;
  2. the component or integration being changed;
  3. the supported version relationship;
  4. any license requirements;
  5. whether configuration or data-format behavior changes;
  6. how you will validate the workload after the change.

For managed platform upgrades, use the supported iVedha upgrade workflow rather than upgrading platform components independently.

See prepare for upgrades.

Version matrices

This documentation intentionally does not publish a single global compatibility matrix.

Supported combinations can change between platform releases and integration-package versions.

The deployed platform version, available Fleet integrations, Elastic documentation, and supported iVedha workflows should be used together to determine compatibility for a specific deployment.

See available stack versions for the verified target used by new managed deployments. That target does not replace the exact version baseline of an existing deployment.