Fix kafka dashboard field names: kafka.topic.name & kafka.broker.id.

[lalit-satapathy]

What does this PR do?

Fix kafka dashboard field names: kafka.topic.name & kafka.broker.id

Why is it important?

The kafka dashboard was broken.

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.

Author's Checklist

How to test this PR locally

Run Metricbeat against a working kafka cluster.

Related issues

• Relates Fix use of removed fields in Kafka dashboard in 8.x integrations#2770
• Relates https://github.com/elastic/sdh-beats/issues/2557

Screenshots

Before:

After:

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b kafka-update-dashboard upstream/kafka-update-dashboard
git merge upstream/main
git push upstream kafka-update-dashboard

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @lalit-satapathy? 🙏.
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

[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: 2022-12-02T04:48:41.483+0000

• Duration: 55 min 26 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3963
Skipped	881
Total	4844

💚 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!)

[ishleenk17]

The issue mentions that atleast these 2 fields were deprecated from previous version.
I think it would be worthwhile to see what other fields got deprecated between these 2 kafka versions. To avoid any further issues.

Otherwise, the change looks good

[ishleenk17]

I see these fields present in the field mapping.
Do we need to do some changes there as well?

[lalit-satapathy]

Let me check if any of these need to dropped from integration field mapping. Also briefly check, if any obsolete field still used. Not planning to do major kafka package changes for now.

[lalit-satapathy]

Also updated for "kafka.consumergroup.partition -> kafka.partition.id".

The corresponding integration PR elastic/integrations#4530 has many old filed mapping that are getting dropped.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b kafka-update-dashboard upstream/kafka-update-dashboard
git merge upstream/main
git push upstream kafka-update-dashboard

[ishleenk17]

Looks good!

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b kafka-update-dashboard upstream/kafka-update-dashboard
git merge upstream/main
git push upstream kafka-update-dashboard

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
6.5% Duplication