Upload
extra-technology
View
149
Download
0
Embed Size (px)
DESCRIPTION
iDash Overview presented by Daniel Chidgey (October 2014)
Citation preview
CA WATS 2014
Workload Automa4on iDash Overview Daniel Chidgey
Agenda
• Introduc4on • What is iDash? • iDash Components • Product Features • iDash Reports • CLI
2
3
What is this iDash product all about…?
4
iDash Components
5
iDash Components -‐ iDash Daemon Generates forecasts Monitors AutoSys health and job execu4ons Calculates upstream Cri4cal Path and Cri4cal Path progress for all jobs with SLA defined Generates CA Workload Automa4on AE Alarms for Start / End SLAs:
– At risk – Predicted to be missed – Missed
6
iDash Components -‐ iDash Database Stores iDash data (Configura4on, Security, SLA defini4ons and Audit trail) Repository for AutoSys historical data (from auto archive files)
– Job runs – Events – Audit informa4on – Performance sta4s4cs
iDash Database supported types: – Oracle – SQL Server – Sybase
7
iDash Components -‐ iDash Clients Op4on 1 – The iDash GUI
– Available for Linux and Windows. – Monitor, report, forecast, and control the SLA thresholds and the
Cri4cal Path jobs – No local client install on your PC
Op4on 2 -‐ The iDash Client CLI – set of commands that can be deployed to any supported system – Permits users to perform certain Administra4on func4ons (e.g.
manage SLA defini4ons, load CA Workload Automa4on AE archive files, and generate iDash reports in PDF, HTML, and CSV formats).
8
Super Easy Deployment…
• Windows/Linux Server
• Apache Tomcat (6 or 7)
• Java JRE (6 or 7)
• iDash Database (SQL/Oracle/Sybase) – (Single or Dual)
9
Key Features • The ability to easily control and manage SLAs • Understand the impact of real 4me events before they cause
issues • Automa4cally take correc4ve ac4on (Script) • Early no4fica4on • Historical Data -‐ Hold vast amounts of data without impact to
workload performance. • New with r11.3.6 – iDash integra4on with CA7
10
SLA Requirements – Where you might use iDash
• The en4re job stream must complete successfully by a par4cular 4me.
• A job within the job stream must start by a par4cular 4me.
• A job or a set of jobs within a job stream must start and finish by a par4cular date and 4me
11
SLA Requirements – What you need.. • Start deadline (Time job/jobs must start by)
• End deadline (Time job/jobs must complete by)
• Or Both
12
Understanding some key iDash terms
13
Run Validity
SLA Time 10:00am
Execu4on Time
Run Validity set to 10 minutes.
14
At Risk Warning
Current Time
Calculated Execu4on Time
At Risk
SLA Deadline
15
Cri3cal Path
JOBA
JOBB
JOBE
JOBC
JOBD
16
Cri3cal Path
JOBA (5mins)
JOBB (25mins)
JOBE (10mins)
JOBC (5mins)
JOBD (5mins)
17
Cri3cal Path
JOBA (Complete)
JOBB (6 Mins Leh)
JOBE (10mins)
JOBC (5 Mins Leh)
JOBD (5 Mins Leh)
18
Live Demo
Showing SLA & Cri4cal Path
19
iDash Reports
20
Job Status Report
21
Job Status Report
22
Job Run Report
23
Job Run Report
24
AutoSys Event Report
25
AutoSys Event Report
26
AutoSys Event Report
27
AutoSys Autotrack Report
28
AutoSys Autotrack Report
29
Live Demo
Showing iDash Report Genera4on
30
IDash CLI.. again • Quickly generate reports in required format (PDF/HTML/CSV/XLS)
• Load archived job run data into iDash Database
• Manage SLA’s
31
CLI: Generate AutoSys Run Report PDF
idgenpdf -t run.report -n <ReportName>-f C:\<Output Name>.pdf
32
CLI: View SLA defini4on idlist -t sla –n <SLA NAME> -i <Instance>
33
Live Demo
Showing CLI Example