[FAQ] What is the lag between sending multiple datapoints that have returned Code 202? 12.29.2014 01:40 PM
Q: I recently used postMultiple for the first time. I received the Status Code 202 that says
"The request has been accepted for processing, but the processing will be completed asynchronously".
Because it was not what I was expecting to see (I thought it would update in relatively real-time like the PUT function), it has raised the following questions.
What is the lag between sending datapoints that have returned Code 202 and having them show up in the on-line graphs?
Can updating using a timestamp generated by my device be done similarly to the PUT function using another function or method?
The main reason I used the postMultiple function was so I could assign the timestamp in order to assure datapoints are in the right order. They seem to get out of order at times when using the PUT function. Is there a better way to do this?
Any insight is appreciated.
The 202 means that the server has accepted the value(s) and is performing post-processing. Part of that process is to replicate the value(s) to our multiple data centers. Under normal circumstances, you should see the data point within the refresh time window of the chart (5 secs).
The PUT command will assign a timestamp to the value when it is received by our server. Network latency, or delays on the client side are just a couple of circumstances that could cause the data points to "get out of order". Because of that reason, the recommended function to use is the POST, so that you, the end-user, can control the order of the values.
Please confirm that you want to flag this content as inappropriate.
Please confirm that you want to delete this content.