Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hey Marcus, This capability has been added as of the 7.1.0 release that released on Oct 24th, 2024
Thanks Marcus and Chris. After further discussions with the team, we have accepted the idea and will start to work on it.
At the end of the day, my customer needs this, and we cannot utilize the API. So the ask here is to just have the ulBWItol, and dlBwutil values from the syslog messages be included in NMS.
Hi Deva, I think so long as the intfUtilLog is being used instead of the API call to gather interface statistics, this would not have any gap that doesn't already exist. The guidance for using the intfUtilLog instead of the API already has updates to the settings to stop the gaps. The main issue here as I see it would be the correct settings of the interface speed - this is a customer configuration issue on the Versa though.
Hey Chris, Using the ulBwUtil and dlBwUtil figures for down_capacity_percentage and up_capacity_percentage has implications that may lead to datagaps since the same object has indicators coming in from multiple log types at different times..
My suggestion is to use Synthetic indicators since we already collect bw_up and bw_down metrics and if you use the rx_kbps and tx_kbps metrics to come up with a calculation for the object type, we can easily achieve what you are looking for.
Let me know if that suffices your use cases, or if you are looking for us to ship a Synthetic indicator with this calculation in future builds. Note that it might not be the same indicator 'down_capacity_percentage' or 'up_capacity_percentage' since we have a naming standard for Synthetic indicators that start with a 'S1_'
Adding the verbiage from the Versa link -
The Versa Operating SystemTM (VOSTM) device owner tenant generates WAN interface utilization logs to report information about SD-WAN link interface utilization.
WAN Interface Utilization Message Format
WAN Interface Utilization Message Fields
Log Type
Log Description
applianceName
Name of the VOS device. This is the name displayed in the output of the show system identification CLI command on the VOS device.
tenantName
Name of the organization (tenant).
generateTime
Time when the log was generated, in UNIX epoch time format.
tenantId
Tenant identifier. This value is allocated internally by the VOS device.
vsnId
Identifier of the virtual service node, or virtual machine (VM).
sentOctets
Number of bytes sent on the interface.
recvdOctets
Number of bytes received on the interface.
ulBwUtil
Uplink bandwidth utilization. This is computed as a percentage of the bandwidth configured in the uplink direction on the physical interface. If the uplink bandwidth is not configured, this field reports the total physical interface bandwidth.
dlBwUtil
Downlink bandwidth utilization. This is computed as a percentage of the bandwidth configured in the downlink direction on the physical interface. If the downlink bandwidth is not configured, this field reports the total physical interface bandwidth.
duration
Measurement duration.
siteName
Name of the SD-WAN site or branch.
cktName
Name of the SD-WAN circuit used for the SD-WAN link.
intfName
Name of the SD-WAN interface.
These could be inserted into existing indicators already supporting Viptela - down_capacity_percentage and up_capacity_percentage
2018-11-01T20:09:39+0000 intfUtilLog, applianceName=SDWAN-Branch3, tenantName=provider-org, generateTime=1541103000, tenantId=1, vsnId=0, sentOctets=532156644, recvdOctets=418779640, ulBwUtil=1.41, dlBwUtil=1.11, duration=300034, siteName=SDWAN-Branch3, cktName=WAN2, intfName=vni-0/1.0