Date: Thu, 28 Mar 2024 23:21:06 +0000 (UTC) Message-ID: <1213364858.5543.1711668066083@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5542_1541582606.1711668066080" ------=_Part_5542_1541582606.1711668066080 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Uptime Infrastructure Monitor tool bar provides quick= access to the following:
This panel contains various dashboards t= hat present the status of your resources from various perspectives. For exa= mple, the Global Scan dashboard presents a comprehensive view of your infra= structure, and allows you to drill down by system group, system, or alert s= tatus. Default dashboards include the following:
Administrators and users can also create custom dashboard= s, built from component widgets, that provide a specific view not provided = out of the box.
For more information about using the Dashboards panel, se= e Overseeing Your = Infrastructure.
By default, when users log into Uptime Infrastructure Mon= itor, the first view they are presented with is the My Portal panel. The My Portal panel gives quick access to basic Uptime Infrastru= cture Monitor functions and to saved reports. The My Portal panel is divide= d into the following sections:
For more information about using the My Portal panel, see= My Portal.
The My Infrastructure panel provides an = inventory of your resources. You can view information about systems and the= ir monitoring status. From the My Infrastructure panel, you can add and vie= w:
For more information about using the My Infrastructure pa= nel, see Managing Yo= ur Infrastructure.
The Services panel enables you to manag= e and configure services, which are provided by an application to perform a= specific task. Uptime Infrastructure Monitor monitors both services and ap= plications to ensure that performance and availability are maintained.
In the Services panel, you can manage and configure the f= ollowing:
For more information about using the Services panel, see = Using Service Monitors= .
The Users panel enables you manage all = users, user groups, Notification Groups and their associated permissions. Y= ou can view, create, edit, and delete the following:
For more information about using the Users panel, see User Management.
The Reports panel enables you to manage = and create detailed, custom reports on the performance and availability of = the resources in your enterprise.
Using the Reports panel, you ca= n:
For more information about using the Reports panel, see <= a href=3D"/display/UT76/Using+Reports">Using Reports.
The Config panel enables you to configu= re the following:
You can also generate problem reports and edit some Uptim= e Infrastructure Monitor system configuration options from the Config panel= . For more information about using the Config panel, see Configuring = and Managing Uptime Infrastructure Monitor.
As you enter text in the Search Uptime f= ield, Uptime Infrastructure Monitor configuration actions, as well as the d= isplay names of Elements, are displayed.
For example, initially entering the string =E2=80=9Cserv
=E2=80=9D displays the Add Service Monitor and=
Add Service Group commands. The string could also display=
Element names such as "QA Server 1
" and "Active Directo=
ry
". In the latter example, the match would occur if the Element=E2=
=80=99s host name were "AD-Server
".
For all Elements, the string entered is compared with the= Element=E2=80=99s host name, display name, architecture, and custom fields= .
The system list (Syslist) is a popup win= dow that contains the following information:
You access the system list by clicking the Sysli= st icon in the top-right corner of the Uptime Infrastructure Monit= or Web interface. The Syslist is also a tool for quick navigation within th= e Uptime Infrastructure Monitor Web interface. Each display name is a hyper= link. Click a display name to view the information about the system in the = System Information subpanel.
Uptime Infrastructure Monitor includes a powerful set of = reporting and graphing tools that enable you to visualize performance data.= You can use the reports and graphs as the starting point when analyzing pr= oblems in your environment.
For more information, see Understanding Reports Options and Using Graphs.
Reports enable you to visually analyze how individual cri= tical resources-- such as memory, CPU, and disk resources--are consumed ove= r a specific period of time.
For detailed information about reports, see Using Reports.
If you need to regularly run certain reports, you can sav= e them to the My Portal panel. See Scheduling Repo= rts for more information.
You can graph performance information when you need to vi= ew the most common or pertinent performance information for servers in your= environment. For example, you can use a graph to determine CPU usage or th= e available capacity on a file system. Graphs give you a fine level of perf= ormance detail.
You can view graphs using the Java graphing to= ol on any platform (e.g., in Firefox, running on Linux). For more informati= on about graphing, see Using Graphs.=
Agents are small applications that are installed on the s= ystems that you are monitoring. Agents do the following:
Certain Uptime Infrastructure Monitor monitors poll the a= gents for data at a frequency that you can configure. The data collector co= mponent of the Monitoring Station then stores the results in the Uptime Inf= rastructure Monitor DataStore for use in a report or graph.
Agents enable you to collect very detailed information ab= out a system, such as information about processes and low-level system stat= istics. The level of granularity of the information collected by agents is = greater than that of the information collected by agentless monitors.
Each Uptime Infrastructure Monitor agent is configured by= default to collect and return performance information for every Uptime Inf= rastructure Monitor agent service monitor. You do not need to configure the= agent to collect information for a service.
On Windows, an agent is installed with the Uptime Infrast= ructure Monitor Monitoring Station. However, you need to deploy the agent o= n the systems you are monitoring. On other operating systems, you must down= load the agent from the IDERA Web site and manually install it.
When you install Uptime Infrastructure Monitor, you insta= ll a Monitoring Station and one or more Uptime Infrastructure Monitor agent= s. You could have different versions of Monitoring Stations and agents. For= example, you could have different platforms and different Uptime Infrastru= cture Monitor agent versions running on each system.
Regardless of operating system platform, the majo= r version is the number to the left of the decimal. In the diagram above th= e major number of the Windows agent is 3; the = major number of the UNIX agent is 3; the major= number of the LINUX agent is 4.0.
Minor version numbers follow the major version nu= mber. These numbers are used to distinguish each minor version of a major v= ersion.
On UNIX and Linux, the minor version is the first= number to the right of the decimal. In the diagram above, the minor versio= n number of the UNIX agent is 8 and the minor = version number of the Linux agent is 0.
On Windows, the minor version is the last set of = numbers in the complete version. In the diagram above, the minor version nu= mber of the Windows agent is 1061.
For major version 4 and later for Windows, the mi= nor version number is the number immediately after the decimal that follows= the major number. For example, for Windows agent version 4.0, the minor nu= mber is 0.
The DataStore is a database in which Uptime Infrastructur= e Monitor stores different types of information:
Like any other database, the DataStore consists of a numb= er of tables. Data that you enter and save, or which Uptime Infrastructure = Monitor collects from hosts, is written to specific tables in the DataStore= .
Access to the DataStore is determined by one of the three= installed user accounts: root, uptime, and reports. Each account gives use= rs varying levels of access to the contents of the DataStore. For more info= rmation about these accounts, see the Uptime Knowledge Base article =E2=80= =9CSecuring MySQL Database and Adding Users.=E2=80=9D
Uptime Infrastructure Monitor can also use either an Orac= le or MS SQL Server database as its DataStore.
You can extract data from the DataStore for use in custom= reporting or data warehousing by connecting to the DataStore using an ODBC= connection. Once the connection is established, you can import the content= s of the DataStore into such tools as MySQL Query Browser, Microsoft Excel = and Crystal Reports.
Before you can connect to the DataStore using ODBC, the c= lient system that is accessing the database must have the MySQL ODBC driver= installed. The ODBC driver enables the client system to communicate with t= he DataStore.
For detailed information on installing and configuring th= e MySQL ODBC driver, see the Uptime Knowledge Base article =E2=80=9CConnect= ing to the Uptime Infrastructure Monitor DataStore via ODBC.=E2=80=9D
Uptime Infrastructure Monitor service monitors ensure the= performance and availability of services in your environment. Using servic= e monitors, you can ensure that the systems in your environment - including= databases, mail servers, networking protocols, and file systems - are oper= ating as required. Uptime Infrastructure Monitor also captures performance = metrics collected from hardware profiles of physical systems in your enviro= nment and can present this data in a graph.
Uptime Infrastructure Monitor can track the performance o= f services using over 30 monitors. As well, Uptime Infrastructure Monitor e= nables you to configure custom monitors that you can use to extend your ser= vice monitoring capability.
For detailed information on service monitors, see Using Service Monitors.
There are two types of monitors for MySQL, Oracle, and SQ= L Server databases:
These monitors determine whether the database is = running and listening on the expected port. You can also run queries agains= t the databases using scripts.
These monitors collect detailed information about= database processes, which you can later use for reporting and graphing.
Net-SNMP suite of command line and graphical applications= that interact with SNMP agents that are installed on hosts. Net-SNMP prese= nts a set of SNMP MIBs (Management Information Base, which is a listing tha= t defines variables needed by the SNMP protocol to monitor and control netw= ork equipment). The MIBs are used to collect system performance information= for use by the Uptime Infrastructure Monitor Monitoring Station.
The Net-SNMP monitor uses the HOS= T-RESOURCES MIB to collect the following data:
The HOST-RESOURCES MIB can collect other configuration data, but the Mon= itoring Station does not use this information.
For more information on SNMP and Net-SNMP, see SNMP-Based Systems .
Services are specific tasks, or sets of tasks, performed = by an application in your environment. For example, network services such a= s FTP or TCP transmit data in a network. Database services, such as Oracle,= SQL Server, MySQL, or Sybase store and retrieve data in a database. Uptime= Infrastructure Monitor service monitors continually check the condition of= services to ensure that they are providing the functions required to suppo= rt your business.
Uptime Infrastructure Monitor service monitors use a comm= on template to ensure that the configuration of service monitors is the sam= e across all monitors. For more information on services, see Using Service Monitors.
Service groups are service monitor templates that enable = you to simultaneously apply a common service check to one or more hosts. De= fining and using service groups greatly simplifies the task of initially se= tting up and maintaining common service checks that you wish to perform acr= oss many hosts in an identical manner.
For example, you can create a service group called CPU Pe= rformance Check that is associated with 50 different servers. You can apply= a common performance monitor check to 50 servers.
With service groups, you save time by not having to manua= lly re-create an individual service monitor with the exact same service che= ck and Alert Profile for each server you want to monitor. There is no pract= ical limit to the number or complexity of your service groups and the under= lying service monitors associated with them.
Service groups can be created for both physical infrastru= cture assets that are monitored by Uptime Infrastructure Monitor, as well a= s virtual assets managed by VMware vSphere. Although they are functionally = identical, vSphere service groups are automatically applied to newfound ESX= hosts, VMs, and other VMware vCenter objects that are discovered through t= he vSync process.
See VMware vSphere Monitoring Concepts for information on vSyn= c, and Service Groups for information on creating service= groups.
Uptime Infrastructure Monitor monitors can return the fol= lowing statuses for a service:
The services are functioning properly.
There is a potential problem with one of more of = the services.
There is a critical problem with one or more serv= ices.
This status is returned when:
Each status reflects the state of the service that is ass= igned to the system that you are currently viewing. Uptime Infrastructure M= onitor picks up these error codes and triggers an alert or an action. If a = service is in a warning or critical state, you can acknowledge an alert so = that Uptime Infrastructure Monitor does not generate subsequent notificatio= ns.
The status of the services associated with a system are d= isplayed on the Global Scan dashboard.
The figures in each column on the Global Scan dashboard i= ndicate the number of services for that particular machine that are in each= state. Click a number to view the System Status screen for a particular sy= stem. See Viewing the Status of a System for more information.
When you are configuring graphs or reports, you must spec= ify a range of dates and times over which the graph or report charts inform= ation. Uptime Infrastructure Monitor only collects information for the peri= ods that you specify.
You specify data and time ranges in the Date Rang= e area of the Reports and Graphing subpanels.
To set dates and times for a graph or report, do one the = following:
You can also click the calendar icon to select dates.
The end date for any of these options is the cur= rent date and time. For example, if you select 1 and Days, then the graph or report covers t= he 24-hour period from the previous day until the date and time on which yo= u created the report.
The This Month option collects information from the fir= st day of the current month to the day on which the report or graph is = ; generated. The Last Month option collects information from the beginning = to the end of the previous month.
Uptime Infrastructure Monitor enables you to save some or= all of the metrics that its monitors collect to the DataStore. You can use= the retained data to generate a Service Metrics report (see Service = Monitor Metrics Report) or a Service Metrics graph.
The data that you can retain varies from monitor to monit= or. For example, with the Windows Service Check monitor you can save the Se= rvice Status and Response Time metrics. With the Exchange monitor you can s= ave all Web Mail and SMTP metrics.
You can save data to the DataStore by clicking the