ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

iDash log in Event Demon logfile on AE Server (AE Application server)

book

Article ID: 200116

calendar_today

Updated On:

Products

iDash Workload Automation

Issue/Introduction

Found the following idash staments in the Event Demon logfile on AE server.

grep -i "idash" /opt/CA/WorkloadAutomationAE/autouser.TQ1/out/event_demon.TQ1
[09/17/2020 04:31:00] <
iDash:SLA ID=IGSLQ_37_AMERICAS_FUNDJOBQ1^TQ1-20200917-0130 : Deadline=2020-09-17 01:30 -0400 : SLA=IGSLQ_37_AMERICAS_FU
NDJOBQ1^TQ1 : Next forecasted start:2020-09-17 06:54 :
iDash server=tdnidasha1>
[09/17/2020 05:31:42] <
iDash:SLA ID=IGSLQ_37_AMERICAS_FUNDJOBQ1^TQ1-20200917-0130 : Deadline=2020-09-17 01:30 -0400 : SLA=IGSLQ_37_AMERICAS_FU
NDJOBQ1^TQ1 : Next forecasted start:2020-09-17 06:54 :
iDash server=tdnidasha1>



How is it impact to size of event_demon logfile?
Is it possible to manage which logs should be present in event demon logfile?

Environment

Release : 12.1

Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7

Resolution

These are just alarms from iDash SLA for that job.

By default, it can only insert alarms into the DB. You can also set up sendevents and commands to send the AE server through the legacy clients, but those would only be done manually, by an operator. It would not be done by iDash itself. iDash is really meant only to monitor what the instance does, not to control it.