• In progress

    • WWW0108 Blackbox probe failed OTCS Rest API

    Owned by Fabian Mangelsdorf
    Last updated: Sept 08, 2023
    1 min read

    E-Mail Message:

    Text

    Picture

    Text

    Picture

    Alerts Firing:
    Labels:

    • alertname = BlackboxProbeFailedOTCSRestAPI

    • HID = WWW0108

    • Help =

    WWW0108 Blackbox probe failed OTCS Rest API

    • env = TEST

    • hid = OTCSRESTLB

    • instance =

    https://FQDN/OTCS/llisapi.dll/api/v1/ping

    • job = blackbox_exporter_otcs_rest

    • severity = P3

    • severity_desc = Moderat

    • team = hit-opsgenie

    Annotations:

    • description = Blackbox probe failed

    VALUE = 0
    LABELS: map[__name__:probe_failed_due_to_regex env:TEST hid:OTCSRESTLB instance:https://FQDN/OTCS/llisapi.dll/api/v1/ping job:blackbox_exporter_otcs_rest]

    • summary = Blackbox probe failed due to regex (instance

    https://FQDN/OTCS/llisapi.dll/api/v1/ping)
    Source: https://OTWATCH/prometheus/graph?g0.expr=probe_failed_due_to_regex%7Bhid%3D~%22OTCSREST.%2A%22%7D&g0.tab=1

     TBD

     

    Applies to

    System

    Approved

    System

    Approved

     OTCS FE

     

     OTCS LB

     

     

     

    Summary

     The availablity of the OTCS Rest API service can be checked by verifying the URL https://OTCSinstance/OTCS/llisapi.dll/api/v1/ping for presence of the string below:

    {"rest_api":[{"build":2,"href":"api\/v1","version":1}]}

     

    Sources of Errors

    In case the service is unresponsive it has a huge impact on the Content Server functionalities. Reason could be an overload or not running OTCS services.

    Solution

    Check the thread-status of the OTCS instances.

    Check if the Content Server itself is available.

    Try restarting the Content Server services.

    In any case further analysis is required.

    opentext KB

     

    Copyright @ handel gmbh