Product Deep Dive: WhatsUp Gold 360 Notification Management

Jason Alberino | Posted on August 18, 2026 | Monitoring

From Alert Noise to Notification Control

How WhatsUp Gold 360 Notification Management routes the right monitoring events to the right people, channels and schedules—and where the experience could go next.

TL;DR — WhatsUp Gold 360 Notification Management gives administrators and users a shared cloud layer for defining providers, communication channels, topics, subscriptions, filters and schedules. Email and SMS are joined by Microsoft Teams and Slack delivery introduced in the July 2026 release. The result is more control over who receives supported infrastructure notifications, where they receive them and when. Future concepts discussed in this post—including customer-managed authentication, expanded incident workflows, mobile experiences and smarter event context—are directional, not commitments.

A Monitoring Event Is Only Useful If It Reaches the Right Person

Network monitoring teams rarely suffer from a shortage of signals. The harder problem is turning those signals into messages that reach the correct responder without flooding everyone else. A branch-office connectivity loss belongs with the network operations team. A license-expiration notice may belong with an administrator or procurement owner. A threshold breach affecting a production service may need a team channel during business hours and a personal channel for the on-call engineer overnight.

That routing logic becomes harder when an organization operates several WhatsUp Gold instances, multiple sites and different collaboration tools. Recipients change. On-call schedules rotate. One business unit lives in Microsoft Teams while another works in Slack. Equivalent notification rules maintained separately on every monitoring server can drift over time.

WhatsUp Gold 360 Notification Management introduces a centralized cloud model for supported notifications. Rather than treating every destination as a one-off address, it separates the event, the audience, the delivery channel and the timing rules. That separation is what makes the feature more than another “send an email” dialog.

What WhatsUp Gold 360 Notification Management Is

Notification Management is a built-in WhatsUp Gold 360 capability documented in the July 2026 release. It organizes event-driven notifications around topics. A topic represents a notification scenario, such as a monitored resource becoming unavailable or a performance threshold being breached. Users subscribe to relevant topics and can apply supported filters and schedules. Administrators configure the providers and organizational channels that make delivery possible.

The same system also supports notices: system-defined informational messages from Progress, such as license reminders, planned maintenance information or feature announcements. Some notices can be mandatory. Topics and notices serve different purposes, but both give the portal a consistent way to connect information with an intended audience.

The practical model: An event or notice identifies what happened. A subscription identifies who is interested. Filters and schedules determine whether the message should be sent in the current context. A communication channel determines where it goes. A provider handles delivery.

The Notification Pipeline, Step by Step

Layer	What it controls	Illustrative example
Event or notice	The condition or information that starts the workflow	A monitored resource becomes unavailable; Progress announces planned maintenance
Topic	The notification scenario to which a user can subscribe	Resource unavailable or performance threshold breached
Subscription	The relationship between a user and a topic or notice	The branch-network engineer subscribes to connectivity events
Filters and rules	The supported conditions that narrow delivery	Only a selected site, connector or severity
Schedule	The time window in which delivery is allowed	Weekdays during a regional support shift
Channel	The destination used for the message	Personal email, SMS, a Teams channel or a Slack channel
Provider	The service that powers delivery	An administrator-configured SMTP server, SMS gateway or webhook destination

This structure matters operationally because each layer can change independently. A team can change its collaboration destination without redefining the underlying event. A user can update a personal channel without asking an administrator to rebuild an organizational route. Administrators can adjust schedules when support coverage changes while preserving topic subscriptions.

Personal Channels and Organizational Channels Serve Different Jobs

Personal channels put delivery preferences close to the user

A personal channel belongs to an individual user. Examples include an email address or phone number. Personal channels are useful when delivery should follow the person rather than the team: an on-call engineer’s SMS number, an administrator’s email address or a reviewer’s preferred destination.

This model gives users control over how they receive the topics to which they subscribe. It also reduces the need to encode every individual address into a shared team configuration. That flexibility still needs governance. Critical services should not depend on one person’s channel without a documented backup path, and personal channels should be tested after role or contact changes.

