2 lines
4.2 KiB
JavaScript
2 lines
4.2 KiB
JavaScript
import{_ as e,o as t,c as o,R as i}from"./chunks/framework.1625126e.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/services.md","filePath":"en_US/guide/services.md","lastUpdated":1694095078000}'),n={name:"en_US/guide/services.md"},a=i('<p><strong>Service area is a function setting area for setting up Agents to monitor external websites or servers</strong><br><strong>The monitoring results can be viewed on the "Services" page in the home page</strong><br></p><h2 id="how-to-use" tabindex="-1">How to use <a class="header-anchor" href="#how-to-use" aria-label="Permalink to "How to use""></a></h2><p>To add a new monitor, you can go to the "Services" page in the administration panel and click "Add Service Monitor".</p><p>To add a service monitor, you need to complete the following settings:</p><ul><li><p><code>Name</code> - Customize a name</p></li><li><p><code>Type</code> - Select a monitoring type. Nezha currently supports three monitoring types: "HTTP-GET", "ICMP-Ping" and "TCP-Ping".</p></li><li><p><code>Target</code> - Depending on the type you choose, the target is set in different ways</p></li></ul><blockquote><ul><li><code>HTTP-GET</code>: Selecting this type, you should enter a URL as the target, the URL should be added with <code>http://</code> or <code>https://</code> <strong>If your target URL is <code>https://</code>, it will also monitor the SSL certificate of that URL and trigger a notification when the SSL certificate expires or changes.</strong><br> For example: <a href="https://example.com" target="_blank" rel="noreferrer">https://example.com</a></li></ul></blockquote><blockquote><ul><li><code>ICMP-Ping</code>: When selecting this type, you should enter a domain name or IP without a port number<br> For example: 1.1.1.1 or example.com</li></ul></blockquote><blockquote><ul><li><code>TCP-Ping</code>: When selecting this type, you should enter a domain name or IP and include the port number<br> For example: 1.1.1.1:80 or example.com:22</li></ul></blockquote><ul><li><p><code>Interval</code>： Sets the time interval in seconds between each time Agent sends requests to the target</p></li><li><p><code>Coverage</code>： Select a rule to determine which Agents to use to send requests to the target</p></li><li><p><code>Specific Servers</code>： Use with coverage to select the Agent to be excluded from the rule</p></li><li><p><code>Notification Group</code>： Select the notification method you have set up on the "Notification" page. <a href="/en_US/guide/notifications.html#flexible-notification-methods">Click here</a> for more information</p></li><li><p><code>Enable Failure Notification</code>： Select whether to receive target failure notifications as needed, default is inactive</p></li></ul><p>After setting, click "Add" and you are done.<br> Wait for a moment to go to the "Services" page on the home page to view the monitoring results<br><br></p><h2 id="notification-of-delay-changes" tabindex="-1">Notification of delay changes <a class="header-anchor" href="#notification-of-delay-changes" aria-label="Permalink to "Notification of delay changes""></a></h2><p>Nezha Monitoring monitors and statistics the delay between the Agent and the target server, and sends notifications in case of significant changes<br> Use this feature to help you monitor your server's routes for changes</p><ul><li><code>Enable delay notifications</code>：When enabled, notifications will be sent when the Agent to target server delay is higher than the <code>Max delay</code> or lower than the <code>Min delay</code><br><br></li></ul><h2 id="management-monitor" tabindex="-1">Management Monitor <a class="header-anchor" href="#management-monitor" aria-label="Permalink to "Management Monitor""></a></h2><p>To manage existing service monitoring, you can go to the "Services" page in the administration panel<br> Select a monitoring configuration and click the icon on the right to edit or delete it</p>',15),r=[a];function c(s,l,d,h,u,p){return t(),o("div",null,r)}const f=e(n,[["render",c]]);export{m as __pageData,f as default};
|