Sign in
scheduledQueryRules

Update log search Rule.

patch/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/scheduledQueryRules/{ruleName}

Path parameters

ruleNamestring required

The name of the rule.

Parameters

../../../../../common-types/resource-management/v2/types.json#/components/parameters/SubscriptionIdParameter — unresolved $ref
../../../../../common-types/resource-management/v2/types.json#/components/parameters/ResourceGroupNameParameter — unresolved $ref
../../../../../common-types/resource-management/v2/types.json#/components/parameters/ApiVersionParameter — unresolved $ref

Request body

tagsobject

Resource tags

Response

Successful request to update an Log Search rule

idstring

Azure resource Id

namestring

Azure resource name

typestring

Azure resource type

locationstring required

Resource location

tagsobject

Resource tags

kindstring

Metadata used by portal/tooling/etc to render different UX experiences for resources of the same type; e.g. ApiApps are a kind of Microsoft.Web/sites type. If supported, the resource provider must validate and persist this value.

etagstring

The etag field is not required. If it is provided in the response body, it must also be provided as a header per the normal etag convention. Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the etag (section 14.19), If-Match (section 14.24), If-None-Match (section 14.26), and If-Range (section 14.27) header fields.

Changes

Changed in 2 of the 13 revisions of this API.11