[o365] No delays until up-to-date

[chrisberkhout]

Proposed commit message

[o365] No delays until up-to-date

Instead of fetching history continuously until reaching the current day
then waiting the interval time between requests, keep fetching until
within one batch length of the current time.

With the default settings, waiting 3 minutes between requests for one
hour batches would significantly extend the time required to get
up-to-date. For example, it's 45 minutes of waiting to cover 15 hours.
It's particularly disruptive to the user experience if there is no
historical data and new data has such a delay.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0cc7dba

History

• 💚 Build #28815 succeeded 3cd936b

cc @chrisberkhout

[efd6]

Thanks

[elastic-vault-github-plugin-prod]

Package o365 - 2.18.7 containing this change is available at https://epr.elastic.co/package/o365/2.18.7/