Print Download PDF Send Feedback

Previous

Next

Using the Log View

In SmartConsole:

  1. Go to Logs and Monitoring > View.
  2. Click New, and select New View.
  3. In the New View window, enter:
    • Name
    • Category – For example, select Access Control
    • Description (optional)
  4. In the new window that opens, create a query. Click Options > View Filter and select blade and app control.
  5. Click Add Widget to customize how you see the data that comes back from the query.

    Start with a Timeline of all events.

    In Table, you can create a table that contains multiple fields such as user, application name, and the amount of traffic. There are more widgets you can use: map, infographic, rich text, chart, and container (for multiple widgets).

    After you save the dashboard (done), you can schedule and get an automatic email at multiple intervals.

This is an example of the Log view.

SmartConsole_logs_GUI

Item

Description

1

Queries - Predefined and favorite search queries.

2

Time Period - Search with predefined custom time periods.

3

Query search bar - Define custom queries in this field. You can use the GUI tools or manually enter query criteria. Shows the query definition for the most recent query.

4

Log statistics pane - Shows top results of the most recent query.

5

Results pane - Shows log entries for the most recent query.

Viewing Threat Prevention Rule Logs

To see logs generated by a specified rule:

  1. In SmartConsole, go to the Security Policies view.
  2. In the Threat Prevention Policy, select a rule.
  3. In the bottom pane, click one of these tabs to see:
    • Summary - Rule name, rule action, rule creation information, and the hit count. Add custom information about the rule.
    • Logs - Log entries according to specified filter criteria - Source, Destination, Blade, Action, Service, Port, Source Port, Rule (Current rule is the default), Origin, User, or Other Fields.

Predefined Queries

The Logs & Monitor Logs tab provide a set of predefined queries, which are appropriate for many scenarios.

Queries are organized by combinations of event properties, for example: