zbx-hpmsa

Utility for retrieve hardware info and stats about HPE MSA storages via XML API for Zabbix Monitoring Platform.
Zabbix Share page: https://share.zabbix.com/component/mtree/storage-devices/hp/hp-msa-2040-xml-api

zbx-hpmsa provides ability to make Low Level Discovery (LLD) of HPE MSA storage components via it's XML API and retrieve many of some other metrics like health statuses, temperature etc.
Developed with Python 3.7, works with Python 3.4 and higher.

Latest stable versions: 0.7.4

Please, read Requirements and Installation section on Wiki page before use.

v0.6 vs v0.7

There are a couple of important changes in v0.7 of the script:

Removed 'health' argument. It was used for working with old Zabbix versions, which doesn't support JSONPath preprocessing (like 3.0 and 3.2). So, version 0.7 supports only Zabbix 4.0 and 4.2; 3.4 also will work, but LLD doesn't;
Version 0.7 breaks compatibility with template distributed for version 0.6.x. Now, master item contains JSON with shorten key names.
E.g. version 0.6.8 outpul was:

[root@server ~]# ./zbx-hpmsa_v0.6.8.py full storage-ip-address fans
{"fan_1.1":{"health-num":"0","status-num":"0","speed":"3770"},"fan_1.2":{"health-num":"0","status-num":"0","speed":"3910"}}

And from 0.7 it becomes like that:

[root@server ~]# ./zbx-hpmsa_v0.7.py full storage-ip-address fans
{"fan_1.1":{"h":"0","s":"0","sp":"3910"},"fan_1.2":{"h":"0","s":"0","sp":"3920"}}

I hope it will reduce total received bytes by Zabbix database.

Also, version 0.7 contains two new cli arguments: '--pretty' and '--human'. The first one is for printing JSON with linebeaks and the second for translate shorten JSON keys to full human readable names.

[root@server ~]# ./zbx-hpmsa_v0.7.py --pretty full storage-ip-address fans
{
  "fan_1.1":{
    "h":"0",
    "s":"0",
    "sp":"3900"
  },
  "fan_1.2":{
    "h":"0",
    "s":"0",
    "sp":"3930"
  }
}
[root@server ~]# ./zbx-hpmsa_v0.7.py --human --pretty full storage-ip-address fans
{
  "fan_1.1":{
    "health":"0",
    "status":"0",
    "speed":"3890"
  },
  "fan_1.2":{
    "health":"0",
    "status":"0",
    "speed":"3930"
  }
}

Dependencies

requests
sqlite3

Feautres

Common:

Bulk requests for dependent items (Zabbix 4.0+)
HTTPS support
Login cache (SQLite3)
'install' argument to prepare script to work

LLD and full data in JSON:

Usage

You can find more examples on Wiki page, but I placed some cases here too.

LLD of enclosures, controllers, virtual disks and physical disks:

[root@server ~] # ./zbx-hpmsa.py lld 10.0.0.1 volumes
{"data":[{"{#VOLUME.ID}":"Test_Volume","{#VOLUME.SN}":"00c0ff2896a400008fb7265a01000000","{#VOLUME.TYPE}":"standard"}}

Request full available data in JSON. E.g. all disks:

[root@server ~] # ./zbx-hpmsa.py full 10.0.0.1 disks
{"1.1":{"h":"0","t":"25","ts":"1","cj":"0","poh":"15050"},"1.2":{"h":"0","t":"25","ts":"1","cj":"0","poh":"15050"}, ... }

Zabbix templates

In addition I've attached preconfigured Zabbix Templates here, so you can use them in your environment and build your own template based on it.
Templates using LLD functionality and {HOST.CONN} macro to determine HTTP(S) connection URL, so make sure that it points to right DNS name or IP and your MSA has HTTP(S) protocol enabled.
Also template expects what MSA storage has default user with default password - 'monitor'@'!monitor', but if it isn't true - correct it with '-u' and '-p' or '-f|--login-file' options.
If you want to use HTTPS, you must correct template and be sure what {HOST.CONN} macro contains FQDN. By the way, look at relevant Wiki page for HTTPS support.
Started with version v0.5.4 I've attached new template file for Zabbix 4.0, which using dependent items functionality and can retrieve much more metrics from storage than earlier versions. Check Wiki to read more about it or if you speak russian look at my post on habr.com.

Have fun and don't forget to rate it on share.zabbix.com if you like it. =)

Tested myself with:
HPE MSA 2040, HPE MSA 2050

Reported about correct working with
HP MSA P2000 G3, HP MSA2324FC (2000 G2 series, I think, will works too)

Known Issues: