All work

Select view

Select search mode

 
47 of 47

Asset Record Components Not Supported When Using nodes(assetRecord) Template Query

Description

Trying to filter out using assestRecord in nodes() template query with different components not all components currently supported.

e.g. nodes(assetRecord.city)

1- Not Supported Components with Helm (while supported with Meridian) 

address1
address2
city
state
zip

2- Not Supported Components with Helm (while supported with PRIS)

Asset_address1
Asset_address2
Asset_city
Asset_country
Asset_latitude
Asset_longitude
Asset_state
Asset_vmwareManagedEntityType
Asset_vmwareManagedObjectId
Asset_vmwareManagementServer
Asset_vmwareState
Asset_vmwareTopologyInfo
Asset_zip

  • List of all components can be checked in two references below:

1- Meredian Parameters

https://docs.opennms.com/meridian/2022/reference/configuration/filters/parameters.html

2- Pris Asset Field Mapper
https://docs.opennms.com/pris/1.3.2/mapper/asset-fields.html

 

Attachments

1

Lucidchart Diagrams

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Fix versions

Priority

PagerDuty

Created September 27, 2022 at 5:24 PM
Updated February 27, 2024 at 9:19 PM

Activity

Show:

AlbertoMay 24, 2023 at 6:36 PM

Asset records now support address1, adddress2, city, state, country and zip.

http://localhost:8980/opennms/api/v2/nodes/properties/

Jeff GehlbachNovember 10, 2022 at 6:25 PM

that comment is ten years old I'm not sure whether we've done any work in the meantime toward implementing OnmsGeoLocation. For the moment, those asset fields are the mechanism of record for conveying physical location. I see we're already exposing a great many other asset fields, so only good things can come of adding these ones.

AlbertoNovember 9, 2022 at 10:46 PM

To work on this request and we need to clarify what approach to take regarding Geolocation. 

There a few comments about removing all the following fields and replace them with Geolocation when there is a Geolocation table in place. I'm not sure if there is a jira for the Geolocation piece that could explain what kind of work that involves. Or should we just ignore them and go ahead and use the current AssetRecords fields instead....I don't think thats an ideal option. Sounds more like we should do the Geolocation implementation instead. do you know what is this about?

 

Asset_address1
Asset_address2
Asset_city
Asset_country
Asset_latitude
Asset_longitude
Asset_state

Asset_zip

Jeff GehlbachOctober 11, 2022 at 9:17 PM

Pulling into refined backlog for the upcoming sprint, along with its companion NMS issue.

Jeff GehlbachOctober 11, 2022 at 9:11 PM

seems to describe a superset of the items identified as missing in .