Hubject’s Heartbeat monitor has been developed as a tool to quickly inform partners about Hubject's system status, in particular about the current state of selected microservices.
Heartbeat monitoring observes the runtimes of all Hubject server communications. We aim to be transparent about situations where our system is likely to cause high runtimes to enable efficient error monitoring for partners.
IMPORTANT NOTE: Heartbeat does not represent your specific connection with Hubject, but an average of all partners' connections with Hubject.
- Authorization Start
- Authorization Remote Start
- Charge Detail Record
- ICD Authorization
The information is updated every 30 minutes on the clock (i.e., 11:00 AM, 11:30 AM, 12:00 PM, etc.)
The performance is based on the average run time that the system takes to process each request. Based on the average runtime we indicate if the system is performing optimally, encountering some issues, or down.
Every time the average runtime reaches levels that are considered slow performance or performance issues, we log a performance event, so that users are informed about performance issues for the last 7 days.
Please click See more if you would like more detailed information on each microservice.
You will be redirected to another page where you can find the average runtime and the targets for the selected microservice. The performance events in the last seven days will be shown below (if there are any).
How does it work?
For each microservice, Hubject’s Heartbeat monitor will show the current average eRoaming runtime. This runtime is updated every 30 minutes and is calculated by summing up the runtimes of all requests over that period of time and dividing it by the respective number of requests.
The eRoaming runtime is a part of the total runtime of a request, specifically, the part of the time that is exclusively spent on Hubject server systems. We count neither the runtime on a partner’s backend systems, nor the time spent for communication between servers, to ensure that we can make a statement about Hubject’s server health.
A regular runtime is represented by a green color, indicating that Hubject’s system is running smoothly and server processes on our end are working as intended. In that case, partners that face errors or high runtimes themselves may have a problem on their end.
Unusual runtimes are marked in yellow or red. In those cases, Hubject’s system may face problems and is causing high runtimes.
Please do not hesitate to contact us if you would like to learn more about this feature.