<p>ARGUS, Ping An&nbsp;Cloud monitoring services, targets businesses in which a small number of people operate a large number of machines. When ARGUS is configured with alarms, a template is used. You can configure a template for each type of application and associate the template with a specific host. To adjust an alarm strategy, you can modify the strategy in the template.</p>


<p><strong>Flexible and easy-to-use: </strong></p> <p>After login, you can directly view the metrics of each resource.</p> <p>Based on their own business requirements, users can configure the monitoring chart of multiple instances on one page to facilitate business inspection.</p> <p><strong>Natural integration:</strong></p> <p>A cloud host can be delivered in 1-2 minutes. You can also get more hosts with the same configuration through clone technology, so as to save deployment time.</p> <p><strong>Flexible alarm: </strong></p> <p>Users can set alarm rules for metrics. Alarm management is based on templates. Users can modify a number of machines&#39; alarm strategies in batches.</p>


<p><strong>1.&nbsp;&nbsp;&nbsp; </strong><strong>Product monitoring </strong></p> <p>1.1&nbsp;&nbsp; Host monitoring</p> <p>During system initialization, an agent will be installed on the machine to collect performance data. The agent can automatically collect data of CPU, memory, disk, network traffic and other machine performance metrics. Users can view the host&#39;s performance data to facilitate operation, maintenance and fault location.</p> <p>1.2&nbsp;&nbsp; ELB monitoring</p> <p>After an ELB instance is created, inbound and outbound traffic of each port and other metrics will be collected from the load balancer. Users can view the metrics on their own ELB instance on the page.</p> <p>1.3&nbsp;&nbsp; Network quality monitoring</p> <p>After a network quality monitoring task is created and monitoring starts, the performance data will be submitted to the monitoring system. Users can view their testing tasks, network latency, packet loss rate and other metrics by region or carrier.</p> <p>1.4&nbsp;&nbsp; Database monitoring</p> <p>After a database instance is created, the database management program will collect metrics of the database instance and submit them to the monitoring system. Users can view the metrics of their own database instance.</p> <p><strong>2.&nbsp;&nbsp;&nbsp; </strong><strong>Alarm template management</strong></p> <p>Users can configure an alarm template for each of their own business modules. All machines of this module are associated with this alarm template. If the module is expanded, the new machine will be associated with this template. Adjustments of alarm strategies can be made by editing the alarm template.</p> <p><strong>&nbsp;</strong></p> <p><strong>3.&nbsp;&nbsp;&nbsp; </strong><strong>Receiver group management </strong></p> <p>The receiver group is used for alarm notification. Generally the group consists of persons in charge of each business. Based on priority of the alarm, there will be different notification methods (telephone, SMS, e-mail etc.)</p> <p><strong>4.&nbsp;&nbsp;&nbsp; </strong><strong>Dashboard</strong></p> <p>The dashboard is mainly used for users&#39; business inspection. Persons in charge of business can put the resources used in this business into a dashboard, which enables real-time view of performance data and trends over the past period. In this way, the operation and maintenance staff can learn about business trends and whether there&#39;s a need for expansion.</p>

Terms and Descriptions

<table border="1" cellpadding="0" cellspacing="0"> <tbody> <tr> <td> <p><strong>Terms</strong></p> </td> <td style="vertical-align:top"> <p><strong>Description</strong></p> </td> </tr> <tr> <td> <p>Dashboard</p> </td> <td style="vertical-align:top"> <p>Based on their own business requirements, users can configure the performance metrics of multiple instances on a chart to facilitate business inspection.</p> </td> </tr> <tr> <td> <p>dashboard group</p> </td> <td style="vertical-align:top"> <p>Users can divide self-defined dashboards into several groups, one of which may contain multiple dashboards.&nbsp;</p> </td> </tr> <tr> <td> <p>graph</p> </td> <td style="vertical-align:top"> <p>A dashboard is composed of multiple graphs.</p> </td> </tr> <tr> <td> <p>metric</p> </td> <td style="vertical-align:top"> <p>Monitoring indicators such as cpu usage, memory usage and disk load.</p> </td> </tr> <tr> <td> <p>Tag</p> </td> <td style="vertical-align:top"> <p>Used to supplement metrics, e.g. df.bytes.used</p> <p>(disk usage) needs to have two tags. One is mount (mount point), and the other is fstype (file system type).</p> </td> </tr> <tr> <td> <p>priority</p> </td> <td style="vertical-align:top"> <p>Define the severity of alarms, currently being divided into 6 levels (P1-P6).</p> <p>&nbsp;P1: fatal, 2: less fatal, 3: critical, P4: less critical, P5: warning, 6: info</p> </td> </tr> <tr> <td> <p>strategy</p> </td> <td style="vertical-align:top"> <p>Description of an alarm condition; for example, you can configure this strategy: an alarm will be given when cpu usage exceeds 90% for 5 minutes in a row, max alarming time is 3, and the priority is P3.</p> </td> </tr> <tr> <td> <p>Template</p> </td> <td style="vertical-align:top"> <p>Alarm template, a collection of multiple alarm strategies and receiver group information.</p> </td> </tr> <tr> <td> <p>User</p> </td> <td style="vertical-align:top"> <p>Alarm receivers, with their name, mobile phone number, e-mail address and other information.</p> </td> </tr> <tr> <td> <p>Receiver group</p> </td> <td style="vertical-align:top"> <p>A set includes multiple alarm receivers that can be heads of business.</p> </td> </tr> </tbody> </table>
Did the above content solve your problem? Yes No
Please complete information!

Call us


Email us


Online customer service

Instant reply

Technical Support

cloud products