Examining current resource considerations and future operational needs helps you to make preliminary decisions about resource monitoring prior to setting up specific monitoring criteria in OpenEdge Management.
For example, consider the following as you evaluate your current resource-related operations and processes:
Which employee at your company is typically notified that a resource is down, and what method do you typically use to contact that individual? Is there too much downtime between a resource trouble report and the response from personnel assigned to handle a given problem? Do problems stack up because your system does not prioritize and queue these problems to the correct person's attention?
What is your typical weekly resource load? Can you define the peak load times for your applications? If so, do you have procedures in place to address the higher-than-average strain these events place on your resources? Similarly, do you also experience idle time? Do you adequately plan this slower-than-normal time into your schedule so that you can routinely run other processes at this time?
Do you have a scheduling process that enables you to run your applications, and automatically notify interested personnel when these jobs are done? Can this process also alert you to a problem and take predefined, corrective action?
As these questions suggest, there are considerations you must address as you move from your present approach for determining your resource needs to systematically analyzing and fulfilling those needs using OpenEdge Management.
Which employee at your company is typically notified that a resource is down, and what method do you typically use to contact that individual? Is there too much downtime between a resource trouble report and the response from personnel assigned to handle a given problem? Do problems stack up because your system does not prioritize and queue these problems to the correct person's attention?