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.

Sign up for GitHub

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

Jump to bottom

Winlogbeat Registry File (.winlogbeat.yml) not properly tracking event logs #5813

Closed
krasekhi opened this issue Dec 5, 2017 · 1 comment · Fixed by #5815
Closed

Winlogbeat Registry File (.winlogbeat.yml) not properly tracking event logs #5813

krasekhi opened this issue Dec 5, 2017 · 1 comment · Fixed by #5815
Labels
bug v6.0.0 Winlogbeat

Comments

@krasekhi
Copy link

krasekhi commented Dec 5, 2017 •
edited by andrewkroh
Loading

For confirmed bugs, please report:

  • Version: Winlogbeat 6.0.0
  • Operating System: Windows 10
  • Steps to Reproduce: Install Agent

6.0.0

update_time: 2017-12-05T15:16:38.2530588Z
event_logs:
- name: wineventlog
  record_number: 528669
  timestamp: 2017-12-05T15:16:31.1188124Z

5.5.2

update_time: 2017-12-05T15:16:07.841893Z
event_logs:
- name: Application
  record_number: 250502
  timestamp: 2017-12-05T15:16:02.6721303Z
- name: Microsoft-Windows-Diagnostics-Performance/Operational
  record_number: 204
  timestamp: 2017-11-28T00:27:30.1588877Z
- name: System
  record_number: 137622
  timestamp: 2017-12-05T15:08:40.0562157Z

Reference : https://discuss.elastic.co/t/winlogbeat-6-0-0-registry-file/110384
andrewkroh added a commit to andrewkroh/beats that referenced this issue Dec 5, 2017
@andrewkroh
Fix Winlogbeat registry file
1706008 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes elastic#5813
@andrewkroh andrewkroh mentioned this issue Dec 5, 2017
Merged
andrewkroh added a commit to andrewkroh/beats that referenced this issue Dec 5, 2017
@andrewkroh
Fix Winlogbeat registry file
2a808d1 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes elastic#5813

(cherry picked from commit 1706008)
This was referenced Dec 5, 2017
Merged
Merged
andrewkroh added a commit to andrewkroh/beats that referenced this issue Dec 5, 2017
@andrewkroh
Fix Winlogbeat registry file
eb80a09 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes elastic#5813

(cherry picked from commit 1706008)
@andrewkroh
Copy link
Member

I have prepared a PR to fix this issue and opened cherry-picks to the release branches.

ruflin pushed a commit that referenced this issue Dec 5, 2017
@andrewkroh @ruflin
Fix Winlogbeat registry file (#5815)
d73b380 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes #5813
ruflin pushed a commit that referenced this issue Dec 5, 2017
@andrewkroh @ruflin
Fix Winlogbeat registry file (#5816)
bf7b6fc 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes #5813

(cherry picked from commit 1706008)
ruflin pushed a commit that referenced this issue Dec 5, 2017
@andrewkroh @ruflin
Fix Winlogbeat registry file (#5817)
9f8dd44 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes #5813

(cherry picked from commit 1706008)
@andrewkroh andrewkroh mentioned this issue Sep 17, 2018
Closed
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@andrewkroh @ruflin
Fix Winlogbeat registry file (elastic#5817)
3230e8f 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes elastic#5813

(cherry picked from commit 1706008)
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@andrewkroh @ruflin
Fix Winlogbeat registry file (elastic#5816)
52ca6cc 
The registry file did not contain the event log name, and therefore resumption after restart did not work
at all and Winlogbeat would start from the beginning. This fixes that issue.

Fixes elastic#5813

(cherry picked from commit 1706008)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug v6.0.0 Winlogbeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix Winlogbeat registry file andrewkroh/beats
2 participants
@andrewkroh @krasekhi