{"files":{"SKILL.md":"---\nname: monitormanagementclient\ndescription: \"MonitorManagementClient API skill. Use when working with MonitorManagementClient for {resourceUri}. Covers 1 endpoint.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# MonitorManagementClient\nAPI version: 2019-03-01\n\n## Auth\nOAuth2\n\n## Base URL\nhttps://management.azure.com\n\n## Setup\n1. Configure auth: OAuth2\n2. GET /{resourceUri}/providers/Microsoft.Insights/metricBaselines -- **lists the metric baseline values for a resource**.\n3. Explore available endpoints below\n\n## Endpoints\n1 endpoint across 1 group. See references/api-spec.lap for full details.\n\n### {resourceUri}\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /{resourceUri}/providers/Microsoft.Insights/metricBaselines | **Lists the metric baseline values for a resource**. |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all metricBaselines?\" -> GET /{resourceUri}/providers/Microsoft.Insights/metricBaselines\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api MonitorManagementClient\n@base https://management.azure.com\n@version 2019-03-01\n@auth OAuth2\n@endpoints 1\n@toc {resourceUri}(1)\n\n@endpoint GET /{resourceUri}/providers/Microsoft.Insights/metricBaselines\n@desc **Lists the metric baseline values for a resource**.\n@required {resourceUri: any # The identifier of the resource.}\n@optional {metricnames: any # The names of the metrics (comma separated) to retrieve. Special case: If a metricname itself has a comma in it then use %2 to indicate it. Eg: 'Metric,Name1' should be **'Metric%2Name1'**, metricnamespace: any # Metric namespace to query metric definitions for., timespan: any # The timespan of the query. It is a string with the following format 'startDateTime_ISO/endDateTime_ISO'., interval: any # The interval (i.e. timegrain) of the query., aggregation: any # The list of aggregation types (comma separated) to retrieve., sensitivities: any # The list of sensitivities (comma separated) to retrieve., $filter: any # The **$filter** is used to reduce the set of metric data returned. Example: Metric contains metadata A, B and C. - Return all time series of C where A = a1 and B = b1 or b2 **$filter=A eq 'a1' and B eq 'b1' or B eq 'b2' and C eq '*'** - Invalid variant: **$filter=A eq 'a1' and B eq 'b1' and C eq '*' or B = 'b2'** This is invalid because the logical or operator cannot separate two different metadata names. - Return all time series where A = a1, B = b1 and C = c1: **$filter=A eq 'a1' and B eq 'b1' and C eq 'c1'** - Return all time series where A = a1 **$filter=A eq 'a1' and B eq '*' and C eq '*'**. Special case: When dimension name or dimension value uses round brackets. Eg: When dimension name is **dim (test) 1** Instead of using $filter= \"dim (test) 1 eq '*' \" use **$filter= \"dim %2528test%2529 1 eq '*' \"** When dimension name is **dim (test) 3** and dimension value is **dim3 (test) val** Instead of using $filter= \"dim (test) 3 eq 'dim3 (test) val' \" use **$filter= \"dim %2528test%2529 3 eq 'dim3 %2528test%2529 val' \"**, resultType: any # Allows retrieving only metadata of the baseline. On data request all information is retrieved.}\n@returns(200) Successful request to get the list of metric baseline values.\n\n@end\n"}}