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

[fortinet_fortigate] add hostname parsing for syslog #11678

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Nacon96
Copy link

@Nacon96 Nacon96 commented Nov 8, 2024

Proposed commit message

The current parser is not processing the hostname field of syslog messages, so in some cases, the observer.name field remains empty.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

@Nacon96 Nacon96 requested a review from a team as a code owner November 8, 2024 18:57
Copy link

cla-checker-service bot commented Nov 8, 2024

💚 CLA has been signed

@andrewkroh andrewkroh added Integration:fortinet_fortigate Fortinet FortiGate Firewall Logs needs CLA User must sign the Elastic Contributor License before review. Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices] labels Nov 8, 2024
@elasticmachine
Copy link

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@andrewkroh andrewkroh added bugfix Pull request that fixes a bug issue and removed needs CLA User must sign the Elastic Contributor License before review. labels Nov 8, 2024
Copy link
Contributor

@taylor-swanson taylor-swanson left a comment

Choose a reason for hiding this comment

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

Some minor changes, but otherwise seems good to me.

The top-level manifest version needs to be updated as well:

manifest.yml:

- version: "1.26.0"
+ version: "1.27.0"

Copy link
Author

@Nacon96 Nacon96 left a comment

Choose a reason for hiding this comment

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

i see the changes adequate, thanks.

Copy link
Contributor

@taylor-swanson taylor-swanson left a comment

Choose a reason for hiding this comment

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

In case I wasn't clear, the changes I requested are ones I'm requiring.

  • For how we use semver, any additional fields added require at least a minor change to versioning. Patch versions are reserved for bugfixes/enhancements that don't alter the structure of documents, among other things.
  • We don't need to set fields from a grok only to not use them and only remove them later. This just adds unnecessary actions to the pipeline.

Copy link
Contributor

@taylor-swanson taylor-swanson left a comment

Choose a reason for hiding this comment

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

Updated changes LGTM, we just need to bump the version in the manifest.

packages/fortinet_fortigate/manifest.yml

- version: "1.26.0"
+ version: "1.27.0"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Pull request that fixes a bug issue Integration:fortinet_fortigate Fortinet FortiGate Firewall Logs Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants