Application Version and Upgrade Details
Application Version | Bug fixes / Enhancements |
---|---|
1.0.3 | Metric label support |
1.0.2 | Full discovery support added. |
1.0.1 | Alert custom macros support. |
Click here to view the earlier version updates
Application Version | Bug fixes / Enhancements |
---|---|
1.0.0 | Initial sdk2.0 application discovery & monitoring implementation. |
Introduction
Smart, innovative, tailor-made interactive solutions that provide tools needed to facilitate enhanced outcomes from collaborative working.
Single large format solutions, interactive video walls, and scalable multi projector solutions support instant video conferencing, creative applications, interactive lectures and meeting plus infotainment systems.
Prerequisites
- OpsRamp Classic Gateway 14.0.0 and above.
- OpsRamp NextGen Gateway 14.0.0 and above.
Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
Default Monitoring Configurations
NEC Displays application has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates, and Global Device Management Policies. OpsRamp recommends doing this activity before installing the application to avoid noise alerts and data.
Default Global Device Management Policies
OpsRamp has a Global Device Management Policy for each Native Type of NEC Displays. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:
{appName nativeType - version}
Ex: nec-displays NEC Displays - 1 (i.e, appName = nec-displays, nativeType = NEC Displays, version = 1)
Default Global Templates
OpsRamp has a Global Template for each Native Type of NEC Display. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:
{appName nativeType 'Template' - version}
Ex: nec-displays NEC Displays Template - 1 (i.e, appName = nec-displays, nativeType = NEC Displays, version = 1)
Default Global Monitors
OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:
{monitorKey appName nativeType - version}
Ex: NEC Displays Monitor nec-displays NEC Displays 1 (i.e, monitorKey = NEC Displays Monitor, appName = nec-displays, nativeType = NEC Displays, version = 1)
Configure and Install the NEC Displays Integration
- From All Clients, select a client.
- Go to Setup > Account.
- Select the Integrations and Apps tab.
- The Installed Integrations page, where all the installed applications are displayed.
Note: If there are no installed applications, it will navigate to the ADD APP page. - Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

- Click ADD in the NEC Displays application.
- In the Configurations page, click + ADD. The Add Configuration page appears.
- Enter the below mentioned BASIC INFORMATION:
Functionality | Description |
---|---|
Name | Enter the name for the configuration. |
Host Name / IP Address | Host Name/IP address of the target. |
Port | Port Note: By default 161 is added. |
SNMP Version | Select the SNMP Version from the drop down. Note: By default version2c is added. |
Community String | Enter the community string information. |
Note:
- Host Name / IP Address and Port should be accessible from Gateway.
- Select App Failure Notifications; if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
- Select the below mentioned Custom Attribute:
Functionality | Description |
---|---|
Custom Attribute | Select the custom attribute from the drop down list box. |
Value | Select the value from the drop down list box. |
Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).
- In the RESOURCE TYPE section, select:
- ALL: All the existing and future resources will be discovered.
- SELECT: You can select one or multiple resources to be discovered.
- In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
- Minutes
- Hourly
- Daily
- Weekly
- Monthly
- Click ADD.
Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.
- Click NEXT.
- Below are the optional steps you can perform on the Installation page.
Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.
Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

- Click +ADD to create a new collector by providing a name or use the pre-populated name.

- Select an existing registered profile.

- Click FINISH.
The integration is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.
Modify the Configuration
See Modify an Installed Integration or Application article.
Note: Select the NEC Displays application.
View the NEC display details
The NEC-display integration is displayed in the Infrastructure > Resources > Network Devices > VoIP. You can navigate to the Attributes tab to view the discovery details, and Metrics tab to view the metric details for NEC display devices.


Supported Alert Custom Macros
Customize the alert subject and description with below macros then it will generate alert based on customisation.
Supported macros keys:
Click here to view the alert subject and description with macros
${resource.name}
${resource.ip}
${resource.mac}
${resource.aliasname}
${resource.os}
${resource.type}
${resource.dnsname}
${resource.alternateip}
${resource.make}
${resource.model}
${resource.serialnumber}
${resource.systemId}
${Custome Attributes in the resource}
${parent.resource.name}
Supported Metrics
Click here to view the supported metrics
Native Type | Metric Names | Display Name | Unit | Application Version | Description |
---|---|---|---|---|---|
NEC Displays | nec_display_Power_State | Power State | 1.0.0 | Provides current power status of the device.Possible values \n1: \"Other\",\n2: \"Unknown\",\n6: \"Active Off\",\n7: \"Standby\",\n8: \"Power Saving\",\n9: \"Cooling\",\n10: \"Warming\",\n 11: \"On\" |
Risks, Limitations & Assumptions
- Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
- Connectivity Exception
- Authentication Exception
- Application will not send any duplicate/repeat failure alert notification until the already existed critical alert is recovered.
- Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
- Application cannot control monitoring pause/resume actions based on above alerts.
- Metrics can be used to monitor nec display resources and can generate alerts based on the threshold values.
- No support of showing activity log and applied time.
- This application supports both Classic Gateway and NextGen Gateway