prometheus-metrics

In test_configuration.py, check if metric_start_time and metric_end_time are valid (here).

For example, the end time should not be greater (newer) than the current time.

Is your feature request related to a problem? Please describe.
The existing example workflows are all quite simple. They don't well represent a real-world workflow.

Describe the solution you'd like
There should be a new workflow example in the examples/ directory which carries out the following steps:

• create namespace
• create deployment
• delete deployment
• delete namespace

The exporter doesn't support metrics in a JSON payload with dots in the key, since it uses gojsonq's Find() method which valuates a dot as a delimiter in a JSON path.

This means an MQTT message payload like the following will not work since the JSON parser expects a nested JSON structure:

{"particles_2.5um": 5}

The examples don't imply that the metric names are intended to

Is your feature request related to a problem? Please describe.

As a user, I would like to get aggregated data using the "get_metric_range_data" method. The default resolution of data is in seconds. If I want data for a year, the number of data points is huge and it takes a lot of compute resources to download and store the data. I would like to get the data in hourly or daily frequency. F