Skip to main content

FreeRADIUS

Plugin: go.d.plugin Module: freeradius

Overview​

This collector monitors FreeRADIUS servers.

It collect metrics by sending status-server messages to the server.

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​

It automatically detects FreeRadius instances running on localhost.

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 FreeRADIUS instance​

These metrics refer to the entire monitored application.

This scope has no labels.

Metrics:

MetricDimensionsUnit
freeradius.authenticationrequests, responsespackets/s
freeradius.authentication_access_responsesaccepts, rejects, challengespackets/s
freeradius.bad_authenticationdropped, duplicate, invalid, malformed, unknown-typespackets/s
freeradius.proxy_authenticationrequests, responsespackets/s
freeradius.proxy_authentication_access_responsesaccepts, rejects, challengespackets/s
freeradius.proxy_bad_authenticationdropped, duplicate, invalid, malformed, unknown-typespackets/s
freeradius.accountingrequests, responsespackets/s
freeradius.bad_accountingdropped, duplicate, invalid, malformed, unknown-typespackets/s
freeradius.proxy_accountingrequests, responsespackets/s
freeradius.proxy_bad_accountingdropped, duplicate, invalid, malformed, unknown-typespackets/s

Alerts​

There are no alerts configured by default for this integration.

Setup​

Prerequisites​

Enable status server​

To enable status server, follow the official documentation.

Configuration​

File​

The configuration file name for this integration is go.d/freeradius.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/freeradius.conf

Options​

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

Config options
NameDescriptionDefaultRequired
update_everyData collection frequency.1no
autodetection_retryRecheck interval in seconds. Zero means no recheck will be scheduled.0no
addressServer address.127.0.0.1yes
portServer port.18121no
secretFreeRADIUS secret.adminsecretno

Examples​

Basic​

A basic example configuration.

Config
jobs:
- name: local
address: 127.0.0.1
port: 18121
secert: adminsecret

Multi-instance​

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

Collecting metrics from local and remote instances.

Config
jobs:
- name: local
address: 127.0.0.1
port: 18121
secert: adminsecret

- name: remote
address: 192.0.2.1
port: 18121
secert: adminsecret

Troubleshooting​

Debug Mode​

To troubleshoot issues with the freeradius 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 freeradius

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