Type to search.

Orchestrator fields

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Fields that describe the resources which container orchestrators manage or act upon.

Field Description Level
orchestrator.api_version API version being used to carry out the action

type: keyword

example: v1beta1
extended
orchestrator.cluster.id Unique ID of the cluster.

type: keyword
extended
orchestrator.cluster.name Name of the cluster.

type: keyword
extended
orchestrator.cluster.url URL of the API used to manage the cluster.

type: keyword
extended
orchestrator.cluster.version The version of the cluster.

type: keyword
extended
orchestrator.namespace Namespace in which the action is taking place.

type: keyword

example: kube-system
extended
orchestrator.organization Organization affected by the event (for multi-tenant orchestrator setups).

type: keyword

example: elastic
extended
orchestrator.resource.annotation The list of annotations added to the resource.

type: keyword

Note: This field should contain an array of values.

example: ['key1:value1', 'key2:value2', 'key3:value3']
extended
orchestrator.resource.id Unique ID of the resource being acted upon.

type: keyword
extended
orchestrator.resource.ip IP address assigned to the resource associated with the event being observed. In the case of a Kubernetes Pod, this array would contain only one element: the IP of the Pod (as opposed to the Node on which the Pod is running).

type: ip

Note: This field should contain an array of values.
extended
orchestrator.resource.label The list of labels added to the resource.

type: keyword

Note: This field should contain an array of values.

example: ['key1:value1', 'key2:value2', 'key3:value3']
extended
orchestrator.resource.name Name of the resource being acted upon.

type: keyword

example: test-pod-cdcws
extended
orchestrator.resource.parent.type Type or kind of the parent resource associated with the event being observed. In Kubernetes, this will be the name of a built-in workload resource (e.g., Deployment, StatefulSet, DaemonSet).

type: keyword

example: DaemonSet
extended
orchestrator.resource.type Type of resource being acted upon.

type: keyword

example: service
extended
orchestrator.type Orchestrator cluster type (e.g. kubernetes, nomad or cloudfoundry).

type: keyword

example: kubernetes
extended
Location Field Set Description
orchestrator.entity.* entity Fields to describe various types of entities across IT environments.