You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deployment/index.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ password: examplepassword
14
14
15
15
The `address` value is either a resolvable hostname or IP address of the management interface on the storage system. The `username` value identifies a storage system user with privileges described below.
16
16
17
-
| Storage System | User Type | Minimal Role | Open Ports Requirements |
Include the `--accept-eula` option or set the environment variable `ACCEPT_HPE_STANDARD_EULA=yes` to confirm your acceptance of the [HPE license restrictions](../legal/eula/index.md).
57
61
58
62
59
63
# Using a Container Image
60
64
61
-
A container image is hosted at `quay.io/hpestorage/array-exporter:v1.0.3`, with v1.0.3 replaced by the desired release version.
65
+
A container image is hosted at `quay.io/hpestorage/array-exporter:v1.0.4`, with v1.0.4 replaced by the desired release version.
62
66
63
67
When deploying the array exporter as a container, the configuration file must be mounted as a volume.
64
68
@@ -71,13 +75,13 @@ In this example, the configuration file at `/tmp/storage-system.yaml` is bound t
71
75
```markdown
72
76
docker run -it --name hpe-array-exporter -p 9090:8080 \
Include the `--accept-eula` option or set the environment variable `ACCEPT_HPE_STANDARD_EULA=yes` to confirm your acceptance of the [HPE license restrictions](/legal/eula/index.html).
84
+
Include the `--accept-eula` option or set the environment variable `ACCEPT_HPE_STANDARD_EULA=yes` to confirm your acceptance of the [HPE license restrictions](../legal/eula/index.md).
81
85
82
86
Consult the [Docker command line documentation](https://docs.docker.com/engine/reference/commandline/run/) for more information on running containers using Docker.
Copy file name to clipboardExpand all lines: docs/index.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,17 @@ This documentation shows how to [deploy](deployment/index.md) the exporter, the
10
10
11
11
HPE Storage Array Exporter for Prometheus is compatible with these storage arrays:
12
12
13
-
* HPE Alletra Storage MP Block
13
+
* HPE Alletra Storage MP B10000<sup>1</sup>
14
14
* HPE Alletra 9000
15
15
* HPE Alletra 5000/6000
16
16
* HPE Nimble Storage
17
17
* HPE Primera
18
18
* HPE 3PAR
19
19
20
+
<small>
21
+
<sup>1</sup> = The B10000 platform from release 10.4 has its own [onboard exporter](onboard/index.md) and customers are recommended to use that. The external HPE Storage Array Exporter for Prometheus is not guaranteed future compatibility with the B10000 platform.
22
+
</small>
23
+
20
24
See the [compatibility chart](releases/index.md) for specific versions and releases.
Copy file name to clipboardExpand all lines: docs/integration/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ It's most common to have scrape targets statically defined in a Prometheus confi
15
15
16
16
When running Prometheus as either a standalone executable or a container, a [configuration file](https://prometheus.io/docs/prometheus/latest/configuration/configuration/) (conventionally named prometheus.yml) is used. In it, a scrape job can be added for the exporter with configuration content similar to the following example.
17
17
18
-
```markdown
18
+
```yaml
19
19
scrape_configs:
20
20
- job_name: 'hpe-array-exporter'
21
21
# A scrape interval of 30 seconds or more is recommended
@@ -54,7 +54,7 @@ The ServiceMonitor's `namespaceSelector` and `selector` fields in turn control h
Copy file name to clipboardExpand all lines: docs/metrics/index.md
+21-17Lines changed: 21 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,19 +4,22 @@ The metrics provided by the HPE Storage Array Exporter for Prometheus vary accor
4
4
5
5
[TOC]
6
6
7
-
## HPE Alletra 9000and Primera
7
+
## Alletra Storage MP B10000, Alletra 9000, Primera and 3PAR
8
8
9
-
The metrics provided for HPE Alletra 9000 and Primera storage systems (3PAR is also supported) are equivalent, with the metric names reflecting the storage system type.
9
+
The metrics provided for 3PAR derived systems are equivalent, with the metric names reflecting the storage system type.
10
+
11
+
!!! error "Recommendation"
12
+
For HPE Alletra Storage MP B10000 it's recommended to use the [onboard exporter](../onboard/index.md).
10
13
11
14
### Common Provisioning Group (CPG) Space
12
15
13
16
| Metric | Type | Description |
14
17
| :--- | :--- | :--- |
15
-
| hpealletra9000_cpg_capacity_bytes<br/>hpeprimera_cpg_capacity_bytes<br/>hpe3par_cpg_capacity_bytes | Gauge | Total capacity allocated to a CPG |
16
-
| hpealletra9000_cpg_used_bytes<br/>hpeprimera_cpg_used_bytes<br/>hpe3par_cpg_used_bytes | Gauge | CPG capacity in use |
17
-
| hpealletra9000_cpg_available_bytes<br/>hpeprimera_cpg_available_bytes<br/>hpe3par_cpg_available_bytes | Gauge | CPG capacity available |
|hpealletrastoragemp_cpg_capacity_bytes<br/>hpealletra9000_cpg_capacity_bytes<br/>hpeprimera_cpg_capacity_bytes<br/>hpe3par_cpg_capacity_bytes | Gauge | Total capacity allocated to a CPG |
19
+
|hpealletrastoragemp_cpg_used_bytes<br/>hpealletra9000_cpg_used_bytes<br/>hpeprimera_cpg_used_bytes<br/>hpe3par_cpg_used_bytes | Gauge | CPG capacity in use |
20
+
|hpealletrastoragemp_cpg_available_bytes<br/>hpealletra9000_cpg_available_bytes<br/>hpeprimera_cpg_available_bytes<br/>hpe3par_cpg_available_bytes | Gauge | CPG capacity available |
21
+
|hpealletrastoragemp_cpg_volume_used_bytes<br/>hpealletra9000_cpg_volume_used_bytes<br/>hpeprimera_cpg_volume_used_bytes<br/>hpe3par_cpg_volume_used_bytes | Gauge | CPG capacity reserved for volumes |
22
+
|hpealletrastoragemp_cpg_snapshot_used_bytes<br/>hpealletra9000_cpg_snapshot_used_bytes<br/>hpeprimera_cpg_snapshot_used_bytes<br/>hpe3par_cpg_snapshot_used_bytes | Gauge | CPG capacity reserved for snapshots |
20
23
21
24
Each of these metrics includes the following label.
22
25
@@ -28,9 +31,10 @@ Each of these metrics includes the following label.
| hpealletra9000_volume_used_bytes<br/>hpeprimera_volume_used_bytes<br/>hpe3par_volume_used_bytes | Gauge | cpg, provisioning, volume | Space used for volume data, including reserved space for a fully-provisioned volume |
33
36
| hpealletra9000_volume_snapshot_used_bytes<br/>hpeprimera_volume_snapshot_used_bytes<br/>hpe3par_volume_snapshot_used_bytes | Gauge | cpg, provisioning, snap_cpg, volume | Space used for volume snapshots |
37
+
| hpealletrastoragemp_volume_total_used_bytes | Gauge | cpg, provisioning, snap_cpg, volume | Space used for both user data and volume snapshots |
34
38
35
39
The labels have the following meanings.
36
40
@@ -45,12 +49,12 @@ The labels have the following meanings.
45
49
46
50
| Metric | Type | Description |
47
51
| :--- | :--- | :--- |
48
-
| hpealletra9000_volume_reads_per_second_avg5m<br/>hpeprimera_volume_reads_per_second_avg5m<br/>hpep3par_volume_reads_per_second_avg5m | Gauge | Read operations performed on the VLUNs for a volume per second, averaged over a fixed five-minute interval (read IOPS) |
49
-
| hpealletra9000_volume_writes_per_second_avg5m<br/>hpeprimera_volume_writes_per_second_avg5m<br/>hpe3par_volume_writes_per_second_avg5m | Gauge | Write operations performed on the VLUNs for a volume per second, averaged over a fixed five-minute interval (write IOPS) |
50
-
| hpealletra9000_volume_read_bytes_per_second_avg5m<br/>hpeprimera_volume_read_bytes_per_second_avg5m<br/>hpe3par_volume_read_bytes_per_second_avg5m | Gauge | Bytes read from the VLUNs for a volume per second, averaged over a fixed five-minute interval (read throughput) |
51
-
| hpealletra9000_volume_write_bytes_per_second_avg5m<br/>hpeprimera_volume_write_bytes_per_second_avg5m<br/>hpe3par_volume_write_bytes_per_second_avg5m | Gauge | Bytes written to the VLUNs for a volume per second, averaged over a fixed five-minute interval (write throughput) |
52
-
| hpealletra9000_volume_seconds_per_read_avg5m<br/>hpeprimera_volume_seconds_per_read_avg5m<br/>hpe3par_volume_seconds_per_read_avg5m | Gauge | Seconds elapsed during a single read from the VLUNs for a volume, averaged over a fixed five-minute interval (read latency) |
53
-
| hpealletra9000_volume_seconds_per_write_avg5m<br/>hpeprimera_volume_seconds_per_write_avg5m<br/>hpe3par_volume_seconds_per_write_avg5m | Gauge | Seconds elapsed during a single write to the VLUNs for a volume, averaged over a fixed five-minute interval (write latency) |
52
+
|hpealletrastoragemp_volume_reads_per_second_avg5m<br/>hpealletra9000_volume_reads_per_second_avg5m<br/>hpeprimera_volume_reads_per_second_avg5m<br/>hpep3par_volume_reads_per_second_avg5m | Gauge | Read operations performed on the VLUNs for a volume per second, averaged over a fixed five-minute interval (read IOPS) |
53
+
|hpealletrastoragemp_volume_writes_per_second_avg5m<br/>hpealletra9000_volume_writes_per_second_avg5m<br/>hpeprimera_volume_writes_per_second_avg5m<br/>hpe3par_volume_writes_per_second_avg5m | Gauge | Write operations performed on the VLUNs for a volume per second, averaged over a fixed five-minute interval (write IOPS) |
54
+
|hpealletrastoragemp_volume_read_bytes_per_second_avg5m<br/>hpealletra9000_volume_read_bytes_per_second_avg5m<br/>hpeprimera_volume_read_bytes_per_second_avg5m<br/>hpe3par_volume_read_bytes_per_second_avg5m | Gauge | Bytes read from the VLUNs for a volume per second, averaged over a fixed five-minute interval (read throughput) |
55
+
|hpealletrastoragemp_volume_write_bytes_per_second_avg5m<br/>hpealletra9000_volume_write_bytes_per_second_avg5m<br/>hpeprimera_volume_write_bytes_per_second_avg5m<br/>hpe3par_volume_write_bytes_per_second_avg5m | Gauge | Bytes written to the VLUNs for a volume per second, averaged over a fixed five-minute interval (write throughput) |
56
+
|hpealletrastoragemp_volume_seconds_per_read_avg5m<br/>hpealletra9000_volume_seconds_per_read_avg5m<br/>hpeprimera_volume_seconds_per_read_avg5m<br/>hpe3par_volume_seconds_per_read_avg5m | Gauge | Seconds elapsed during a single read from the VLUNs for a volume, averaged over a fixed five-minute interval (read latency) |
57
+
|hpealletrastoragemp_volume_seconds_per_write_avg5m<br/>hpealletra9000_volume_seconds_per_write_avg5m<br/>hpeprimera_volume_seconds_per_write_avg5m<br/>hpe3par_volume_seconds_per_write_avg5m | Gauge | Seconds elapsed during a single write to the VLUNs for a volume, averaged over a fixed five-minute interval (write latency) |
54
58
55
59
Each of these metrics includes the following labels.
56
60
@@ -59,12 +63,12 @@ Each of these metrics includes the following labels.
59
63
| cpg | Name of the CPG containing the volume |
60
64
| volume | Volume name |
61
65
62
-
## HPE Alletra 5000/6000 and Nimble
66
+
## Alletra 5000/6000 and Nimble Storage
63
67
64
-
The metrics provided for HPE Alletra 5000/6000 and Nimble Storage systems are equivalent, with the metric names reflecting the storage system type.
68
+
The metrics provided for Alletra 5000/6000 and Nimble Storage systems are equivalent, with the metric names reflecting the storage system type.
65
69
66
70
!!! note
67
-
HPE Alletra 5000 metrics will appear as "hpealletra6000".
71
+
Alletra 5000 metrics will appear as "hpealletra6000".
0 commit comments