As a PRTG user, I want to parse time-series data (i.e. time-stamped data sets) in Custom EXE/XML Advanced sensor XML/JSON structure in the same manner as built-in PRTG AWS RDS sensor already does it by using XML <time> element.
Details of user story
Modern cloud providers deliver some metrics (for instance CPU, RAM, etc.) along with timestamps for measurements made in past. Adding the support for XML/JSON <time> element would reduce the load and cost.
The load can be reduced by reducing the frequency of queries to grab the metrics (1x per 15min instead of 15x per 15min, or 1x per 1h instead of 60x per 1h, and so forth) The monetary cost can reduced since every cloud request to grab metrics adds fractional costs. Thus reducing the number of requests, the total costs can be reduced.
Be aware, that PRTG product has already this functionality BUT only for built-in AWS sensors, for example, AWS RDS sensors parses metrics.
- Criterion #1 XML/JSON <time> element for Custom EXE/XML Advanced sensor
- Criterion #2 Date format: OLE Automation Date and/or RFC3339
Although the OLE Automation date (oaDate) stamps can be used as well, as AWS RDS already does it. The RFC3339-to-oaDate and oaDate-to-RFC3339 conversation can be done programmatically by customers within the EXE script. Alternatively the RFC3339 can be used to parse time-stamps.