Right this moment, our clients set up and handle their Azure digital networks at scale. As their variety of community assets grows, the query of tips on how to keep connectivity and safety amongst their scale of assets arises. That is the place Microsoft Azure Digital Community Supervisor is available in—your one-stop store for managing the connectivity and safety of your community assets at scale (at present in preview). And when clients use Azure Digital Community Supervisor, additionally they want visibility into what sort of adjustments have been made in order that they’ll audit these occasions, analyze these adjustments over time, and debug points alongside the way in which. This functionality is now a actuality—Azure Digital Community Supervisor occasion logging is now in preview.
Azure Digital Community Supervisor (AVNM) makes use of Azure Monitor for telemetry assortment and evaluation like many different Azure companies. AVNM now gives occasion logs that you could work together with by means of Azure Monitor’s Log Analytics device within the Azure Portal, in addition to by means of a storage account. You too can ship these logs to an occasion hub or associate resolution.
With this preview announcement, Azure Digital Community Supervisor will present a log class for community group membership change. Within the context of AVNM, community teams are outlined by the person to include digital networks. The membership of a community group may be manually offered (akin to by deciding on VNetA, VNetB, and VNetC to be part of this community group) in addition to conditionally set by means of Azure Coverage (akin to by defining that any digital community inside a sure subscription that incorporates some string in its identify shall be added to this community group). The community group membership change log class tracks when a selected digital community is added to or faraway from a community group. This can be utilized to trace community group membership adjustments over time, to seize a snapshot of a selected digital community’s community group membership, and extra.
What attributes are a part of this occasion log class?
This community group membership change class emits one log per community group membership change. So, when a digital community is added to or faraway from a community group, a log is emitted correlating to that single addition or elimination for that individual digital community. In case you’re taking a look at one in all these logs out of your storage account, you’ll see a number of attributes:
| Attribute | Description |
| time | Datetime when the occasion was logged. |
| resourceId | Useful resource ID of the community supervisor. |
| location | Location of the digital community useful resource. |
| operationName | Operation that resulted within the digital community being added or eliminated. All the time the “Microsoft.Community/virtualNetworks/networkGroupMembership/write” operation. |
| class | Class of this log. All the time “NetworkGroupMembershipChange.” |
| resultType | Signifies profitable or failed operation. |
| correlationId | GUID that may assist relate or debug logs. |
| stage | All the time “Data.” |
| properties | Assortment of properties of the log. |
Inside the properties attribute are a number of nested attributes:
| properties attribute | Description |
| Message | Primary success or failure message. |
| MembershipId | Default membership ID of the digital community. |
| GroupMemberships | Assortment of what community teams the digital community belongs to. There could also be a number of “NetworkGroupId” and “Sources” listed inside this property since a digital community can belong to a number of community teams concurrently. |
| MemberResourceId | Useful resource ID of the digital community that was added to or faraway from a community group. |
Inside the GroupMemberships attribute are a number of nested attributes:
| GroupMemberships attribute | Description |
| NetworkGroupId | ID of a community group the digital community belongs to. |
| Sources |
Assortment of how the digital community is a member of the community group.
|
Inside the Sources attribute are a number of nested attributes:
| Sources attribute | Description |
| Sort | Denotes whether or not the digital community was added manually (“StaticMembership”) or conditionally by way of Azure Coverage (“Coverage”). |
| StaticMemberId | If the “Sort” worth is “StaticMembership,” this property will seem. |
| PolicyAssignmentId | If the “Sort” worth is “Coverage,” this property will seem. ID of the Azure Coverage task that associates the Azure Coverage definition to the community group. |
| PolicyDefinitionId | If the “Sort” worth is “Coverage,” this property will seem. ID of the Azure Coverage definition that incorporates the circumstances for the community group’s membership. |
How do I get began?
Step one you’ll must take is to arrange your Log Analytics workspace or your storage account, relying on the way you wish to devour these occasion logs. You need to notice that in case you’re utilizing a storage account or occasion hub, it’ll must be in the identical area of the community supervisor you’re accessing logs from. In case you’re utilizing a Log Analytics workspace, it may be in any area. The community supervisor you’re accessing the logs of received’t must belong to the identical subscription as your Log Analytics workspace or storage account, however permissions might limit your skill to entry logs cross-subscription.
Notice that at the least one digital community have to be added or faraway from a community group in an effort to generate logs. A log will generate for this occasion a pair minutes later.
Accessing Azure Digital Community Supervisor’s occasion logs with Log Analytics
Step one is to navigate to your required community supervisor and choose the Diagnostic settings blade underneath the Monitoring part. Then you possibly can choose Add diagnostic setting and choose the choice to ship the logs to your Log Analytics workspace.
Then you possibly can navigate to your Log Analytics workspace straight by means of your community supervisor by deciding on the Logs blade underneath the Monitoring part.
Alternatively, you can too navigate to your Log Analytics workspace within the Azure Portal and choose the Logs blade.
From both place, you possibly can run your personal queries in your community supervisor’s emitted logs for community group membership adjustments, or you can too run our preloaded queries. Our preloaded queries can fetch the latest community group membership adjustments and failed community group membership adjustments.
Accessing Azure Digital Community Supervisor’s occasion logs with a storage account
Step one is to once more navigate to your required community supervisor and choose the Diagnostic settings blade underneath the Monitoring part. Then you possibly can choose Add diagnostic setting and choose the choice to archive the logs to your storage account.
Then you possibly can navigate to your storage account and choose the Storage browser blade.
Choose Blob containers. A blob container shall be mechanically generated as soon as community group membership adjustments happen.
Navigate down the blob container’s file path till you attain a JSON file for the datetime specified by that file path.
Obtain the JSON file to view the uncooked logs for the file path’s datetime.
Be taught extra about Azure Digital Community Supervisor occasion logging
In just some clicks, you’ve arrange your community supervisor to route occasion logs to your Log Analytics workspace or your storage account. Now, you will get visibility into every incidence of a digital community coming into or leaving a community group. Further log classes are within the works, and within the meantime, be at liberty to take a look at our public documentation for extra on Azure Digital Community Supervisor.
