I agree that the API needs more support for developers. However, the majority of customers looking to do something like you're doing actually do use the rsyslog to auto process events. An rsyslog server can easily parse out the event for you, you just need to look for certain event types which are doc'd by DS8000 and then tell the syslog server what the events are and what to do should they get the event. And most rsyslog servers provide hooks into ticketing systems now adays.
But please open the RFE so that we can look at returning whether an event is active or inactive as well.
Original Message:
Sent: Mon March 27, 2023 06:44 AM
From: Hlynur Kristjánsson
Subject: DS8000 API for monitoring
Thank you for the suggestions but I'm not looking to parse and handle every event, that would entail a considerably more complex solution than simply asking the array what is currently wrong with it and forwarding that to our monitoring and ticketing systems. The Array maintains this information and is capable of presenting it, but for some reason this information doesn't seem to be available via the API interface. The API doesn't seem to get a lot of love from the developers and is very limited in it's features compared to other storage platforms, even IBMs own storwize.
I'll look for other methods access this information, thank you again for your responses.
------------------------------
Hlynur Kristjánsson
Original Message:
Sent: Fri March 17, 2023 06:02 AM
From: Hlynur Kristjánsson
Subject: DS8000 API for monitoring
I'm trying to set up some basic monitoring of a DS8000 system using the API reference as a guide. I'd like to be able to query the system every few minutes and filter out active errors/warnings for our monitoring systems.
https://publibfp.dhe.ibm.com/epubs/pdf/c2798230.pdf
Can anyone here clarify for me if it is possible to filter events by active / inactive status via the API like you can do via the UI?
The limited information in the API doc doesn't provide a way to do this. The parameters returned in the query do not indicate whether the event is inactive either.
Query
GET /v1/events[?severity=info,warning,error&after=2014-04-20T13:00:00+0800&before=2014-04-20T13:00:59+0800]
Response
...
"id" : "SE..."
"type" : "PoolCapacityChanged" ,
"severity" : "error",
"time" : "2014-04-20T13:00:23-0700",
"resource_id" : "",
"formatted_parameter" : [ ]
...
When I issue the query I end up with a bunch of warnings and errors and have no way of verifying if they are still relevant or have already been addressed.
Any suggestions?
------------------------------
Hlynur Kristjánsson
------------------------------