auditd: Fix invalid event.type: stop->end

[haesbaert]

Proposed commit message

stop is not a valid event.type, use end where applicable.

https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-type.html#ecs-event-type-end

Related to: https://github.com/elastic/sdh-beats/issues/4763

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.

How to test this PR locally

I've tested with elastic-package, and run the tests for the respective package.

Related issues

Related to: https://github.com/elastic/sdh-beats/issues/4763

Screenshots

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 2914acd

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[andrewkroh]

LGTM.

@haesbaert Would you mind creating an issue to fix go-libaudit please? I see it has stop.

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[elasticmachine]

Package auditd - 3.19.2 containing this change is available at https://epr.elastic.co/search?package=auditd