- Notifications
You must be signed in to change notification settings - Fork 15
Temporarily store signals in disk 3/3 #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…nto AppInfoService
This reverts commit 15b3694.
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
| | ||
| public PersistenceConfiguration build() { | ||
| if (exportScheduler == null) { | ||
| exportScheduler = ExportScheduler.getDefault(60 * 60 * 1000); // Every hour by default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the default for exporting data to the collector 60 minutes? 60 seconds should be more appropriate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong opinion about this, so if the iOS agent uses 60 seconds already then I'll do the same here to keep consistency!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's updated now
…istence exportings
# Conflicts: # CHANGELOG.asciidoc
Closes #94
Final changes to fully add support for disk persistence of signals. I've also updated the docs to include information on how to use this new feature!