We’ve built our platform to handle high volumes of usage events, and we encourage customers to send us rich, granular usage data, as this allows us to provide you with more flexibility and value from it once ingested.
There are two methods of sending usage data to m3ter - API and file upload.
Our ingest API is the primary mechanism for ingesting usage data. It’s built with scale and flexibility in mind, allowing up to 1,000 measurements in each API request.
If your existing systems and data flow better suit uploading a file containing usage data, perhaps at the end of a batch operation, we offer a file upload service. Make an API call to generate a temporary upload URL, then upload your file; we’ll do the rest, and any errors are reported to you via the normal Alerts service.
More Details? See the Submitting Usage Data section for instructions and examples.
There are many reasons measurements might get lost or duplicated on their way to the m3ter platform, so a key quality of the m3ter ingest service is that sending a measurement is an idempotent operation within a 35-day window. This means that if a measurement with the same UID arrives multiple times in that timeframe, we will only ingest it once.
When unsure whether a network connectivity issue or application crash affected measurements being sent, resend them with their original UID and we’ll de-duplicate and only store the missing ones.
When dealing with ephemeral usage events, we recommend putting the events on a queue such as Amazon SQS or Azure Storage Queues within your environment, then read from that queue when sending it to the m3ter API. This adds a layer of protection against data loss because of network or software issues.
No. Do not send personally identifiable information (PII) in the usage data. Use an anonymous unique identifier that you can map to individual information in your CRM.
Yes. Our ingest agent can poll external systems and submit it to the m3ter API. Various sources and formats are supported out of the box, but we can also help develop custom collectors should one be required.
Measurements are immutable once ingested, but it’s possible to make adjustments to correct aggregated data by submitting corrective measurements (either positive or negative).
Yes, you can view, filter, aggregate, and export usage data via our Data Explorer in the m3ter Console, or via the API. In the future, we shall introduce additional features enabling you to export larger volumes of data.
If you send measurements containing data that you have not configured in your Meter yet, we will still store the data. When you create a Data Field with the same code field, it will become available.
Removing a Data Field from a Meter does not delete the existing measurements, but it becomes unavailable for other m3ter features.
Login to the Support portal for additional help and to send questions to our Support team.