DevOps Loop pod references to check logs for troubleshooting
You can use pod references to identify the Kubernetes pods associated with DevOps Loop services and capabilities. The pod names correspond to the service names, so that you can easily identify the correct pod when you review logs or troubleshoot issues
If a component fails, the first step is to identify which service is responsible, then inspect the logs of the corresponding pod.
Viewing pod logs
To inspect logs for a specific service, you must run the following command:
kubectl logs <pod_name> -n devops-loop
Example:
kubectl logs devops-loop-ibm-devops-loop-analyticsai-7d6dc49657-6jdgs -n devops-loop
DevOp Loop pods and their purpose
| Pod_name | Purpose | Log review scenarios |
|---|---|---|
| devops-loop-ibm-devops-loop-analyticsai-* | This pod processes AI and analytics tasks used by DevOps Loop features. | AI processing errors, analytics issues, and model execution problems. |
| devops-loop-ibm-devops-loop-frontend-* | This pod runs the user interface and frontend services for DevOps Loop. | UI failures, page loading issues, and frontend API errors. |
| devops-loop-ibm-devops-loop-learning-webserver-* | This pod hosts the web services used for learning-related features in the platform. | Issues related to learning workflows or web server responses. |
| devops-loop-ibm-devops-loop-licensing-* | This pod validates product licenses and manages licensing checks. | Licensing failures, invalid license messages, and entitlement issues. |
| devops-loop-ibm-devops-loop-loop-* | This pod runs the core backend services that manage workflows and internal processing in DevOps Loop. | Core workflow failures or backend processing issues. |
| devops-loop-ibm-devops-loop-mcploop-* | This pod manages MCP loop services and integrations. | MCP integration or communication errors. |
| devops-loop-ibm-devops-loop-tenant-* | This pod manages tenant configuration and tenant-related operations. | Multitenant configuration issues or tenant-specific errors. |
Note:
The asterisk (*) indicates the base pod name. The actual pod
name includes a dynamically generated suffix. For example:
devops-loop-ibm-devops-loop-analyticsai-7d6dc49657-6jdgs.DevOps Loop capabilities and corresponding pods
| Capability | Pod | Purpose | Log review scenarios |
|---|---|---|---|
| Plan | devops-loop-ibm-devopsplan-prod-0 | This pod runs the DevOps Plan service and handles planning operations and REST API requests. | Planning workflow failures, API errors, or issues related to plan management |
| Control | devops-loop-control-* | This pod runs the DevOps Control service and supports monitoring and control features in DevOps Loop. | Control feature errors or service failures. |
| Build | devops-build-server-* | This pod runs the DevOps Build server and provides the Build user interface and core build services. | Build UI not accessible, Loop creation failures, or TeamSpace creation failures. |
| devops-build-agent-* | This pod runs the default DevOps Build agent that executes build jobs. | Builds fail because the default agent is not active. | |
| devops-build-mcp-server-* | This pod runs the MCP server used by the Build capability for MCP-related services. | MCP server access issues or MCP integration failures. | |
| Deploy | devops-loop-ibm-ucd-prod-0 | This pod runs the Deploy API that handles requests related to applications. | Deployments fail, or deployment processes do not start. |
| devops-loop-ibm-ucd-prod-mysql-* | This pod runs the MySQL database used by the UrbanCode Deploy server. | Database connectivity problems occur. | |
| devops-loop-ibm-ucda-prod-0 | This pod runs the UrbanCode Deploy agents that perform deployment tasks. | Deployment steps fail to run on agents. | |
| Measure and Release | application-api-* | This pod runs the Velocity API that handles requests related to applications. | Application requests fail, or application data does not load. |
| background-processor-* | This pod runs background jobs and processes tasks that run behind the scenes. | Background tasks or scheduled jobs do not run correctly. | |
| continuous-release-consumer-* | This pod receives and processes release data from other systems. | Release data is not processed, or updates are missing. | |
| continuous-release-poller-* | This pod checks external systems for new release updates. | Release updates are not detected. | |
| continuous-release-ui-* | This pod runs the user interface for continuous release features. | Continuous release UI does not load or shows errors. | |
| mcp-server-* | This pod runs the MCP server used for integrations and plugin communication. | MCP integrations fail, or the MCP service is inaccessible. | |
| multi-app-pipeline-api-* | This pod runs the API for managing pipelines that include multiple applications. | Multiapplication pipeline operations fail. | |
| release-events-api-* | This pod processes and provides APIs for release event data. | Release events are missing or event APIs fail. | |
| release-events-ui-* | This pod runs the user interface for viewing release events. | Release events are not displayed in the UI. | |
| reporting-consumer-* | This pod receives and processes metrics and test results sent by plugins. | Plugin metrics or test results do not appear in dashboards. | |
| security-api-* | This pod manages authentication and security-related requests. | Users cannot log in or access services. | |
| velocity-rabbitmq-0 | This pod runs the RabbitMQ messaging service used by Velocity components. | Services cannot communicate or message queues fail. | |
| velocity-router-* | This pod routes incoming requests to the correct Velocity services. | Requests fail to reach backend services. |