Read the catalogue:
- Basic introduction
- Using configuration
- Deployment instance
- Panel Properties
- Summarize
Basic introduction
Opserver is an open source monitoring system for stack exchange, which is based on net and MVC, so net programmers can easily build on it two times. It mainly monitors:
- Servers
- SQL clusters/instances
- Redis
- Elastic Search
- Exception logs
- Haproxy
The Opserver provides a detailed panel to quickly display the overall condition of the monitored system. The following opserver example of the monitoring UI interface is very detailed:
Using configuration
Project Address: Https://github.com/opserver/Opserver
After downloading with VS Open or IIS direct deployment, the following is its support monitoring system of the view directory, the structure is relatively clear.
Security Configuration
Opserver system itself after the login verification, support 3 types of security authentication methods:
<?xml version="1.0"encoding="Utf-8"? ><securitysettings provider="AD"> <!--optional, the network below can be accessed without verifying direct access--<InternalNetworks> <network name="SE Internal"Cidr="10.0.0.0/8"/> </InternalNetworks></SecuritySettings><!--Everyone is admin accessible<securitysettings provider="Alladmin"/>-->
If you use Active Directory authentication, you can configure viewgroups, admingroups directly in Web. config, or you can add viewgroups, admingroups separately in each system monitoring JSON configuration file:
"viewgroups":"*","admingroups":"sysadmins","User":"User","Password":"Pass","AdminUser":"Adminuser","AdminPassword":"AdminPass",
Monitoring Configuration
Configuration monitoring place in the/config/directory, Stack Exchange provides a configuration example of the corresponding system, and if no system monitoring files are configured, the "No Configuration" warning is reported when browsing the Opserver page. In this case, for Redis, the monitoring configuration is as follows:
{ "allservers": { "name":" All", "instances": [ { "name":"Local Master", "Port":"6379" }, { "name":"Local slave1", "Port":"6380" }, { "name":"Local Master2", "Port":"6382" } ] }, "Servers": [ { "name":"127.0.0.1" } ]}
Deployment instance
Authentication configuration <securitysettings provider= "Alladmin" > Everyone is admin, open browser access, enter account admin, password admin:
You can see that there are 2 groups of instances, where 6380 is slave,6379 is master, and the shelf relationship can be clearly seen from the chart.
Example list:
Click on a single Redis instance to see it in.
Panel Properties
The properties of the panel display are available through the Redis Info command, and the opserver is displayed more clearly.
Ops (/sec) per second processing capacity
Memory (used) is Used_memory_rss (used_memory)
Used_memory_rss : Returns the total amount of memory allocated by Redis (commonly known as the resident set size) from the operating system's perspective. This value is consistent with the output of commands such as top and PS .
used_memory_peak : Peak memory consumption (in bytes) for Redis
used_memory : Total amount of memory allocated by the Redis allocator, in bytes (byte)
Summary is the overall overview section.
Memory usage is important .
Persistence are the state of the RDB and aof. Keyspace key stored in the case, analyze in to see the detailed distribution. Stats client Command key hit rate and processing amount clients see which IP (or machine name) come over the number of connections, it is convenient to locate the application end of the machine for a long time not to release the connection,Important。
The command log that is accepted by the slow command log server.
Summarize
Opserver is a relatively lightweight monitoring system, deployment changes are very convenient, such as increasing the number of connections or memory alarm function.
Redis Series (v) Monitoring of-opserver