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

Adding Cisco support for the Syslog parser #10760

Merged
merged 8 commits into from
Feb 18, 2019
Merged

Conversation

ph
Copy link
Contributor

@ph ph commented Feb 14, 2019

Add support for the "sequence" number in the log format send by cisco devices.
The number will be extracted to "event.sequence"

Fixes: #10654

ph added 3 commits February 14, 2019 16:08
@ph ph requested a review from a team as a code owner February 14, 2019 21:24
@ph
Copy link
Contributor Author

ph commented Feb 14, 2019

@webmat I am currently extracting the sequence number generated from Cisco switch (syslog variant), I've looked at ECS, I saw there was a proposal to add an event.sequence to the format but nothing concrete. I think its a good time to add it, WDYT?

filebeat/input/syslog/parser.rl Outdated Show resolved Hide resolved
filebeat/input/syslog/parser.rl Outdated Show resolved Hide resolved
filebeat/input/syslog/parser_test.go Outdated Show resolved Hide resolved
@ph
Copy link
Contributor Author

ph commented Feb 14, 2019

@andrewkroh I've made the changes, I think that should be ok

Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for adding this. 🥇

CHANGELOG.next.asciidoc Outdated Show resolved Hide resolved
@@ -81,7 +81,7 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d
- The `elasticsearch/deprecation` fileset now indexes the `component` field under `elasticsearch` instead of `elasticsearch.server`. {pull}10445[10445]
- Remove field `kafka.log.trace.full` from kafka.log fielset. {pull}10398[10398]
- Change field `kafka.log.class` for kafka.log fileset from text to keyword. {pull}10398[10398]
- Address add_kubernetes_metadata processor issue where old source field is
- Address add_kubernetes_metadata processor issue where old source field is
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change intended?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I presume I wont be the only one removing the additional space, I propose we make the change :)

@ph
Copy link
Contributor Author

ph commented Feb 15, 2019

jenkins test this please

@webmat
Copy link
Contributor

webmat commented Feb 15, 2019

Yes, I like this change. I've made a note to introduce officially to ECS. I agree with the datatype and the name.

Go for it!

@ph ph added the needs_backport PR is waiting to be backported to other branches. label Feb 18, 2019
@ph ph merged commit dd92b6f into elastic:master Feb 18, 2019
@inqueue
Copy link
Member

inqueue commented Apr 26, 2019

Hi @ph Is there any chance this can be backported to 6.7?

@ph
Copy link
Contributor Author

ph commented Apr 29, 2019

@inqueue I can backport it, in retrospect is more of a bug than a new feature.

ph added a commit to ph/beats that referenced this pull request Apr 29, 2019
* Adding Cisco support for the Syslog parser

Add support for the "sequence" number in the log format send by Cisco switch devices.

Fixes: elastic#10654
(cherry picked from commit dd92b6f)
@ph
Copy link
Contributor Author

ph commented Apr 29, 2019

@inqueue backport PR at #11977

webmat pushed a commit to elastic/ecs that referenced this pull request May 1, 2019
- Added `event.code` (See elastic/beats#10333)
- Added `event.sequence` (See #129, elastic/beats#10760)
- Added `event.provider` (See #321)
  - Note: Beats modules currently put the Syslog "programname" in `process.name` which is sometimes accurate, sometimes not (e.g. "kernel"). event.provider would be a better field for this.
- Explain event.module and event.dataset without mentioning Beats
hrak pushed a commit to hrak/beats that referenced this pull request Mar 4, 2020
Adding Cisco support for the Syslog parser

* Adding Cisco support for the Syslog parser

Add support for the "sequence" number in the log format send by Cisco switch devices.

Fixes: elastic#10654, elastic#15979

(cherry picked from commit dd92b6f)
ph added a commit that referenced this pull request Mar 5, 2020
Adding Cisco support for the Syslog parser

* Adding Cisco support for the Syslog parser

Add support for the "sequence" number in the log format send by Cisco switch devices.

Fixes: #10654, #15979

(cherry picked from commit dd92b6f)

Co-authored-by: Pier-Hugues Pellerin <[email protected]>
@andrewkroh andrewkroh removed the needs_backport PR is waiting to be backported to other branches. label Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Filebeat] Syslog parse error with Cisco Switch logs
6 participants