Are you seeing either of these error messages?
This article explains why these messages display and what you can do about it.
Why am I seeing this error message?
You'll see one of these messages if your data feed includes a LOT of rows. To respect fair use limits and enable optimum performance for all customers, we limit the number of rows of data that can be ingested per hour, per account. This limit is applied during metric creation, when metrics are refreshed and new data is ingested, and when you choose to delete and re-import data for a metric. If you see either of these error messages, it means you have reached or exceeded your hourly data ingestion limit.
Where can I view my data ingestion usage and limits?
You can view current data ingestion information for your account either by clicking “See your ingestion limit” in the error message (as shown above) or by clicking the Usage button in the side nav (as shown below).
What can I do to fit within the limit?
When creating data feeds for custom metrics, we strongly recommend adding a date column. This is especially true for larger data feeds. Learn more about creating custom metrics.
If the data feed doesn’t include a date column, we need to ingest the entire feed when a metric is created (and on every refresh) which may cause you to hit the maximum ingestion limit.
If the data feed includes a date column, we group the rows in the data feed into daily buckets using the selected time dimension and count the number of rows in each daily bucket. The daily ingestion value for the custom metric is calculated using the single, highest row count of all the daily buckets, instead of a total of ALL the rows. This significantly reduces the data being ingested and makes it less likely you'll exceed the maximum limit.
To fit within the data ingestion limit, try:
- Reducing the number of rows in your data feed, for example, by applying filters when querying your data for custom metrics.
- Adding a date column to your data feed if it doesn't have one.