Monitoring operation and maintenance system implementation scheme--monitoring object information gathering stage

Monitoring operation and maintenance system is not an overnight thing, nor overnight can be easily completed, monitoring operation and maintenance system scale and size of the server and software is closely related to the need for careful analysis and planning to achieve a usable monitoring operation and maintenance system.
In order to visually represent the current system (unless the special instructions refer to the operating system) and the running state of the application, it is possible to make the leader of the operation and maintenance knowledge understand the current running state, the best way is to show the logical relationship between these systems and applications by using the graph method. Depending on the system and the business, they can be divided into three graphs (which can be called system frame composition, software frame composition, and business logic diagrams).
1. System Architecture Diagram: Represents the stacking relationships of all systems, such as physical servers and virtual servers, which are shown in different forms in the diagram, and can be seen with a glance at the problems of those systems.
2. Business logic diagram: The business logic is represented separately, and the dependencies and other relationships between the business logic are expressed, so that when the overall fault is discovered, it is possible to determine where there is a problem that can lead to the overall failure, and through this graph one can see those business problems, what problems exist
3. Software Architecture diagram: Represents a business-to-system relationship, that is, which systems the business is running on, or which operations are running on each system, and which systems or modules to troubleshoot when a problem occurs

In order to achieve a better monitoring effect, you need to prepare the following elements:
1. Hardware level: The actual use of the current server, such as the number of servers, host name (specification of the FQDN), IP address (how many addresses to write how many addresses), operating system categories, management and management information (how to Telnet, user name and password, etc.); It is best to include information about network devices such as how to connect to the server, bandwidth, etc.
2. Operating system level: regardless of whether the operating system is virtual or non-virtual, for monitoring is a complete monitoring entity, and hardware-level server, it also needs to know exactly the host name (canonical FQDN), IP address (how many addresses to write how many addresses, and distinguish between management address and business address, etc.), Operating system categories, management and management information (how to Telnet, user name and password, etc.)
3. Software (business) level: The name of each business module, the functionality provided, the dependencies (what other business modules are required for the business module, which business modules need the business module), the process or service name, the IP address and port (socket) to listen on, The monitored status of each business module when it is functioning (such as how much normal the return value is, what string is normal, etc.)
4. Each business module in the software level corresponds to the operating system level, the business module requires those packages (dependencies) in the operating system, the installation path, the available diagnostics and maintenance tools, etc.

Some tables to refer to

Table 1: Server monitoring list

Server serial Number	Host Name	IP Address 1	IP Address 2	Operating system Categories	How to sign In	Manage addresses	Manage user Names	Manage passwords	Note
1	rc220.domain.cn	221.0.92.31	192.168.1.100	Linux Ubuntu	IDRAC	221.0.93.31	Username	Password
2	bb200.domian.cn	-	192.168.1.200	VMware ESXi5.5	UCS Manager	192.168.1.200	Username	Password

Table 2: Operating system Monitoring list

Operating system serial Number	Host Name	IP Address 1	IP Address 2	Operating system Categories	Whether the virtual machine	How to sign In	User name	Password	Note
1	node1.domain.cn	221.0.92.31	192.168.1.100	Linux Ubuntu	-	Ssh	Username	Password
2	node2.domain.cn	-	192.168.1.101	Linux Ubuntu	-	Ssh	Username	Password
3	vcenter.domian.cn	-	192.168.1.201	Linux SUSE	Is	VSphere Client	Username	Password

Table 3: Business Module monitoring list

Business Module Serial Number	Module name	Module function Description	Dependency A	Dependency b	Process name (full command line)	Listening for IP addresses	Listening port	Normal status description
1	relational database	MySQL Database	-	Information Collection Services Information Enquiry Service	Mysqld_safe--datadir=/data/mysql	192.168.1.100	3306	3306 port is listening, process exists, allow connection, database exists, database table exists, database field exists
2	Information Collection Services	Collecting User Information	relational database Web server 1	End user Information Enquiry Service	Command--parameter=/path	192.168.1.101	8081	XXX port is listening, XXX process exists, return value is xxx,xxx URL return xxx
3	Information Enquiry Service	Querying user Information	relational database Information Collection Services	End user	Command--parameter=/path	192.168.1.102	8082	XXX port is listening, XXX process exists, return value is xxx,xxx URL return xxx
4

Table 4: Business modules and operating system correspondence

Number	Module name	Business Module Serial Number	Operating system serial Number	Package/Compile Parameters	Installation path	Available Diagnostics	Maintenance tools	Note
1	relational database	1	1	Mysql-server,mysql,musql-libs,mysql-devel	/usr	Msyql,mysqladmin	Mysql,mysqladmin
2	Information Collection Services	2	2	-	/usr/local/wwwroot	Curl,wget	-

Reference Graphics:

The reference graphics can be drawn in Visio, and the composition needs to be made according to the table above, by system architects, software architects, or system operators who have known the system architecture and software architecture for many years.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;border-bottom:0px;border-left:0px; " Border= "0" alt= "image" Src= "http://s3.51cto.com/wyfs02/M01/6F/AB/wKiom1WkmeWhQ_VmAACUK-GOWgI928.jpg" height= "179" />650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;border-bottom:0px;border-left:0px ; "border=" 0 "alt=" image "Src=" http://s3.51cto.com/wyfs02/M01/6F/A9/wKioL1Wkm73juyITAACgSZsAzG8425.jpg "height=" "/>650" this.width=650; "title=" image "style=" border:0px;width:210px;height:148px; "border=" 0 "alt=" image "src = "Http://s3.51cto.com/wyfs02/M02/6F/A9/wKioL1Wkm77xUjbaAACHim-FFMg554.jpg" height= "148" width= "hspace=" 0 " Vspace= "0"/>

The above three charts are the system architecture diagram, the software architecture diagram, and the general example of the business and operating system mapping diagram.

--end--

This article is from "Communication, My Favorites" blog, please make sure to keep this source http://dgd2010.blog.51cto.com/1539422/1674040

Monitoring operation and maintenance system implementation-monitoring object information collection phase