Would like to know on what basis iDash collects job data, it seems somewhat random. Have 1087 SLA and data is collected for those. However have many other jobs in Autosys for jobs that do not have SLA's and for some of those jobs there is SLA data.
For example, we have an app code for jobs au_cba_hado% and there is job data for some jobs in the iDash database, but not all of them. I am wondering why this is?
What basis does iDash Autosys collect job data into the iDash DB. Is is it if SLA's, OR reports, or some other.
On reading the manual / techdoc content and the sql script, it seems that a table index xak_idash_ujo_proc_event is created on the Autosys Database, and not on the iDash database. Please confirm if this is correct.
From the techdoc:
b) Run aedb_index_for_import.sql.
This will create an index in the AutoSys database if the auto import feature in iDash is enabled and an existing index isn't already in the database.
Have checked the Autosys database for the index xak_idash_ujo_proc_event and it does not exist, so seems auto import is not enabled.
The manual / techdoc entry is a bit ambiguous. How can i determine if the auto import feature is enabled? I don't see anything in the iDash GUI for it?
Please confirm if my understanding is correct.
Release : 12.1.02
The index referenced in the iDash Techdoc is to be created on the Autosys database.
This index is on two columns of the Autosys ujo_proc_event table: que_status_stamp and evt_num. If there is an existing index for these two columns, even if it has a different name, you do not need to create this index. If there is no matching index, you should create this one for increased performance on the import. Under normal operations, this will not make a lot of difference. If you are ever in a position where you are recovering from an iDash outage and importing multiple days of data from Autosys, this index will help the import go quicker.
To determine if the auto import feature is enabled, take a look at the Autosys instance definition in the iDash Admin Tool. You will find a tab for Archive Data Settings. There are three data types that iDash will import: Job Runs, Events, and AutoTrack. If any of these have a checkmark in the Archive box, then auto import is enabled for that datatype. If it is enabled, there is also a setting to tell iDash how much data to keep.
To be clear: the index on the Autosys database is not a requirement to have auto import enabled. It can, however, improve import performance under certain circumstances.
In answer to your questions:
Regarding file settings on the iDashDB Archive Tab settings.
The file names in the iDash DB / Archive tab are for uploading Job, Event, or Autotrack data from the Autosys archive files. In past releases, these files could be uploaded using the Admin Tool, and this tab is where you would do that. Currently, this feature is disabled from the Admin Tool, and uploads of Autosys archive files are done using the CLI. There is no impact in not having any files listed on these tabs.
The SLA Settings tab contains time limits for archiving and deleting data related to SLA runs and CA 7 alerts. If you click the blue question mark button, the online help panel that opens will give you a breakdown of what specific things each of these values controls.