Type to search.

Package 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.

These fields contain information about an installed software package. It contains general information about a package, such as name, version or size. It also contains installation details, such as time or location.

Field Description Level
package.architecture Package architecture.

type: keyword

example: x86_64
extended
package.build_version Additional information about the build version of the installed package.

For example use the commit SHA of a non-released package.

type: keyword

example: 36f4f7e89dd61b0988b12ee000b98966867710cd
extended
package.checksum Checksum of the installed package for verification.

type: keyword

example: 68b329da9893e34099c7d8ad5cb9c940
extended
package.description Description of the package.

type: keyword

example: Open source programming language to build simple/reliable/efficient software.
extended
package.install_scope Indicating how the package was installed, e.g. user-local, global.

type: keyword

example: global
extended
package.installed Time when package was installed.

type: date
extended
package.license License under which the package was released.

Use a short name, e.g. the license identifier from SPDX License List where possible (https://spdx.org/licenses/).

type: keyword

example: Apache License 2.0
extended
package.name Package name

type: keyword

example: go
extended
package.path Path where the package is installed.

type: keyword

example: /usr/local/Cellar/go/1.12.9/
extended
package.reference Home page or reference URL of the software in this package, if available.

type: keyword

example: https://golang.org
extended
package.size Package size in bytes.

type: long

example: 62231
extended
package.type Type of package.

This should contain the package file type, rather than the package manager name. Examples: rpm, dpkg, brew, npm, gem, nupkg, jar.

type: keyword

example: rpm
extended
package.version Package version

type: keyword

example: 1.12.9
extended