Skip to content
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

Make leading time stamp optional #3

Open
daniel-gallagher opened this issue Sep 13, 2017 · 0 comments
Open

Make leading time stamp optional #3

daniel-gallagher opened this issue Sep 13, 2017 · 0 comments

Comments

@daniel-gallagher
Copy link

daniel-gallagher commented Sep 13, 2017

This is more of a request instead of an issue, but there may also be some underlying bug at work. I have been fighting with weird time stamp issues when using the connector and think it would be a good idea to make it optional for Graylog to add a leading time stamp to each log. This will allow for Splunk to parse the stamp on its own and will keep the raw log in its original form. Actually, it may even be desirable to omit the time stamp addition entirely to preserve the raw log data.

The challenge I had today was an issue where a FirePower log had a time stamp in the raw data and Graylog seemed to correctly parse it and display the logs during a search, but the data sent to Splunk had a leading stamp that was +4 UTC. It was like Graylog assumed the stamp it parsed was -4 UTC and it added 4 to output UTC time. This was incorrect and made the leading stamp +8 more than the correct time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant