How to access Agent logs

Process logs and Instances give a lot of detail about what is happening on the execution level, and most of the time, this is all it takes to figure out what is wrong. Sometimes the reason for issues in Processes is somewhere deeper, and the logs the Agents provide can shed some light on the root cause.

Step by Step Tutorial Available

If you prefer more visual or interactive guidance on how to view Agent logs in Frends, you can find a step-by-step walkthrough from your own environment's home page, under Onboarding by selecting "Tutorial 2b, Step 4: Agent Logs" tutorial.

Requirements

In order to access Agent logs, you will need to have at least Editor role in Frends. In case the roles and permissions have been changed, having at least Environments.View permission is required. Some actions are restricted to Environments.Admin level, but viewing the Agent logs is possible with only the View level.

Viewing the Agent logs

You can access the Agent logs by heading over to Administration menu and opening Environments.

Once in Environments, you will be presented the currently selected Agent Group and its features and settings. On the left, you have a list of Environments and Agent Groups within them, to change which Agents you are looking at.

You can learn more about the architecture Frends has for the execution environment at Hybrid Integration Architecture section.

For viewing the Agent logs, we want to click on the Agent(s) shown under Agent Groups.

By clicking on the Agent's name or the Agent card in general, you will directly access the Agent's logs, what is happening on the background. These logs will show, among others, errors coming from the Processes and Subprocesses, as well as resource usage and message queue warnings and errors.

By clicking on the error and warning messages, you can get more accurate message what happened at that point.

Below the Agent logs, you can also find Triggers that are deployed to the Agent. From these you can confirm which Processes and Triggers should be running on the Agent, as well as receive the whole URL for an API or HTTP endpoint, as long as the external URL is configured for your Agent.