 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AUTOMATED
SYSTEM
MONITORING
Avoid
costly
downtime
and
other
conditions
that
could
prevent
CoreCard
software
from
running
in
an
optimal
environment.
CoreDASHBOARD
does
the
heavy
lifting
associated
with
the
monitoring
process.
CoreDASHBOARD
automatically
monitors
the
status
and
performance
of
all
the
servers
where
CoreCard
applications
are
running.
ALERTS
AND
ALARMS
CoreDASHBOARD
can
be
configured
to
send
alerts
and
notification
alarms
via
email
to
the
people
charged
with
maintaining
your
systems
regarding
specific
conditions
for
individual
as
well
as
groups
of
computers.
-
Establish alarms and alerts to be generated if certain conditions arise in a single computer or a group of computers. Alerts may be defined for many processes, such as an application running, down, frozen, etc.
-
Keep informed as to when all CoreCard applications are brought online or taken offline.
-
Send notifications via email when certain conditions are met, such as CPU load, free memory, used memory, used disk space, free disk space, CoreISSUE status, CoreACQUIRE status, CoreCOLLECT status, etc. For example, an alarm can be set when the CPU load is over 90% on the servers.
-
Set alert messages for application servers and send an email when a certain value is reached.
-
Define custom alerts to monitor batch and VB script activity and send emails when scripts fail. Dashboard’s alerts are not hard-coded so they can be adjusted whenever needed and additional alert scripts can easily be added according to your requirements.
-
Send an email warning when a workflow appears to be “stuck” or when there appears to be no work for a workflow to perform.
-
Send an email informing you that a workflow is finished.
REPORTING
AND
QUERIES
-
Run live queries against the databases. Queries can be a disposable “run once and discard” type of query, or a stored query that you can link to a scheduler function to monitor a scheduled process.
-
View logs of all user and machine activity, including an outage report that displays a record of the time an outage began and ended for CoreISSUE, CoreACQUIRE, and CoreCOLLECT for a specified date range.
SCHEDULE
ACTIVITY
-
Bundle multiple, similar computers for monitoring, maintenance and scheduling. For example, you can define a group named “non-interactive workflows” so that all the computers in that group can be scheduled to each start five instances of non-interactive workflows at a designated time each day.
-
Start and stop processes and workflows via a schedule and launch processes real-time.
-
Set workflows to run on certain machines on specific days of the month.
-
Perform a system check of everything that is running, such as a percentage of total CPUs, a percentage of total memory, and a percentage of hard drive usage, for each computer in your network.
Return
to
CoreENGINE |
|
|
|
|
|
|
|
|
|
|
