Altostrat’s Orchestration Log provides transparent visibility into the actions performed on your MikroTik devices. It captures scripts, API calls, and automated tasks, allowing you to monitor and troubleshoot changes across your network.

​
Why the Orchestration Log Matters

  • Audit Trail Keep a record of who did what and when—essential for compliance.
  • Debugging If something goes wrong with a script or API call, you can quickly spot the failure reason.
  • Monitoring Automated Tasks See all scheduled or triggered actions performed by Altostrat’s backend on your routers.

​
Accessing the Orchestration Log

1

Open the Site in Altostrat

From your Dashboard, click on Sites, then select the site you want to investigate.
2

Navigate to Orchestration Log

In the site’s overview page, look for the Orchestration Log tab or menu option. Click it to open the device’s orchestration records.

​
Understanding the Log Interface

Each entry in the Orchestration Log typically shows:
  • Description: Name or purpose of the action, e.g., “Create Configuration Backup” or “Deploy Policy.”
  • Created / Run: Timestamp when the action was initiated and when it was executed (if applicable).
  • Status: Indicates if the action is Pending, Completed, or Failed.

​
Expanded Log Entry

Clicking an entry opens detailed information about the job:
  • Timestamped Events: Each step, from job creation to completion.
  • Device Information: Target device(s), site ID, or associated metadata.
  • Job Context: JSON payload containing job ID, scripts, API calls, or additional parameters.
  • Status Messages: “Job created,” “Script downloaded,” “Express execution requested,” etc.

​
How to Use the Orchestration Log

  1. Track Automated Jobs Monitor things like firmware updates, backup schedules, or script executions.
  2. Verify Success Ensure tasks completed without errors. Look for Completed or Failed statuses.
  3. Troubleshoot Failures If a script failed, check the Status Message or Job Context for clues.
  4. Copy JSON For deeper analysis, copy the payload and share it with support or store it in your records.

​
Best Practices

  • Regularly Check: Make orchestration log reviews part of your change-management process.
  • Filter by Status: Look for frequent failures or pending actions that never complete.
  • Combine with Notification Groups: If you want alerts on specific job failures, create relevant rules in Notification Groups.