Aviz Networks details ONES 2.0 integration with Slack and Zendesk

Aviz Networks released ONES 2.0, adding a rule engine that routes network alerts into Slack and Zendesk to reduce noise and speed incident handling within existing collaboration and ticketing workflows.

Product update

ONES 2.0 introduces a rule engine that evaluates network telemetry and can forward alerts via webhooks to Slack channels and Zendesk endpoints for ticket creation or updates.

The release also documents supportability functions that include generation of tech-support dumps and syslogs and access to devices via console or Secure Shell (SSH).

Technical breakdown

The vendor describes the rule engine as using Machine Learning (ML) techniques and pattern analysis rather than only simple threshold checks to detect anomalies in network data.

Configuration options include rule parameters, threshold types, notification targets, and the ability to provide Application Programming Interface (API) tokens and channel identifiers for ticketing and messaging integrations; the system also delivers a weekly digest that lists metric names, threshold types, device addresses, and related device indicators.

Operational impact

The blog states alerts include contextual details about issue type, severity, and suggested actions so teams receive targeted information instead of generic notifications.

The vendor reports the integration can shorten mean time to detect and mean time to respond by routing alerts into collaboration and ticketing workflows and by automating ticket creation.

Key findings

ONES 2.0 supports customizable rules that administrators can tune to their network environment, with options to adjust conditions, thresholds, and notification channels.

The integration is presented as compatible with Slack and Zendesk and extensible to other messaging or ticketing systems via webhooks and API tokens.

Leadership perspective

The vendor frames the release as intended to help NetOps teams move from reactive monitoring to a workflow that pushes alerts into existing operational tools.

Documentation emphasizes rule customization, weekly summaries of rule activity, and standard support functions to assist operational teams in incident investigation and remediation.

This Blog Signals brief summarizes the vendor blog; enterprise IT and security leaders can use the described ONES 2.0 capabilities to route alerts into collaboration and ticketing workflows and maintain incident logs within existing systems. This “Blog Signals brief” is a fact-based summary of the vendor blog.