Kong Mesh data collection

Uses: Kong Mesh

Tags

#security

Related Resources

Audit logs

Kong Mesh can collect information about your deployment to continuously improve the product and gather anonymous feedback. The collected data is sent to Kong servers securely for storage and aggregation.

You can use the following environment variable to enable data collection when installing the control plane in Kubernetes, or before running kuma-cp in Universal mode:

KUMA_REPORTS_ENABLED=true

Copied!

You can also set the reports.enabled field to true in the YAML configuration file.

For more information, see the control plane configuration docs.

What data is collected

Field	Description
`version`	The installed version of Kong Mesh you’re running.
`product`	The static value “Kong Mesh”.
`unique_id`	The control plane hostname followed by a random UUID generated each time the control plane instance is restarted.
`backend`	The storage mode for your configuration: in-memory, etcd, or Postgres.
`mode`	The control plane mode: zone or global.
`hostname`	The hostname of each Kong Mesh control plane deploy.
`signal`	A `start` signal sent when the control plane starts, followed by a `ping` once each hour.
`cluster_id`	Unique identifier for the entire Kong Mesh cluster. The value is the same for all control planes in the cluster.
`dps_total`	The total number of data plane proxies across all meshes.
`meshes_total`	The total number of meshes deployed.
`zones_total`	The total number of zones deployed.
`internal_services`	The total number of services running inside your meshes.
`external_services`	The total number of external services configured for your meshes.
`services_total`	The total number of services in your mesh network.

Kong Mesh data collection

What data is collected

Help us make these docs great!

Still need help