Plugin: go.d.plugin Module: whoisquery
This collector monitors the remaining time before the domain expires.
This collector is supported on all platforms.
This collector supports collecting metrics from multiple instances of this integration, including remote instances.
This integration doesn't support auto-detection.
The default configuration for this integration does not impose any limits on data collection.
The default configuration for this integration is not expected to impose a significant performance impact on the system.
Metrics grouped by scope.
The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
These metrics refer to the configured source.
Labels:
| Label | Description |
|---|---|
| domain | Configured source |
Metrics:
| Metric | Dimensions | Unit |
|---|---|---|
| whoisquery.time_until_expiration | expiry | seconds |
The following alerts are available:
| Alert name | On metric | Description |
|---|---|---|
| whoisquery_days_until_expiration | whoisquery.time_until_expiration | time until the domain name registration expires |
No action required.
The configuration file name for this integration is go.d/whoisquery.conf.
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/whoisquery.confThe following options can be defined globally: update_every, autodetection_retry.
Config options
| Name | Description | Default | Required |
|---|---|---|---|
| update_every | Data collection frequency. | 1 | no |
| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
| source | Domain address. | yes | |
| days_until_expiration_warning | Number of days before the alarm status is warning. | 30 | no |
| days_until_expiration_critical | Number of days before the alarm status is critical. | 15 | no |
| timeout | The query timeout in seconds. | 5 | no |
Basic configuration example
Config
jobs:
- name: my_site
source: my_site.com
Note: When you define more than one job, their names must be unique.
Check the expiration status of the multiple domains.
Config
jobs:
- name: my_site1
source: my_site1.com
- name: my_site2
source: my_site2.com
To troubleshoot issues with the whoisquery 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.ddirectory, usually at/usr/libexec/netdata/plugins.d/. If that's not the case on your system, opennetdata.confand look for thepluginssetting under[directories].cd /usr/libexec/netdata/plugins.d/ -
Switch to the
netdatauser.sudo -u netdata -s
-
Run the
go.d.pluginto debug the collector:./go.d.plugin -d -m whoisquery