|
|
|
|
|
 |
Problem:
Most of today’s monitoring solutions don’t provide for a simple, integrated method of manual or automated remediation. The most common reason is that most traditional monitoring systems are not vendor agnostic and most monitoring tool vendors are uninterested in providing in depth remediation of competitors’ products. Consequently, users are required to keep lists of computer names, IP addresses, log locations, and terminal server port numbers. In addition, they must maintain definitions of the thousands of the often cryptic error messages each device may issue. These lists are often out of date and kept by individuals, making shared remediation responsibilities problematic.
Because most solutions depend on agents, they are dependent upon a production quality environment where all the attendant components such as the operating system, the memory and the Central Processing Unit (CPU) are functional.
Effects of Problem:
When a problem occurs on a system, administrators have to find the information they need for remediation from many data sources. They then must attempt to isolate and connect to the suspected failed devices. Worse yet, in many cases they have to physically go to the data center containing the failed system, find a crash cart, find the failed device among the many others, find the equipment required to connect to the failed device, then connect to the hardware management interface to first determine what the problem might be, then remediate.
In addition, because of the dependencies of the agent technology, administrators have no immediate means of determining the root cause of the device failure. For example, if a device appears to have failed, it may in reality be the result of one of the many dependant components failing, such as the operating system, the hardware, the network, or simply the agent.
The Ideal Solution:
In an ideal world, we would click on an icon for a failing component in our integrated monitoring and management solution and have instant, secure access to the failing system. We would have logs of who connected to the system, when they connected and what they did, keystroke by keystroke. We would never have to dispatch someone to a data center. We would never have to fumble with cables, connectors and crash carts. We wouldn’t have to install client software on any computer and as long as we had internet connectivity to the management application, we could get a connection to every monitored system.
TDI Solution:
In the ConsoleWorks world, we have real time notification of a problem often including root cause using any standard means of notification including email, cell phones and text messaging. An icon identifies the failing component and provides instant, secure, remote access eliminating the need to visit the data center. ConsoleWorks provides centralized, digitally signed, time stamped logs of all device activity including who has connected, when they connected and what they did, keystroke by keystroke. ConsoleWorks provides a clear understanding of the vendor error messages with best practices, internal links to operations procedures manuals, and complete example of previous remediation for the same event.
Access using a command line or web browser interface does not require cables, connectors, crash carts or agents. The solution allows for hardware reconfiguration and diagnostics, operating system patches, and application or network restarts and just plain connectivity to the managed device even after the operating system has failed.
With ConsoleWorks mean time to remediate is significantly reduced which reduces costly downtime. In addition, remediation is performed in a consistent manner eliminating unanticipated negative impacts on other systems.
ConsoleWorks provides the following:
- Monitoring 24X7
- Aggregated event monitoring from the entire enterprise
- Real-time notification of events
- Real -time logging of events
- Goes a step beyond SNMP monitoring tools like HP OpenView, Tivoli, BMC Patrol to event management
|
|
- (CIP 002-009, Sarbanes-Oxley, SAS 70, GLB, HIPAA and others)
- Monitor and manage critical compliance events in addition to operations events
- Real-time business intelligence surrounding compliance events
- Understand the business intelligence of when an event occurred, where it occurred, who managed the event, and how the event was managed
|
|
|
|
|
|
|
|
