- 3 minutes to read

Step 12: Update Agent Configurations and Non-Events URIs

The v6 addresses no longer exist. On Windows Server, every v7 Core Service is its own IIS web site with its own port: the Web Client at the site root, the Web API at https://{host}:{port}/api/..., and the Log API at https://{host}:{port}/LogAPI/.... Every configuration that stored a v6 address must point at the new one, whether or not you enabled TLS. Use https:// when you completed Option A in Step 10, otherwise http://, and never localhost.

Understanding Which Addresses Change

flowchart LR AP["fa:fa-bell Alarm Plugins
Web Client URL"] -->|"Links in alerts"| WC["fa:fa-globe Web Client site"] NE["fa:fa-hourglass Non-Events agent
Log View API URI"] -->|"/api/..."| WA["fa:fa-cloud Web API site"] LA["fa:fa-bolt Logic Apps agent
LogAPI URI"] -->|"/LogAPI/"| LG["fa:fa-cloud-arrow-down Log API site"] PU["fa:fa-inbox Pickup Service
Log API Endpoint"] -->|"/LogAPI/"| LG RL["fa:fa-cloud-arrow-up Relay agents
connection string"] -->|"v7 format"| SB["fa:fa-cloud Azure Relay"] style AP fill:#E47528 style NE fill:#E47528 style LA fill:#E47528 style PU fill:#E47528 style RL fill:#E47528 style WC fill:#2678BD style WA fill:#2678BD style LG fill:#2678BD style SB fill:#9E59BB

Orange nodes are settings you update in this step; blue nodes are the v7 Core Services web sites they point at, and purple is Azure Relay. The Alarm Plugins link to the Web Client, the Non-Events agent queries Log Views through the Web API, the Logic Apps agent and the Pickup Service post to the Log API, and agents behind Service Bus Relaying need a v7 connection string.

Prerequisites

Alarm Plugins – Update the Web Client URL

The Web Client URL on the Configuration tab of an Alarm Plugin embeds a direct link to the signaling Monitor View in outgoing notifications. Update it even if you used TLS with the same host name in v6. It must be reachable by the recipient, so never use localhost.

  1. Open the Web Client → Administration → Settings → Alarm Plugins.
  2. Open each Alarm Plugin entry and go to the Configuration tab.
  3. Set Web Client URL to the new v7 address, for example https://nodinite.contoso.com:<Web Client port>/.
  4. Save.

Alarm Plugin Configuration tab with the Web Client URL field
Example of the Web Client URL field on the Configuration tab of the E-mail with options plugin; update it on every Alarm Plugin entry that has it.

Logic Apps – Update the LogAPI URI

If you use the Azure Logic Apps agent, set the LogAPI URI on its Logging tab to the v7 Log API, for example https://nodinite.contoso.com:<Log API port>/LogAPI/. See Configure Logging.

Pickup Service – Confirm the Log API Endpoint

Confirm that the Log API Endpoint of the Pickup Log Events Service uses the v7 Log API address and that Log Events flow; you configured it in Step 11.

Non-Events URI Updates (If Applicable)

If you use the Non-Events Monitoring Agent, update every Log View API URI: v7 changed the Web API structure, and Non-Events monitoring fails until you do.

  1. Confirm that the Non-Events agent runs v7; it was updated with the agents package in Step 7.
  2. In the Web Client, open the Log View that a Non-Events configuration uses and click Copy API URI.
  3. Paste the URI into the Log View API URI field of the matching Non-Events configuration.
  4. Save and repeat for every configuration.

Service Bus Relay Agents

If a Monitoring Agent is reached through Azure Relay, its connection string format changed in v7; the old SharedAccessKeyName=...;AuthenticationKey=... format is obsolete. Update it as described in Configure Service Bus Relaying for Monitor Agents.

Completion Checklist

  • Web Client URL updated on every Alarm Plugin that has it
  • Logic Apps LogAPI URI updated (if used)
  • Pickup Service Log API Endpoint confirmed
  • Every Non-Events Log View API URI replaced (if used)
  • Relay connection strings in the v7 format (if used)
  • The Non-Events and Logic Apps errors noted in Step 8 are gone

Next Steps