We configured the input interval to 3000.
After 10 minutes the collection job stops, but not all build plans are loaded.
If the collection job started again we git the following notification in /opt/splunk/var/log/splunk/libs_bamboo.log:
2018-10-10 16:56:56,965 INFO pid=25059 tid=MainThread file=bamboo_service.py:make_url_request_obj:24 | req https://server:443/rest/api/latest/result/DEMO-SAM1-53.json?max-results=1000
2018-10-10 16:56:57,076 INFO pid=25059 tid=MainThread file=bamboo.py:collect_events:294 | Looking at detailed result
2018-10-10 16:56:57,077 INFO pid=25059 tid=MainThread file=bamboo.py:collect_events:297 | Build complete date:2018-06-29T13:22:24.933+02:00 Last sync date:2018-10-10 16:50:34+0000
2018-10-10 16:56:57,077 INFO pid=25059 tid=MainThread file=bamboo.py:collect_events:303 | Not writing this event because it is already indexed
But this is not true, cause the bamboo.py script checks only the Last sync date against the Build complete date without checking if the last job got all old build plans.
... View more