The All Events page displays an overall, consolidated, high‐level view of your network environment. You can view all types of events that are being logged in your SRX platform. You can view abnormal events, attacks, viruses, spam attacks when log data is correlated and analyzed. This page provides you with an advanced filtering mechanism and visibility into actual events.
Note
For the events to be logged, registered, and displayed in the graph, the device should be in stream mode. You can configure stream mode in the Configure > Device Setup > Basic Settings > Logging page.
Starting in Junos OS Release 19.1R1, All Events option is available for logical system users.
To monitor all events, select Monitor>Events>All Events in the J-Web user interface.
Time Range graph displays the trend of all events or flow for all the events that has transpired in the device.
You can specify the duration of time for which you want to view the trend for all events. The available options are 30m, 1h, 2h,… and so on, which are displayed at the top right hand side of the page. For example, if you choose 30m, the end time is the current system time and the start time is the preceding 30 minutes from the current system time.
Click Custom to specify a customized time range. The Custom Time Range Selection popup window is presented. You can set the from and to date and time, and click OK to set the time range.
To refresh the graph on demand, click the refresh button.
You can also drag the slider in the Time Range graph from the extreme left or right of the graph and set the time range to see the trend or flow of events that has transpired in that time range.
Table 1 summarizes key output fields in the All Events page.
Table 1: Events Monitoring Page
Field | Value | Additional Information |
---|---|---|
Chart View—Displays the trend analysis, displayed in the Time Range graph, in numbers. | ||
Total Events | Displays the total number of events that occurred in the specified time range. | - |
Virus Instances | Displays the number of virus instances that occurred in the specified time range. | - |
Attacks | Displays the number of IDP or IPS attacks that occurred in the specified time range. | - |
Interface Down | Displays the total number of interfaces that are down. | - |
Sessions | Displays the total number of firewall events or sessions that occurred during the time period specified in the Time Range graph. | - |
Graphs Firewall Web Filtering IPSec VPNs Content Filtering Antispam Antivirus IPS | The graphs display the trend analysis in swim lane chart for the time range that you specified in the Time Range graph. The legend in each graph shows the colors and its related interpretation. For example, in the Firewall graph, blue color represents all firewall events and black represents blocked firewall events. Similarly, in the IPS graph, orange, amber, and yellow represent critical, high, and medium IPS attacks respectively. | Mouse over at any point in the swim lane chart to view further details at that point. |
Grid View—Displays information in grids that are lazy loaded with infinite scrolling. You can narrow down your search to a particular event based on IP address, description, or attack name. | ||
Filters:The dropdown filters that are displayed above the grids. First dropdown filter | Options available in the first filter dropdown are: Firewall, Webfilter, ContentFilter, Antispam, Antivirus, Ipsecvpn, and IPS. | Select the event that you want to filter in the first dropdown filter. |
Second dropdown filter | Options available in the second filter dropdown are: event-name, source-address, destination-address, application, user, service, policy, nested-application, source-interface, and source-zone. | Select the next criteria of the event on which you want to filter from the second dropdown filter. |
Text box | Displays the filter parameter that you selected from the second filter dropdown. Note: In the filter statement the following limitation exists.
For example, if you have used & operator and the parameter event-name once, I cannot use them again in the same filter statement CORRECT USAGE: event name = rt_flow_session_close & application=TELNET WRONG USAGE:event name=rt_flow_session_close & event-name = rt_flow_session_create WRONG USAGE:event name = rt_flow_session_close & source-address=x.x.x.x & application=TELNET Note: The filter statement is NOT case-sensitive. | Add the parameter for which you want to filter. For example, in the first dropdown if you selected Firewall as the event filter and in the second filter dropdown you selected event-name as the parameter, then the text box displays event-name = . If you add rt_flow_session_closeto see only Firewall events then the text box displays event name = rt_flow_session_close. |
Go | Executes the filter statement that is displayed in the text box. | Click Go. |
X | Clears the filters. | Click x. |
Show Hide Column Filter icon represented by three vertical dots | Enables you to show or hide a column in the grid. |
Table 2 describes the grid elements that are displayed in the Detailed View.
Table 2: All Events - Grid Elements in Detailed View
Grid Element | Description |
---|---|
Threat Severity | The severity level of the threat. |
Event Name | The event name of the log. |
Description | The description of the log. |
Attack Name | Attack name of the log: Trojan, worm, virus, and so on. |
UTM Category or Virus Name | The UTM category of the log. |
Event Category | The event category of the log. |
Source IP | The source IP address from where the event occurred. |
Source Port | The source port of the event. |
Destination IP | The destination IP address of the event. |
Destination Port | The destination port of the event. |
Application | The application name from which the events or logs are generated. Note: Starting in Junos OS Release 19.2R1, you can see that an application displays the same value as a nested application (if the application supports nested application). |
User Name | The username from whom the log is generated. |
Hostname | The host name in the log. |
Service Name | The name of the application service. For example, FTP, HTTP, SSH, and so on. |
Protocol ID | The protocol ID in the log. |
Policy Name | Policy name in the log. |
SourceZone | User traffic received from the zone. |
Destination Zone | The destination zone of the log. |
Nested Application | The nested application in the log. Note: Starting in Junos OS Release 19.2R1, you can see that an application displays the same value as a nested application (if the application supports nested application). |
Roles | Role names associated with the event. |
Reason | The reason for the log generation. For example, a connection tear down may have an associated reason such as authentication failed. |
NAT Source Port | The translated source port. |
NAT Destination Port | The translated destination port. |
NAT Source Rule Name | The NAT source rule name. |
NAT Destination Rule Name | The NAT destination rule name. |
NAT Source IP | The translated (or natted) source IP address. It can contain IPv4 or IPv6 addresses. |
NAT Destination IP | The translated (also called natted) destination IP address. |
Traffic Session ID | The traffic session ID of the log. |
URL | Accessed URL name that triggered the event. |
Object Name | The object name of the log. |
Path Name | The path name of the log. |
Logical System Name | The name of the logical system. |
Rule Name | The rule name of the log. |
Action | Action taken for the event: warning, allow, and block. |
Time | The time when the log was received. |