2025-W34 Release - August 23th

• FortiGate FortiOS API Backups

  We’ve improved the backup functionality to default to API when available. The UI will display a green checkmark if either CLI or API credentials are valid and backups are running, and a key icon if credentials are valid but no API backups are detected. The tooltips will explain the difference between CLI and API authentication, helping you quickly identify whether issues are due to missing credentials or insufficient permissions.

  For Fortinet API backups to work, the API user must have Read/Write access to the System section of their Administrator Profile, with Read access for all other sections, and REST API Access enabled.

  To configure this:

  • Log into the Fortinet Web UI with a Super_Admin account.

  • Navigate to System → Admin → Profiles, create or edit a profile, set System Configuration to Read/Write, all other permissions to Read, and enable REST API Access.

  • Go to System → Admin → Administrators, create a REST API Admin user, assign the profile, and generate an API key

• Auvik Collector now supports Ubuntu 24.04 LTS

  Auvik Collector now supports Ubuntu 24.04 LTS (“Noble Numbat”), giving you a secure, future-proof platform. Collectors can be deployed via OVA, bash script, or cloud installs.

  For new customers or brand-new installs, simply deploy a new collector on Ubuntu 24.04 LTS—no additional steps are required.

  For existing collectors, wanting to upgrade, you have two options to move to 24.04:

  Deploy a new collector (recommended for simple setups): Install a fresh 24.04 collector, and to avoid disruptions ensure that you:

  • Rebuild configurations (e.g., networks to scan, shared collector site mappings, etc.).

  • Preferably use the same static collector IP as the one you are replacing.

  • Update TrafficInsights and Syslog settings (if the collector IP changes), map it to your monitored networks, and remove the old one.

  Upgrade your existing collector (recommended for complex setups): Depending your current version, upgrade sequentially (Example: 20.04 → 22.04 → 24.04) using the provided guides from 20.04 to 22.04 & from 22.04 to 24.04 . This approach doesn't require you to re-configure as mentioned in first option.

  This enhancement keeps Auvik aligned with customer OS standards, strengthens security, and ensures long-term reliability for network monitoring.

  Note:

  Ubuntu 20.04 Collectors is EOS as of Jul-28-2025

  Auvik continues to fully support collectors running on Ubuntu 22.04 LTS (“Jammy Jellyfish”), but we recommend planning an upgrade to 24.04 LTS to future-proof your deployments for the longer support timeline.

• Ada — Get Help Faster — Right from the Auvik Knowledge Base

  We’ve made it even easier to get the answers you need.

  You can now access Ada, Auvik’s virtual assistant, directly from our Knowledge Base. Whether you’re looking for step-by-step guides, troubleshooting advice, or quick how-tos, Ada can help you find the right documentation or answer in seconds. Just click on the support button at the bottom of the Knowledge Base window.
  
  

  Need more help? If you're logged in, you'll also be able to connect with a live Auvik support agent—right from the same window.

  No more switching tabs. No more hunting for the support link. Just fast, reliable help when and where you need it

  

Improved

• VPN Tunnel Status Handling

  We’ve improved how Auvik handles VPN tunnel status when devices stop reporting data. Previously, if we stopped receiving status information, the tunnel would disappear from view, which could prevent alerts from triggering. With this update, tunnels without incoming data will now be shown in an “unknown” state instead of being removed. Stale tunnels will be automatically cleaned up after a week.

• Meraki Integration Test Connection Handling

  We’ve updated the “Test Connection” feature so it now runs through the same Collector-based process used by real production connections. The change has been implemented in the backend to route test requests through the Collector, with added safeguards to match both successful and failed connection scenarios.

• Empty Device Name Sync Issues

  We’ve fixed an issue where devices without assigned names—including the default Device@IP format—could cause inventory sync failures with Autotask, ConnectWise, and ServiceNow. This typically happened when a device had no IP address, preventing the assignment of a default name.

• Okta Identity Management Integration - Gain deeper visibility into how users interact within your SaaS environment. By ingesting Okta security and event logs, this integration surfaces detailed insights into application usage helping IT teams monitor access patterns, identify anomalies, and strengthen overall security.

• Multi-IdP Integration Support - Support for multiple identity providers per Client enables using Okta alongside Google Workspace or Microsoft Entra ID. This flexibility ensures broader user coverage and a more complete picture of identity and application activity across your organization.

Improved

• Filter by Tags within Application Inventory

  Users can now filter applications by Tags within the Application Inventory table.

• Open Apps in New Tab from Reports

  Users can now open applications in a new tab when reviewing them from any report, ensuring the report view remains intact and avoids re-rendering.

• Updated Client Table Export

  The Client table export now includes Devices and an individual breakdown of Identity Management Providers and their status. Export includes; Tenant Name, Tenant Id, Active User Count, Identity Management Provider & Status, Devices Count, Count of Applications Classified Count of Applications Unclassified, and Total Applications.

• Application Insights & Insights Dashboard Removed 

  We’ve removed the Application Insights and Insights Dashboard pages. Their insights are now available in the enhanced Client Dashboard. The SaaS Health Score remains in the Customer Business Review Report.

• Application Adoption & Usage Chart Moved

  The Application Adoption and Usage chart has been moved from the Application Insights page to the Organizational Usage Report and now includes a detailed breakdown of discovered applications over the selected time period.

• Workflow Renamed to Alerting

  We’ve updated in-product terminology: Workflow is now called Alerting for greater clarity and consistency.

• Enhanced User Visibility on Identity Provider User Page

  The Identity Provider User Page now displays separate columns indicating whether a user has been imported into Auvik SaaS Management and whether they are disabled; note that activity is not collected for users in excluded groups, even if imported.

• Improved Group Insights on Identity Provider Group Page

  The Identity Provider Group Page now displays the total number of users per group and includes a column indicating whether the group has been excluded.

Fixed

• Fixed an issue where reports were generated and emailed in dark mode if enabled—reports are now consistently rendered and sent in light mode.

Coming Soon

• Adobe licensing visibility via SaaS Ops Integration

• Accessing licensing data via ASM API

• Smart Alert Suppression
• Google Workspace Identity Management Integration
• Okta Identity Management Integration

• Microsoft Entra ID Identity Management Integration
• How to install the Auvik collector from a bash script
• How to configure Ubuntu 24.04 for the Auvik collector
• Auvik collector and other system requirements
• How to enable SNMP on Ubuntu Linux 22.04/24.04 or above
• How to install the Auvik collector in a cloud environment