Available solutions
Oracle Cloud Block Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) block volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.4 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI block volumes automatically, create host prototypes for each discovered
block volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of {$OCI.HTTP.PROXY}
user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$HTTP.TLS.VERIFY} | TLS certificate verification for script items: "none" - disabled, "peer" - verify the certificate chain and expiration, "full" - full verification. Any other value enables full verification. To override the setting for this template only, define the macro with the context "Oracle Cloud Block Volume", e.g. {$HTTP.TLS.VERIFY:"Oracle Cloud Block Volume"}. |
full |
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the block volume state. |
Script | oci.block.volume.state Preprocessing
|
| Get metrics | Gets block volume metrics. |
Script | oci.block.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.block.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.block.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.block.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.block.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.block.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.block.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Block Volume: Block volume terminated or faulty | Block volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) >= 4 |
High | |
| OCI Block Volume: Block volume state unknown | Block volume state is unknown. |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Block Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) block volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.2 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI block volumes automatically, create host prototypes for each discovered
block volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of {$OCI.HTTP.PROXY}
user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the block volume state. |
Script | oci.block.volume.state Preprocessing
|
| Get metrics | Gets block volume metrics. |
Script | oci.block.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.block.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.block.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.block.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.block.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.block.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.block.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Block Volume: Block volume terminated or faulty | Block volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) >= 4 |
High | |
| OCI Block Volume: Block volume state unknown | Block volume state is unknown. |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Block Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) block volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.0 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI block volumes automatically, create host prototypes for each discovered
block volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of {$OCI.HTTP.PROXY}
user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$HTTP.TLS.VERIFY} | TLS certificate verification for script items: "none" - disabled, "peer" - verify the certificate chain and expiration, "full" - full verification. Any other value enables full verification. To override the setting for this template only, define the macro with the context "Oracle Cloud Block Volume", e.g. {$HTTP.TLS.VERIFY:"Oracle Cloud Block Volume"}. |
full |
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the block volume state. |
Script | oci.block.volume.state Preprocessing
|
| Get metrics | Gets block volume metrics. |
Script | oci.block.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.block.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.block.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.block.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.block.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.block.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.block.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Block Volume: Block volume terminated or faulty | Block volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) >= 4 |
High | |
| OCI Block Volume: Block volume state unknown | Block volume state is unknown. |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Block Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) block volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 6.4 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI block volumes automatically, create host prototypes for each discovered
block volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of {$OCI.HTTP.PROXY}
user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| OCI Block Volume: State | Gets the block volume state. |
Script | oci.block.volume.state Preprocessing
|
| OCI Block Volume: Get metrics | Gets block volume metrics. |
Script | oci.block.volume.metrics.get |
| OCI Block Volume: Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.read Preprocessing
|
| OCI Block Volume: Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.write Preprocessing
|
| OCI Block Volume: Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.block.volume.read.ops Preprocessing
|
| OCI Block Volume: Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.block.volume.write.ops Preprocessing
|
| OCI Block Volume: Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.block.volume.throttled.ops Preprocessing
|
| OCI Block Volume: Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.block.volume.vpu Preprocessing
|
| OCI Block Volume: Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.block.volume.iops Preprocessing
|
| OCI Block Volume: Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.block.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Block Volume: Block volume terminated or faulty | Block volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) >= 4 |
High | |
| OCI Block Volume: Block volume state unknown | Block volume state is unknown. |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Block Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) block volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 6.0 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI block volumes automatically, create host prototypes for each discovered
block volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of {$OCI.HTTP.PROXY}
user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| OCI Block Volume: State | Gets the block volume state. |
Script | oci.block.volume.state Preprocessing
|
| OCI Block Volume: Get metrics | Gets block volume metrics. |
Script | oci.block.volume.metrics.get |
| OCI Block Volume: Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.read Preprocessing
|
| OCI Block Volume: Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.block.volume.write Preprocessing
|
| OCI Block Volume: Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.block.volume.read.ops Preprocessing
|
| OCI Block Volume: Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.block.volume.write.ops Preprocessing
|
| OCI Block Volume: Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.block.volume.throttled.ops Preprocessing
|
| OCI Block Volume: Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.block.volume.vpu Preprocessing
|
| OCI Block Volume: Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.block.volume.iops Preprocessing
|
| OCI Block Volume: Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.block.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Block Volume: Block volume terminated or faulty | Block volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) >= 4 |
High | |
| OCI Block Volume: Block volume state unknown | Block volume state is unknown. |
min(/Oracle Cloud Block Volume by HTTP/oci.block.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Boot Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) boot volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.4 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI boot volumes automatically, create host prototypes for each discovered
boot volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of the
{$OCI.HTTP.PROXY} user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$HTTP.TLS.VERIFY} | TLS certificate verification for script items: "none" - disabled, "peer" - verify the certificate chain and expiration, "full" - full verification. Any other value enables full verification. To override the setting for this template only, define the macro with the context "Oracle Cloud Boot Volume", e.g. {$HTTP.TLS.VERIFY:"Oracle Cloud Boot Volume"}. |
full |
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the boot volume state. |
Script | oci.boot.volume.state Preprocessing
|
| Get metrics | Gets boot volume metrics. |
Script | oci.boot.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.boot.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.boot.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.boot.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.boot.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.boot.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.boot.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Boot Volume: Boot volume terminated or faulty | Boot volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) >= 4 |
High | |
| OCI Boot Volume: Boot volume state unknown | Boot volume state is unknown. |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Boot Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) boot volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.2 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI boot volumes automatically, create host prototypes for each discovered
boot volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of the
{$OCI.HTTP.PROXY} user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the boot volume state. |
Script | oci.boot.volume.state Preprocessing
|
| Get metrics | Gets boot volume metrics. |
Script | oci.boot.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.boot.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.boot.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.boot.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.boot.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.boot.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.boot.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Boot Volume: Boot volume terminated or faulty | Boot volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) >= 4 |
High | |
| OCI Boot Volume: Boot volume state unknown | Boot volume state is unknown. |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Boot Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) boot volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 7.0 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI boot volumes automatically, create host prototypes for each discovered
boot volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of the
{$OCI.HTTP.PROXY} user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$HTTP.TLS.VERIFY} | TLS certificate verification for script items: "none" - disabled, "peer" - verify the certificate chain and expiration, "full" - full verification. Any other value enables full verification. To override the setting for this template only, define the macro with the context "Oracle Cloud Boot Volume", e.g. {$HTTP.TLS.VERIFY:"Oracle Cloud Boot Volume"}. |
full |
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| State | Gets the boot volume state. |
Script | oci.boot.volume.state Preprocessing
|
| Get metrics | Gets boot volume metrics. |
Script | oci.boot.volume.metrics.get |
| Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.read Preprocessing
|
| Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.write Preprocessing
|
| Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.boot.volume.read.ops Preprocessing
|
| Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.boot.volume.write.ops Preprocessing
|
| Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.boot.volume.throttled.ops Preprocessing
|
| Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.boot.volume.vpu Preprocessing
|
| Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.boot.volume.iops Preprocessing
|
| Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.boot.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Boot Volume: Boot volume terminated or faulty | Boot volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) >= 4 |
High | |
| OCI Boot Volume: Boot volume state unknown | Boot volume state is unknown. |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Boot Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) boot volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 6.4 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI boot volumes automatically, create host prototypes for each discovered
boot volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of the
{$OCI.HTTP.PROXY} user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| OCI Boot Volume: State | Gets the boot volume state. |
Script | oci.boot.volume.state Preprocessing
|
| OCI Boot Volume: Get metrics | Gets boot volume metrics. |
Script | oci.boot.volume.metrics.get |
| OCI Boot Volume: Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.read Preprocessing
|
| OCI Boot Volume: Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.write Preprocessing
|
| OCI Boot Volume: Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.boot.volume.read.ops Preprocessing
|
| OCI Boot Volume: Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.boot.volume.write.ops Preprocessing
|
| OCI Boot Volume: Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.boot.volume.throttled.ops Preprocessing
|
| OCI Boot Volume: Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.boot.volume.vpu Preprocessing
|
| OCI Boot Volume: Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.boot.volume.iops Preprocessing
|
| OCI Boot Volume: Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.boot.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Boot Volume: Boot volume terminated or faulty | Boot volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) >= 4 |
High | |
| OCI Boot Volume: Boot volume state unknown | Boot volume state is unknown. |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) = 0 |
Warning | Depends on:
|
Oracle Cloud Boot Volume by HTTP
Overview
This template monitors Oracle Cloud Infrastructure (OCI) boot volume resources.
This template is not meant to be used independently, but together with Oracle Cloud by HTTP as a template for LLD host prototypes.
For communication with OCI, this template utilizes script items which execute HTTP GET and POST requests.
POST requests are required for OCI Monitoring API as it utilizes Monitoring Query Language (MQL) which uses
HTTP request body for queries.
Requirements
Zabbix version: 6.0 and higher.
Tested versions
This template has been tested on:
- Oracle Cloud Infrastructure
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
This template is not meant to be used independently. A host with the Oracle Cloud by HTTP template will
discover OCI boot volumes automatically, create host prototypes for each discovered
boot volume, and apply it this template.
If needed, you can specify an HTTP proxy for the template to use by changing the value of the
{$OCI.HTTP.PROXY} user macro.
If using a proxy, the returned OK HTTP response could change from "200" to a different value. In that case,
please adjust the user macro {$OCI.HTTP.RETURN.CODE.OK}
LLD filter values and trigger threshold values can be changed with respective user macros.
Macros used
| Name | Description | Default |
|---|---|---|
| {$OCI.HTTP.PROXY} | Set an HTTP proxy for OCI API requests if needed. |
|
| {$OCI.HTTP.RETURN.CODE.OK} | Set the HTTP return code that represents an OK response from the API. The default is "200", but can vary, for example, if a proxy is used. |
200 |
Items
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| OCI Boot Volume: State | Gets the boot volume state. |
Script | oci.boot.volume.state Preprocessing
|
| OCI Boot Volume: Get metrics | Gets boot volume metrics. |
Script | oci.boot.volume.metrics.get |
| OCI Boot Volume: Volume read throughput | Read throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.read Preprocessing
|
| OCI Boot Volume: Volume write throughput | Write throughput. Expressed as bytes read per interval. |
Dependent item | oci.boot.volume.write Preprocessing
|
| OCI Boot Volume: Volume read operations | Activity level from I/O reads. Expressed as reads per interval. |
Dependent item | oci.boot.volume.read.ops Preprocessing
|
| OCI Boot Volume: Volume write operations | Activity level from I/O writes. Expressed as writes per interval. |
Dependent item | oci.boot.volume.write.ops Preprocessing
|
| OCI Boot Volume: Volume throttled operations | Total sum of all the I/O operations that were throttled during a given time interval. |
Dependent item | oci.boot.volume.throttled.ops Preprocessing
|
| OCI Boot Volume: Volume guaranteed VPUs/GB | Rate of change for currently active VPUs/GB. Expressed as the average of active VPUs/GB during a given time interval. |
Dependent item | oci.boot.volume.vpu Preprocessing
|
| OCI Boot Volume: Volume guaranteed IOPS | Rate of change for guaranteed IOPS per SLA. Expressed as the average of guaranteed IOPS during a given time interval. |
Dependent item | oci.boot.volume.iops Preprocessing
|
| OCI Boot Volume: Volume guaranteed throughput | Rate of change for guaranteed throughput per SLA. Expressed as megabytes per interval. |
Dependent item | oci.boot.volume.throughput Preprocessing
|
Triggers
| Name | Description | Expression | Severity | Dependencies and additional info |
|---|---|---|---|---|
| OCI Boot Volume: Boot volume terminated or faulty | Boot volume state is "terminated"/"terminating" or "faulty". |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) >= 4 |
High | |
| OCI Boot Volume: Boot volume state unknown | Boot volume state is unknown. |
min(/Oracle Cloud Boot Volume by HTTP/oci.boot.volume.state,5m) = 0 |
Warning | Depends on:
|
