We would need the information on the number of retries done from the AIOps when the ITSM system is down.
Release : SaaS
Component : CA DOI NOTIFICATIONS
ITSM retries for 5 times. And the retry is exponential. If first retry is after 5 secs, then next retry will be at 25 secs, then next will be at 125 secs and so on for 5 times.
And in case of NIM pod, for unauthorized error (401) there is one retry.
5n |
Value | Time | Notes |
0 | |||
1 | 5 | ||
2 | 25 | ||
3 | 125 | 2.08 | |
4 | 625 | 10.42 | |
5 | 3125 | 52.08 | 1 hr 2 mins 30 secs |
Consider after 20 mins the ITSM system comes to normal then will the ticket get created on 21st min or will it wait for the next retry at 1 hr. -->
A. It will wait for the next retry at 1hr . But if the same alarm updated in between, then previous copy of the alarm which is in cache will be evicted and then the process will again start with the updated alarm (start from attempt 1) .