Files
sicabe-core/deploy/config/trino/jmx-exporter.yml
T

32 lines
1.7 KiB
YAML
Raw Normal View History

2026-10-09 02:35:14 +07:00
# =============================================================================
# eBdesk SiCABE — konfigurasi sidecar `trino-jmx-exporter` (M3 observabilitas)
# =============================================================================
# Dibaca `jmx_prometheus_standalone.jar` (image bitnami/jmx-exporter):
# java -jar jmx_prometheus_standalone.jar 9404 /config/config.yml
#
# hostPort : target JMX coordinator via RMI — HARUS sama dengan port &
# java.rmi.server.hostname di config/trino/jvm-coordinator.config.
#
# includeObjectNames : PEMBATAS CARDINALITY. Tanpa ini (`rules: ".*"` saja)
# jmx-exporter memaparkan SEMUA MBean (~9.700 metrik) — termasuk
# io.trino.filesystem.s3, io.airlift.*, org.eclipse.jetty.*, java.lang.*,
# trino.server, trino.security, dst yang tidak dipakai.
# Di sini dibatasi ke domain EKSEKUSI Trino yang DIPAKAI saja:
# trino.execution:* → QueryManager, QueryExecution, TaskManager
# trino.execution.executor.* → task executor (timesharing/dedicated)
# trino.execution.resourcegroups:* → resource group
# SENGAJA DIKECUALIKAN: trino.execution.scheduler[.faulttolerant]*
# (≈1.614 metrik statistik penjadwalan FT — stack ini tidak memakai
# fault-tolerant execution). Tambahkan kembali bila FT dipakai.
# (Konsekuensi: metrik JVM `java_lang_memory_*` juga tidak ada.)
---
hostPort: trino-coordinator:9080
lowercaseOutputName: true
lowercaseOutputLabelNames: true
includeObjectNames:
- "trino.execution:*"
- "trino.execution.executor.*:*"
- "trino.execution.resourcegroups:*"
rules:
- pattern: ".*"