Background
The Verizon SA360 application requires access to alert/event data from IBM Concert Operate / AIOps. SA360 provides an Alerts Dashboard used by Verizon NMC operators. These users do not access the AIOps native UI.
The dashboard must support large Areas of Responsibility (AORs). Verizon cited examples where an AOR may contain 97,000+ alerts. The SA360 UI requires efficient retrieval and navigation of this data.
Verizon Requirement
Verizon is requesting API support that allows the dashboard to:
- Request a specific page of alert data using page number/page size or limit/offset.
- Receive only the requested subset of records rather than the entire dataset.
- Receive an exact total alert count to support page navigation (e.g., "Page X of Y").
Sort results by one or more alert fields such as severity, date, and alert type.
This capability is required to support daily operational use of the SA360 Alerts Dashboard.
Investigation Performed
The IBM team engaged the Concert Operate product team to evaluate the requirement and identify supported approaches.
Key findings from the product team review:
The existing GET Alerts API supports filtering, limits, and offsets but does not provide traditional server-side pagination.
The API does not return exact counts suitable for "Page X of Y" navigation.
The AIOps native UI does not use server-side pagination and uses the same underlying API capabilities.
The product team highlighted challenges associated with traditional pagination against large, dynamic alert datasets, including count calculations, deep-page performance, and changing alert positions due to real-time updates.
IBM Recommended Approach
Based on discussions with the product team, IBM recommended using the built-in Concert Operate Db2 integration to export alerts into a dedicated downstream database and implementing pagination, sorting, counting, and optimized querying against that database.
This recommendation was based on the current product capabilities and limitations.
Verizon Response
Verizon has now rejected the recommended solution. Their position is:
The Verizon SRE organization has already rejected use of Db2 because Db2 is not an approved Verizon North Star technology.
Verizon wants to leverage the operational platform APIs rather than maintain a separate datastore.
Verizon believes the AIOps GUI successfully retrieves and displays alert information today and has requested a detailed walkthrough of how the existing GUI uses the GET Alerts API so they can attempt to replicate that behavior within SA360.
Verizon considers this capability blocking for Phase 1 validation and expressed concern about meeting the October 2026 commitment without a workable solution.
Requested Product Enhancement
Verizon is effectively requesting a product-supported API capability for large-scale alert retrieval that can satisfy dashboard-style navigation requirements without requiring a separate downstream data store. Desired capabilities include:
- Server-side pagination support.
- Exact or product-supported count retrieval.
- Multi-column sorting support.
- Scalable retrieval of large filtered alert populations.
Support for operational dashboards that need to browse alert data efficiently.
Business Impact
This requirement is tied to Verizon's SA360 operational dashboard and is currently considered a blocker to Phase 1 validation activities. Verizon has indicated urgency and is requesting a path forward as soon as possible.
Ask
Please evaluate this as a high-priority enhancement request and advise:
- Whether a product roadmap item already exists for this capability.
- Whether an alternative product-supported approach exists that avoids a separate Db2 datastore.
Whether the GET Alerts API (or a new API) could be enhanced to provide dashboard-friendly pagination, count, and sorting capabilities for large alert datasets.
