Microsoft Azure

Azure Monitor: Log Profiles

Monitor Management Client

Developer tools#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Monitor Management Client

Endpoints 5

LogProfiles

  • GETLogProfiles_List/subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofilesList the log profiles.
  • GETLogProfiles_Get/subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofiles/:logProfileNameGets the log profile.
  • PUTLogProfiles_CreateOrUpdate/subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofiles/:logProfileNameCreate or update a log profile in Azure Monitoring REST API.
  • DELETELogProfiles_Delete/subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofiles/:logProfileNameDeletes the log profile.
  • PATCHLogProfiles_Update/subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofiles/:logProfileNameUpdates an existing LogProfilesResource. To update other fields use the CreateOrUpdate method.

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
5 operations on 2 pathsGET 2PUT 1PATCH 1DELETE 1
Main resources
LogProfiles 4
Response formats
application/json
Description format
Swagger 2.0, API version 2016-03-01

How to test the Azure Monitor: Log Profiles in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Monitor: Log Profiles collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “LogProfiles_List” (GET /subscriptions/:subscriptionId/providers/Microsoft.Insights/logprofiles), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure Monitor: Log Profiles?

Monitor Management Client It is listed under Developer tools and has 5 endpoints.

Who publishes the Azure Monitor: Log Profiles?

It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Azure Monitor: Log Profiles?

Requests go to https://management.azure.com. Endpoint paths are added to this base URL.

How do I authenticate with the Azure Monitor: Log Profiles?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure Monitor: Log Profiles have?

5 operations on 2 paths (2 GET, 1 PUT, 1 PATCH, 1 DELETE). The largest groups are LogProfiles.

Is forking the Azure Monitor: Log Profiles free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.