iDash Workload Automation

 View Only
  • 1.  iDash Schema

    Posted Nov 06, 2019 03:14 PM
    Hi All,
    We are in the process of designing some custom reports during the process of migration ​of our existing tool Axway Sentinel to iDash. We need little more information on iDash database. If we can get information on schema or any document which can explain idash database table.

    Thanks


  • 2.  RE: iDash Schema

    Broadcom Employee
    Posted Nov 07, 2019 09:28 AM
    Hi Ahmad,

    Can you please explain what kind of customization are you looking at for reports? We can then discuss if the existing iDash reporting capabilities can meet your goals. We do not have a document on the iDash Database schema because we would like to not expose this information.

    Sincerely,
    Chirag


  • 3.  RE: iDash Schema

    Posted Nov 08, 2019 02:43 AM

    iDash just provide simple reports and we want to build custom reports, notification and alerts using data from iDash database. Following are just few from our list.

    1. After critical job's aborts wants to create the 3 steps escalation process. After abort notify the on-call developers, If it is not acknowledged in 60 min escalate to Team Management than in next Departmental Management.
    2. Alert specific team if more than 5 jobs aborts at the same time range.
    3. Alert if jobs running in day time if other specific critical jobs are running.
    4. Notify comparison of long running jobs between different area.

      Thanks



  • 4.  RE: iDash Schema
    Best Answer

    Broadcom Employee
    Posted Nov 08, 2019 10:35 AM
    Hi Ahmad,

    The first two scenarios can be managed through the iDash CLI alarm report where you can verify the alarm status of the AutoSys jobs/SLAs in interest and take the appropriate action. More information here: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/automation/ca-workload-automation-idash/12-0-5/using/reports/generate-reports-with-cli-commands/alarm-report-cli.html

    Can you elaborate on point 3? For point 4, if you are looking for any job that runs longer than its average runtime then you can use the job run reports to compare the average runtime vs duration for jobs that are in a RUNNING state.

    Sincerely,
    Chirag