This issue captures all the work done and additional work required to migrate obs-cloud-monitoring owned packages to format_version 3.0.0.

In order to get some packages passing the new package-spec validations, several validation exclude rules were added. For these packages, the underlying issues should be fixed as soon as possible and the exclude rules removed. The fixes required for this are also captured in this issue.

The packages being migrated as part of this issue are:

• aws
• aws_logs
• awsfargate
• awsfirehose
• azure
• azure_application_insights
• azure_billing
• azure_metrics [BLOCKED]
• gcp
• gcp_metrics

PRs

• Update (most) obs-cloud-monitoring owned packages to format_version 3.0.0 #8041
• Update azure package to format_version 3.0.0 #8050
• Update azure_metrics package to format_version 3.0.0 #8191

Issues blocking migration to format_version 3.0.0

• [azure_metrics] convert legacy visualizations to lens #8207

Issues that need fixing but are currently skipped in 'validation.yml'

• [aws] inline visualisations in all dashboards (SVR00004)
• [awsfargate] add dataset filters to all dashboards (SVR00002)
• [azure_application_insights] add dataset filters to all dashboards (SVR00002)
• [azure_application_insights] inline visualisations in all dashboards (SVR00004)
• [azure_billing] add dataset filters to all dashboards (SVR00002)
• [azure_metrics] add dataset filters to all dashboards (SVR00002)
• [azure] add dataset filters to all dashboards (SVR00002)
• [azure] inline visualisations in all dashboards (SVR00004)
• [gcp] inline visualisations in all dashboards (SVR00004)

Other non-blocking issues that should be fixed in the future

• [azure] remove root level geo fields from data streams
• [azure] azure.auditlogs.properties.additional_details.user_agent mapping does not match format of sample logs