There is very minimal error checking on the API frontend, as Datadog queues all data for asynchronous processing. The goal is to always, always accept your data in production situations and decouple Datadog’s systems from yours.
It is, therefore, possible for you to receive a 202 ‘success’ response but not see your data in Datadog. The cause of this is most likely:
To check your timestamp is correct, run:
date -u && curl -s --head https://app.datadoghq.com 2>&1 | grep date
This outputs the current system’s date, and then make a request to Datadog’s endpoint and grab the date on that end. If these are more than a few minutes apart, you may want to look at the time settings on your server.
There are also certain fields which are not mandatory for submission, but do require a valid input. For example, in submitting an event, the priority field must be one of the four given options. Any other text results in a 202 ‘success’ but no event showing up. Having an invalid
source_type_name doesn’t prevent the event from showing up, but that field is dropped upon submission.