Take a look ↓↓↓
PRESENCE
These days, many components make up the infrastructure for delivery of a quality ERP, CRP or Decision Support system.
Ensuring that these components are alive and running 24/7 is often essential just to ensure User Access.
Whether the component is a serious IBM POWER server, a Mainframe, an Intel Server or indeed simply a Switch or a SAN, ISSO247 will monitor each component and send up the alarm if any device goes off-line or cannot be reached. This is what we see as the very minimum requirement in a Monitoring system, such like a DC might provide.
That’s just the first step.
Now let’s look at managing the Capacity…
CAPACITY
Checking that a resource or service is present is one thing, checking its health is another. The ISSO247 service, using Command Reach, is also checking the capacity of the processing resource, the memory or the storage used.
This then starts to set ISSO247 apart from the standard in-house ‘Ping’ monitoring services as it provides a new level of ensuring availability by providing good quality Capacity Management information.
The information can be recorded, where appropriate, and used to measure Peaks, Troughs and Growth over a long period. Information can be viewed by you through the Command Reach Web Portal and all responsibility for processing and storage of the information is on Essist, not your own resources.
OK, The servers are healthy, what about the APPLICATION>>>
AVAILABILITY
What about the APPLICATION?
To some, Availability just means that the resource is responding to a ‘Ping’ test. However, in many cases, whilst the server may be up and running and the disks spinning, the service it is designed to deliver is just not available to the users.
Consider an IBM POWER server which is holding the database for your application. The server may be running and the SAN or Disk Storage arrays be all in good health but if certain jobs are not running or certain Subsystems are not active and free, the Application may become stalled; users unable to process the business information properly.
This is where ISSO247 really starts to score, when it is actually looking at the APPLICATION itself and the DATABASE and ensuring that services are running, and are running correctly.
Take a look at the INCIDENT RESPONSE section…
INCIDENT ALERT
In all of the places, at all of the time, monitoring continues and occasionally, a threshold is breached or an issue arises and each of these will initially provoke an Alarm.
These are trapped by the ISSO247 service and recorded. Sometimes it is recording high usage; not a show stopper but something we will analyse later, say, monthly, and review whether services need to be upgraded.
Even down to specific jobs that either need to be running, must definately NOT be running or need to start and stop at specific times, all can be tracked, monitored and managed by the ISSO247 service.
Everything tracked and recorded… but what if it is fixable?
We need to RESPOND>>>
INCIDENT RESPONSE
Occasionally, where an Alarm prompts an Incident, it is often well within the bounds of the ISSO247 service to manage the Incident. Maybe at 02:00am, a subsystem or an auto-start job that we know MUST be active to underpin the application has failed and needs to be restarted or perhaps we need to manually change the schedule because of a process overrun… With the huge Essist Knowledge Base of these Incidents – and with your consent – the services can be restored by the Essist team so that the Application can continue.
Deeper Incidents and Problems are escalated to you and/or specialist resources to be addressed. Essist, – and ISSO247 – will manage the Incident through to resolution.
Whether the Incident is dealt with or escalated, all action is tracked and reported back for assessment and, possibly, a plan can be made to avoid the Incident in the future.
Let’s see what we are recording and REPORTING>>>
ANALYSIS AND REPORT
All available through the Command Reach Web Portal, Alerts, Incidents and Problems are recorded and can be analysed over time…
LINK TO COMMAND REACH
User activity and server activity is also recorded. We can see Who did What, When and Where… not just now but for any time in the past…
