Plugin: python.d.plugin Module: boinc
This collector monitors task counts for the Berkeley Open Infrastructure Networking Computing (BOINC) distributed computing client.
It uses the same RPC interface that the BOINC monitoring GUI does.
This collector is supported on all platforms.
This collector supports collecting metrics from multiple instances of this integration, including remote instances.
By default, the module will try to auto-detect the password to the RPC interface by looking in
/var/lib/boinc for this file (this is the location most Linux distributions use for a system-wide BOINC installation), so things may just work without needing configuration for a local system.
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.
BOINC requires use of a password to access it’s RPC interface. You can find this password in the
gui_rpc_auth.cfg file in your BOINC directory.
The configuration file name for this integration is
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 python.d/boinc.conf
There are 2 sections:
The following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.
Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition.
Every configuration JOB starts with a
job_name value which will appear in the dashboard, unless a
name parameter is specified.
|Sets the default data collection frequency.
|Controls the order of charts at the netdata dashboard.
|Sets the job re-check interval in seconds.
|Indicates whether to apply penalty to update_every in case of failures.
|Job name. This value will overwrite the
job_name value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works.
|Define a hostname where boinc is running.
|The port of boinc RPC interface.
|Provide a password to connect to a boinc RPC interface.
A basic JOB configuration for a remote boinc instance
Note: When you define multiple jobs, their names must be unique.
Collecting metrics from local and remote instances.
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 entire monitored application.
This scope has no labels.
|New, Downloading, Ready to Run, Compute Errors, Uploading, Uploaded, Aborted, Failed Uploads
|Uninitialized, Preempted, Scheduled
|Uninitialized, Executing, Suspended, Aborted, Quit, Copy Pending
The following alerts are available:
|average number of total tasks over the last 10 minutes
|average number of active tasks over the last 10 minutes
|average number of compute errors over the last 10 minutes
|average number of failed uploads over the last 10 minutes
To troubleshoot issues with the
boinc collector, run the
python.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
Switch to the
sudo -u netdata -s
python.d.plugin to debug the collector:
./python.d.plugin boinc debug trace