Unlock Your Full Network Monitoring Flow Potential

by May 27, 2019

Traditionally, network monitoring software was designed to act in isolation, limited to features and capabilities defined by what’s within their code base. But with the advent of modern networks, corporations use a variety of tools and applications in their ecosystem to arrive at a solution to satisfy their requirements. Silos in the data is no longer acceptable. When a network monitoring tool and other applications can talk to each other or share data; they open up new areas to satisfy critical use-cases which otherwise would prove very difficult; if not impossible to solve with a single tool.

One popular method used by applications lately is to expose APIs which allow interactions with other network monitoring tools in the ecosystem (data interchange) and the ability to use scripts or automation to perform actions (application customizations) vs using a traditional approach of click-through graphical interfaces.

Our latest AIOps for NetOps network monitoring release exposes several key APIs for Network Flow use-cases which now allow the flow interaction with our unified NetOps Portal and with external applications such a Splunk or Grafana for analysis and automation as well as performing administrative tasks.

Network Flow Analysis (NFA) REST API is provided by the OData Services that runs on the NFA console. The OData service connects to the NFA console and Harvester Databases and enables data retrieval using the simplified OData Data Model.

Typical administrative use-cases can range from enabling interfaces, deleting old interfaces, etc. Below are two scenarios:

1. System Administrator has configured a network router to send NetFlow Data to NFA and wants to enable Interface(s) for Flow Analysis.

Enable single interface:


Enable multiple interfaces (Bulk API):

“InterfaceIds”:[<Enter the list of Interface_ids separated by a comma>]

2. System Administrator wants to know which interfaces have not received data after ‘X’ time and wants to delete all those interfaces for Flow Analysis.

Retrieve interfaces that has not received data after specific timestamp:

http://<nfa odata host>:<nfa odata port>/odata/api/interfaces?$filter = LastData eq 1547805618&$select =ID

Delete single interface:

http://<nfa odata host>:<nfa odata port>/odata/api/interfaces(<interface_id>)

Delete multiple interfaces (Bulk API):

http://<nfa odata host>:<nfa odata port>/odata/api/com.ca.nfa.odata.deleteInterfaces
“InterfaceIds”:[<Enter the list of Interface_ids separated by a comma>]

With AIOps for NetOps, our network monitoring solution provides administrators the ability to interact with Network Flow via APIs, increasing possibilities for automation and synergy with external applications.

We invite you to comment below and share your views on how Network Flow APIs can be used in your networks!

WEBCAST REPLAY: Did you miss the recent “What’s New in CA NetOps Fault Management”? Watch the replay here.

Additional Contributor:
Manvendra Singh is a Software Architect within the Broadcom Enterprise Software Division and is focused on AIOps solutions. He is passionate about designing and developing solutions to improve the Network Operations (NetOps) experience for customers. He holds a Bachelor Degree in Engineering and has over 13 years of experience in the Designing and Development of Software.