docs/managed-datahub/remote-executor/monitoring.md
import FeatureAvailability from '@site/src/components/FeatureAvailability';
This guide covers all aspects of monitoring your Remote Executor deployment:
The Remote Executor uses file-based health checks that can be monitored by your container platform:
/tmp/worker_liveness_heartbeat/tmp/worker_readiness_heartbeatThese files are automatically managed by the Remote Executor and can be used by Kubernetes liveness/readiness probes or ECS health checks.
Monitor Remote Executor health directly in the DataHub UI:
The Remote Executor exposes metrics on port 9087/tcp in Prometheus/OpenMetrics format. Metrics can be collected by Prometheus stack or compatible agents, such as DataDog.
Ingestion Metrics
datahub_executor_worker_ingestion_requests - Total jobs receiveddatahub_executor_worker_ingestion_errors - Failed jobs (v0.3.9+)Resource Metrics (v0.3.9+)
datahub_executor_memory_*datahub_executor_cpu_*datahub_executor_disk_*datahub_executor_net_*Example ServiceMonitor resource to allow scraping Remote Executor metrics in Prometheus:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
labels:
name: datahub-remote-executor
spec:
endpoints:
- port: metrics
selector:
matchLabels:
app.kubernetes.io/name: datahub-remote-executor
View metrics endpoint directly:
curl http://your-executor:9087/metrics
Read annotations in Prometheus UI
Search datahub_executor_* in your monitoring system
:::note Platform-specific metrics (e.g., container restarts) should be monitored through native tooling (CloudWatch for ECS, Kubernetes metrics for K8s). :::