Scheduling Advanced Analytics Dashboards

Users can schedule Personal, Group, or Netskope Library dashboards as well as widgets. In addition, schedule owners can manage (view / edit) their own schedules in their Personal, Group, or Netskope Library folders. However, if you are not the schedule owner, you may see a report listed in a schedule but you cannot view or edit the report. If you click the report link, the system displays an error message. 

Report Admins can view all scheduled reports listed in their Personal, Group, or Netskope folders.

Navigate to Advanced Analytics > Folders > Scheduled to view all scheduled dashboards and widgets.

The list view page displays the following information:

Click the ellipses at the end of a dashboard name to view and manage the schedule.

The delete option is only available for the schedule owner. Deleting a schedule does not delete the report.

In addition, a deactivated user’s schedule is removed automatically from any scheduled dashboards. If all recipients unsubscribe from a scheduled email delivery, that schedule is deleted from the Scheduled list view page.

Admins can view details for the scheduled dashboard or widget such as create date, description, and activities.

You can filter a time range and one or more activities associated with the dashboard or widget. Activities include:

Scheduling Conditional Widgets

For recurring deliveries of widgets, you can customize the schedule to deliver the widget content only when certain conditions are met. For example, you can schedule a daily report to only send if users trigger the ‘shared credentials’ alert in the last 24 hours by selecting the option ‘send this schedule if there are results’ option.

In the Advanced options >  Send this schedule if dropdown, specify whether you want to deliver the widget content only if there are results, only if there are no results, or if there are either results or no results. For example, you can user filters to create conditions for situations you want to monitor and then deliver the content only if that condition is reached.

You can also specify there to be a delivery only if the query results have changed since the last data delivery was sent by checking the box next to and results changed since last run.

Limit

You can limit the size of your delivery by selecting one of the following limit options for your data:

• Results in Table: Data is sent as a single delivery.

• All Results: Data is streamed. This is useful for large datasets, as it bypasses file-size, browser, and memory limitations.

If you choose Results in Table, the system will respect the row limitations you’ve set up in the saved widget or the Explore. If you choose All Results, the system will return all the rows of the query, regardless of any saved widget settings, and regardless of system’s typical 5,000 row limit. This can be desirable for retrieving very large datasets, but you should use caution to ensure the query is not too large for your database. See guidelines in the Advanced Analytics General Guidelines section below.

Limit Options for Email

When sending widgets and Explores, you can limit the size of your email to stay within your email server’s message size limitations. Select one of the following limit options for your data:

• Results in Table: Data is sent with a 5,000 row limit. This is the only choice available for emails using the Data Table or Visualization options. Emails with over 5,000 rows will not be sent.

• All Results: If you are using the Text, CSV, JSON — Simple, XLSX, or HTML options, you can send all of the rows of the results of a saved widget. This option ignores any limits set on a saved widget or the typical 5,000 row limit. There is, however, a total data limit of 15 MB so that email applications will accept the attachment. Emails over 15 MB with an attachment will not be sent. If you specify a Data Table or Visualization format and then select All Results, the system automatically changes the format to use a text attachment to support sending all results.

To verify that you are within the row or data limit for scheduled emails, you can enter your own email address as the recipient and click Send Test to send the data to yourself immediately. If you do not receive the email, it is likely that you have reached the row limit or the data limit for emails.

Advanced Analytics General Guidelines

Before using Netskope Advanced Analytics consider the following key takeaways. These general guidelines and tips will help you create, run, and export efficient dashboards. To learn more: Advanced Analytics Best Practices

For Each Dashboard

• No hard limit for the number of widgets, but it is strongly recommended to create less than 15 widgets per dashboard.

For Each Widget in the Dashboard

• Supports up to 5000 rows and 200 columns for pivoted or unpivoted query results.
• For browser performance, 20 or fewer columns is recommended.

For Each Backend Query Triggered from Explore, Widgets, or Dashboards (including scheduled and non-scheduled reports)

• No guarantee for the data processing time. The more data you request, the longer the data processing time may take.
• The data enrichments, such as (but not limited to) RBAC control, user group information lookup, geolocation lookup, and application information (e.g., CCI, CCL), also introduce additional backend query processing time.

For Generated Reports

• Supports up to 15MB. Query results exceeding 15 MB cannot be delivered to scheduled or ad-hoc report recipients.
• The All Results option is not guaranteed to be available in all cases. Even when it is available, use it cautiously when downloading or scheduling a report with all results. Some queries can generate very large datasets, potentially containing thousands or even millions of rows, which may exceed the limits of most spreadsheet programs.

Optimize Data Volume for Performance

• Start with the minimum number of fields required for your analysis.
• Apply filters to reduce the size of query results.
• Adjust your Netskope product policies to capture only the events needed attention or auditing.

Adopt a Coarse-to-Fine Strategy for Widgets

• When designing widgets, begin with high-level fields to provide an overview of the data. Avoid using overly detailed fields such as URL, referrer, or object name, as these can obscure key insights.

Effectively Group Data

• For numeric-type and timestamp-type fields, always use the coarsest granularity that meets your needs. For example, use timestamp-type fields such as monthly, weekly, or daily timestamps, rather than second-level precision unless you really need it.

Limit Columns in Table Views

• When creating table view widgets, keep the number of columns below 20, whether they are pivot columns or selected fields, to ensure optimal performance and usability.

Data Enrichments take cost

• While filtering data by user group, RBAC, or geolocation can reduce query result sizes, retrieving and joining such information introduces additional overhead for data processing. Advanced features, such as merged results, custom fields, and table calculations introduce additional data processing overhead as well. Balance enrichment needs against performance considerations.
• Use Advanced Analytics as an analytical tool, rather than a raw data exporter.

Advanced Features

Advanced features, such as merged results, custom fields, and table calculations, consume more backend resources and significantly increase its data processing time. The more post-query processing features used, the more time needed for the dashboard load.