filebeat/module/apache: Rename the field apache2.module.error to apache.module.error

[herrBez]

Proposed commit message

Rename field apache2.module.error to apache.module.error in the Dashboard

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

None

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• [Filebeat][Apache] apache2.error.module should be renamed to apache.error.module in error dataset's Dashboard #39480

Use cases

Screenshots

The original saved search uses apache2.error.module, while the correct field apache.error.module (added by me) shows that it is actually populated with a meaningful value.

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @herrBez? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[shmsr]

Nice find. Can you also open a PR for the integrations repo? See: https://github.com/search?q=repo%3Aelastic%2Fintegrations+path%3A%2F%5Epackages%5C%2Fapache%5C%2Fkibana%5C%2F%2F+apache2&type=code

[shmsr]

Please add an entry to the changelog.

[herrBez]

Thank you. I think I addressed both points now :) . I am on it for the integration's PR

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-05-09T07:24:58.495+0000

• Duration: 159 min 47 sec

Test stats 🧪

Test	Results
Failed	0
Passed	8428
Skipped	773
Total	9201

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[shmsr]

Changes LGTM. However, I would like another member of my team to review this as well before we merge.

[devamanv]

LGTM

[ishleenk17]

@shmsr @devamanv : I think this can be merged in beats as well?

[herrBez]

I see some failures in the build, but I hardly believe they are related with the change introduced here:
https://github.com/elastic/beats/pull/39481/checks?check_run_id=25345121364 .

[shmsr]

@herrBez CI is passing. Let's merge?

[herrBez]

Done. Thank you for the help and support!