Issue with `az monitor data-collection rule create` when updating existing DCR rule

[pensivepaddle]

Describe the bug

Followed the guide to update an existing DCR. Modified JSON accordingly and attempted pushing using CLI in Cloud shell. It kept returning error

Related command

az monitor data-collection rule create

Errors

The command claims DCR kind is different, and blank, while it indeed is not. It is further confirmed as using the API variant from the docs, with the same JSON file, worked with no issue.

(InvalidPayload) The new DCR kind `` is different from the previous one `Linux`. The kind is immutable.
Code: InvalidPayload
Message: The new DCR kind `` is different from the previous one `Linux`. The kind is immutable.
Exception Details:      (InvalidPayload) The new DCR kind `` is different from the previous one `Linux`. The kind is immutable.
        Code: InvalidPayload
        Message: The new DCR kind `` is different from the previous one `Linux`. The kind is immutable.

Issue script & Debug output

N/A

Expected behavior

DCR is pushed successfully

Environment Summary

azure-cli 2.61.0

core 2.61.0
telemetry 1.1.0

Extensions:
ai-examples 0.2.5
ml 2.26.0
monitor-control-service 1.0.2
ssh 2.0.3

Dependencies:
msal 1.28.0
azure-mgmt-resource 23.1.1

Additional context

No response

[yonzhan]

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

[AllyW]

@pensivepaddle the (InvalidPayload) message is justified by service and it should be the case in service side. Can you show me how you achieved it using the API?