Skip to main content

Rubrik Security Cloud GraphQL API

Connector dependencies​

The following monitoring connectors will be installed when you install the Rubrik Security Cloud GraphQL API connector through the Configuration > Connectors > Monitoring Connectors menu:

Pack assets​

Templates​

The Monitoring Connector Rubrik Security Cloud GraphQL API brings a host template:

  • App-Rubrik-Graphql-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
ClusterApp-Rubrik-Cluster-Graphql-customCheck the status and I/O metrics of the Rubrik cluster
DisksApp-Rubrik-Disks-Graphql-customCheck the disk status of the Rubrik cluster
NodesApp-Rubrik-Nodes-Graphql-customCheck the node status of the Rubrik cluster
Rubrik RSC SLA ComplianceApp-Rubrik-Compliance-Graphql-customCheck the SLA compliance of protected objects
StorageApp-Rubrik-Storage-Graphql-customCheck the storage usage of the Rubrik cluster
TasksApp-Rubrik-Tasks-Graphql-customCheck Rubrik backup task status and last success time

The services listed above are created automatically when the App-Rubrik-Graphql-custom host template is used.

Discovery rules​

Service discovery​

Rule nameDescription
App-Rubrik-Graphql-Job-NameDiscover jobs and monitor status

More information about discovering services automatically is available on the dedicated page and in the following chapter.

Collected metrics & status​

Here is the list of services for this connector, detailing all metrics and statuses linked to each service.

NameUnit
statusN/A
clusters#cluster.io.read.usage.bytespersecondB/s
clusters#cluster.io.write.usage.bytespersecondB/s
clusters#cluster.io.read.usage.iopsiops
clusters#cluster.io.write.usage.iopsiops
clusters#cluster.network.received.usage.bytespersecondB/s
clusters#cluster.network.transmitted.usage.bytespersecondB/s

Prerequisites​

Rubrik Security Cloud provides a GraphQL API for interacting with protected objects, backups and compliance data.

To access the API, you must:

  • Have access to Rubrik Security Cloud (RSC)
  • Create a Service Account
  • Assign the required RBAC permissions
  • Generate OAuth credentials (client_id and client_secret)

Please refer to the Rubrik Security Cloud API documentation for more information.

Installing the monitoring connector​

Pack​

The installation procedures for monitoring connectors are slightly different depending on whether your license is offline or online.

  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Connectors > Monitoring Connectors menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-applications-rubrik-graphql
  1. Whatever the license type (online or offline), install the Rubrik Security Cloud GraphQL API connector through the Configuration > Connectors > Monitoring Connectors menu.

Plugin​

Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. When this feature is enabled, you can skip the installation part below.

You still have to manually install the plugin on the poller(s) when:

  • Automatic plugin installation is turned off
  • You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet

More information in the Installing the plugin section.

Use the commands below according to your operating system's package manager:

dnf install centreon-plugin-Applications-Rubrik-Graphql

Using the monitoring connector​

Using a host template provided by the connector​

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill in the Name, Alias & IP Address/DNS fields according to your resource's settings.
  3. Apply the App-Rubrik-Graphql-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.

IP Address/DNS is your Rubrik RSC Tenant hostname (e.g. dummy.my.rubrik.com)

MacroDescriptionDefault valueMandatory
RUBRIK_RSC_API_PROTOProtocol usedhttps
RUBRIK_RSC_API_PORTPort used443
RUBRIK_RSC_CLIENT_SECRETService account secret (with --service-account option)X
RUBRIK_RSC_CLUSTERFilter cluster. Multiple values can be separated by comma. This filter is passed directly to the GraphQL API (server-side filtering). Depending on its format this parameter is treated as either a name or a UUID
RUBRIK_RSC_EXCLUDE_CLUSTERExclude cluster (can be a regexp). Depending on its format this parameter is treated as either a name or a UUID
RUBRIK_RSC_INCLUDE_CLUSTERInclude cluster (can be a regexp). Depending on its format this parameter is treated as either a name or a UUID
RUBRIK_RSC_SERVICE_ACCOUNTService account ID (with --secret option)X
TIMEOUTSet timeout in seconds120
RUBRIK_RSC_EXTRA_OPTIONSAny extra option you may want to add to every command (a --verbose flag for example). All options are listed here.
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector​

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
MacroDescriptionDefault valueMandatory
START_TIMESet start time for filtering clusters by registration date. Accepts ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ), or YYYY-MM-DD, or YYYY-MM-DD HH:mm:ss
END_TIMESet end time for filtering clusters by registration date. Accepts ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ), or YYYY-MM-DD, or YYYY-MM-DD HH:mm:ss
LASTSet duration to filter last registered clusters. Use 'd' for day, 'h' for hour, 'm' for minute (e.g., 24h, 30m, 7d)
WARNING_READWarning threshold for read throughput (B/s)
CRITICAL_READCritical threshold for read throughput (B/s)
WARNING_READ_IOPSWarning threshold for read IOPS
CRITICAL_READ_IOPSCritical threshold for read IOPS
WARNING_RECEIVEDWarning threshold for network bytes received per second (B/s)
CRITICAL_RECEIVEDCritical threshold for network bytes received per second (B/s)
CRITICAL_STATUSDefine the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}%{status} !~ /connected/ || %{system_status} !~ /ok/
WARNING_STATUSDefine the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}
WARNING_TRANSMITTEDWarning threshold for network bytes transmitted per second (B/s)
CRITICAL_TRANSMITTEDCritical threshold for network bytes transmitted per second (B/s)
WARNING_WRITEWarning threshold for write throughput (B/s)
CRITICAL_WRITECritical threshold for write throughput (B/s)
WARNING_WRITE_IOPSWarning threshold for write IOPS
CRITICAL_WRITE_IOPSCritical threshold for write IOPS
EXTRA_OPTIONSAny extra option you may want to add to the command (a --verbose flag for example). All options are listed here.--verbose
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

