search

dynatrace-extensions / dynatrace-extensions-vscode

A VisualStudio Code extension to support all aspects of developing Dynatrace Extensions 2.0
Apache License 2.0
16 stars 7 forks source link

[Bug]: JMX Conversion - Array has too many items #257

Open andrewbreitfeld opened 5 days ago

andrewbreitfeld commented 5 days ago

Description

Hello,

I am assisting a customer converting JMX 1.0 extensions to 2.0, noticing an issue with some of the visualizations being converted for a few of the 1.0 extensions (Dynatrace self-mon 1.0 extensions). Receiving the mention "Array has too many items. Expected 10 or fewer."

I have tried adding more subgroups to reduce the number of metrics reporting in each to be below 10. Also, I tried updating the screen.chart.metric.table.definition.schema maxItems mention without success.

Seeking some assistance for a workaround or if these visualizations essentially need to be deleted/recreated for 2.0?

Other details: Customer is offline, don't have the ability to send/upload support archive to GitHub. OS - Windows 10 Enterprise 22H2 MS VS Code - 1.92.2 Dynatrace Extension Add-on version - 2.6.1

Thanks, Andrew

extension.txt

image

image

Steps to reproduce

  1. Following the standard 1.0 to 2.0 conversion process mentioned here https://developer.dynatrace.com/develop/dynatrace-extensions-vscode/guides/migrate/jmx-conversion/
  2. Added more subgroups to reduce metrics included to be 10 or less per category and tried editing the screen.chart.metric.table.definition.schema maxItems mention to see if that helped resolve the issue.

Support information

radu-stefan-dt commented 4 days ago

Hi. Thanks for creating this bug. This is, indeed, an oversight in the extension conversion automation.

While we work on an official fix, please create more cards to accommodate a maximum of 10 metric per card. The subgroups part of the yaml will have no effect, it will be something that needs editing in metricTableCards.

andrewbreitfeld commented 3 days ago

Hi Radu, Thanks for taking a look at this and working on a future fix. Also, helping me better understand the best remediation for this. Appreciate it!