Overview
We strongly recommend using the timestamp/date in your resolver config attributes because there is no guarantee that events always come in "real-time.â Some reporters send their reports with a delay; sometimes, queues can build up in AbuseHQ. And we strongly recommend giving a caching timespan as big as your system allows it to be.
Example
(The time this event arrives at AbuseHQ doesn't matter! Let's say it's 2020-11-29T22:00:00Z) an event comes in and includes the IP 10.0.0.2 and the timestamp 2020-11-29T08:00:00Z
Both the IP and the timestamp are sent to the resolver.
The resolver responds with:
{
 "subscriber": {
  "id": 111111,
  "resolver_data": {
   [...]
  }
 },
 "contract": {
  [...]
 },
 "result_valid_from": "2020-11-29T02:00:00",
 "result_valid_until": "2020-11-29T12:00:00Z"
}
This result is added to the cache, and every following event with the same IP and timestamp between 02:00 and 12:00 on 11-29 will not be queried again!
Learn more
If you want to read about AbuseHQ Data Structure, we recommend reading this article: Understanding The AbuseHQ Data Structure.
Still, need help?
No problem; click the chat button in the bottom right-hand corner of the screen and send us your questions. Alternatively, you can email us at support@abusix.com
also, follow our LinkedIn Channel for updates & subscribe to our YouTube Channel for the latest Abusix how-to-videos.