How to check in the CLI that the configuration is OK and what are the main options for?​

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine). Test that the connector is able to monitor a resource using a command like this one (replace the sample values by yours):

/usr/lib/centreon/plugins/centreon_rubrik_graphql.pl \
	--plugin=apps::backup::rubrik::graphql::plugin \
	--mode=tasks \
	--hostname='dummy.my.rubrik.com' \
	--service-account='' \
	--secret='' \
	--port='443' \
	--proto='https' \
	--cluster='' \
	--include-cluster='' \
	--exclude-cluster='' \
	--timeout='120'  \
	--start-time='' \
	--end-time='' \
	--last='' \
	--task-category='' \
	--object-type='' \
	--task-status='' \
	--task-type='' \
	--display-on-status='canceled|failed' \
	--warning-succeeded='' \
	--critical-succeeded='' \
	--warning-failed='' \
	--critical-failed='' \
	--warning-canceled='' \
	--critical-canceled='' \
	--verbose

The expected command output is shown below:

OK: succeeded: 51099 failed: 8320 canceled: 76390 | 'tasks.succeeded.count'=51099;;;0; 'tasks.failed.count'=8320;;;0; 'tasks.canceled.count'=76390;;;0;

Troubleshooting​

Please find the troubleshooting documentation for Centreon Plugins typical issues.

Available modes​

In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins/centreon_rubrik_graphql.pl \
	--plugin=apps::backup::rubrik::graphql::plugin \
	--list-mode

The plugin brings the following modes:

ModeLinked service template
cluster [code]App-Rubrik-Cluster-Graphql-custom
compliance [code]App-Rubrik-Compliance-Graphql-custom
disks [code]App-Rubrik-Disks-Graphql-custom
jobs [code]App-Rubrik-Jobs-Graphql-custom
nodes [code]App-Rubrik-Nodes-Graphql-custom
storage [code]App-Rubrik-Storage-Graphql-custom
tasks [code]App-Rubrik-Tasks-Graphql-custom

Available options​

Generic options​

All generic options are listed here:

