Collect CockroachDB node and cluster ids in Metricbeat module

[jsoriano]

CockroachDB has the native concept of node and cluster ids. As a user one may want to filter data per instance or per cluster.

We need to confirm the identifiers to use for each case, some options:

Cluster ID:

• Using the SQL interface: SELECT value FROM crdb_internal.node_build_info where field = 'ClusterID';

Node ID:

• Using the SQL interface:
  • SELECT value FROM crdb_internal.node_metrics where name = 'node-id';
  • SELECT DISTINCT node_id FROM crdb_internal.node_build_info;
• In the prometheus response:

  # HELP node_id node ID with labels for advertised RPC and HTTP addresses
  # TYPE node_id gauge
  node_id{advertise_addr="roach1:26257",http_addr="roach1:8080"} 1.0
  

This may be an important change because current CockroachDB module is a light module collecting prometheus exposed metrics, and this may require enriching events with metadata obtained with SQL queries.

Related:

• Cluster ID for kubernetes: [Metricbeat] Add cluster identifier to Kubernetes metadata #17467
• Cluster ID for kafka: Collect kafka cluster id in Metricbeat module #21781

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!