Difference between revisions of "Template:Networking rutos manual events reporting"
(3 intermediate revisions by 2 users not shown) | |||
Line 77: | Line 77: | ||
<li><i>LAN3</i></li> | <li><i>LAN3</i></li> | ||
<li><i>LAN4</i></li> | <li><i>LAN4</i></li> | ||
− | <li><i>WAN</i></li>| RUT2 | RUT2M | RUT36X | TCR1 | TRB1 | TRB2 | TRB5 = | + | <li><i>WAN</i></li>| RUT2 | RUT2M | RUT36X | TCR1 | TRB1 | TRB2 | TRB2M | TRB5 = |
<li><i>LAN1</i></li> | <li><i>LAN1</i></li> | ||
<li><i>WAN</i></li>| RUT9 | RUT9M = | <li><i>WAN</i></li>| RUT9 | RUT9M = | ||
Line 107: | Line 107: | ||
<ul> | <ul> | ||
<li><i>Device startup completed</i></li> | <li><i>Device startup completed</i></li> | ||
+ | <li><i>After unexpected shutdown</i></li> | ||
</ul> | </ul> | ||
</td> | </td> | ||
Line 153: | Line 154: | ||
</tr>{{#ifeq: {{{eth}}} | 1 | | </tr>{{#ifeq: {{{eth}}} | 1 | | ||
<tr> | <tr> | ||
− | <td><b>Topology | + | <td><b>Topology changes</b></td> |
<td>Informs on changes to the device's network topology. Possible triggers are: | <td>Informs on changes to the device's network topology. Possible triggers are: | ||
<ul> | <ul> | ||
Line 190: | Line 191: | ||
</td> | </td> | ||
</tr>|}} | </tr>|}} | ||
+ | <tr> | ||
+ | <td><b>FOTA</b></td> | ||
+ | <td>Informs about a new Firmware update. Possible triggers are: | ||
+ | <ul> | ||
+ | <li><i>Firmware update is now available</i></li> | ||
+ | </ul> | ||
+ | </td> | ||
+ | </tr> | ||
</table> | </table> | ||
Line 218: | Line 227: | ||
<tr> | <tr> | ||
<td>Event type</td> | <td>Event type</td> | ||
− | <td>Config change {{!}} New DHCP client {{!}} Startup {{!}} Mobile data {{!}} SMS {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{simswitch}}}|1|{{!}} Sim witch|}}{{#ifeq:{{{wifi}}}|1|{{!}} New WiFi client|}}{{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover|}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}; default: <b>Config change</b></td> | + | <td>Config change {{!}} New DHCP client {{!}} Startup {{!}} Mobile data {{!}} SMS {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{simswitch}}}|1|{{!}} Sim witch|}}{{#ifeq:{{{wifi}}}|1|{{!}} New WiFi client|}}{{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover|}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}} {{!}} FOTA; default: <b>Config change</b></td> |
<td>Event that will trigger the rule.</td> | <td>Event that will trigger the rule.</td> | ||
</tr> | </tr> | ||
Line 279: | Line 288: | ||
<tr> | <tr> | ||
<td>Event type</td> | <td>Event type</td> | ||
− | <td>Config change {{!}} Startup {{!}} New DHCP client {{#ifeq:{{{mobile}}}|1|{{!}} Mobile data {{!}} SMS {{!}} Signal Strength {{!}}|{{!}}}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}{{#ifeq:{{{wifi}}}|1|{{!}} New WiFi client|}}{{#ifeq:{{{simswitch}}}|1|{{!}} Sim switch|}}; default: <b>Config change</b></td> | + | <td>Config change {{!}} Startup {{!}} New DHCP client {{#ifeq:{{{mobile}}}|1|{{!}} Mobile data {{!}} SMS {{!}} Signal Strength {{!}}|{{!}}}} Reboot {{!}} SSH {{!}} WebUI {{#ifeq:{{{eth}}}|1|{{!}} Ports state {{!}} Topology changes |}}{{#ifeq:{{{failover}}}|1|{{!}} WAN Failover |}}{{#ifeq:{{{gps}}}|1|{{!}} GPS|}}{{#ifeq:{{{wifi}}}|1|{{!}} New WiFi client|}}{{#ifeq:{{{simswitch}}}|1|{{!}} Sim switch|}} {{!}} FOTA; default: <b>Config change</b></td> |
<td>Event that will trigger the rule.</td> | <td>Event that will trigger the rule.</td> | ||
</tr> | </tr> |
Latest revision as of 11:11, 26 August 2024
The information in this page is updated in accordance with firmware version .
Summary
The Events Reporting feature provides the possibility to configure rules that inform via SMS or email when certain trigger events occur.
This page is an overview of the Events Reporting section for {{{name}}} devices.
Events Reporting Rules
The Events Reporting Rules section is used to manage existing Events Reporting rules and to add new ones. Events Reporting Rules trigger on certain, user specified events and send an SMS message or email to a specified number informing of the occurred event.
All possible trigger events are listed in the table below.
Event | Event subtype |
---|---|
Config change | Informs on changes to the device's configuration. Possible triggers are:
|
New DHCP client | Informs on new DHCP lease give outs. Possible triggers are:
|
Reboot | Informs after device reboot occurrences. Possible triggers are:
|
Startup | Informs when device startup completed. Possible triggers are:
|
SSH | Informs on successful or unsuccessful SSH login attempts. Possible triggers are:
|
WebUI | Informs on successful or unsuccessful HTTP/HTTPS login attempts. Possible triggers are:
|
FOTA | Informs about a new Firmware update. Possible triggers are:
|
Events Reporting Configuration
The Events Reporting Rules list is empty by default. Before you can begin configuration you must add at least one new rule. This can be done by clicking the 'Add' button:
After adding a rule you should be redirected to its configuration page.
Send email
When an Events Reporting rule is configured to send emails, the device (this {{{name}}}) will connect to an existing email account when a user specified trigger event occurs and send an email to another email address informing of the occurred event.
In order to send emails, the device requires access to an existing email account. You can configure email accounts in the System → Administration → [[{{{name}}} Administration#Recipients|Recipients]] page. Allowing access to less secure apps may be required for some email service providers.
[[File:Networking_rutos_manual_events_reporting_events_reporting_rules_send_email_dual_modem_{{{dualmodem}}}_v1.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: on | Turns the rule on or off. |
Event type | Config change | Startup | New DHCP client | Reboot | SSH | WebUI | FOTA; default: Config change | Event that will trigger the rule. |
Event subtype | Varies | More specific event type that will trigger the rule. |
Action | Send email; default: Send email | Selects the method of reporting on the specified event. |
Subject | string; default: none | Subject of the sent email. |
Message text on Event | string; default: Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts; | Text to be included in the body of the report email. |
Email account | email account; default: none | The account that will be used to send an email. |
Recipient's email address | email address; default: none | Email address of the recipient. |
Send test email | - (interactive button) | Sends an email based on the current configuration. This is used to test whether the configuration works as intended. |
[[Category:{{{name}}} Services section]]