1. Why is discovery not happening?

    Ans: Refer to No single resource was discovered.

  2. Why are some resources not being discovered?

    Ans: Refer to Some native type resources were not discovered.

  3. Why are metric graphs not populating?

    Ans: Refer to Metric graph data is not getting on all resources.

  4. Why are Resource Filters not working?

    Ans: Complete the following procedure:

    1. When adding filters, ensure you click on the plus (+) button to save them.
    2. Use the predefined keys supported by each app to filter resources. Refer to the Resource Filter Keys section in the app documentation to find the correct keys.
    3. Ensure each key is used only once. Duplicate keys are not allowed.
    4. Avoid using comma-separated values for a single key. Each key should only have one value.
    5. If the specified filter conditions do not match any resources, the system will discover all resources.

  5. Why are Resource Name and IP Address blank in the alert subject and description?

    Ans: There could be two possible reasons:

    • The discovery API is not fetching these attribute details.
    • The macro details are not being properly stored in the cache.
    • First case: If the API itself does not fetch these details, the alert subject and description will remain blank. Once the API retrieves the data, it will be reflected accordingly.
    • Second case: Macros such as “Resource Name” and “IP Address” are stored in the cache under the store name "{app-name}_resource_info_{configId}".

    To fetch the macro details for a specific resource:

    1. Connect to the gateway and open the GCLI console using the command gcli.
    2. Use the following command with the appropriate app name, configId, and resource_moId: sdkgetvalbystoreandkey {app-name}_resource_info_{configId} {moId}

    Example: sdkgetvalbystoreandkey vmware-nsx-t_resource_info_ADAPTER-MANIFEST-ada05396-31a5-4bc1-a220-ad4499b3bb75 deb9e0fc-ad71-4ef6-9a00-f848a4ef2c8e

    1. If Resource Name and IP Address are available in the response, they will be included in the alert subject and description.
    2. If the command returns a null response, try running a full discovery and execute the command again.

  1. Events are generated on the end device but not showing on the OpsRamp device through Event/Alert Polling?

    Ans:

    • Check whether Event/Alert Polling is enabled in the app configuration. If not selected, no events will be generated.
    • If Event/Alert Polling is enabled but events are still not generated on the OpsRamp UI, follow these steps:
      • Verify that the time zones on the Gateway and the end device are the same. If they differ, the event-related response will not be included in the API response, and OpsRamp will not process such events.
      • Ensure both time zones are synchronized for proper event processing.