This repository has been archived by the owner on Dec 2, 2020. It is now read-only.
Addition of option to allow events to expire after a certain time #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Set event_ttl_seconds in bin\collector-config.js to specify the time in seconds that an event will be MongoDb
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added the ability to specify a value for MongoDb's expireAfterSeconds property.
This can help reduce the volume of data in the database at any one time. From http://docs.mongodb.org/manual/tutorial/expire-data/: "This is ideal for some types of information like machine generated event data, logs, and session information that only need to persist in a database for a limited period of time."
The value is optional and is set in the collector-config file.