[Azure] - Using Flattened type fields #7465

Identify the integrations that are using the flattened type fields and non-flattened type fields. As there is an ongoing effort to change the object fields to flattened types, we can use this issue to capture the findings here.

Field: azure.dimensions, azure.resource.tags

Both the above fields has a flattened type for the Application insights and the billing metrics and object type in the Azure Metrics integration.
The above fields with flattened type are renamed and .* is removed from the suffix. This is because there is new validation added to the package-spec which fails when using .* in the suffix for flattened fields. find more details here.

Below is the list of integrations using the flattened and non-flattened types for tags and dimensions field.

Flattened type

• Application insight - app_insight, app_state
• Azure Billing - billing

Non-Flattened type

• Azure Metrics - compute_vm
• Azure Metrics - compute_vm_scaleset
• Azure Metrics - compute_vm_instance
• Azure Metrics - container_instance
• Azure Metrics - container_registry
• Azure Metrics - container_service
• Azure Metrics - database_account
• Azure Metrics - Monitor
• Azure Metrics - storage_account

When to change field type flattened?

• As the flattened type supports most of the aggregations for the keyword field. The keyword fields are ideal candidate for flattened types.
• Any numeric field can be ignored for now.

Next Steps:

Verify the below integrations tags and dimension fields are suitable for making the types as flattened types

• Azure Metrics.
• Azure Function integrations.