Google Kubernetes Engine ↗
Note
It's also possible to use a Custom - Filebeat based Collector to ingest logs related to file activity on your endpoints and servers without using the Cortex XDR agent. For more information, see Elasticsearch Filebeat.
You can configure collecting Google Kubernetes logs and data using a Custom - Filebeat based Collector (standard data source), content pack integration (onboarded prior to July 26, 2026), or connector (onboarded after July 26, 2026):
| Collection Method | Description |
|---|---|
| Custom - Filebeat based Collector overview (standard data source) overview | Forward container logs from Google Kubernetes Engine using Elasticsearch Filebeat to Cortex XSIAM using the Custom - Filebeat based Collector data source. |
| Link to custom collector (standard data source) instructions | Ingest logs from Google Kubernetes Engine |
| Links to content pack/integration instructions (onboarded prior to July 26, 2026) | <p>The Google Kubernetes Engine content pack builds and manages container-based applications in Google Cloud Platform (GCP), powered by the open source Kubernetes technology. It contains the Google Kubernetes Engine Operations Generic Polling playbook as well as the following integration:</p><ul><li>Google Kubernetes Engine: Use this integration to build and manage container-based applications in Google Cloud Platform (GCP), utilizing the open source Kubernetes technology. This integration is used by the Google Kubernetes Engine Operations Generic Polling playbook, which checks operation status and facilitates the waiting between steps in cluster configuration.</li></ul> |
| Link to connector (onboarded after July 26, 2026) | Google Cloud |