REST API Reference for Offline Mediation Controller

Get Node Manager Logs

get

/v1/logs/nodemanager/{id}

Retrieves logs for the specified Node Manager.

Request

Path Parameters

id(required): string

The unique identifier of the Node Manager.

Query Parameters

limit: integer(int64)

The size (in MB) of logs to retrieve.

There's no request body for this operation.

Response

Supported Media Types

application/json

200 Response

The logs were retrieved successfully.

Root Schema : schema

Type: object

401 Response

The client does not have the correct privileges.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

403 Response

The request was not authorized.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

404 Response

The requested resource cannot be found.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

405 Response

This method is not allowed.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

409 Response

The request could not be processed due to a conflict with the existing state of the resource.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

500 Response

The system has encountered an internal server error.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

Examples

The following example shows how to retrieve logs for a specific Node Manager by submitting a GET request on the REST resource using cURL. For more information about cURL, see Use cURL.

curl -X GET 'http://hostname:port/logs/nodemanager/{id}'

Example of the Response Body

If successful, the response code 200 is returned with the following response body.

{     "logs": "2025-12-19 06:05:42;INFO ;Logger for : NodeManager.nodemgr
      created!#EOR#\n2025-12-19 06:05:42;INFO ;JVM Resources: [\n\tAvailable processors: 1, \n\tFree
      memory: 2095523664 bytes, \n\tTotal memory: 2147483648 bytes, \n\tMax memory: 2147483648
      bytes]#EOR#\n2025-12-19 06:05:42;INFO ;error code file exists:loading it#EOR#\n2025-12-19
      06:05:42;INFO ;Successfully loaded ocomc_errocodes.xml#EOR#\n2025-12-19 06:05:42;INFO
      ;DataFlowMap operation: Load data flow map#EOR#\n2025-12-19 06:05:42;INFO ;DataFlowMap
      operation:writing data flow information into LDM config#EOR#\n2025-12-19 06:05:42;INFO
      ;DataFlowMap operation:writing data flow information into RDM config#EOR#\n2025-12-19
      06:05:42;INFO ;Readiness probe is updated#EOR#\n2025-12-19 06:05:42;INFO ;StatusGetter:refresh
      interval=2#EOR#\n2025-12-19 06:05:42;INFO ;The Disk Status monitor is disabled. Possible
      reasons - Metastat not supported by this OS, DiskStatus Monitor not
      configured#EOR#\n2025-12-19 06:05:44;INFO ;NM is registered on ip:port
      nm-cc-0:55109#EOR#\n2025-12-19 06:05:44;INFO ;Node Manager nodemgr is ready#EOR#\n2025-12-19
      06:05:44;INFO ;creating node implementation#EOR#\n2025-12-19 06:05:44;INFO ;[LDM] Starting the
      Local Data Manager...#EOR#\n2025-12-19 06:05:44;INFO ;[LDM] No source ids, no workers
      created#EOR#\n2025-12-19 06:05:44;INFO ;[LDM] LDM started successfully.#EOR#\n2025-12-19
      06:05:44;INFO ;done creating node implementation#EOR#\n2025-12-19 06:05:44;INFO ;creating node
      implementation#EOR#\n2025-12-19 06:05:44;INFO ;[RDM] Starting the Remote Data
      Manager...#EOR#\n2025-12-19 06:05:44;INFO ;[RDM] delay = 2000#EOR#\n2025-12-19 06:05:44;INFO
      ;[RDM] dataFlowMap =
      /home/ocomcuser/install/ocomc/config/rdm/remotedataflow.cfg#EOR#\n2025-12-19 06:05:44;INFO
      ;[RDM] Initializing RDMWorker ...#EOR#\n2025-12-19 06:05:44;INFO ;RDM Configurations : \n
      [RDMWorker] RDM_THREAD_COUNT = 1 \n[RDMWorker] RDM_THREAD_MAX_TRY_COUNT = 10 \n[RDMWorker]
      RDM_THREAD_MAX_WAIT_MILLI_SEC = 20000 \n[RDMWorker] CONN_LOST_LOG_INTERVAL_MILLI_SEC = 10000
      \n[RDMWorker] OCOMC_RDM_MAX_PERSIST_LIMIT = -1 \n#EOR#\n2025-12-19 06:05:44;INFO ;[RDMWorker]
      Building table#EOR#\n2025-12-19 06:05:44;INFO ;Remote Data Manager successfully
      started...#EOR#\n2025-12-19 06:05:44;INFO ;done creating node implementation#EOR#\n2025-12-19
      06:05:44;INFO ;NodeMgr : firing nodeManagerChanged Event#EOR#\n2025-12-19 06:05:45;INFO ; ***
      Started Micrometer service at port : 9090 *** #EOR#\n2025-12-19 06:05:45;INFO ;Alerts service
      is disabled.#EOR#\n" }