Auth Network Monitor
Elevate network monitoring with real-time, quantum-ready, HTTP, ICMP, DNS, SMTP checks, this tool alerts you 24/7.
Elevate network monitoring with real-time, quantum-ready, HTTP, ICMP, DNS, SMTP checks. This plugin provides an interface to the free network monitor API services, allowing users to add hosts to monitor, edit host configuration, and reset alerts. With this plugin, users can easily manage their network monitoring needs without the need to make direct API calls. Alerts can be customized and users will receive email notifications for any down events. The plugin also offers detailed response and status information for each monitored host. Stay on top of your network's health with this powerful monitoring tool!
How to
Comments (0)
API docs
Learn how to use Auth Network Monitor effectively! Here are a few example prompts, tips, and the documentation of available commands.
Example prompts
-
Prompt 1: "I want to monitor a website and receive alerts when it goes down."
-
Prompt 2: "How can I edit the configuration for a monitored host?"
-
Prompt 3: "I want to delete a host from my monitoring list."
-
Prompt 4: "Can you help me reset the alerts for a specific host?"
-
Prompt 5: "What are the response times and statuses for a host in the last 24 hours?"
Features and commands
| Feature/Command | Description |
|---|---|
AddHostGPTAuth | This command allows you to add a new host to monitor. You need to provide the host address and endpoint type. |
EditHostGPTAuth | This command allows you to edit the configuration of a monitored host. You need to provide the host address to edit, and any other fields you want to update. |
ResetAlert | This command resets the alert for a specific host. You need to provide the host ID. |
ResetAllAlertsForUser | This command resets all alerts for all hosts for the authorized user. |
GetMonitorIPsWithFilterAuth | This command retrieves a filtered list of host configurations (MonitorIPs) for the authorized user. You can filter the results based on various parameters like address, port, endpoint type, and more. |
GetMonitorIPsFromUserID | This command retrieves a list of host configurations (MonitorIPs) for the authorized user. |
GetDataSets | This command retrieves a list of all data sets. Each data set represents data for a time range of 6 hours. |
GetDataSetsByDateGPT | This command retrieves a list of data sets for a given date range. You need to provide the start and end datetime. |
GetPingInfosByMonitorPingInfoIDAuth | This command retrieves a detailed list of response times and statuses (PingInfos) for a specific host. You need to provide the MonitorPingInfoID. |
GetPingInfosByDateRangeAuth | This command retrieves detailed response times and status (PingInfo) data for a given date range and MonitorPingInfoID. You need to provide the start and end datetime. |
GetMonitorPingInfosByDataSetIDAuth | This command retrieves a list of summary monitoring data (MonitorPingInfos) for a given DataSetId. The user must be authorized. |
GetMonitorPingInfosByHostAddressAuth | This command retrieves a list of summary monitoring data (MonitorPingInfos) for a given host address. You can filter the results using MonitorPingInfoQuery. |
For AI
NameauthNetworkMonitor
DescriptionYou will be providing the user experience to interface with the free network monitor API services. With these network monitor services, you can add hosts to monitor, edit host configuration, and reset alerts sent for that host. You will make all the API calls on behalf of the user without giving them the function call details. If a user wants to monitor a host, ask them for a host address and endpoint type. If the user wants to edit a host, ask them for the host address to edit; you can use this to lookup the host id if necessary. If the user wants to delete a host then edit the host and set hidden=true, this can not be undone so warn the user of this. They can disabled host monitoring without deleting by setting enabled=false. If a user wants to reset an alert, then again you can lookup the host id to perform this action for the user. The data structure of the backend is: There is a set of data sets (DataSet). Each data set represents data for a time range, typically 6 hours. Within each data set, there will be a list of hosts that have been configured to be monitored; each one is called a MonitorPingInfo. The response times and detailed data are recorded within each MonitorPingInfo as MonitorPingInfo.PingInfos. The Current status of each MonitorPingInfo is stored in MonitorPingInfo.MonitorStatus. So in summary, MonitorPingInfo is the host config and statistics for that host within the time range of the data set. MonitorPingInfo.PingInfos is the response times for all monitor events within that MonitorPingInfo. MonitorPingInfo.MonitorStatus contains the number of down events since the last alert reset, whether an alert has been raised, whether an alert has been sent, The last or latest event status. In order to help the user if they ask for detail response or status then quering PingInfos gives the most detail. If they want summary information MonitorPingInfo and MonitorPingInfo.Status is useful. Look out for long list of data and paginated where the api allows. When a host is flagged as down the user will receive an email giving information about this event. The user does not need to provide an email address as the email address they use to login to the plugin will be used. A users email address must be verfied to receive email alerts. Ask the user to check spam folder as this may prevent them from receving alerts. If it is a gmail address then verfication is not necessary but being flagged as spam could be a problem.
Updates
First added25 August 2023