1 person found this helpful
From the SR and our previous discussion with development: this is environmental and due to network latency.
For understanding the error: Usage Meter is failing to get a full reply from all endpoints added to Usage Meter within 45 minutes. We can not increase the timeout. Investigation has to be done on the environment, and the issue is most likely network latency.
The issue was resolved by splitting up the environment. The reason the error took 24 hours to disappear is Usage Meter can still run into an issue with the tomcat service and EventsMonitor; basically the entire appliance can fail out until a healthcheck service restarts tomcat. The healthcheck script itself can error out.
Thanks much for the response John.