Get each command stats from INFO all command on redis module

[zanyou]

What does this PR do?

This PR makes to collect redis commandstats on redis module.
This PR overlaps in purpose with #28012, but that PR looked like it needed a lot of fixing and had stopped being updated, so I created a new one.

Why is it important?

The current redis module are collect only default metrics from INFO command.
commandstats provide stats of each commands. It includes the number of calls and The total CPU time consumed by these commands. The information is very important for monitoring of redis.

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

I had run only below commands. If need another tests, Please let me know.

style@FO-951 beats % go test -tags=integration ./metricbeat/module/redis/info/ -data
ok      github.com/elastic/beats/v7/metricbeat/module/redis/info        26.385s

Related issues

• Closes [Metricbeat] Add Redis commandstats (INFO all) to metricset #3008

Use cases

Screenshots

Logs

[cla-checker-service]

💚 CLA has been signed

[mergify]

This pull request does not have a backport label. Could you fix it @zanyou? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[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-03-14T01:05:50.807+0000

• Duration: 85 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	7746
Skipped	2031
Total	9777

💚 Flaky test report

Tests succeeded.

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

[zanyou]

I have signed the Contributor Agreement.

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[aspacca]

on my redis version (6.2.6) I have also rejected_calls and failed_calls in cmdstat

what do you think about adding them as well?

[aspacca]

@zanyou thanks for the contribution!

please, see my comments

[zanyou]

@aspacca
Thank you for comments!

on my redis version (6.2.6) I have also rejected_calls and failed_calls in cmdstat
what do you think about adding them as well?

These fields were added in redis 6.2 rc2 redis/redis#8305. But I didn't add it because the current module only tested with versions up to 5.0-rc4. I think it's a useful field, so I'll add it along with testing with 6.2.6.

[aspacca]

/test

[aspacca]

hi @zanyou , sorry for taking so long in review the last commits.

all good on my side: once the CI is green we can merge

[aspacca]

@zanyou could please fix the python integration test?
thanks

[aspacca]

and also add an entry in the changelog :)

[zanyou]

/test

[zanyou]

Hi @aspacca , sorry for taking so long time.
I fixed the python integration test and add entry to changelog.

[aspacca]

/test

[aspacca]

/test

[aspacca]

all good @zanyou , thanks for the contribution!