HERE Marketplace enables you to review your subscribers data usage and generate reports. Marketplace reports on two types of metrics, input and output. The input metrics represent the data that is published by the Provider and can be calculated via Bytes, APIs, or Messages. The output metric represents the data that is consumed by the Consumer and can be calculated via Bytes, APIs.
The platform allows using HTTP and/or Kafka connectors read from or write data to a stream layer. You can get metrics in the form of API calls when HTTP connectors are used or bytes in case of Direct Kafka connector.
You can generate reports for the catalog-based and the Neutral Server listing subscriptions.
API calls usage metrics would not be available if you read or write data via Kafka connector.
Usage metrics will be slightly higher than actual payload due to Kafka overhead and extra metadata.For Provider, the overhead is low. For Consumer, overhead is accumulated while there is a running Consumer. If Consumer has a 24/7 running pipeline to pull data from the stream layer and there is nothing that was ever published to this layer –, there still would be bytes_out metrics reported. The approximate overhead is 150bytes-1k/s, depending on how many partitions exist in the topic.
When adding an object store layer to a Marketplace catalog and offer with a subscription option, keep in mind that subscription reporting currently does not generate usage metrics. Subscription reporting will support object store layers in the next release.
HERE recommends using bytes to estimate volume of usage for billing purposes.
Real-time data might lag under certain circumstances.
It takes some time for the usage metrics data to update. When generating a report, allow at least 72 hours for accuracy.