Webhooks are real-time HTTP requests to send information from source application to destination application when a certain event is triggered. Now, you can integrate Webhooks with NetFlow Analyzer to send information to specified webhook URL of an integrated application. It is now possible to integrate NetFlow Analyzer with Microsoft Teams, Cisco Webex , Telegram and Pager Duty along with any third-party applications that supports Webhook URL.
With Webhook, NetFlow Analyzer sends details of the alert to the particular URL of the specified third-party application.
Integration with Webhook enables apps to transfer data smoothly without any hassles when any event occurs. It is essential to collaborate with other apps with NetFlow Analyzer to boost network performance, troubleshoot issues faster.
NetFlow Analyzer monitors network performance, detect anomalies and track bandwidth consumption. Webhooks aides NetFlow Analyzer to send alert to applications like PagerDuty, Telegram, MSTeams, Cisco Webex by leveraging its bandwidth monitoring capabilities. An alert is raised when a threshold is violated and the alarm details are sent to the concerned applications immediately.
NetFlow Analyzer sends the alert data to the concerned URL as an HTTP request once the desired event takes place. In return, the app will send an HTTP response to NetFlow Analyzer. You must get the Webhook URL of the application to which the data is sent.
After HTTP request is raised, a acknowledgement response code will be added in NetFlow Analyzer logs. Similarly for every failed HTTP request, a failure response code will be added in the logs.
In NetFlow Analyzer, you can specify the type of request made to the third-party application in the given Webhook URL method types:
You can add any number of alarm variables and custom fields like IP Address, Device Type, Severity, Location, Contact Details, and more, therefore whenever an event occurs, these details will be sent as a parameter to the specified webhook URL.
The message that will be shared to the webhook URL in the above case is shown below:
Note: Proxy variables have been used in the above example. The actual values will be updated for the variables when the webhook is invoked from NetFlow Analyzer.
Unlike the form-data and form-url encoded data types, choosing the raw data type gives you option to add a raw payload content that is not restricted by any parameters.
The payload types of HTTP requests supported by NetFlow Analyzer are: