VISTA System Management Daily or Weekly Tasks - Revision history

Shabiel: /* VISTA Specific */

2015-04-23T17:50:19Z

VISTA Specific

← Older revision		Revision as of 17:50, 23 April 2015
Line 17:		Line 17:

	== VISTA Specific ==		== VISTA Specific ==
	* Taskman performance, especially:		* Taskman performance, especially:
	** Resource Devices		** Resource Devices
	** Printer Devices		** Printer Devices
	* Global growth by specific Fileman file		* Global growth by specific Fileman file
	* HL7 messages continuous flow		* HL7 messages continuous flow
	* Error trap		* Error trap
	* Taskman error trap		* Taskman error trap
	* Check ^TMP, ^XTMP and ^%ZTSK making sure that they are appropriately purged daily		* Check ^TMP, ^XTMP and ^%ZTSK making sure that they are appropriately purged daily
	* Check programmer mode log-ins		* Check programmer mode log-ins
	* Check excessive log-ins from a single location		* Check excessive log-ins from a single location
	* Check that nightly tasks ran (can be ignored as long as there are no history of problems)		* Check that nightly tasks ran (can be ignored as long as there are no history of problems)
	* Mailman		* Mailman
	** Check disk usage		** Check disk usage
	** Check user's usages		** Check user's usages
	** Check queues to make sure that they are not backed up		** Check queues to make sure that they are not backed up
	* Check Alerts		* Check Alerts
	** How many?		** How many?
	** Who isn't processing them?		** Who isn't processing them?
	** System (errors) or Clinical Alerts?		** System (errors) or Clinical Alerts?
	* PIMS Reports		* PIMS Reports
	** Potential duplicate patients recently entered		** Potential duplicate patients recently entered
	** Patient movements that are incomplete (I don't know how to do that)		** Patient movements that are incomplete (I don't know how to do that)

Shabiel: /* Other system */

2015-04-23T17:49:35Z

Other system

← Older revision		Revision as of 17:49, 23 April 2015
Line 10:		Line 10:

	== Other system ==		== Other system ==
	* Check disk space for all partitions		* Check disk space for all partitions
	* Check printer queues		* Check printer queues
	* # of processes		* # of processes
	* Processes consuming 100% of a single CPU that are running for more than 1 hour		* Processes consuming 100% of a single CPU that are running for more than 1 hour
	* Network latency for all major network nodes in which the database is spread out; and from where it is usually accessed by users.		* Network latency for all major network nodes in which the database is spread out; and from where it is usually accessed by users.

	== VISTA Specific ==		== VISTA Specific ==

Shabiel: /* VISTA System Management Daily and Weekly Tasks */

2015-04-23T17:49:08Z

VISTA System Management Daily and Weekly Tasks

← Older revision		Revision as of 17:49, 23 April 2015
Line 1:		Line 1:
	~~= VISTA System Management Daily and Weekly Tasks =~~
	The VISTA system, like any other database, needs to be monitored appropriately. I will mention here database related monitoring and then VISTA related monitoring. Many of the tasks that are inexpensive to check are better checked with a continuous such as Nagios or Munin.		The VISTA system, like any other database, needs to be monitored appropriately. I will mention here database related monitoring and then VISTA related monitoring. Many of the tasks that are inexpensive to check are better checked with a continuous such as Nagios or Munin.

	== Database monitoring ==		== Database monitoring ==
	* Global growth rate		* Global growth rate
	* Lock table consumption		* Lock table consumption
	* Daily back-up is happening daily; weekly check that the backup that was made can actually bring the system back-up		* Daily back-up is happening daily; weekly check that the backup that was made can actually bring the system back-up
	* Journal file growth rate		* Journal file growth rate
	* Back-up and Journal file rotation (delete old ones based on business requirements)		* Back-up and Journal file rotation (delete old ones based on business requirements)
	* Database blocks integrity checks		* Database blocks integrity checks

	== Other system ==		== Other system ==

Shabiel: Created page with "= VISTA System Management Daily and Weekly Tasks = The VISTA system, like any other database, needs to be monitored appropriately. I will mention here database related monitor..."

2015-04-23T17:48:24Z

Created page with "= VISTA System Management Daily and Weekly Tasks = The VISTA system, like any other database, needs to be monitored appropriately. I will mention here database related monitor..."

New page

= VISTA System Management Daily and Weekly Tasks =
The VISTA system, like any other database, needs to be monitored appropriately. I will mention here database related monitoring and then VISTA related monitoring. Many of the tasks that are inexpensive to check are better checked with a continuous such as Nagios or Munin.

== Database monitoring ==
* Global growth rate
* Lock table consumption
* Daily back-up is happening daily; weekly check that the backup that was made can actually bring the system back-up
* Journal file growth rate
* Back-up and Journal file rotation (delete old ones based on business requirements)
* Database blocks integrity checks

== Other system ==
* Check disk space for all partitions
* Check printer queues
* # of processes
* Processes consuming 100% of a single CPU that are running for more than 1 hour
* Network latency for all major network nodes in which the database is spread out; and from where it is usually accessed by users.

== VISTA Specific ==
* Taskman performance, especially:
** Resource Devices
** Printer Devices
* Global growth by specific Fileman file
* HL7 messages continuous flow
* Error trap
* Taskman error trap
* Check ^TMP, ^XTMP and ^%ZTSK making sure that they are appropriately purged daily
* Check programmer mode log-ins
* Check excessive log-ins from a single location
* Check that nightly tasks ran (can be ignored as long as there are no history of problems)
* Mailman
** Check disk usage
** Check user's usages
** Check queues to make sure that they are not backed up
* Check Alerts
** How many?
** Who isn't processing them?
** System (errors) or Clinical Alerts?
* PIMS Reports
** Potential duplicate patients recently entered
** Patient movements that are incomplete (I don't know how to do that)