|
|
|
|
|
|
|
Observer can monitor all aspects of your LAN- and WAN servers, workstations and IP devices. When problems are detected, you're notified via SMS, e-mail or pager message. When a failure is detected, the network monitor tool will try to correct the problem. The application can do the following checks and more;
IP-based : ICMP, DNS, HTTP(s), FTP, SMTP, POP3, SNMP, SNMP Traps, LDAP, NTP, NNTP and more.
Windows OS : CPU, File/Directory, Disks, Event Log, Memory, Process, Service, Terminal Server and more.
Windows BackOffice : MS Exchange, MS SharePoint, MS ISA, MS Message Queue and more.
Windows Anti-Virus : McAfee, Norton, NOD32, Kaspersky, Trend Micro, Sophos, Avast, AVG, Norman, Panda and more.
Linux/Unix OS : CPU, File/Directory, Disks, Memory, Daemon and more.
Database : MS SQL, MySQL, Oracle, MS Access, ODBC, OLE/DB (Progress, SyBase, Informix, Paradox, IBM DB2, ...)
Environmental: Temperature, Humidity, Wetness, Smoke, Motion, Resistance, Light, Door, Power and more .Detay
Windows : PowerShell, VBScript
Linux/Unix : SSH, RSH
Notifications : E-mail, SMS (GSM, SMPP, HTTP), Pager, SNMP Trap, Network Popup
CONTROLS
Internet Protocols
DNS: Checks if a DNS server is working well by reading a particular 'A' record on the DNS server and verifying the result.
FTP: Observer Network Monitor can check the availability of FTP sites. With the FTP check, you can check for a file in one of the subdirectories on the FTP server, and even check for a specific pattern in the file.
HTTP(s): Observer Network Monitor allows you to check the availability of HTTP and HTTPs sites, on default ports (i.e.: 80 and 443) or on alternate ports. If the HTTP(s) server is not directly accessible, you can configure Observer Network Monitor to go through a Proxy server to access the particular HTTP(s) server, even passing credentials for that Proxy server (to be able to make use of the Proxy). Additionally, you can pass credentials (username and password) to access the actual HTTP(s) site if required. Observer Network Monitor supports web site content checking; contents of web sites can be searched for text patterns (including tags).
ICMP Ping: ICMP Ping checks a remote host for availability. Local hosts should normally respond to ping requests within milliseconds. However, on a very congested network it may take up to 3 seconds or longer to receive an echo packet from the remote host. If the timeout is set too low under these conditions, it will appear that the remote host is not reachable (which is almost the truth). Observer Network Monitor checks servers for availability by sending ICMP Echo commands and wait for the responds. An ICMP timeout failure doesn't necessarily mean that the remote host is actually functioning beyond its ability to echo packets.
IMAP MailServer: Observer Network Monitor can check IMAP mail servers by establishing a connection on the remote IMAP port (usually port 143) and do a handshake. By handshaking, Observer Network Monitor can verify that the remote server's IMAP protocol is working well.
LDAP: LDAP (Lightweight Directory Access Protocol) is a protocol for querying (and modifying) directory services like Microsoft Active Directory and Novell Netware.
NNTP: Observer Network Monitor can check NNTP news servers by establishing a connection on the remote TCP port (usually port 119) and do a handshake. By handshaking, Observer Network Monitor can verify that the remote server's NNTP protocol is working well.
NTP: The NTP protocol is the protocol used to synchronize times between workstations and servers, and external time sources. Observer Network Monitor uses the IP based NTP protocol to check availability of internal and external time sources.
POP3: Observer Network Monitor can check POP3 mail servers by establishing a connection on the remote TCP port (usually port 110) and do a handshake. By handshaking, Observer Network Monitor can verify that the remote server's POP3 protocol is working well.
SMTP: Observer Network Monitor can check SMTP mail servers by establishing a connection on the remote TCP port (usually port 25) and do a handshake. By handshaking, Observer Network Monitor can verify that the remote server's SMTP protocol is working well.
SMTP to POP3: Checks if an e-mail service is working properly by sending a test e-mail message through an SMTP server and verifying that it has been delivered to the recipient's mailbox.
SNMP GET - SNMP means: Simple Network Management Protocol. The SNMP GET message allows the Network Monitor Engine to request information about a specific variable on a remote computer or device. The agent, upon receiving a GET message, will issue a GET-RESPONSE message to the Network Monitor Engine with either the information requested or an error indication as to why the request cannot be processed.
SNMP Traps: The SNMP Trap Receive check listens for real-time network traps for processing. An SNMP Trap Receive check works different than other checks in Network Monitor: the SNMP Trap Receive check is event-driven. The check is not executed at timed intervals, but is triggered as soon as a new trap is received.
TCP: Observer Network Monitor can check local- or remote servers by challenging a specific port. It makes a connection to it, and performs a challenge/respond (by sending a sequence of bytes to it, wait for the respond and analyzing the received information).
TFTP: Observer Network Monitor can check the availability of TFTP hosts. With the FTP check, you can check for a file in one of the subdirectories on the TFTP host, and even check for a specific pattern in the file.
WINDOWS
Anti-Virus: İThe Anti-Virus check allows monitoring various popular Anti-Virus packages on workstations and servers. The following Anti-Virus software packages are supported: McAfee VirusScan Enterprise, Norton Internet Security, Norton Anti-Virus, NOD32, Kaspersky Internet Security, Kaspersky Anti-Virus Server, Kaspersky Anti-Virus Workstation, Trend Micro Internet Security, Sophos Anti-Virus, !avast Anti-Virus, AVG Anti-Virus, Norman Anti-Virus, Panda Internet Security, Norman Anti-Virus.
CPU Usage: Observer Network Monitor provides the 'CPU Usage' check to monitor processor(s) on Windows platforms. When the CPU load exceeds the limit, an alert is generated. For multi-processor systems, you can select to monitor all CPU's (default) or monitor an individual CPU.
Directory: You are running Windows Server and some of your users insist on copying the contents of their notebook computer to your file server. Other users want to download everything they see on the Web. Unfortunately, you're running out of disk space. Disk space is your server's most expensive subsystem, so it's a good practice to monitor - for instance - user's Home Directories. The 'Directory check' can be of good help.
Disk Sürücüleri: Windows işletim sisteminin koştuğu sunucularda tüm fiziksel disk sürücüleri izlenebilir. Sağlıklı çalışmayan bir disk sürücüsü saptandığında yetkililer uyarılır.
Disk Drives: Observer Network Monitor can monitor all physical disk drives on servers running the Windows operating system. If a malfunctioning disk drive is detected on the computer, an alert is generated.
Disk Space: The amount of free disk space is checked periodically, and if it drops too low you're immediately notified. It can also notify if used space gets too high.
Event Log: Observer Network Monitor can read Windows Event logs on local- or remote computers. It can look for specific Event Sources, Categories, Event ID's and so on. It can look for a pattern in the Description of the Event. It can do advanced filtering in Event Logs; it can look for multiple events in the Event Log, and notify the system administrator if one of the Events occurred in a specific time interval. For instance, as a network administrator, you want an alert if there's a McAfee or Norton virus message in the Application Event Log, but only if the event is posted in the last 30 minutes.
File: Observer Network Monitor can monitor file existence, file size and file content. This is particularly useful in situation where results of scheduled batch jobs need to be checked. In many organizations, batch jobs run at night and produce logging information; Observer Network Monitor can check this logging information and analyze it. It can check the existence, or search for patterns. It can also check the size of a file.
Memory Usage: Observer Network Monitor can check the memory usage of the Windows Operating System. It can monitor the total available physical memory usage, the committed memory or the pages per second.
MS Exchange: Observer Network Monitor monitors the status of the Exchange services, and monitors the most important performance counters. Among these performance counters are: performance counters for the Information Store, mailboxes, public folders and SMTP connector. If it drops too low you're notified immediately. One can extend the Exchange check function by checking more services and monitoring more performance counters.
MS ISA Server: Observer Network Monitor monitors the status of the MS ISA Server services. It can monitor a caching-only ISA server, a firewall-only ISA server, or an integrated (caching+firewall) ISA server.
MSMQ: Observer Network Monitor monitors the status of the MS Message Queue's. It can check a queue for its length (i.e.number of jobs in the queue) or for its total size (MB).
MS SharePoint: Observer Network Monitor monitors the status of the MS SharePoint Server services. It can monitor the following MS SharePoint flavors: 'Microsoft Office SharePoint Portal Server 2007', 'Windows SharePoint Services 3.0 (framework for MOSS 2007)', 'Microsoft Office SharePoint Portal Server 2003' and 'Windows SharePoint Services 2.0 (framework for MOSS 2003)'.
MS Terminal Server: Observer Network Monitor monitors the status Terminal Server (part of Windows 2008/Vista/2003/2000/XP) server by checking the number of active/inactive sessions.
Printer: Observer Network Monitor checks printers for availability by checking its status. Windows knows a wide range of printer status values, like: 'Running', 'In Test', 'Power Off', 'Offline', 'Power Save', and so on. If the Printer Status is not equal to Running or Power Save, then the printer is considered as malfunctioning.
Process: Observer Network Monitor allows users to check processes on local- and remote computers; if a process is active, a computer is considered available. Additionally, memory usage of a process can be checked, to detect memory leaks.
Scheduled Task: With the Scheduled Task check, one can check if a scheduled task has completed successfully or not. A Scheduled Task check can only be applied to a task that should run today. I.e. you cannot check the completion of a task that ran - for instance - yesterday
Service: Service monitoring involves a probe that returns the status of a service. Observer Network Monitor monitors services on local- and remote computers by checking if the status equals 'Running'. If so, the server is running fine, otherwise it's not.
Windows Scripting
VBScript : Observer Network Monitor provides a programming interface to IT administrators. VBScript is the standard scripting language in Observer Network Monitor product. VBScript is the most popular scripting language in Windows environments. By default, Observer Network Monitor can process up to 8 VBScript scripts simultaneously (multithreaded). Uses the powerful Visual Basic Scripting Engine provided by the Operating System. By making use of ActiveX controls, WMI and ADSI, you can write virtually any check yourself.
Database
Database Query: Observer Network Monitor uses OLE DB (also known as ADO) to check availability of databases. OLE DB (sometimes written as OLEDB or OLE-DB) is an API for accessing different types of data stores in a uniform manner, including: MS SQL, MS Access, Oracle, MySQL, SyBase, Informix, Paradox and IBM DB2 and more.
ODBC: Observer Network Monitor uses ODBC to check availability of a variety of databases. Most major database systems support ODBC, such as: Microsoft SQL Server, Microsoft Access, Microsoft Excel, Oracle, FoxPro, Paradox, SyBase, Informix, OpenIngres, InterBase, Progress, IBM LANDP, DB2 and AS/400. You must configure ODBC (from the Control Panel on the server where Observer Network Monitor is running on) before Observer Network Monitor can check ODBC compliant databases.
Oracle: Observer Network Monitor uses SQL*Net to monitor Oracle servers for availability. The role of SQL*Net is to establish and maintain a connection between the client application and the server and exchange messages between them. SQL*Net is a software layer that is required to communicate between Oracle clients and servers. It provides both client-server and server-server communications across any network. It enables client tools to access, modify, share, and store data on Oracle servers over a Network. The communication between client applications and servers takes place across one or more networks, and is referred to as client/server communication.
Miscellaneous
Serial Device : Observer Network Monitor allows you to query a serial device (e.g. a modem, a weight indicator, etc.) and analyze the response. The device must have a serial port interface, for instance an RS-232 interface. USB devices are also supported, but only if the device ships with a driver to emulate a serial port.
User/groups : Observer Network Monitor monitors groups and group membership. In case of unexpected members in certain groups (for instance: unexpected Domain Admins members), it'll notify the network administrators. Observer Network Monitor checks different kinds of Directory Services. Novell NDS is one of them. You can configure Observer Network Monitor to check user accounts (locked out, disabled, etc.), groups, group membership, organizational units, and so on.
|
|
|