show service order logs
Syntax
show service order logs service-order-name
show service order logs service-order-name run-id
show service order logs service-order-name task task-id
show service order logs service-order-name severity (ALL | DEBUG | ERROR | FATAL | INFO)
Description
Displays the Airflow task logs for a service order's workflow run. This is the quickest way to find out why a service order failed without leaving the service orchestration cMGD CLI.
If you do not specify a run ID, the most recent workflow run is used. If you do not specify a task, the logs of the failed task are displayed.
Options
|
service-order-name |
Enter the name of the service instance, in the |
|
run-id |
Enter the unique ID of the workflow run. It defaults to the most recent run |
| task task-id | Enter a specific task ID to view the logs of the specified task. It defaults to the failed task in the run. |
| severity | Enter the minimum severity to display: ALL, DEBUG, INFO, ERROR or FATAL. Log records below this severity are suppressed. |
Sample Output
show service order logs
root@cmgd-5bcb9568c6-hfkdj> show service order logs internal_l3-addr task update_service_order_status
===== Task: update_service_order_status =====
*** Found local files:
*** * /opt/airflow/mount/logs/dag_id=modify-l3-addr-0_2_17/run_id=fh.foghorn__b627
08a9-3fa7-4dc2-97e6-a96fa2a89df8/task_id=update_service_order_status/attempt=1.log
[2026-08-24T14:53:53.323+0100] {taskinstance.py:2865} INFO - Starting attempt 1 of 1
[2026-08-24T14:53:53.691+0100] {python.py:240} INFO - Done. Returned value was: {}
[2026-08-24T14:53:53.736+0100] {taskinstance.py:352} INFO - Marking task as SUCCESS.
[2026-08-24T14:53:53.767+0100] {local_task_job_runner.py:266} INFO - Task exited with
return code 0
Release Information
Command introduced in Juniper Routing Director Release 2.10.0.