Organizational channels create shared destinations

Administrators define organizational channels for teams, groups or common operational destinations. A Microsoft Teams channel for the network operations center, a Slack channel for a cloud operations group or a shared delivery route for a regional support desk are examples. Organizational channels make ownership visible and reduce the maintenance burden of duplicating recipients across many rules.

The distinction also supports a useful division of responsibility: administrators govern shared providers, approved destinations and schedules; individual users manage personal preferences and subscriptions within the available model. That is more scalable than forcing one role to maintain every recipient and every route.

Email, SMS, Microsoft Teams and Slack: Choose the Channel for the Job

WhatsUp Gold 360 Notification Management supports email and SMS delivery. The July 2026 release also introduced Microsoft Teams and Slack integrations. Teams and Slack use incoming webhooks tied to a destination channel rather than an individual inbox. Administrators can define the destination, verify connectivity and enable or disable the channel independently of other providers.

Channel	Best fit	Important consideration
Email	Detailed messages, broad accessibility and non-urgent follow-up	Inbox volume can bury operational messages; use topic scope and schedules deliberately
SMS	Time-sensitive personal delivery when a responder may be away from a workstation	Keep the recipient set narrow; confirm gateway, usage and escalation expectations
Microsoft Teams (Beta)	Shared visibility in a Microsoft-centered operations workflow	Delivery targets a channel through a webhook; current setup documentation labels the channel beta
Slack (Beta)	Shared visibility for teams already coordinating in Slack	Delivery uses a workspace/channel webhook; current setup documentation labels the channel beta

A channel is not an escalation policy by itself. Posting every event to chat may simply move alert noise from the inbox to a busier room. The useful design question is not “Which integrations do we have?” It is “Which audience needs this topic, through which destination, during which coverage window?”

Five Practical Notification Management Examples

The following scenarios are illustrative. They show how the documented notification model can be applied; they are not customer case studies or promises that every event and filter described is available in every tenant configuration.

1. A branch loses internet connectivity after hours

A retailer has dozens of remote sites, but only one engineer covers overnight connectivity incidents. The administrator creates an organizational email channel for the network operations group and maintains the provider used to send messages. The on-call engineer configures a personal SMS channel. Subscriptions and schedules route the relevant connectivity topic to the group during staffed hours and to the on-call path overnight.

This design works when the connector and cloud path can report the condition. It also needs a fallback for failures that prevent cloud delivery. The operations runbook should state how the team validates the site, checks connector status and escalates if the notification path itself is unavailable.

2. A manufacturing team wants production alerts, not branch-office noise

A manufacturer operates separate WhatsUp Gold environments for corporate IT and plant networks. The plant support team subscribes to the topics relevant to its operational scope and applies supported site, connector or severity filters. Corporate events remain available to the central network team without filling the plant team’s channel.

The advantage is not simply fewer messages. Ownership becomes explicit. A recipient can see why the message was routed to that destination, and administrators have a central place to review shared channels and schedules. For safety-critical or regulated processes, the cloud notification layer should supplement—not silently replace—approved local alarm and escalation procedures.

3. Teams and Slack coexist after an acquisition

The parent company coordinates incidents in Microsoft Teams, while a recently acquired business uses Slack. WhatsUp Gold 360 can route supported notifications into each group’s existing collaboration channel through separate webhook-based destinations. The monitoring event does not need to be rewritten merely because the audience uses a different collaboration platform.

Webhook ownership is the hidden operational issue. Teams should document who created each webhook, how it is protected, how rotation or revocation is handled and what happens if the destination channel is renamed or archived. A test send should be part of onboarding and change management, not a one-time setup step.

4. A threshold breach should reach people only during their shift

A regional support team needs performance-threshold notifications during its operating hours, but another team covers nights and weekends. Schedules can control when channels are eligible for delivery. Each group can receive the same topic during a different window without cloning the monitored resource or rebuilding the underlying monitoring logic.

