Skip to content

Commit 991fa56

Browse files
committed
remove postman reference
1 parent 62d2f25 commit 991fa56

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

support/azure/partner-solutions/ingestion-key-rotation-log-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To work around the issue, manually update the ingestion key using the following
2929

3030
1. Find the **resource ID** of the Azure New Relic resource associated with the account where the ingestion key was rotated. If multiple resources are linked to the same account, you can make the API call for any one of them.
3131

32-
2. Make the API call to update the ingestion key. Use an API client (like **Postman** or **Bruno**) to make a **POST** request to the following endpoint:
32+
2. Make the API call to update the ingestion key. Use an API client (like **Bruno**) to make a **POST** request to the following endpoint:
3333

3434
```HTTP
3535
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/NewRelic.Observability/monitors/{monitorName}/refreshIngestionKey

0 commit comments

Comments
 (0)