ELOVADE
Reads the ELOVADE partner portal (distributor for Hornetsecurity/Altaro, among others) and provides the booked services per end customer.
Credentials (gear icon)
| Field | Meaning |
|---|---|
| API URL | https://my.elovade.com |
| API key | API key from the ELOVADE account |
Metrics
Per customer, the booked services; the dashboard tile shows Storage (TB).
Specifics
- Customer numbers are stable → automatic rename detection.
- The consumption list is read completely or not at all: a page that fails fails the snapshot for the night (the previous one keeps counting) instead of storing a part of the list. A single tenant without a readable storage figure does not stop the portal: it is recorded as not read and keeps the figure of its last snapshot — it is never stored as 0 TB. Several tenants of one customer number add up to one figure; if one of them cannot be read, the whole customer number keeps its last figure instead of the sum of the others. A tenant without a customer number runs under its name. Fractions of a TB are kept (1.5 TB is no longer cut down to 1).
- ELOVADE delivers no daily figures: every snapshot holds the purchased storage of the last day of the previous month — all snapshots of October show the storage of September 30. For the invoice a month therefore has the figure it started with and the one read after it, and bills the higher: the run on the 1st takes an ELOVADE snapshot itself before it bills, so the September invoice carries the storage of September 30 — or that of August 31 where storage was given up in September (see quantity determination). The monthly CSV export follows the same rule.