Schedules reduce avoidable delivery, but they create boundary conditions. Time zones, daylight-saving changes, holidays and gaps between shifts should be tested. If a schedule ends at the exact moment another begins, the team should verify how events at that boundary are handled and document the expected behavior.

5. An administrator needs product notices without sending them to the NOC

Not every message is an infrastructure incident. A license-expiration reminder, planned WhatsUp Gold 360 maintenance window or feature announcement may require administrative attention without interrupting the network operations channel. Notices give these messages their own subscription and delivery model. Mandatory notices provide a path for information that Progress determines must be delivered.

This separation helps keep operational channels focused. It also gives administrators a reason to review notice ownership whenever licensing, procurement or platform responsibilities change.

From Multiple WhatsUp Gold Servers to One Notification Layer

The centralized model becomes more valuable as the number of monitored environments grows. A WhatsUp Gold Enterprise or Enterprise Plus customer may operate independent instances by geography, business unit, security zone or operational function. Local servers continue to perform monitoring and many administrative tasks, while WhatsUp Gold 360 provides a common layer for supported cloud visibility and notifications.

Without a common layer, a recipient change may need to be repeated across multiple servers. Schedules can diverge. One site may still route to a former employee. Another may use an obsolete team channel. Centralized Notification Management creates a place to standardize supported destinations and subscriptions while preserving local monitoring independence.

What centralization does not mean: WhatsUp Gold 360 is not a cloud-hosted replacement for every local WhatsUp Gold action, alert policy or administrative workflow. Teams should document which notifications originate in WhatsUp Gold 360, which remain local and how duplicate or missing coverage will be detected.

Design Notification Management Like an Operational System

A successful rollout needs more than creating notification channels. Treat notification routing as a small operational system with owners, tests and lifecycle controls.
Inventory audiences before destinations. Identify the teams and roles responsible for each class of event. Do not begin with a list of email addresses.
Separate urgent events from informational notices. An outage, a threshold breach and a product announcement should not compete in the same route by default.
Define personal versus organizational ownership. Decide which channels users maintain and which destinations administrators govern.
Map coverage windows. Include time zones, shift boundaries, weekends, holidays and regional handoffs.
Test every path. Verify provider connectivity, webhook destinations, message rendering and delivery to an actual recipient.
Plan for failure. Keep an independent route or local workflow where cloud connectivity, connector availability or third-party delivery could interrupt notification.
Review usage and billing. Email and SMS are tracked for monthly usage; administrators should understand the applicable consumption model before broad rollout.
Audit the lifecycle. Revalidate channels when personnel, phone numbers, team names, workspaces, providers or support contracts change.

Common Mistakes to Avoid

Sending every topic to every channel. More destinations do not create better coverage if responders cannot distinguish urgency or ownership.
Treating chat as guaranteed delivery. A webhook can fail, a channel can be muted and a collaboration platform can be unavailable.
Using one personal channel as a team route. Staff changes can break coverage without an obvious configuration error.
Ignoring duplicate notifications. Local WhatsUp Gold actions and WhatsUp Gold 360 subscriptions may both fire unless the operating model is designed deliberately.
Skipping post-change tests. A saved configuration does not prove that the provider, webhook and destination still work end to end.
Assuming all future events are supported today. Topic coverage, filters and workflows should be checked against current documentation and the tenant before deployment.

What Comes Next: From Message Routing to an Incident Experience

Notification Management establishes reusable building blocks: identity, topics, subscriptions, filters, schedules, providers and delivery channels. Those components can support a broader operational experience over time. The logical direction is a system that does more than send a message—one that helps teams understand, own and act on an incident across multiple monitoring environments.

The concepts below describe future intent supplied from previously shared roadmap direction. They are not statements of availability, dates or contractual commitments. Product development, naming, packaging, timing and scope may change.

Bring your own authentication

