Skip to content

Continuous Workflow Monitoring Support
Compare
Choose a tag to compare
@JKashyap96 JKashyap96 released this 18 Oct 09:05
· 6 commits to main since this release
v2.2.0
f3d3480
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Features

  1. The workflow-collector job now runs in a loop, continuously assessing the health of all jobs in the Workflow. Any status change in jobs will now be sent to SumoLogic. Only once all Jobs are no longer in some form of running/in process state will the workflow-collector finish. This addresses the current issue with the workflow-collector where only the initial job status will be sent to Sumo, and often some are completely missed as they aren't running when the first API call is made to CircleCI.

  2. Added timeout-seconds parameter (defaults to 180s/3mins) to end the workflow-collector early when required. This helps to account for any unforeseen edge cases which could cause the loop to never end, therefore consuming large amounts of CircleCI credits unintentionally.

  3. Manually setting the Workflow status based on the overall health as the final step. This is a bit of a workaround to the workflow-collector job itself being a blocker to the workflow ever reaching its final state.

Bug Fixes

  1. The workflow-collector job will now always send compact JSON payloads to SumoLogic.

  2. The provided custom-data is now added to the job updates when sent to SumoLogic (this won't happen when job-collector command is being used as a step in the job as no data is sent to Sumo for these jobs by the workflow-collector).

Assets 2
Loading