{"files":{"SKILL.md":"---\nname: monitormanagementclient\ndescription: \"MonitorManagementClient API skill. Use when working with MonitorManagementClient for subscriptions. Covers 1 endpoint.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# MonitorManagementClient\nAPI version: 2015-04-01\n\n## Auth\nOAuth2\n\n## Base URL\nhttps://management.azure.com\n\n## Setup\n1. Configure auth: OAuth2\n2. GET /subscriptions/{subscriptionId}/providers/Microsoft.Insights/eventtypes/management/values -- provides the list of records from the activity logs.\n3. Explore available endpoints below\n\n## Endpoints\n1 endpoint across 1 group. See references/api-spec.lap for full details.\n\n### Subscriptions\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /subscriptions/{subscriptionId}/providers/Microsoft.Insights/eventtypes/management/values | Provides the list of records from the activity logs. |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all values?\" -> GET /subscriptions/{subscriptionId}/providers/Microsoft.Insights/eventtypes/management/values\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 2015-04-01\n@auth OAuth2\n@endpoints 1\n@toc subscriptions(1)\n\n@endpoint GET /subscriptions/{subscriptionId}/providers/Microsoft.Insights/eventtypes/management/values\n@desc Provides the list of records from the activity logs.\n@required {$filter: any # Reduces the set of data collected.This argument is required and it also requires at least the start date/time.The **$filter** argument is very restricted and allows only the following patterns.- *List events for a resource group*: $filter=eventTimestamp ge '2014-07-16T04:36:37.6407898Z' and eventTimestamp le '2014-07-20T04:36:37.6407898Z' and resourceGroupName eq 'resourceGroupName'.- *List events for resource*: $filter=eventTimestamp ge '2014-07-16T04:36:37.6407898Z' and eventTimestamp le '2014-07-20T04:36:37.6407898Z' and resourceUri eq 'resourceURI'.- *List events for a subscription in a time range*: $filter=eventTimestamp ge '2014-07-16T04:36:37.6407898Z' and eventTimestamp le '2014-07-20T04:36:37.6407898Z'.- *List events for a resource provider*: $filter=eventTimestamp ge '2014-07-16T04:36:37.6407898Z' and eventTimestamp le '2014-07-20T04:36:37.6407898Z' and resourceProvider eq 'resourceProviderName'.- *List events for a correlation Id*: $filter=eventTimestamp ge '2014-07-16T04:36:37.6407898Z' and eventTimestamp le '2014-07-20T04:36:37.6407898Z' and correlationId eq 'correlationID'.**NOTE**: No other syntax is allowed.}\n@optional {$select: any # Used to fetch events with only the given properties.The **$select** argument is a comma separated list of property names to be returned. Possible values are: *authorization*, *claims*, *correlationId*, *description*, *eventDataId*, *eventName*, *eventTimestamp*, *httpRequest*, *level*, *operationId*, *operationName*, *properties*, *resourceGroupName*, *resourceProviderName*, *resourceId*, *status*, *submissionTimestamp*, *subStatus*, *subscriptionId*}\n@returns(200) Successful request to get a page of events in the activity logs\n\n@end\n"}}