Anyone knows a fix for this issue
Or how I can make an event request from ocum 9.10 or 9.9 and use the severity filter to get only events that are warning critical or error severity.
1 messages · Page 1 of 1 (latest)
Anyone knows a fix for this issue
Or how I can make an event request from ocum 9.10 or 9.9 and use the severity filter to get only events that are warning critical or error severity.
/api/management-server/events?severity=warning
Only one severity can be specified in the request at a time.
Well in 9.6 u could have specified 3 severities in a request by sending the following:
/api/management-server/events?severity=warning|critical|error
Is there no longer a way to that?
Using a , or | results in a
{
"error": {
"message": "No enum constant com.netapp.dfm.entity.platform.event.EventSeverity.warning,critical",
"target": null,
"code": null
}
}
It appears to only accept a single value.