One of the biggest benefits of using Zenaton to run background jobs is the visibility that developers have into all of their processes on the dashboard. To take it to the next level, we are offering new level of visibility into your Agents.
Now you can see a real time overview of your connected Agents — to verify that the are installed and running as they should. If there is a problem, you can quickly troubleshoot and fix it.
So check it out. For a given environment (“dev” in our example below) the ‘Agents’ section on the dashboard displays the following information:
- A list of all installed Agents with CPU and RAM usage
- Real-time activity per Agent (tasks running)
- Tasks and workflows that are assigned to that Agent
- Agent Settings that are configured at deployment.
Once you select an Agent, you have access to more information that is split into several tabs.
Watch a real-time progression of tasks being executed on the Agent for single tasks and tasks within workflows.
View the Agent parameters that are currently in use by your Agent which you set during deployment (mostly what you have set in the .env file)
- Shows which types of tasks Agent is configured to execute.
- Allows you to confirm that all settings are configured as expected
It’s useful to check if the currently used parameters match your expectations, after a new Agent configuration deployment for example.
Note: normally tasks are distributed evenly over all Agents but the Agent can be configured to run specific types of tasks to optimize performance.
Zenaton dynamically deploys a queue for each new type of task or workflow encountered. Agents are dynamically configured to listen those queues — according to their own configuration.
So, the queue tab shows a list of all tasks or workflows that have been assigned to that Agent and have run or started to run. This allows you to see the capability of the Agent — what tasks or workflows are allowed to run.
It might be useful to check the advanced setup if you want the Agent to “specialize” and use the
For example, if you have a workflow for resizing images, and you want it to be run only by the second Agent that has more CPU capacity.
SDT OUT & STD ERR
While an Agent is running tasks, the output is written to two files:
zenaton.out for std-out and
zenaton.err for std-err.
Those tabs respectively give you the paths of the
zenaton.err files on your Agent.
Agent monitoring is another step on the Zenaton roadmap towards full visibility into your background processes. We see it as another tool in the developer toolset to verify everything is running as it should or…if there is a problem…to quickly identify the origin and fix it.
Please share your feedback and requests below 👇🏻! And keep shipping