Content Comparison

...

The tags beginning with cloud.azure identify events generated by Microsoft Azure.

Valid tags and data tables

...

Take into account the following when you define the tag:

According to the technology, the tag structure must be the following: cloud.azure.<product>.<type>.<region>.<version>.<category> , where the region field is mandatory.
The final table where each event is stored follows the format: cloud.azure.<product>.<type>
When the tag is sent, apart from the first 4 levels, there are some additional fields as seen above:
- region: this field is mandatory and must always be included in the tag, otherwise the event will go to the unknown.unknown table.
- version and category: optional fields.

Below is an example for a specific table and the different scenarios for each case:

Event tag	Destination table	Reason / Comment
`cloud.azure.activity.events`	`unknown.unknown`	The `region` has not been added, so the event would go to the proper table.
`cloud.azure.activity.events.eu`	`cloud.azure.activity.events` `region`: eu `version`: - `category`: -	Added `region` field, so it would go to the appropriate table with the corresponding value filled in.
`cloud.azure.activity.events.eu.1`	`cloud.azure.activity.events` `region`: eu `version`: 1 `category`: -	Added `region` field, so it would go to the appropriate table with the corresponding value filled in.
`cloud.azure.activity.events.eu.1.eh`	`cloud.azure.activity.events` `region`: eu `version`: 1 `category`: eh	Added `region` field, so it would go to the appropriate table with the corresponding value filled in.

These are the valid tags and corresponding data tables that will receive the parsers' data:

...