Account Traffic Graphs¶
We provide a useful summary of your account activity on your account profile page in the Incoming Traffic graph. You can navigate to this by selecting the “Metric Traffic” submenu from the “Metrics” tab.
The Your Traffic card provides a quick overview of your recent traffic. The icon in the status column provides information on your last received data. The green icon indicates that we have seen data arrive recently on that interface. The yellow and red icons show that no data has arrived on that interface for at least 5 and 15 minutes respectively. The blue icon indicates that we have never seen any traffic on that interface.
Concurrent Metrics Graph¶
In the graph above, the orange line is the concurrent metric limit - the number of metrics you can update in a rolling 5-minute period. One metric name might look something like ‘my.server.cpu.load’. In this example it is set at 10,000, allowing 10,000 metric names to be sent at the same time.
The yellow line is the number of concurrent metrics incoming for the account, on this graph it fluctuates between around 5,000 and 6,000 concurrent metrics. When we see more than the limit sent at the same time, some metrics will be dropped.
Datapoint Rates Graph¶
In the graph above, the green line is the number of data points allowed per second, or the datapoint rate limit. In this example it is set at 100,000, allowing the user to send 100,000 data points a second.
The remaining lines are the datapoints per second received by the five busiest servers associated with your account. In this example they range from about 5,000 to 15,000 datapoints per second. The name in the legend indicates what protocol it is handling, in this example there are 3 pickle servers and 2 UDP servers.
The datapoint rate limit applies on a per server basis so when we see more than the limit sent at the same time for any one server, some metrics will be dropped.
Why are there account limits?¶
TL;DR - As a prevention measure against accidents and malice.
It’s possible for a user to run a script which accidentally (or deliberately) updates millions of metrics a second. Sensible limits on what data we process ensures that one customer cannot affect the quality of service for others. For our paid accounts, we monitor and increase any limits as necessary. In general, we want any customer to be able to send data at a high rate.