At Priya International Ltd, we provide a comprehensive console for your server monitoring requirements, be it Network related, functional/operational irregularity, LAN AND WAN, workstations, infrastructural set up, IP and other devices automatically in real time.
We monitor the network for failures and irregularities automatically. We 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, we will try to correct the problem.
DNS - Checks if a DNS server is working well by reading a particular 'A' record on the DNS server and verifying the result.
FTP - We 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) - We can 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 We 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. We 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). We checks servers for availability by sending ICMP Echo commands and wait for the responds.
IMAP Mail Server - We can check IMAP mail servers by establishing a connection on the remote IMAP port (usually port 143) and do a handshake. By handshaking, we can verify that the remote server's IMAP protocol is working well.
POP3 - We can check POP3 mail servers by establishing a connection on the remote TCP port (usually port 110) and do a handshake. By handshaking, we can verify that the remote server's POP3 protocol is working well.
SMTP - We can check SMTP mail servers by establishing a connection on the remote TCP port (usually port 25) and do a handshake. By handshaking, we can verify that the remote server's SMTP protocol is working well.
SNMP GET -SNMP means: Simple Network Management Protocol. The SNMP GET message 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 monitoring server 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.
TCP - We 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).
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 - We 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 Drives - We can monitor all physical disk drives on servers running the Windows operating system. We can check their total, used & free space & configure alert on predefined amount of use. If a malfunctioning disk drive is detected on the computer, an alert is generated.
Network Interfaces - We monitor the interfaces running on the device and automatically begins monitoring them. The following screenshot shows the interfaces on our server along with various bits of configuration information, including the interface Name, IP Address, Network, MAC address, operational status, administrative status.
Event Log - We can read Windows Event logs on local- or remote computers. It can look for specific Event Sources, Categories, and 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 - We 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; We 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 - We can check the memory usage of the Windows Operating System. We can monitor the total available physical memory usage, the committed memory or the pages per second.
Printer - We check 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 - We 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 – We 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. We monitor services on local and remote computers by checking if the status equals 'Running'. If so, the server is running fine, otherwise it's not.
ODBC - We can 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.