This repository has been archived by the owner on Dec 29, 2020. It is now read-only.
Added fileid in all the events and also added support of last_record_location #41
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.
Changes contains two parts:
(1) Added the fileid in the events where fileid is the unique id of each fw.log
links:
bc20976
419acaa
efd8d71
(2) Added code to support last_record_location along with the read cursor file.
Description about last_record_location:
Support of the last_record_location along with the cursorfile. We should able to pass the last_record_location as commandline argument. last_record_location would be like
{fileid:loc}
i.e.
{123333:3232}
. We can use this parameter to get the events from the particular location. So if we pass the commandline argument last_record_location, We will use the argument instead of the cursor file.
(1) If current fileid matches with the --last_record_location fileid then only we will use the loc to get the next events from the same fileid.
(2) If current fileid will not match with the stored fileid then we will read the whole fw.log file.
(3) Command line arguments along with fw1-loggrabber.conf and lea.conf