The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

Looking for the Perfect Dashboard: InfluxDB, Telegraf and Grafana – Part XXVIII (Monitoring HPE StoreOnce)

- Written in: hpe, opensource

Greetings friends, a new week is a week with a new dashboard, this is so, I would like to be able to offer you many more use cases, with many other technologies, but time is very limited and I only have some nights to prepare this.

Today we are going to see a very interesting topic, I was talking about HPE StoreOnce in previous posts, so as you can imagine, today this Dashboard is about this technology, from which we will extract information using the RESTful API that it brings with it.

Once you have finished this tutorial, you will have something similar to this, it is better to give it several days or weeks to see the full potential:

In awesome light-mode:In the always Matrix-look dark-mode:

RESTful API topology, InfluxDB and Grafana monitoring disk usage and much more about HPE StoreOnce

Although I have already shown you in some occasions the diagram of how would be the monitoring using Grafana and InfluxDB, I leave you again the diagram, this time monitoring all the information of HPE StoreOnce thanks to its RESTful API:

We will be able to create a user with only privileges to see graphs in HPE StoreOnce, in the following way, inside our interface, in Settings – Users and Groups:

We can click now in Add user or group: We can select between Local user, Directory User or Group, select the one that you are using, with a new username and pass, and select the role Observer:

Download and configure the hpe_storeonce_grafana.sh script

We will download the script that will make all this work, we will download the latest version from the Github repository:

This shell script should be run from anywhere you have a Linux, for example the Grafana server is fine. We will have to edit the configuration parameters:

##
# Configurations
##
# Endpoint URL for InfluxDB
InfluxDBURL="http://YOURINFLUXSERVER" #Your InfluxDB Server, http://FQDN or https://FQDN if using SSL
InfluxDBPort="8086" #Default Port
InfluxDB="telegraf" #Default Database
InfluxDBUser="INFLUXUSER" #User for Database
InfluxDBPassword='INFLUXPASS' #Password for Database

# Endpoint URL for login action
storeonceUsername="HPEUSERNAME" #Your username, if using domain based account, please add it like [email protected] (if you use domain\account it is not going to work!)
storeoncePassword='HPEPASS'
storeonceRestServer="https://STOREONCEFQDNORIP"
storeonceRestPort="443" #Default Port

Let’s make it executable with the next command:

chmod +x hpe_storeonce_grafana.sh

We will make sure we have jq installed, an apt-get install jq or yum install jq if we use CentOS:

sudo apt-get install jq

We can run it now with the next command ./hpe_storeonce_grafana.sh and if everything has run smoothly, here will be the output:

Writing hpe_storeonce_parametrics Operations to InfluxDB
HTTP/1.1 204 No Content
Content-Type: application/json
Request-Id: ee3d9629-f0ef-11ea-ae91-dca632b112f7
X-Influxdb-Build: OSS
X-Influxdb-Version: 1.8.2
X-Request-Id: ee3d9629-f0ef-11ea-ae91-dca632b112f7
Date: Mon, 07 Sep 2020 09:53:07 GMT

Also, it would be nice to put it in the cron to run every 30 minutes, maybe every 15, or less, it’s up to you:

sudo crontab -e
*/30 * * * * /home/oper/hpe_storeonce_grafana.sh >> /var/log/hpestoreonce.log 2>&1

That’s it, let’s move to the next step.

Grafana Dashboard

I have created a Dashboard from scratch selecting the best requests to the database, finishing colors, thinking about graphics and how to show them, and also everything is automated so that it fits our environment without any problem and without having to edit anything manually. The Dashboard can be found here, once imported, you can see all the graphics:

How to easily Import the Grafana Dashboard

So that you don’t have to waste hours configuring a new dashboard, and ingesting and debugging you want, I have already created four wonderful dashboards with everything necessary to monitor our environment in a very simple way, it will look like the image I showed you above. Select the name you want and enter the ID: 12881, which is the unique ID of the Dashboard, or the URL:

We’ll have everything popping up without any problem: I hope you like it, and I would like to leave you the complete series here, so you can start playing with the plugins that I have been telling you about all these years:

Reader Interactions

Comments

  1. squawell says

    Hi sir,I have a question,does this script support HPE Storeonce 3520(FW:3.18.18-1945.1) ?Because,when i try to excute , i got this error:

    Writing hpe_storeonce_dashboard to InfluxDB
    HTTP/1.1 400 Bad Request
    Content-Type: application/json
    Request-Id: b31977eb-8176-11eb-83db-000c29fe5038
    X-Influxdb-Build: OSS
    X-Influxdb-Error: unable to parse ‘hpe_storeonce_dashboard,hpehostname=,hpeproduct=,hpeserialnumber=,hpeversion= hpelocaldisk=,hpelocaluser=,hpelocalfree=,hpelocalcapacity=,hpeclouddisk=,hpeclouduser=,hpecloudfree=,hpecloudcapacity=,hpecatalyst=,hpecloudbank=,hpenasshares=,hpevtl=,hpenasreplica=,hpevtlreplica=,hpededuperatio=,hpecapacitysaved=,hpecapacitysavedpercent=’: missing tag value

    username and password is correct.

  3. haiph says

    Hello jorgedelacruz

    I have errro as below when run script hpe_storeonce_grafana.sh. Can you help me check it.
    curl: (3) Bad URL, colon is first character

  4. haiph says

    Hello
    After deploy follow intruction i see error as below , can you help me check ?
    {“code”:”unauthorized”,”message”:”Unauthorized”}Writing hpe_storeonce_parametrics CPU to InfluxDB
    HTTP/1.1 401 Unauthorized
    Content-Type: application/json; charset=utf-8
    X-Influxdb-Build: OSS
    X-Influxdb-Version: v2.7.4
    X-Platform-Error-Code: unauthorized
    Date: Fri, 15 Dec 2023 06:55:18 GMT
    Content-Length: 48

  5. dave says

    haiph, seems your issue is that you’re connecting to an influxdb version 2.7.4 while this is meant to v1.8.2 as per the post.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.