Idea Details

OpenAPI: CAPC Alias Names needed

Last activity 05-31-2019 02:15 AM
Matthias Lurschack's profile image
11-28-2016 08:47 AM

Based on some use cases we need an option to include CAPC Alias Names (devices, interfaces, components) in OpenAPI Queries, as the discovered DEvice / Interface / Component Name is in many cases not usable (thats the reason why we use Alias Names in CAPC). 

Currently we have to do some additional steps & queries to get Alias Names from CAPC or external data sources (webservices, databases...). 


Comments

02-01-2018 02:46 AM

Hi Jason, we see now Alternate Names for Device and Interface. Is it planned to do also for Components ? We have several use cases where we change names especially for specific IP SLA tests ... 

09-11-2017 11:06 AM

Alias information for Devices and Interfaces will be available via OpenAPI in our upcoming 3.5 release.

09-11-2017 10:53 AM

stoma11, we have a customer in LATAM using Device Alias Name for a friendly device name and they are using OpenAPI to extract performance data to generate external dashboards. They need to have the Device Alias Name accessible through the OpenAPI, since the regular device name does not contain useful data for their dashboards.

07-14-2017 10:31 AM

This idea is under consideration.  It would not only benefit direct OpenAPI users, but could also enable the possibility of a separate follow-on enhancement to be able to leverage Alias Names in the Unified IM CABI Reporting platform, which pulls CAPM data through OpenAPI.  Let's see whether this idea generates additional interest.

07-01-2017 01:52 PM

Any considerations for future releases ? 

01-30-2017 09:43 AM

Currently it is also not possible to get the Index information of interfaces with OpenAPI queries. This information is already available on the DA.

 

So please include CAPC Alias Names and Index in OpenAPI Queries.