Supported Target Versions
SSH (version 1 and version 2)

Application Version and Upgrade Details

Application VersionBug fixes / Enhancements
  • Metric label support.
  • Missing component alert support.
2.0.2Full discovery support
2.0.1App enhancements, error handling & macro replacements support in the alert subject & description
Click here to view the earlier version updates
Application VersionBug fixes / Enhancements
  • Bug fix - creation resource ip address issue fix.
  • Renamed metric “crestron_Controller_Status” to “Crestron_Application” and changed the metric display name, descriptipon
1.0.0Initial resource discovery and monitoring implementations


Crestron leads the way with best in class av integration equipment, where video comes to life and audio is crystal clear.


  • 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..

Supported Metrics

Click here to view the supported metrics
Native TypeMetric NameDisplay NameMetric LabelApplication VersionUnitDescription
Crestroncrestron_average_CPULoadAverage CPU LoadUsage%1.0.0Provides device average CPU load
crestron_IPTable_ConnectionsStatusIP Table Connection StatusAvailability1.0.0Provides crestron-av device state info. Possible outcomes are 2- CONFAILED, 1 - ONLINE, 0 - OFFLINE
crestron_ApplicationCrestron ApplicationAvailability2.0.0provides crestron device application info. Possible outcomes are 1 = us.zoom.zrc and 0 = Crestron Default"

Default Monitoring Configurations

Crestron 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.

  1. Default Global Device Management Policies

    OpsRamp has a Global Device Management Policy for each Native Type of Crestron. 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 the below naming convention:

    {appName nativeType - version}

    Ex: crestron Crestron - 1 (i.e, appName = crestron , nativeType = Crestron , version = 1)

  2. Default Global Templates

    OpsRamp has a Global Template for each Native Type of Crestron. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows the below naming convention:

    {appName nativeType 'Template' - version}

    Ex: crestron Crestron Template - 1 (i.e, appName = crestron , nativeType = Crestron ,version=1)

  3. 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: Crestron Monitor crestron Crestron - 1 (i.e, monitorKey = Crestron Monitor, appName = crestron , nativeType = Crestron, version = 1)

Configure and Install the Crestron Integration

  1. From All Clients, select a client.
  2. Go to Setup > Account.
  3. Select the Integrations and Apps tab.
  4. The Installed Integrations page, where all the installed applications are displayed.
    Note: If there are no installed applications, it will navigate to the Available Integrations and Apps page.
  5. 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.
  1. Click ADD in the Crestron tile.
  2. In the Configurations page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
NameEnter the name for the configuration.
Host Name / IP AddressHost Name/IP address of the target.

Note: By default 22 is added.
CredentialsSelect the credentials from the drop-down list.

Note: Click + Add to create a credential.


  • 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.
  1. Select the below mentioned Custom Attribute:
Custom AttributeSelect the custom attribute from the drop down list box.
ValueSelect 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).

  1. 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.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. 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.

  1. Click NEXT.
  2. 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.

Cisco FirePower
  • Click +ADD to create a new collector by providing a name or use the pre-populated name.
Aruba Airwave Integrations
  1. Select an existing registered profile.
Aruba Airwave Integrations
  1. Click FINISH.

The integration is now installed and displayed on the Installed Integration page. Use the search field to find the installed integration.

Modify the Configuration

View the Crestron details

The Crestron 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 Crestron.

Crestron 4
Crestron 5

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













                                ${Custome Attributes in the resource}


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).
  • No support of showing activity log and applied time.
  • Support for the option to get Latest snapshot metric.
  • Application is not compatible with Cluster Gateway.
  • This application supports both Classic Gateway and NextGen Gateway