I have schedule parameters for cron jobs in the input configurations of http_poller and jdbc plugins:
- http_poller runs at the mark of the hour, i.e.
schedule => { cron => "0 * * * *"} - jdbc runs every 2 minutes, i.e.
schedule => "*/2 * * * *"
I run everything on the same pipeline.
What I observe, is that logstash triggers the http_poller at much shorter and inconsistent intervals, at 2, 3 or 5 minutes instead of once every hour.
I managed to get it working at some point and wonder whether a combination of systemctl restart logstash.service and the plugins being busy causing past values for cron jobs to be stack into the system.