More input to use --endpoint-id with command "az monitor data-collection rule association create"

[unixsubhasish17]

As per the page, options are given to use --data-collection-rule-id & --data-collection-endpoint-id but its no where mentioned that both options can't be use together.
#az monitor data-collection rule association create --name "NAME_OF_DCR_RULE" --rule-id "DCR_RULE_ID" --resource "VM_RESOURCE_ID" with this command, you cannot use --data-collection-endpoint-id "endpoint_resource_id" . Error will be "Association name for resource to endpoint must be configurationAccessEndpoint"

Now, to resolve this error, you need to associate DCR and DCE separately. You cannot use it together.
So, to Associate VM with DCR,
#az monitor data-collection rule association create --name "NAME_OF_DCR_RULE" --rule-id "DCR_RULE_ID" --resource "VM_RESOURCE_ID"

Now, time to associate endpoint with the VM,
#az monitor data-collection rule association create --name "configurationAccessEndpoint" --resource "VM_RESOURCE_ID" --endpoint-id "endpoint_ID"

[yonzhan]

Thank you for opening this issue, we will look into it.

[AllyW]

@unixsubhasish17 yes, that's restricted by service side even if cli removes the name validation part.

Azure service api would raise this "InvalidEndpointAssociationName" error when endpoint-id is provided in request body but association name is anything but not "configurationAccessEndpoint". If it bothers you too much, we can try to raise a feature request to data-collection service team. ;)

[unixsubhasish17]

Hello Ally, Is this possible to raise it and update the documentation? Thanks Subhasish

…

On Wed, 27 Mar 2024 at 10:26, AllyW ***@***.***> wrote: @unixsubhasish17 <https://github.com/unixsubhasish17> yes, that's restricted by service side even if cli removes the name validation part. Azure service api would raise this "InvalidEndpointAssociationName" error when endpoint-id is provided in request body but association name is anything but not "configurationAccessEndpoint". If it bothers you too much, we can try to raise a feature request to data-collection service team. ;) — Reply to this email directly, view it on GitHub <#28338 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BF7LYKENJZQZHQBMGFXTRO3Y2KGDXAVCNFSM6AAAAABDAA6NQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRSGI4TMOBZGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>