Troubleshooting

Troubleshooting through logs is an essential method. Currently, under WeDa privatization, due to resource optimization, no additional log services are provided. Logs are stored in container directories and are retained for a maximum of 7 days.

1. Service Description

The important services involved in WeDa privatization are as follows:

• weda-allin-one-design and allin-one-runtime services

  • Mainly involve data models, approval flows, APIs, permissions, etc.
  • allin-one-runtime: Runtime service
  • weda-allin-one-design: Design-time service
  • Log storage path: /data/log

• proxy

  • Forwarding proxy service, acts as a routing and forwarding role
  • Log viewing method: Can directly view log output in docker logs

• weda-plugin-adaptors

  • External database service
  • Log storage path: /data/log

• gitness

  • Function: Build and publish service

• idaasserver

  • Authentication and authorization service
  • Log storage path: /logs

2. Log Troubleshooting

First, if the frontend service reports an error, you can obtain the RequestId of the error interface to see which functions are involved in the error. For example, if you encounter an error when operating data models, you can check the logs of weda-allin-one-design and allin-one-runtime services.

2.1 Login to the Service Container

2.1.1 Standalone Version

docker exec -it allin-one-runtime bash
# or
docker exec -it weda-allin-one-design bash

2.1.2 Cluster Version

# 1. View pod list (software is the specific namespace)
kubectl -n software get po | grep "allin-one-runtime"

# 2. Enter pod (allin-one-runtime-xxxx-yyyy is the pod name obtained in the previous step)
kubectl -n software exec -it allin-one-runtime-xxxx-yyyy -- bash

2.2 View Logs

After entering the container, execute the following commands:

cd /data/log
# a839bbb426b028 is the id of the error interface request result, i.e., RequestId
grep "a839bbb426b028\" ./*

Check if there are ERROR level logs. If you cannot directly identify the issue, you can save the error logs to a file and consult WeDa personnel for processing and troubleshooting.

3. Submit Issue

To reduce communication costs, you can describe the error scene as follows:

1. Screenshot of the error

2. Current deployment version

   Can be obtained through the image tag, i.e., the tag value is the version value

   docker images

3. Error interface and how to reproduce the error scenario

4. Error logs

   If you can accurately obtain the error interface, you can send the error logs to WeDa personnel