A customer-managed authentication model could let organizations connect WhatsUp Gold 360 access to their established identity environment rather than managing cloud access as a separate island. In practical terms, the intent is to make user access fit more naturally with enterprise identity governance, onboarding and offboarding practices.

The value would be administrative consistency: access could follow the organization’s approved identity lifecycle, and platform ownership could align with existing controls. The implementation details matter, however. “Bring your own authentication” could refer to different protocols, identity providers, federation patterns, domain requirements or licensing conditions. We plan to support OIDC & SAML-based authentication workflows.

A richer notification and incident center

A centralized incident view could give operators one place to review active notifications across sites and WhatsUp Gold instances, see ownership and begin follow-up. Over time, that could reduce the gap between “a message was sent” and “the team understands who is handling it.” Useful future workflows might include acknowledgement of state, incident assignment, escalation context or a clearer event timeline.

Those examples describe potential value, not confirmed functionality. An incident center becomes useful only when state is trustworthy and roles are clear. If acknowledgement in one system does not synchronize with another, operators may still need to reconcile local and cloud views.

Mobile and push-oriented workflows

Email, SMS and chat cover many delivery patterns, but mobile-friendly interaction could make it easier for an on-call engineer to review context and take the next approved step away from a workstation. The important distinction is between receiving a push message and supporting a complete mobile incident workflow. A useful experience needs identity, context, acknowledgement behavior and a clear route into local troubleshooting when deeper action is required.

Smarter context, correlation and root-cause assistance

As WhatsUp Gold 360 receives supported data from multiple environments, future capabilities could help teams group related signals, highlight likely dependencies or summarize the evidence around an event. That direction could reduce the time spent comparing messages from several sites, connectors or monitoring servers. The aim with smart root cause analysis is to provide decision support, not proof of cause.

Correlation can point an operator toward a likely explanation, but configuration data, dependency quality, telemetry coverage and timing all affect the result.The local monitoring system and the engineer’s validation remain essential.

More deployment and delivery flexibility

The longer-term opportunity is to meet customers where their operations already live: different identity systems, collaboration channels, network boundaries and monitoring topologies. Additional providers, integrations or deployment patterns could extend the same topic-and-subscription model without forcing every customer into one route.

Highly isolated or air-gapped environments remain a special case. The currently documented connector model requires cloud connectivity. In the future, we’d like to support isolated deployments with no internet connectivity.

Current Capability or Future Direction?

Capability	Status
Built-in Notification Management	Generally Available in the July 2026 WhatsUp Gold 360 release
Personal and organizational channels	Generally Available; users and administrators have different configuration roles
Topics, subscriptions, filters and schedules	Generally Available for supported notification scenarios
Email and SMS	Generally Available communication methods
Microsoft Teams and Slack	Introduced in July 2026; currently beta
Network Path Health report	Generally Available in the July 2026 WhatsUp Gold 360 release
Bring your own authentication	Future direction
Expanded incident center, mobile/push workflows and Smart RCA	Future direction
Air-gapped or additional deployment models	Future direction

The Goal: Fewer Notification Decisions at the Moment of Failure

When an incident begins, operators should not have to decide from scratch who owns it, which channel to use or whether the recipient is on shift. Those decisions belong in the notification design. WhatsUp Gold 360 Notification Management provides a framework for making them in advance through topics, subscriptions, channels, providers, filters and schedules.

For one environment, that structure can make delivery easier to understand. Across multiple WhatsUp Gold servers, sites and teams, it becomes a shared operating layer. Email, SMS, Microsoft Teams and Slack give organizations several ways to meet responders where they work, while personal and organizational channels keep individual preferences separate from team-owned destinations.

The future opportunity is larger: connect notification delivery with enterprise identity, incident context, mobile workflows and smarter analysis. The foundation is now visible. The next step is to expand what teams can do after the message arrives—without losing the clarity, control and local monitoring independence that made centralized notification management useful in the first place.

Explore WhatsUp Gold 360 Notification Management in the official documentation and validate the available topics, providers, filters, channel status and licensing for your environment before deployment.