Repository navigation
New integrations - #66
Merged
Merged
Conversation
Document two of the new Data-category integrations, each metrics-via- Grafana-Alloy: - Altinity ClickHouse - operator exporter + Keeper metrics in-cluster. - MongoDB - built-in Alloy exporter (clusterMonitor user) plus log collection, with the password/API-key file handling and the keep/drop relabel notes. Both reproduce the install configs verbatim and note the Dashboard data link. Added to the All integrations nav (Data). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the TigerData integration (Data category): Grafana Alloy runs TimescaleDB information-view queries via the Postgres exporter with a custom-queries file, relabeled to its own job. Covers the no-privilege monitoring user, the queries YAML, the Alloy config with allowlist/ relabel notes, sending to OpsPilot, and confirming. Cross-links the PostgreSQL integration for the server itself. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the Microsoft SQL Server integration (Data category): built-in Alloy mssql exporter (login with VIEW SERVER STATE + VIEW ANY DEFINITION) plus error-log collection. Covers the password URL-encoding, the Alloy config, the GODEBUG x509negativeserial certificate workaround, the log stages, and confirming with mssql_local_time_seconds. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the MySQL/MariaDB integration (Data category): built-in Alloy mysql exporter (PROCESS + REPLICATION CLIENT user, SLAVE MONITOR on MariaDB) plus error-log collection handling both log formats. Covers the exporter config with the instance relabel and deadlock collector, and the per-distro log locations incl. the MariaDB-on-Debian journal fix. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the Redis/Valkey integration (Data category): built-in Alloy redis exporter with a narrow ACL user (no key access, config_command disabled) plus log collection parsing Redis's level/role format. Covers keeping credentials out of redis_addr and the per-package log locations. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the Strimzi Kafka integration (Data category): Grafana Alloy discovers Strimzi's Kafka nodes, Kafka Exporters, and operators in the cluster by pod labels and scrapes their existing metrics endpoints. Covers turning on Strimzi's JMX metrics (ConfigMap + Kafka resource), the Alloy discovery/relabel config, and confirming. Completes the seven new Data integrations. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Altinity ClickHouse, MongoDB, MySQL, Redis, Strimzi Kafka, and TigerData have shipped and now have pages, so remove them from the overview's Coming soon list. Kafka (non-Strimzi) and RabbitMQ remain. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the Kubernetes catalog integration (Infrastructure, v1.1.0), which uses the Grafana Kubernetes Monitoring Helm chart (distinct from the existing kube-prometheus-stack monitoring guide). Covers the values file with the required metricsTuning lists, installing the chart, confirming the jobs, resuming the paused alerts, troubleshooting, and removal. Adds it to the Infrastructure nav and drops it from Coming soon. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Kubernetes integration (Grafana Kubernetes Monitoring chart) and the Kube-Prometheus-Stack shipping guide are both valid. Add a note on each pointing at the other and explaining which chart it uses, so readers can pick the one that fits what they already run. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Reconcile against v1.3.0: document the second dashboard (Windows Hosts - Detail), add the six new collectors (tcp, scheduled_task, pagefile, time, thermalzone, cpu_info) with their notes, and correct the job-label behavior - it is now set to integrations/windows automatically, not forced via job_name, so the confirm query and troubleshooting drop the job selector. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.