ControlUp Community

Connect, Learn, and Grow

Unified Communications Related Training & Support Archives

Unified Communications training and support-related archives from inside the ControlUp Community on Slack.

Latest ControlUp Updates: Anomaly Detection & License Reclamation

Posted on

Busy, busy — no slowing down when it comes to delivering a better DEX experience. Below are two new ControlUp features worth your attention: 1. Anomaly Detection ControlUp now includes anomaly detection that cuts through alert noise by focusing on behavior rather than static thresholds. Instead of firing every time a metric crosses an arbitrary line, it learns what normal looks like in your environment and flags meaningful deviations.…

Read the entire article here...

ControlUp Release AI Assistant Powered by Pulse AI!

Posted on

At a technical level, Pulse AI is ControlUp’s intelligence layer. It continuously correlates telemetry across endpoints, sessions, applications, networks, identity, and tickets, understands context, and drives action. Not “AI as a chatbot,” and not dashboards with a different coat of paint—but an agentic service designed to reduce the manual correlation work IT teams are forced to do today.

Read the entire article here...

Introducing Global DEX Findings by ControlUp

Posted on

Over the past several months, we’ve been using ControlUp’s global, anonymized telemetry to look for real patterns—crash surges, unstable binaries, regressions tied to specific builds, and behavior that only becomes obvious when you zoom out beyond a single environment. Not alerts. Not anecdotes. Actual signals that repeat across many customers.

Read the entire article here...

Troubleshooting Device Details Error in ControlUp Endpoints

Posted on

There was a discussion about an error message popping up when opening details for a specific device in Physical Endpoints/Dex portal. Support was contacted and a workaround for this issue has been found. A status update was provided and it was suggested to contact support. The maintenance was completed, but some users are still experiencing the error. The fix should be applied shortly, and logging out of SAML and logging back in is suggested to resolve the issue.

Read the entire article here...