Skip to main content
The CXDOT Collector offers configurable integrations to collect telemetry data from various tools, apps, and services and send that data to Palo Alto Networks Cortex XCOR. To configure integrations for the CXDOT Collector, update the Collector’s configuration file. You can browse the full catalog of integrations in the Integrations Hub.

Apache

Apache HTTP Server connection, request, traffic, and worker metrics.

Apache Cassandra

Apache Cassandra node, table, and Java Virtual Machine runtime metrics collected over JMX.

cert-manager

Certificate lifecycle and expiry metrics from cert-manager, scraped from its controller’s Prometheus endpoint.

ClickHouse

ClickHouse query, connection, merge, and replication metrics.

Concourse CI

Concourse build, job scheduling, resource check, worker, garbage collection, database and API metrics, scraped from web nodes’ Prometheus endpoint.

Consul

Consul cluster and catalog health metrics from Consul agents.

containerd

Per-container CPU, memory, block I/O, process and uptime metrics from a containerd daemon, plus the size of every image in its store.

Datadog

DogStatsD metrics, Datadog APM traces, and APM span metrics from apps instrumented with Datadog clients.

Docker

Per-container CPU, memory, block I/O, network, process and uptime metrics from a Docker daemon, plus the daemon’s own container and image counts.

Elasticsearch

Collect cluster, node, index, operating system, process, and JVM metrics from Elasticsearch.

Envoy

Envoy listener, cluster, and traffic metrics.

HAProxy

HAProxy connection, request, and session metrics.

Hasura

Hasura GraphQL Engine request, subscription, event trigger, and Postgres connection metrics.

Apache HBase

Apache HBase master and RegionServer metrics collected over JMX, including requests and latency, regions and store files, the block cache, flushes and compactions, the write-ahead log, and the Java Virtual Machine runtime.

Host

Operating system metrics from the machine running the Collector, including CPU, memory, disk, file system, network, load, paging, process counts, and uptime.

HTTP Check

Availability, response time, and certificate expiry metrics for the HTTP endpoints your services depend on.

JMX

Runtime metrics from Java apps that expose Java Management Extensions.

Apache Kafka

Apache Kafka broker and Java Virtual Machine runtime metrics collected over JMX.

Apache Kafka Consumer

Apache Kafka consumer group offsets and lag, partition offsets and replicas, and cluster broker counts collected from the Kafka admin API.

Kubernetes

Kubernetes workload, node, cluster state, and control-plane metrics, and Kubernetes logs.

Linux

Journal records and unit-state metrics from systemd on Linux hosts, optional forwarded syslog records, and target health for the journal, system bus, and listener.

MarkLogic

MarkLogic cluster, database, forest, host, server, request, transaction, storage, and health metrics.

Memcached

Memcached cache, operation, and connection metrics.

Apache Mesos

Apache Mesos cluster metrics read from the masters’ and agents’ HTTP APIs, including cluster-wide task, agent, and resource counts, per-framework and per-role allocations, and each agent’s tasks, executors, and resources, plus Apache Aurora scheduler metrics, including task counts by state, resource offers, preemptions, and cron activity.

Micrometer

Metrics from Java apps instrumented with Micrometer, including Spring Boot, sent to the CXDOT Collector over OTLP.

MongoDB

MongoDB server performance and health metrics, including operations, connections, locks, WiredTiger cache, replication, and database storage.

MySQL

MySQL server performance and health metrics, including buffer pool, connections, commands, query throughput, and index usage.

Neo4j

Neo4j transaction, query, page cache, checkpoint, Bolt connection, and JVM metrics, scraped from the server’s Prometheus endpoint.

NGINX

NGINX connection and request metrics scraped from the stub_status endpoint.

OpenMetrics

Metrics scraped from OpenMetrics and Prometheus endpoints.

Oracle Database

Oracle Database health and workload metrics, including sessions, wait and response time, cache hit ratios, I/O, and tablespace usage per pluggable database.

OTLP

Logs, metrics, and traces ingested over the OpenTelemetry Protocol from instrumented apps.

PostgreSQL

PostgreSQL connection and workload metrics.

Redis

Redis server health and performance metrics, including memory, clients, commands, keyspace, persistence, replication, and cluster state.

SNMP

Availability and performance metrics from SNMP network devices.

Apache Spark

Apache Spark application metrics read from a driver’s REST API, including executor memory and task throughput, garbage collection, shuffle volume, and persisted RDD storage.

Microsoft SQL Server

Microsoft SQL Server workload, memory, lock, transaction, database, file, and backup metrics.

TCP Check

Connectivity checks for TCP endpoints — whether a connection to each configured host and port can be established, how long the connect takes, and failed attempts by cause.

Temporal

Temporal request, workflow, task, and persistence metrics.

Apache Tomcat

Apache Tomcat application and Java Virtual Machine runtime metrics collected over JMX.

Vault

Collects cluster health, request performance, token, and storage backend metrics from HashiCorp Vault.

VMware vSphere

Performance counters, inventory and events of vCenter Servers and standalone ESXi hosts — every host and virtual machine’s CPU, memory, disk and network counters, guest and host properties, and vCenter events as logs.

Windows

Windows Event Log records, service-state metrics, and user-selected performance counters for Windows hosts, with per-channel, Service Control Manager, and per-counter-object target health.

ZooKeeper

ZooKeeper connection, request, latency, and data tree metrics.

For server-side integrations you configure in Cortex XCOR without running a Collector, see Server integrations.