Forum Discussion

Issac's avatar
Issac
Icon for Expert rankExpert
2 months ago
Solved

Run Book Schedule Monitoring

Whether it is possible to monitor the runbook schedules ? We have some critical run book which used to run every day , some times it not running , we need an alert for this.

1313
33
run_book_automation
skylar
Skylar_One
sl1
  • BryanHarding's avatar
    BryanHarding
    2 months ago

    Alfred,

    Each and every RBA policy execution results in a record to `master_logs`.`automation_policy_metrics` capturing which RBA policy, what triggered it, and timestamps for milestones of execution. The two key fields for your presented problem will be: ap_id and trigger_type where:

    ap_id = Local ID of the Run Book Automation Policy. You will be able to parse this from your RBA policy inventory in the UI (Registry > Run Book > Automation).

    trigger_type = The type of trigger method. As your concern is around time-point scheduled RBA you will be looking for this value being "1".

    Filtering on these two fields will show you all scheduled RBA executions and with that list you will be able to see the time the task was evaluated by the RBA engine (task_loaded_time), the time the RBA engine started the task execution (task_started_time), and the time the task was marked as completed (task_completed_time).

    If you understand that an RBA should have been triggered based on a schedule and you are not finding any such record pertinent to that execution within this table it would warrant capturing details about the time point schedule, the RBA policy, and reproducing the behavior while the RBA engine is in DEBUG to engage with our Support team for an in-depth review. 

     

4 Replies

  • BryanHarding's avatar
    BryanHarding
    Icon for Moderator rankModerator
    2 months ago

    All RBA execution, down to the action, are tracked to an internal database for metrics however, unlike event-based RBA execution, schedule RBA execution are not presently logged anywhere UI facing. I can share more information regarding the relevant tables if desired.

    While this particular Ideas Hub post covers more than what you're inquiring, I would certainly draw a connection with logging scheduled RBA execution to the respective device logs in relation to Run Book Logging to Device Log | Nexus ScienceLogic Community and would encourage you to add your support and commentary. If you had something more central in mind, that is not a feature currently roadmapped nor am I aware of any existing requests so if that were the case I'd recommend filing a brand new idea with description of the use cases you're currently trying to achieve and an ideal desired state (for you) to document and garner support and feedback.

  • Alfred_Heijkoop's avatar
    Alfred_Heijkoop
    Icon for Expert rankExpert
    2 months ago

    Hi Bryan,

    We are interested in the relevant tables since we have experienced a couple of time that the RBA schedule was not triggered. 

    Thanks.

    Alfred

    • BryanHarding's avatar
      BryanHarding
      Icon for Moderator rankModerator
      2 months ago

      Alfred,

      Each and every RBA policy execution results in a record to `master_logs`.`automation_policy_metrics` capturing which RBA policy, what triggered it, and timestamps for milestones of execution. The two key fields for your presented problem will be: ap_id and trigger_type where:

      ap_id = Local ID of the Run Book Automation Policy. You will be able to parse this from your RBA policy inventory in the UI (Registry > Run Book > Automation).

      trigger_type = The type of trigger method. As your concern is around time-point scheduled RBA you will be looking for this value being "1".

      Filtering on these two fields will show you all scheduled RBA executions and with that list you will be able to see the time the task was evaluated by the RBA engine (task_loaded_time), the time the RBA engine started the task execution (task_started_time), and the time the task was marked as completed (task_completed_time).

      If you understand that an RBA should have been triggered based on a schedule and you are not finding any such record pertinent to that execution within this table it would warrant capturing details about the time point schedule, the RBA policy, and reproducing the behavior while the RBA engine is in DEBUG to engage with our Support team for an in-depth review.