Skip to content

SQL-exporter: collect cratedb_expected_data_nodes metric #765

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
goat-ssh wants to merge 1 commit into from
Closed

SQL-exporter: collect cratedb_expected_data_nodes metric #765

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGES.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ Unreleased
* Automatically re-create internal system tables after completing a major version
upgrade.

* Add collector for cratedb expected_data_nodes monitoring to the sql_exporter.

2.51.0 (2025-08-06)
-------------------

Expand Down
9 changes: 9 additions & 0 deletions crate/operator/data/cratedb_expected_data_nodes-collector.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
collector_name: cratedb_expected_data_nodes_collector
metrics:
- help: "Number of expected data nodes"
metric_name: cratedb_expected_data_nodes
query: select settings['gateway']['expected_data_nodes'] as cratedb_expected_data_nodes from sys.cluster;
type: gauge
values: [cratedb_expected_data_nodes]
min_interval: 60m
Copy link
Contributor Author

@goat-ssh goat-ssh Aug 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WalBeh do you think this interval is good? I'm thinking about alert like:

  - alert: CrateDBExpectedNodesStatefulSetMismatch
    # This alert fires when the number of Kubernetes StatefulSet replicas is less than the expected CrateDB nodes
    expr: |
      max by (environment, provider, region, namespace) (cratedb_expected_data_nodes) 
      > 
      max by (environment, provider, region, exported_namespace) (kube_statefulset_replicas{statefulset=~"crate-data-hot-.*"})
    for: 5m

2 changes: 1 addition & 1 deletion crate/operator/data/sql-exporter.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ global:
# timing out first.
scrape_timeout_offset: 500ms
target:
collectors: [responsivity_collector, cratedb_max_shards_collector, cratedb_cluster_last_user_activity_collector, cratedb_unreplicated_tables_collector, cratedb_large_translogs_collector]
collectors: [responsivity_collector, cratedb_max_shards_collector, cratedb_cluster_last_user_activity_collector, cratedb_unreplicated_tables_collector, cratedb_large_translogs_collector, cratedb_expected_data_nodes_collector]
# To test sql exporter against a local crateDB service you can add "&sslmode=disable" to the data_source_name.
# Please do not use sslmode=disable in production as it hinders security.
data_source_name: "postgres://crate@localhost:5432/?connect_timeout=5"