OptionDescription
--modeDefine the mode in which you want the plugin to be executed (see --list-mode).
--dyn-modeSpecify a mode with the module's path (advanced).
--list-modeList all available modes.
--mode-versionCheck minimal version of mode. If not, unknown error.
--versionReturn the version of the plugin.
--custommodeWhen a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option.
--list-custommodeList all available custom modes.
--multipleMultiple custom mode objects. This may be required by some specific modes (advanced).
--pass-managerDefine the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass.
--verboseDisplay extended status information (long output).
--debugDisplay debug messages.
--show-passwordBy default, sensitive information in command lines is hidden in debug output and replaced with *** (however, debug logs may still display sensitive information). Using the C option will display the passwords in plain text.
--filter-perfdataFilter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data.
--filter-perfdata-advFilter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value.
--explode-perfdata-maxCreate a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '_max' suffix. Example: it will split 'used_prct'=26.93%;0:80;0:90;0;100 into 'used_prct'=26.93%;0:80;0:90;0;100 'used_prct_max'=100%;;;;
--change-perfdata --extend-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()'
--change-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()'
--extend-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()'
--extend-perfdata-groupAdd new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,<names-of-new-metrics>,calculation[,[<new-unit-of-mesure>],[min],[max]] regex: regular expression <names-of-new-metrics>: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated <new-unit-of-mesure> (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: um wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets_wrong,sum(packets_(discard|error)_(in|out))' Sum traffic by interface: --extend-perfdata-group='traffic_in_(.*),traffic_$1,sum(traffic_(in|out)_$1)'
--change-short-output --change-long-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-short-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-long-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-exitReplace an exit code with one of your choice. Example: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state.
--change-output-advReplace short output and exit code based on a "if" condition using the following variables: short_output, exit_code. Variables must be written either %{variable} or %(variable). Example: adding --change-output-adv='%(short_ouput) =~ /UNKNOWN: No daemon/,OK: No daemon,OK' will change the following specific UNKNOWN result to an OK result.
--range-perfdataRewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata.
--filter-uomMask the units when they don't match the given regular expression.
--opt-exitReplace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown.
--output-ignore-perfdataRemove all the metrics from the service. The service will still have a status and an output.
--output-ignore-labelRemove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Example: 'OK: Ram Total:...' will become 'Ram Total:...'
--output-xmlReturn the output in XML format (to send to an XML API).
--output-jsonReturn the output in JSON format (to send to a JSON API).
--output-openmetricsReturn the output in OpenMetrics format (to send to a tool expecting this format).
--output-fileWrite output in file (can be combined with JSON, XML and OpenMetrics options). Example: --output-file=/tmp/output.txt will write the output in /tmp/output.txt.
--disco-formatApplies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML).
--disco-showApplies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery.
--float-precisionDefine the float precision for thresholds (default: 8).
--source-encodingDefine the character encoding of the response sent by the monitored resource Default: 'UTF-8'. <output>.
--filter-countersOnly display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$'
--warning-xxxWarning threshold.
--critical-xxxCritical threshold.
--http-peer-addrSet the address you want to connect to. Useful if hostname is only a vhost, to avoid IP resolution.
--proxyurlProxy URL. Example: http://my.proxy:3128
--proxypacProxy PAC file (can be a URL or a local file).
--insecureAccept insecure SSL connections.
--http-backendPerl library to use for HTTP transactions. Possible values are: lwp (default) and curl.
--memcachedMemcached server to use (only one server).
--redis-serverRedis server to use (only one server). Syntax: address[:port]
--redis-attributeSet Redis Options (--redis-attribute="cnx_timeout=5").
--redis-dbSet Redis database index.
--failback-fileFall back on a local file if Redis connection fails.
--memexpirationTime to keep data in seconds (default: 86400).
--statefile-dirDefine the cache directory (default: '/var/lib/centreon/centplugins').
--statefile-suffixDefine a suffix to customize the statefile name (default: '').
--statefile-concat-cwdIf used with the '--statefile-dir' option, the latter's value will be used as a sub-directory of the current working directory. Useful on Windows when the plugin is compiled, as the file system and permissions are different from Linux.
--statefile-formatDefine the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default).
--statefile-keyDefine the key to encrypt/decrypt the cache.
--statefile-cipherDefine the cipher algorithm to encrypt the cache (default: 'AES').
--hostnameSet hostname (Rubrik RSC tenant).
--portPort used (default: 443)
--protoProtocol used (default: 'https').
--service-accountService account ID (with --secret option).
--secretService account secret (with --service-account option).
--tokenUse token authentication. If option is specified, token is used directly instead of service account credentials.
--timeoutSet timeout in seconds (default: 120).
--unknown-http-statusUnknown HTTP status code.
--warning-http-statusWarning HTTP status code.
--critical-http-statusCritical HTTP status code.
--limitDefine the number of entries to retrieve for the pagination.
--disable-cacheDisable the cache feature.
--cache-ttlCache time to live in minutes (default: 240 = 4 hours).
--clusterFilter cluster. Multiple values can be separated by comma. This filter is passed directly to the GraphQL API (server-side filtering). Depending on its format this parameter is treated as either a name or a UUID.
--include-clusterInclude cluster (can be a regexp). Depending on its format this parameter is treated as either a name or a UUID.
--exclude-clusterExclude cluster (can be a regexp). Depending on its format this parameter is treated as either a name or a UUID.

Modes options​

All available options for each service template are listed below:

OptionDescription
--start-timeSet start time for filtering clusters by registration date. Accepts ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ), or YYYY-MM-DD, or YYYY-MM-DD HH:mm:ss.
--end-timeSet end time for filtering clusters by registration date. Accepts ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ), or YYYY-MM-DD, or YYYY-MM-DD HH:mm:ss.
--lastSet duration to filter last registered clusters. Use 'd' for day, 'h' for hour, 'm' for minute (e.g., 24h, 30m, 7d).
--unknown-statusDefine the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}
--warning-statusDefine the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}
--critical-statusDefine the conditions to match for the status to be CRITICAL (default: '%{status} !~ /connected/ || %{system_status} !~ /ok/'). You can use the following variables: %{status}, %{name}
--warning-readWarning threshold for read throughput (B/s).
--critical-readCritical threshold for read throughput (B/s).
--warning-writeWarning threshold for write throughput (B/s).
--critical-writeCritical threshold for write throughput (B/s).
--warning-read-iopsWarning threshold for read IOPS.
--critical-read-iopsCritical threshold for read IOPS.
--warning-write-iopsWarning threshold for write IOPS.
--critical-write-iopsCritical threshold for write IOPS.
--warning-receivedWarning threshold for network bytes received per second (B/s).
--critical-receivedCritical threshold for network bytes received per second (B/s).
--warning-transmittedWarning threshold for network bytes transmitted per second (B/s).
--critical-transmittedCritical threshold for network bytes transmitted per second (B/s).

All available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/centreon_rubrik_graphql.pl \
	--plugin=apps::backup::rubrik::graphql::plugin \
	--mode=tasks \
	--help