Hi Arun,
thanks for your reply. I am wondering, there is no need to create db rights for events:
Enabled database
views
So my customer wants to have a report of all performance threshold violation. Which create an Event:
e.g. here the view:
output
http://vsa014622:8080/dfm/report/view/events-history/39464
vnsa1177:/vol2_H3I Report | Link to report data in spreadsheet format Add to Favorites |
Events: 1-20 of 158 Page: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8Next Show Maximum
Sev. Event Triggered (descending) Ack'ed By Ack'ed Deleted By Deleted Source
Normal perf:VOLUME_READ_LATENCY:normal 14 Aug 03:10 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 14 Aug 03:04 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 09 Aug 03:09 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 09 Aug 03:05 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 05 Aug 03:03 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 05 Aug 02:51 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 05 Aug 01:30 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 05 Aug 01:25 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 29 Jul 02:17 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 29 Jul 02:12 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 29 Jul 01:43 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 29 Jul 01:31 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 24 Jul 03:09 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 24 Jul 03:03 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 22 Jul 03:27 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 22 Jul 02:27 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 22 Jul 02:13 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 22 Jul 02:08 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Normal perf:VOLUME_READ_LATENCY:normal 22 Jul 01:38 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Error perf:VOLUME_READ_LATENCY:breached 22 Jul 01:29 |
|
|
| Clustered Volume vnsa1177:/vol2_H3I |
Here we want to count the time how long a performance degradion was in sum. This for each volume and rate the volumes with the highest values. Then can make a decission to look closer o that volume with performance advisor to find out the problem. Hopefully Oncommand Insight Report can help here. Otherwise we have to write our own scripts. Or using tools like splunk to combine queries for a report.
Best wishes,
Markus.