Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 8. Viewing CodeReady Workspaces operation logs

After the CodeReady Workspaces pods are created, you can view the operation logs of the application in the terminal or through the OpenShift console.

To view the operation logs on the terminal, run the following commands:

  1. To obtain the names of the pods you must switch to project where CodeReady Workspaces is installed: 

    $ oc get pods -n=<OpenShift-project-name>
    Copy to Clipboard Toggle word wrap

    This command shows the pods that have been created: 

    NAME                                  READY   STATUS    RESTARTS  AGE
codeready-6b4876f56c-qdlll            1/1     Running   0         24m
codeready-operator-56bc9599cc-pkqkn   1/1     Running   0         25m
keycloak-666c5f9f4b-zz88z             1/1     Running   0         24m
postgres-96875bcbd-tfxr4              1/1     Running   0         25m
    Copy to Clipboard Toggle word wrap

  2. To view the operation log for a specific pod, run: 

    $ oc logs <log-name>
    Copy to Clipboard Toggle word wrap

    The output of this command for the codeready-6b4876f56c-qdll pod (as an example) is as follows: 

    2019-03-29 12:22:17,710[ost-startStop-1]  [INFO ] [unknown.jul.logger 49]               - UndertowServer reused (pre-existing).
-------------------------------------------------------------------
GMS: address=codeready-6b4876f56c-qdlll-42917, cluster=WorkspaceStateCache, physical address=fe80:0:0:0:42:acff:fe11:c%eth0:7801
-------------------------------------------------------------------
2019-03-29 12:22:21,784[ost-startStop-1]  [INFO ] [unknown.jul.logger 49]               - namespace [workspaces] set; clustering enabled
2019-03-29 12:22:21,785[ost-startStop-1]  [INFO ] [unknown.jul.logger 49]               - Starting UndertowServer on port 8888 for channel address: codeready-6b4876f56c-qdlll-34344
2019-03-29 12:22:21,786[ost-startStop-1]  [INFO ] [unknown.jul.logger 49]               - UndertowServer reused (pre-existing).
-------------------------------------------------------------------
GMS: address=codeready-6b4876f56c-qdlll-34344, cluster=WorkspaceLocks, physical address=fe80:0:0:0:42:acff:fe11:c%eth0:7802
-------------------------------------------------------------------
2019-03-29 12:22:25,822[ost-startStop-1]  [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 166]   - Configured factories for environments: '[openshift, kubernetes, dockerimage,
    Copy to Clipboard Toggle word wrap

  3. For operation logs of the other pods, run:

    • For the codeready-operator-56bc9599cc-pkqkn pod: oc logs codeready-operator-56bc9599cc-pkqkn
    • For the keycloak-666c5f9f4b-zz88z pod: oc logs keycloak-666c5f9f4b-zz88z
    • For the postgres-96875bcbd-tfxr4 pod: oc logs postgres-96875bcbd-tfxr4

To view the operation logs in the OpenShift console, take the following steps:

  1. Navigate to the OpenShift web console.
  2. In the My Projects pane, click workspaces.
  3. In the Overview tab, click the application that you want to view the logs for (example: codeready-operator, #1).
  4. In the Deployments > <application-name> window, click the name of the pod.
  5. Scroll down to the Pods section and click the <pod-name>.

  6. Click Logs

    Figure 8.1. Clicking View Log

    Clicking View Log
    View larger image
    Clicking View Log

  7. Click Follow to follow the log. 

    time="2019-03-29T12:22:00Z" level=info msg="Updating codeready CR with status: Che API: Unavailable"
time="2019-03-29T12:22:00Z" level=info msg="Custom resource codeready updated"
time="2019-03-29T12:22:00Z" level=info msg="Waiting for deployment codeready. Default timeout: 420 seconds"
time="2019-03-29T12:22:31Z" level=info msg="Deployment 'codeready' successfully scaled to 1"
time="2019-03-29T12:22:31Z" level=info msg="Updating codeready CR with Keycloak URL status: http://keycloak-workspaces.192.168.42.114.nip.io "
time="2019-03-29T12:22:31Z" level=info msg="Custom resource codeready updated"
time="2019-03-29T12:22:31Z" level=info msg="Updating codeready CR with status: CodeReady Workspaces server: Available"
time="2019-03-29T12:22:31Z" level=info msg="Custom resource codeready updated"
time="2019-03-29T12:22:31Z" level=info msg="Updating codeready CR with CodeReady Workspaces server URL: http://codeready-workspaces.192.168.42.114.nip.io "
time="2019-03-29T12:22:31Z" level=info msg="Custom resource codeready updated"
time="2019-03-29T12:22:31Z" level=info msg="CodeReady Workspaces is now available at: http://codeready-workspaces.192.168.42.114.nip.io "
time="2019-03-29T12:22:31Z" level=info msg="Updating codeready CR with version: 1.1-52"
time="2019-03-29T12:22:31Z" level=info msg="Custom resource codeready updated"
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat