[RedisEnterprise] Enable TSDB

[ritalwar]

Proposed commit message

This PR enables TSDB for RedisEnterprise.

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.

Related issues

• Closes [Redis Enterprise] TSDB Enablement #6268

Screenshots

[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: 2023-11-28T10:02:37.296+0000

• Duration: 15 min 8 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5
Skipped	0
Total	5

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (0/0)	💚
Files	100.0% (0/0)	💚
Classes	100.0% (0/0)	💚
Methods	50.0% (4/8)	👎 -48.276
Lines	100.0% (0/0)	💚 11.644
Conditionals	100.0% (0/0)	💚

[harnish-crest-data]

Observation:

The dashboard visualizations have static intervals as 1m rather than Auto. Is this intentional?

[harnish-crest-data]

The visualization Total client connections has an average operation type which seems inappropriate. Can you check if we can use last_value instead of average!

[ritalwar]

The dashboard visualizations have static intervals as 1m rather than Auto. Is this intentional?

This was implemented within this PR. For TSDB migration tests, I only verified if visualizations display data correctly or appear distorted. Perhaps @rajvi-patel-22 can provide insights into why "1m" was chosen over "Auto."

[harnish-crest-data]

The dashboard visualizations have static intervals as 1m rather than Auto. Is this intentional?

This was implemented within this PR. For TSDB migration tests, I only verified if visualizations display data correctly or appear distorted. Perhaps @rajvi-patel-22 can provide insights into why "1m" was chosen over "Auto."

Okay! I have verified that Rajvi has kept the same behaviour of the Redis enterprise lens migration. Please refer to this link for diff changes.

[ritalwar]

The visualization Total client connections has an average operation type which seems inappropriate. Can you check if we can use last_value instead of average!

Could you please create a separate issue and add it to the backlog for implementing the right aggregator functions in visualizations?
Let's keep the TSDB enablement separate.

[harnish-crest-data]

The visualization Total client connections has an average operation type which seems inappropriate. Can you check if we can use last_value instead of average!

Could you please create a separate issue and add it to the backlog for implementing the right aggregator functions in visualizations? Let's keep the TSDB enablement separate.

Created a separate issue as per observation: #8603!

[agithomas]

LGTM!

[elasticmachine]

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