Skip to main content

MaxScale

Plugin: go.d.plugin Module: maxscale

Overview

This collector monitors the activity and performance of MaxScale servers.

It sends HTTP requests to the MaxScale REST API.

This collector is supported on all platforms.

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

Default Behavior

Auto-Detection

The collector can automatically detect MaxScale instances running on:

  • localhost that are listening on port 8989
  • within Docker containers

Note that the MaxScale REST API requires a username and password. While Netdata can automatically detect MaxScale instances and create data collection jobs, these jobs will fail unless you provide the necessary credentials.

Limits

The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Metrics

Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per MaxScale instance

These metrics refer to the monitored MaxScale instance.

This scope has no labels.

Metrics:

MetricDimensionsUnit
maxscale.poll_eventsreads, writes, accepts, errors, hangupsevents/s
maxscale.current_sessionssessionssessions
maxscale.current_zombie_connectionszombieconnections
maxscale.threads_by_stateactive, draining, dormantthreads
maxscale.current_fdsmanagedfds
maxscale.qc_cache_efficiencyhits, missesrequests/s
maxscale.qc_cache_operationsinserts, evictionsoperations/s
maxscale.uptimeuptimeseconds

Per server

These metrics refer to the MariaDB server.

Labels:

LabelDescription
serverServer ID.
addressServer address.

Metrics:

MetricDimensionsUnit
maxscale.server_statemaster, slave, running, down, maintenance, draining, drained, relay_master, binlog_relay, syncedstate
maxscale.server_current_connectionsconnectionsconnections

Alerts

There are no alerts configured by default for this integration.

Setup

You can configure the maxscale collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for maxscale, then click + to add a job.
FileIf you prefer configuring via file, or need to automate deployments (e.g., with Ansible)Edit go.d/maxscale.conf and add a job.
important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

No action required.

Configuration

Options

The following options can be defined globally: update_every, autodetection_retry.

Config options
GroupOptionDescriptionDefaultRequired
Collectionupdate_everyData collection interval (seconds).1no
autodetection_retryAutodetection retry interval (seconds). Set 0 to disable.0no
TargeturlTarget endpoint URL.http://127.0.0.1:8989yes
timeoutHTTP request timeout (seconds).1no
HTTP AuthusernameUsername for Basic HTTP authentication.adminno
passwordPassword for Basic HTTP authentication.mariadbno
bearer_token_filePath to a file containing a bearer token (used for Authorization: Bearer).no
TLStls_skip_verifySkip TLS certificate and hostname verification (insecure).nono
tls_caPath to CA bundle used to validate the server certificate.no
tls_certPath to client TLS certificate (for mTLS).no
tls_keyPath to client TLS private key (for mTLS).no
Proxyproxy_urlHTTP proxy URL.no
proxy_usernameUsername for proxy Basic HTTP authentication.no
proxy_passwordPassword for proxy Basic HTTP authentication.no
RequestmethodHTTP method to use.GETno
bodyRequest body (e.g., for POST/PUT).no
headersAdditional HTTP headers (one per line as key: value).no
not_follow_redirectsDo not follow HTTP redirects.nono
force_http2Force HTTP/2 (including h2c over TCP).nono
Virtual NodevnodeAssociates this data collection job with a Virtual Node.no

via UI

Configure the maxscale collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the maxscale data-collection job to run and click the (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type maxscale (or scroll the list) to locate the maxscale collector.
  5. Click the + next to the maxscale collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/maxscale.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/maxscale.conf
Examples
Basic

A basic example configuration.

jobs:
- name: local
url: http://127.0.0.1:8989
username: admin
password: mariadb

HTTPS with self-signed certificate

MaxScale with enabled HTTPS and self-signed certificate.

Config
jobs:
- name: local
url: http://127.0.0.1:8989
username: admin
password: mariadb
tls_skip_verify: yes

Multi-instance

Note: When you define multiple jobs, their names must be unique.

Collecting metrics from local and remote instances.

Config
jobs:
- name: local
url: http://127.0.0.1:8989
username: admin
password: mariadb

- name: remote
url: http://192.0.2.1:8989
username: admin
password: mariadb

Troubleshooting

Debug Mode

Important: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature.

To troubleshoot issues with the maxscale collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the go.d.plugin to debug the collector:

    ./go.d.plugin -d -m maxscale

    To debug a specific job:

    ./go.d.plugin -d -m maxscale -j jobName

Getting Logs

If you're encountering problems with the maxscale collector, follow these steps to retrieve logs and identify potential issues:

  • Run the command specific to your system (systemd, non-systemd, or Docker container).
  • Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

System with systemd

Use the following command to view logs generated since the last Netdata service restart:

journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep maxscale

System without systemd

Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector's name:

grep maxscale /var/log/netdata/collector.log

Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.

Docker Container

If your Netdata runs in a Docker container named "netdata" (replace if different), use this command:

docker logs netdata 2>&1 | grep maxscale

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.