Updates for All Auvik Partners
User Interface Update
Heads up: The Knowledge Base link is being updated to our Support Portal, where you’ll find all the same helpful resources—plus improved support options.
|
Old |
New |
Why the change?
Updates have been made to improve navigation between submitting tickets, reviewing tickets, and accessing the knowledge base. This update highlights that this link now brings users to the full Support Portal.
Improved
-
Improvement to Cloning in Alerts V2: Option to Detach Sites from the Original Alert Definition
We’ve enhanced the alert cloning experience in Alerts V2 to help you better manage alert coverage across your sites—faster and with less manual work.
Now, when you clone an alert definition at the multi-site level, Auvik will ask if you’d like to remove the selected sites from the original alert definition. If you choose “Detach,” the sites will be removed from the original.
This improvement simplifies a previously manual task, saving time and reducing the chance of configuration errors when segmenting alert behavior across sites.
-
Create Alerts and Tags for Specific Devices by Exact Name
You can now create alerts and tags at the global and multi-site levels in alerts v2 using exact Device Name matches. This enables precise targeting or exclusion of named devices across sites.
Match Options:
- Equals
- Does not equal
This provides greater control for monitoring critical devices and filtering out non-essential ones.
-
Create Alerts and Tags Using Partial Device Name Matches
You can now create alerts and tags in alerts v2 at the global and multi-site levels using partial string matches on the Device Name. This simplifies managing alerts for groups of similarly named devices.
Match Options:
- Starts with / Does not start with
- Ends with / Does not end with
- Contains / Does not contain
This streamlines alert management across large networks using consistent naming patterns.
-
New Variables for Service Alerts: In alerts v2, you can now include device and interface names in service alert messages that are associated with devices or interfaces. When editing the Trigger Message or Clear Message, type $ to see the new variables:
$monitors.monitorStatus.deviceName
$monitors.monitorStatus.interfaceName
These variables provide more context for alerts, like Internet Connection Checks, to help troubleshoot faster.
-
Custom Configuration Status for Active/Inactive Updates in ConnectWise PSA
Customers can choose which Configuration Status is used when Auvik mark configurations Active or Inactive in ConnectWise PSA.Note: If you are using granular permissions for Table Setup in the ConnectWise PSA security role, Company / Configuration Status will need to be added for Auvik to read the available statuses.
Fixed
- When changing the alert type using “Apply Conditions to” in the Alerts v2 creation modal, the trigger condition now clears automatically. This fixes an issue where invalid trigger conditions could remain after switching alert types.
Coming Soon
-
Improved Notification Channel Association in Alerts v2
We’re making it easier to manage how your notification channels are connected to alerts in Auvik’s Alerts v2.
- Simplified site association: When creating or editing an alert definition, you can specify which sites a notification channel applies to. This reduces the extra steps needed to configure notifications for specific sites.
- Bulk alert association: In Manage Alerts → Alerts v2, you can associate a single notification channel with multiple alerts at once. This makes it faster to support new notification channels across your alerts.
These enhancements streamline how you connect alerts to notification channels.
-
Auvik Integration with ServiceNow CMDB
Auvik will be integrating with ServiceNow Configuration Management Database (CMDB) using the Service Graph Connector for Auvik. This integration will automate the synchronization of Auvik’s network device inventory with ServiceNow’s CMDB to help IT teams maintain accurate configuration data for governance, compliance, and operational efficiency.
New
-
MFA Reporting
You can now view MFA status at the user-account level across Microsoft Entra ID and Google Workspace. This new capability provides a centralized view of MFA coverage, helping you quickly identify gaps, reduce security risk and demonstrate compliance with regulatory frameworks and cyber insurance requirements.
Key highlights:
- Surface MFA status per account by integrating with Microsoft Entra or Google Workspace IdP.
- Highlight risk exposure when MFA isn’t enforced on specific accounts.
- Support security and compliance workflows by making gaps clear and remediation straightforward.
Improved
-
Updated Client Menu Export
The Client menu export now includes the RMM Client ID, making it easier to map clients across your RMM and other third-party systems.