Can't identify backed up entity from Recovery Service Activity Logs

[steveharrington1]

Background: We are evaluating ways to make Azure logs more useful in our platform, and are currently looking at some use cases around Azure Recovery Service Vaults. Specifically, there is an activity log that indicates when a Recovery Service backup job is completed that would be useful. However, when referencing the entity that was backed up, it only provides the entity name. This is not enough to be uniquely identifiable- we also need the resource group.

Request: We'd like have the resource group and/or the full resource_id of the backed up entity added to the Activity Log generated from Azure Recovery Service backups. This will allow us to do some helpful correlation/tagging automatically in Datadog that solves some customer use cases.

category: Administrative eventName: AzureBackupActivityLog operation name: Microsoft.RecoveryServices/vaults/backupFabrics/protectionContainers/protectedItems/backup/action

Note: While there are Recovery Service resource logs we could use to get this information, we want to implement this based on activity logs since they are significantly simpler to configure and manage.

[steveharrington1]

Hi @njuCZ is there any update here on when this will be implemented?

cc @SriniBanala

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Sharmistha-Rai.

---

Issue meta data

Issue content:	**Background:** We are evaluating ways to make Azure logs more useful in our platform, and are currently looking at some use cases around Azure Recovery Service Vaults. Specifically, there is an activity log that indicates when a Recovery Service backup job is completed that would be useful. However, when referencing the entity that was backed up, it only provides the entity name. This is not enough to be uniquely identifiable- [we also need the resource group](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftcompute). **Request:** We'd like have the resource group and/or the full resource_id of the backed up entity added to the Activity Log generated from Azure Recovery Service backups. This will allow us to do some helpful correlation/tagging automatically in Datadog that solves some customer use cases. category: Administrative eventName: AzureBackupActivityLog operation name: Microsoft.RecoveryServices/vaults/backupFabrics/protectionContainers/protectedItems/backup/action **Note**: While there are Recovery Service resource logs we could use to get this information, we want to implement this based on activity logs since they are significantly simpler to configure and manage.
Issue author:	steveharrington1
Assignees:	njuCZ
Milestone:	-

[Sharmistha-Rai]

@meeraharidasa, @njuCZ and @SriniBanala - this is an Azure Backup ask. Please assign it to them.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pvrk.

---

Issue meta data

Issue content:	**Background:** We are evaluating ways to make Azure logs more useful in our platform, and are currently looking at some use cases around Azure Recovery Service Vaults. Specifically, there is an activity log that indicates when a Recovery Service backup job is completed that would be useful. However, when referencing the entity that was backed up, it only provides the entity name. This is not enough to be uniquely identifiable- [we also need the resource group](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftcompute). **Request:** We'd like have the resource group and/or the full resource_id of the backed up entity added to the Activity Log generated from Azure Recovery Service backups. This will allow us to do some helpful correlation/tagging automatically in Datadog that solves some customer use cases. category: Administrative eventName: AzureBackupActivityLog operation name: Microsoft.RecoveryServices/vaults/backupFabrics/protectionContainers/protectedItems/backup/action **Note**: While there are Recovery Service resource logs we could use to get this information, we want to implement this based on activity logs since they are significantly simpler to configure and manage.
Issue author:	steveharrington1
Assignees:	-
Milestone:	-

[steveharrington1]

Hi @pvrk , do you have any update on timeline for this request? cc @SriniBanala

[pvrk]

@steveharrington1 : Sincere apologies for the delay. Can you please provide more clarity on the resource group? Which resource group? The backup item resides in the vault and hence the backup item as an ARM object belongs to the vault's resource group. If you are asking for source resource group (the backed up machine's resource group), then please let me know.

[steveharrington1]

Hi @pvrk , yes I'm requesting the source resource group (or the source resource_id would also be fine).

We want enough information to deterministically identify the resource that was backed up.

[pvrk]

@steveharrington1 : Thanks for providing the clarity. I am checking from the backend. Meanwhile can you please let me know how are you extracting the activity logs from the recovery services vault?

[steveharrington1]

@pvrk we are creating Activity Log diagnostic settings that forward all Activity Log Types to an event hub. From there we use a function to export the logs out of Azure to our SaaS platform. Here are the full docs including a PS script for configuring activity logs as described above.

Note that we want to use the subscription level activity logs, not the recovery service vaults resource logs for our feature. Using Activity logs significantly streamlines the setup process and reduces management overhead for our users.

[pvrk]

@steveharrington1 : Thanks for the clarity. Did you already successfully extracted our logs in the methodology stated above? I am asking because we are hearing other concerns about retrieving these logs via PS/CLI or other automation techniques. So, that's why wanted to check with you.

[steveharrington1]

@pvrk Sure. Our customer are not having any issues extracting logs in general, or with the automated scripts we provide. We just want the additional information I've outlined in the recovery service activity logs.

[pvrk]

@steveharrington1 : I have verified from the backend that we are supplying only the 'friendlyName'. Will try to get the entire ARM ID of the resource, if possible. @mepand : To be added to our backlog.

[steveharrington1]

Thanks @pvrk. Can you provide any guidance on timeline?

[mepand]

@steveharrington1 We are checking with the engineering team. Will get back on the timeline by mid Jan.

[mepand]

Apologies for the delay. We couldn't make much progress due to some high priority items. Will update the thread once we get specific ETA from the service team.

[steveharrington1]

@mepand is there any update here? We'd like to add this feature in the next few months, and identifying the specific entity will enable a more complete experience