if you connect to https://testing.tracking.exposed/api/v2/<token>/stats/<optional paging>
you might see a result coming from the timelines. The pipeline of the mongodb query is:
1) look at the $paging timelines, default 20-0 (amount 20, skip 0)
2) look at all the impression collected per timeline (in your case, should be an average of 40?)
3) look at the metadata attributed by the parsers
Imagine to call a query 5 minutes after the scheduled refresh of your bots. then:
based on 1, if the call do not return new timelines -> the bots are down
based on 2, if the call do not return enough impression -> bots working bad
based on 3, if the call has not metadata but impression -> parsers are broken
A new API which can help in this, has been implemented here: https://github.com/tracking-exposed/facebook/issues/126
if you connect to
https://testing.tracking.exposed/api/v2/<token>/stats/<optional paging>
you might see a result coming from the timelines. The pipeline of the mongodb query is:
1) look at the $paging timelines, default 20-0 (amount 20, skip 0) 2) look at all the impression collected per timeline (in your case, should be an average of 40?) 3) look at the metadata attributed by the parsers
Imagine to call a query 5 minutes after the scheduled refresh of your bots. then:
based on 1, if the call do not return new timelines -> the bots are down based on 2, if the call do not return enough impression -> bots working bad based on 3, if the call has not metadata but impression -> parsers are broken
Originally posted by @vecna in https://github.com/tracking-exposed/dashboard/issues/5#issuecomment-486835996