[O11y][Azure Metrics] Migrate Queue Storage Overview dashboard to lens

[kush-elastic]

Urgency

• High

Activity Type

• Enhancement

What does this PR do?

• Manually migrate Azure Queue Storage visualizations to the lens in the current Kibana version 8.9.0 itself.

• Statistics for Azure Queue Storage Lens migration:

Migration stats

	Before Migration			After Migration
	Lens	Visualization	Old Input Controls	Lens	Visualization	New control panels
[Azure Metrics] Queue Storage Overview	0	9	1	9	0	1

Checklist

• I have added an entry to my package's changelog.yml file.
• I have verified that panels are populated with data.
• I have verified that panels are not distorted after being migrated to the lens.
• I have updated screenshots of the dashboard.
• I have verified that the data counts are matching and panel aggregations are the same as before.

Author's Checklist

• Migrated panels should be removed from visualization folder.
• Migrated visualizations are populating in current Kibana version 8.4.0 itself.

Related issues

• Relates [O11y][Azure Metrics] Azure Storage Account Lens migration  #7434

Before Migration

After Migration

[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-09-12T13:03:20.438+0000

• Duration: 15 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	34
Skipped	0
Total	34

🤖 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% (4/4)	💚
Files	100.0% (4/4)	💚
Classes	100.0% (4/4)	💚
Methods	75.758% (25/33)	👍 9.091
Lines	100.0% (32/32)	💚
Conditionals	100.0% (0/0)	💚

[zmoog]

The queue and message count values have decimals:

Isn't this the latest value for this metric?

[zmoog]

Shouldn't these be integer values?

[kush-elastic]

@zmoog
Both the visualizations were already using Average aggregation before migration, we will need to create new tickets to address this issue. As part of this PR scope, our focus will be only on migration.

[zmoog]

The old dashboard version displays the count values as integers; how does it work?

[kush-elastic]

The old dashboard version displays the count values as integers; how does it work?

it's working there because there is a way we can specify the custom format in TSDB.

[zmoog]

it's working there because there is a way we can specify the custom format in TSDB.

So, the old version displays the average value but uses a custom format to show it as an integer, right?

[kush-elastic]

So, the old version displays the average value but uses a custom format to show it as an integer, right?

Yes

[zmoog]

Displaying single count values with decimals doesn't feel right, but I'm not an expert.

@drewdaemon, can you or someone in your team help us understand the best way to represent this kind of data? It could be just me.

[drewdaemon]

Custom formatter was added to Lens in 8.9. Does that cover this?

Screen.Recording.2023-09-08.at.7.45.37.AM.mov

[kush-elastic]

Custom formatter was added to Lens in 8.9. Does that cover this?

Hey @zmoog @drewdaemon,
We are not able to export dashboards from 8.9.0 using the latest elastic-pacakge.

[drewdaemon]

@kush-elastic good point. I had forgotten about elastic/kibana#161969.

The public release for 8.10 is tomorrow, so you could always wait a day or two. Up to @zmoog of course.

[kush-elastic]

The public release for 8.10 is tomorrow, so you could always wait a day or two. Up to @zmoog of course.

@zmoog, what do you think? how should we proceed with this?
what I think is the issue itself is with the aggregation used in the current visualization. if we use the last value it should work just fine without any formatting. I don't see any reason to move dashboards to 8.10 just because of export issues.

We can merge this and create a new issue to track and resolve the wrong aggregation issue. that way we can stay on the current version and target more users at the same time.

[zmoog]

We can merge this and create a new issue to track and resolve the wrong aggregation issue. that way we can stay on the current version and target more users at the same time.

Okay, sounds good.

[rajvi-patel-22]

LGTM!

[elasticmachine]

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