Skip to content

Alter Metrics

Alter metrics⚓︎

Metric Name Type Components Purpose
query_count (deprecated) Counter Alter Count of Alter calls to the catalog.
query_failure (deprecated) Counter Alter Count of failed Alter catalog calls.
query_latency_summary (deprecated) Summary Alter Latency of calls to the catalog.

For a complete list of the metrics used by Hydrolix, including Prometheus, RabbitMQ, and others, see All Metrics.

Prometheus in Hydrolix⚓︎

The Hydrolix stack includes Prometheus, an open-source metrics database. Hydrolix continuously updates its Prometheus instance with metrics information.

You can query, view, and actively monitor this information using a stack's Grafana instance, or you can access it with your own monitoring platform. See Prometheus Integration for more information about setting up Prometheus with an external server.

Use the Prometheus UI⚓︎

Prometheus has its own web-based UI.

This view is a basic metric view, suitable for quickly entering queries and seeing simple, graphed results. This feature is available in Hydrolix without any additional setup.

Navigate to https://hostname.hydrolix.live/prometheus to view dashboards.

For more information about Prometheus metric types, refer to the Prometheus documentation.

Pass additional options to Prometheus⚓︎

Use a list of strings in the prometheus_extra_args tunable to append options after default flags set by Hydrolix.

Set a Custom TSDB Block Duration

1
2
3
spec:
  prometheus_extra_args:
  - --storage.tsdb.max-block-duration=2h

For a list of available flags, see the Prometheus CLI reference, or see Prometheus storage.

Prometheus option resolution⚓︎

Prometheus settings come from and are resolved in the following order from lowest to highest priority:

  • Prometheus: Built-in defaults
  • Hydrolix: Default settings for Prometheus
  • User-specified: Using prometheus_extra_args (highest precedence)

See https://hostname.hydrolix.live/prometheus/config for current Prometheus settings.

If a user-configured flag conflicts with a built-in Prometheus default, the value in prometheus_extra_args overrides the default one. This results in the following resolution by flag type:

  • Scalar flags accept a single value. If a scalar flag in prometheus_extra_args conflicts with a Prometheus built in or Hydrolix-specified default, the value in prometheus_extra_args overrides it.
  • Cumulative flags accept multiple values. If a flag in prometheus_extra_args matches a built-in cumulative flag (for example, --enable-feature), the values are appended rather than replaced.