---
name: azion-watch-orchestrator-logs
description: >-
  Read the Orchestrator Agent log on a managed node, and the log of the services running on it, to confirm a deployment or find why one failed.
---

# Watch Orchestrator logs

**Orchestrator Agent** writes two logs on every node it manages: its own log, and one log for the services bound to that node. You read both from a terminal on the node. Together they say whether the agent reached the server and whether a service's triggers ran.

---

## Prerequisites

- Orchestrator Agent installed on the node. To install it, refer to [Install the Orchestrator Agent](/en/documentation/guides/application-development/automation/install-orchestrator-agent/).
- Shell access to that node, with permission to run `sudo`.

---

## Read the Orchestrator Agent log

The agent writes to `/var/log/azion/edge-orchestrator.log`. Every entry in that file comes from the agent itself, not from a service the agent runs.

To open the agent log on the node:

```bash
sudo vim /var/log/azion/edge-orchestrator.log
```

> **Note**
>
> You can choose the text editor you want, as long as it is installed on the node.

The file opens in the editor. It holds the manifest version, the agent's communication with the server, and the errors the agent recorded.

---

## Read the services log

The services bound to the node write to `/var/log/azion/edge-services.log`, a separate file from the agent's own log.

To open the services log on the node:

```bash
sudo vim /var/log/azion/edge-services.log
```

The file opens in the editor. It holds the records written by the install, update, and delete triggers configured inside those services.

---

## Next steps

- [Real-Time Events](/en/documentation/platform/real-time-events.md): Read the event records Azion products write on the platform, next to the logs the node keeps.
- [Data sources](/en/documentation/platform/real-time-events/data-sources.md): Check which Azion products report event records, and what each one carries.
- [Run scripts on a node](/en/documentation/guides/application-development/automation/run-scripts.md): Act on the node once its logs show what went wrong.
- [Guides and tutorials](/en/documentation/platform/real-time-events/guides.md): Find the other guides that read what the platform recorded.