Using logs

You can use logs to troubleshoot issues with your projects. To view a log, use the command oc logs <log_name>.

Log name Log content
wo-ads-credentials-service-<unique_ID> Information about credential management for machine learning
wo-ads-git-service-<unique_ID> Information about Skill studio project source files
wo-ads-parsing-service-<unique_ID> Information about decision skills editing
wo-ads-rest-api-<unique_ID> Information about Skill studio project management, data models, and decision skills
wo-ads-run-service-<unique_ID> Information about Skill studio project deployment, and decision skill artefacts
wo-ads-runtime-service-<unique_ID> Information about decision skill execution
wo-ads-service-provisioner-<unique_ID> Information about tenant provisioning for Skill Studio and decision related services
wo-docproc-dpi-api-<unique_ID> API entry point for document processor skill execution. If you have a document processor skill error, make sure that the pods have a corresponding API_ENTRY and API_EXIT logs for the skill execution. If these logs exist and are as expected, the issue is not related to document processor.
wo-docproc-dpi-flow-<unique_ID> Document processor and its callback requests. If there are no skill responses and the document processing API show request was processed, check for network connection attempts from org.apache.http.impl.execchain.RetryExec. Repeated network request attempts might be related to poor network connection, or issues communicating with service pods.
wo-digital-employee-server-deployment-<unique_ID> This log can be used for the following purposes:
  • If you see warning log - Using deprecated env var for callback URL {SERVER_SERVICE_ENDPOINT=}, if your environment is IBM Software Hub, ensure that the SERVER_SERVICE_ENDPOINT is set to the correct digital-employee-server.
  • If you have a request that requires a callback, this log contains the ID for that request. You can check your database to make sure that the callback URL and response has been received. See the line info log - Creating a Correlation Object for the Async skill correlation_id=<correlation_ID>..
  • This log indicates that either workflow skills or document processing skills are running. You can use this log to check if these skills are executing in the proper sequence. For example, the log lines will look similar to:
    UAB skill detected, using internal route
    Adding internal route to the Headers
  • You can find the callback URL for skills other than workflow and document processor skills. You can use this log to verify whether these skills are running in the correct order. See the line info log - Adding <callback_url> to the Headers.
  • You can find information about your active conversational skill requests, including the status, skill ID, skillset ID, and tenant ID. You can use this log to verify that your skill is running as expected. See the lines:
    info log - handle_request ==> skill_id=<skill_ID> tenant_id=<tenant_ID>"
    f"skill_set_id=<skill_set_ID> thread_id=<thread_ID> run_id=<run_ID>
  • You can find information about your connection to the server. You can use this log to troubleshoot errors with skill connection or connection credentials. You can try to delete and re-add your credentials if your credentials have timed out. See the line info log - handle_request ==> connection info=<connection_info>.
  • You can find the application server endpoint that is being used for the current skill execution. You can delete and re-upload the server endpoint URL if the correct URL is not being used. See the line info log - Invoking call_service with <cm_service_spec.get_base_url()>
  • If you see error log - Hit exception when transform response into json: {e}, check the external application server to find and fix the logic errors.
  • If you see error log - Error encountered, check the response that was sent from the external application server to make sure that the response has the expected structure, and that there are no parsing errors.
wo-tenant-registry-<unique_ID> Information about an internal server error related to the API call to /webapi-0.0.1-SNAPSHOT/webapi/v1/user from the createUser function. To troubleshoot this error, check the Kafka status and the wo-teams-server pod logs. After you resolve the Kafka errors, re-add the user.
wo-uab-common-form-engine-server-<unique_ID> Information about workflow user tasks
wo-uab-common-model-container-server-<unique_ID> Information about Skill studio static artifacts, including user task components
wo-uab-common-proxy-server-<unique_ID> Information about the Skill studio proxy. All requests to skill studio pass through this proxy and is routed to the corresponding pods in the corresponding tenant.
wo-uab-schema-catalog-server-<unique_ID> Information about Skill studio runtime, Skill studio publication to the skill catalog, Skill studio skill discovery, and skillset API skill discovery
wo-uab-service-broker-server-<unique_ID> Information about Skill studio tenant provisioning
wo-uab-skill-proxy-server-<unique_ID> Information about the proxy that is used for Skill studio components when they call skills and Skill studio skills that are called by APIs
wo-uab-storage-services-server-<unique_ID> Information about the frameworks that are used for Skill studio workflow model validation and model deployment to the workflow server
wo-uab-ui-framework-server-<unique_ID> Information about the Skill studio UI interface components