Sending Email and SMS Notifications for Incidents

When you set actions for an incident notification, one option is to send an email or SMS message to groups or individuals, and you also have an option to specify a template that should be used in the email.

Prerequisites

Procedure

Related Links

Prerequisites

Make sure the email gateway has been configured for your deployment.

You should also have set up any email templates that you want to use for notifications.

Procedure

1. Log in to your Supervisor node.
2. Go to Analytics > Incident Notification Policy.
3. Select the policy that you want to set up the email or SMS notification for.
4. Under Actions, next to the email/sms notification table, click … .
5. For multi-tenant deployments, select the Organization that contains the individuals or groups you want notified.

Under Folders, you will see the user groups for that organization listed.

6. In the Folders pane, select a group.

In the Items pane, you will see a list of users for that group.

7. Select a group and click Folder >> to add a group to the Notification Actions list, or select individual users and click Items >>.
8. Under Notification Actions, select the Method, Email or SMS, that you want to use sending the notification.
9. Select an Email Template if you are sending an email notification. If you leave this blank, the default email template will be used.

Related Links

Setting Up the Email Gateway

Setting Scripts as Notification Actions

Customizing Email Templates for Notifications

Email templates for incident notifications are based on incident variables that you put into the subject and body of the template, which are then populated with the actual attribute values in the incident.

Incident Attribute Variables

Example Email Template

Template

Generated Email

Creating an Email Template

Incident Attribute Variables

These are the incident attribute variables you can use for your email template.

$organization

$status

$hostName

$incidentId

$incidentTime

$firstSeenTime

$lastSeenTime

$incident_severityCat

$incident_severity

$incident_incidentCount

$ruleName

$ruleDescription

$incident_source

$incident_target

$incident_detail

$affectedBizService

Example Email Template

This example first shows a template with the incident attribute variables, and then an email based on this template with the variables populated from an incident.

Template

Email Subject:

$ruleName was triggered at $incidentTime

Email Body:

The host, $incident_target, was being scanned by $incident_source starting at $firstSeenTime and ending at $lastSeenTime. There were $incident_incidentCount hits.

Please investigate and report as necessary.

Generated Email

Subject: Server Memory Warning was triggered at Jan 10 22:43 UTC

Body: The host, Host IP: 192.168.1.23 Host Name: QA-V-WIN03-ORCL, was being scanned by 10.1.1.1 starting at Jan 10 22:05 UTC and ending at Jan 10 22:11 UTC. There were 2 hits.

Please investigate and report as necessary.

Creating an Email Template

1. Log in to your Supervisor node.
2. Go to Admin > General Settings > Incident Email Templates.
3. Click Add.
4. For multi-tenant deployments, select the organization for which you are creating the email template.
5. Enter a Name for the template.
6. Enter the Email Subject and Email Body.

You can select attribute variables from the Insert Content menu to enter into your template, rather than having to type them out by hand.

 

7. Click OK.

be used. To set an email template as default, select the template in the list on the Incident Email Templates page, and then click Set as Default. For multi-tenant deployments, to select a template as default for an organization, first select the organization, then set the default email template for that organization.

 

 

 

 

Creating an Incident Notification Policy

Prerequisites

Make sure you have enabled the settings for sending email or other notification actions as described in Setting Up Routing Information for Reports and Incident Notifications.

You should read the introductory topic on incident notifications to understand how policy conditions are processed..

Procedure

1. Log in to your Supervisor node.
2. Go to Analytics > Incident Notification Policy.
3. Click New.
4. Select the Incident Severity.

Only incidents matching the severity level you select will trigger a notification.

5. For Rules, click … and select the rule or rules you want to trigger this notification.
6. Set a Time Range during which this notification will be in effect.

Notifications will be sent only if an incident occurs during the time range you set here.

7. For Affected Items, click … and use the CMDB Browser to select the devices or applications for which this policy should apply.

Instead of individual devices or groups, you can apply the notification policy to an IP address or range by clicking Add under IP/Range. You can also select a group, and then select the Not option to explicitly exclude that group of applications or devices from the notification policy.

8. For multi-tenant deployments, select the Organizations to which the notification policy should apply.

Notifications will be sent only if the triggering incidents affect the selected organization.

9. Select the Actions to take when the notification is triggered.

See the topics under Sending Email and SMS Notifications for Incidents, Creating Tickets In FortiSIEM In-built Ticketing System, Creatin g Inbound Policies for Updating Ticket Status from External Ticketing Systems, and Setting Scripts as Notification Actions for more information about notification actions.

10. Enter any Comments about the policy.
11. When you are finished creating the notification policy, select Enabled to make it active in your deployment.
12. Click Save.

Device Risk View of Incidents

Viewing Devices Sorted By Risk

1. Go to Incident tab
2. Set Group By to Host Risk Score.
3. Left pane shows Devices Sorted By Risk
4. Right pane shows incidents for the device selected in left panel

Calendar View of Incidents

The calendar view of incidents provides a summary view of the number of incidents that have occurred on a calendar day, grouped by severity. Clicking a group loads a summary of those incidents.

This screenshot shows the calendar view of incidents for the month of February 2015.

Fishbone View of Incidents

The fishbone view of incidents presents a view of networks and devices in those networks, along with the incidents triggered for those devices over the last 24. This view is derived from the Network Segments in the CMDB, with the devices associated with those segments overlaid. The numbers and colors for each device indicate the number and severity of incidents associated with that device.

Clicking on an incident  number will show you a summary of those incidents. Clicking on Last Seen, First Seen, Incident Name, or Incid ent Details in that summary will let you select Incident Details to view more information. Clicking on any IP addresses associated with the device will open a contextual menu that will let you find out more information about that device.

Clicking on an IP number or hostname in the fishbone view will let you view the Quick Info for that device, or you can select Topology to view it within the context of your network topology.

Hovering your mouse cursor over a device or incident number will show you the IP address and host name for that device, as well as the type of device.

This screenshot shows an example fishbone view of network segments, devices, and associated incidents.

Incident Notifications

The sending of notifications when an incident occurs is handled by Notification Policies, which you can see listed in the Analytics > Incident Notification Policies page. Instead of having notifications set for each rule, you can create a policy and have it apply to multiple rules.

When viewing the notification policies, think of  the columns on the page as representing a series of “If … and … then” statements that lead to the notification action. For example, you could read the table columns as a sentence:

“IF Incident Severity is X1 AND Rule is X2 AND Time Range is X3 AND Affected Items includes X4 AND Affected Organizations is X5, THEN take the actions specified in the ACTION column.”

When AccelOps evaluates whether a notification action should be triggered based on the notification conditions, it evaluates all notification policies, and will trigger the actions of all policies that meet the condition, instead of just the first policy that meets the conditions. This means that the order of policies in the list doesn’t matter, and that you can write policies with overlapping conditions that could also, for example, include different actions.

See also the topics under Incident Notification for more information about the methods that are available for sending notifications from AccelOps, including the AccelOps API.

Creating an Incident Notification Policy

Sending Email and SMS Notifications for Incidents

Customizing Email Templates for Notifications

Setting Scripts as Notification Actions

Example of a Windows Restart Script as a Notification Action Incident XML File Format

Viewing Incident Notification History

 

Using Group By Attributes to View Incidents

The Incident Dashboard presents a view of all incidents based on the filter conditions you select. However, there may be situations in which you want to view incidents grouped on incident attributes like Incident Source, Incident Target, Severity, or Incident Name. Once incidents are grouped by their attributes, you can view Incident Details for the entire group.

1. Log in to your Supervisor node.
2. Go to Incidents.
3. In the Group By menu, select the attributes you want to use to group the incidents, and then click Refresh.

The Incident Dashboard will refresh and display incidents grouped according to the attributes you selected, with a COUNT(Matched Events) column that indicates how many incidents are in each group.

4. Select a group and then click on it to open the Options
5. In the Options menu, select Show Incident Details for This Group.

The Incident Dashboard will refresh to show all incidents in the selected incident group, and you can use the Contextual Menus to find out more information about them.

Viewing and Searching Incidents

The Incident Dashboard displays incident information for your IT infrastructure based on the filter conditions you set. You can also view incidents grouped by incident attributes, use values in incident attributes to refine your searches, view information about rules that triggered incidents, and use incident information to create rule exceptions and event dropping rules.

List View of Incidents

Searching for Incidents by Incident Attributes

Using Group By Attributes to View Incidents

Device Risk View of Incidents

Calendar View of Incidents

Fishbone View of Incidents

List View of Incidents

There are two ways you can view the incidents that are occurring in your IT infrastructure.

The Incidents tab, shown in the screenshot for this topic, where you can view incidents and incident details

Dashboard > Incident Dashboard, which includes the same incident summary and user interface controls found in the Incidents tab, but which also provides other views of incidents, including a fishbone view of incidents in your infrastructure, a topology view with the number and severity of incidents overlaid on devices, a calendar view, and a location view that includes both a summary view of incident source and target IP locations and a map view, along with the number and severity of incidents for that location overlaid on the map.

In both locations you can filter the incidents in the dashboard, find out more information about sources and targets of incidents, customize the dashboard layout, and manage the rules associated with incidents.

Incident Attributes

Incident Dashboard User Interface Controls

Incident Dashboard Filter Controls

Incident Management Controls

Contextual Menus

Incident Details

Incident Details

Triggered Events

Related Incidents

Incident Attributes

An Incident has the following attributes.

Attribute Name	Description
Event Severity Category	The severity of the incident, High, Medium, or Low
Last Seen Time	The last time that the incident was triggered
First Seen Time	The first time that the incident was triggered
Incident Name	The name of the rule that triggered the incident
Incident ID	The unique ID assigned to the incident
Incident Source	The source IP or host name that triggered the incident
Incident Target	The IP or host name where the incident occurred
Incident Detail	Event attributes that triggered the incident
Status	The status of the incident, Active, Cleared, Cleared Manually, System Cleared
Cleared Reason	For manually cleared incidents, this displays the reason the incident was cleared
Cleared Time	The time an incident was cleared
Cleared User	The person who cleared the incident
Comments	Any comments that users have entered for the incident
Ticket Status	Status of any tickets associated with the incident
Ticket ID	The ID number of any tickets generated by the incident
Ticket User	The person assigned to any tickets generated by the event
External User	If the ticket was cleared in an external ticket-handling system, this lists the name of the person the ticket was assigned to
External Cleared Time	If the ticket was cleared in an external ticket-handling system, this lists the time it was cleared
External Resolved Time	If the ticket was resolved in an external ticket-handling system, this lists the time it was resolved
External Ticket ID	The ID of the incident in an external ticket-handling system
External Ticket State	The state of the incident ticket in an external ticket-handling system
External Ticket Type	The type assigned to the incident ticket in an external ticket-handling system
Organization	The organization reporting the event
Impacts	Organizations impacted by the event
Business Service	Business services impacted by the incident
Incident Notification Status	Status of any notifications that were sent because of the incident
Notification Recipients	Who received notification of the incident
Incident Count	How many times the incident has occurred during the selected time interval

Incident Dashboard User Interface Controls

This screenshot shows the Incidents tab with the major user interface controls outlined in red.

Incident Dashboard Filter Controls

The filter controls let you control which incidents are shown in the dashboard.

Filter Control	Description
Filter Criteria	You have three options for the filter conditions: ID Search for an incident by ID IP Search for an incident based on an IP address Advanced Use this option to set filter conditions based on event attributes as described in Creating a Structured Real Time Search. See Selecting Attributes for Structured Searches, Display Fields, and Rules for more information about using attributes in search filters.
Group By	Use these options to group incidents in the dashboards based on incident attributes. See Using Group By Attributes to View Incidents for more information.
Severity	Use these options to only see incidents with the selected severity level
Function	Use these options to view incidents related to a specific infrastructure functional area, such as Performance or Security.
Incident Status	Filter incidents to view according to their status
Ticket Status	Filter incidents based on the status of their associated tickets. See Creating Tickets In FortiSIEM In-built Ticketing System for more information.
Time Selection	Select the time interval during which incidents should have occurred. The default is Last 2 Hours.
Organization	For multi-tenant deployments, select the organization you want to view incidents for.
Impacts	For multi-tenant deployments, select an organization to view the incidents that are impacting it

Incident Management Controls

Filter Control	Description
Refresh	Refresh the dashboard view
Edit Rule	Edit the rule associated with the incident. See the topics under Rules for more information.
Exception	Create an exception to the rule associated with the incident. See Defining Rule Exceptions for more information.
Ticket	Create a ticket from the incident. See Creating Tickets In FortiSIEM In-built Ticketing System for more information.
History	View the ticket history associated with an incident.
Clear	Clear the incident. See Defining Clear Conditions for more information on how to set rule conditions that will automatically clear incidents. All non-security related incidents are cleared from the system every night at midnight local time, and will show a status of System Cleared. A status of Manual Clear means that a user cleared the incident from the Incident Dashboard, while Clear means it was cleared by a rule condition.
Comments	Add comments to the incident
Columns	Change the columns displayed in the summary table. Incident Columns describes all the columns that can be added to the Incident Dashboard.
Export	Export the incident information to a PDF or CSV file
Locations	View geolocation information about the incidents. Pin colors on the map indicate incident severity: Red: HIGH Severity Yellow: MEDIUM Severity Green: LOW Severity Black: Incidents with multiple severity levels at the same location

Contextual Menus

Clicking on an item within a column of the incident summary will open a contextual menu, with options depending on whether the incident attribute you selected includes an IP address (Source IP or Target IP, for example), or some other kind of incident attribute. Shared between both menus are an Add to Filter option, which enables you to select a result attribute and add it to the Filter By conditions. Both menus also include most of the same options available in the Incident Management controls to edit and add exceptions to rules. The IP address contextual menu provides options to view more information about the associated device, with many of the same options you would find in the Analysis menu used in search summary dashboards.

This screenshot shows the IP contextual menu open after selecting an IP address in the Incident Source column of the Incidents tab.

Incident Details

The Incident Details pane at the bottom of the Incidents Dashboard provides you with information about a selected incident in three areas: Incide nt Details, Triggered Events, and Related Incidents.

Incident Details

The Incident Details include the ID of the incident, specific details about the event that triggered the incident, and the definition of the rule associated with the incident.

Triggered Events

The list of events that triggered the incident. For columns containing an event type, or host or  IP information, click on an item to open a contextual menu and view more information about it.

Related Incidents

Use this menu to view related incidents based on the Source, Target, Rule Name, or Reporting IP associated with the selected incident.

Searching for Incidents by Incident Attributes

As your review incidents in your dashboard, you may want to build searches based on attributes from selected incidents. For example, you may want to use the value for the Incident Target attribute in an incident as a filter condition to find similar or related incidents, and then add more conditions based on the results of that search.

1. Log in to your Supervisor node.
2. Go to Incidents.
3. In the Incident Dashboard, select an incident.
4. Click on the attribute value for the selected incident that you want to add to the Filter By condition to open the Options menu, and then select Add to Filter.

The type of search will change to Advanced, and the attribute value you selected will be added to the Filter By conditions.

5. Click in the Filter By Conditions field to open the Conditions Builder and add other incident attributes.
6. Click Refresh when you’re done creating filter conditions to see the results.

Real Time Performance Probe

This section describes how to probe monitored devices for real time performance metrics.

Available metrics

GUI launch locations

Running a real time probe

Example – Real time Interface Statistics Display

Available metrics

CPU utilization

Memory utilization

Network interface statistics

Uptime

Disk utilization

SNMP Ping Statistics

Process Utilization

GUI launch locations

Real time Performance Metrics option is available from the following GUI locations

CMDB > Device > IP Address > Right click

CMDB > Device > Interfaces > Name > Right click

Incident > Incident Source and Incident Target > Right click

Running a real time probe

From any of the above locations, select Real Time Performance Metrics

Select the parameters

Select Job Name as the metric of interest

Select polling Frequency in seconds

Select the number of Runs as the number of times the device will be polled

Select the Collector which should communicate to the device

Depending on the job name, you may also need to select a Filter. For example, select Interface Name for Network Interface Statistics.

Example – Real time Interface Statistics Display

 

 

Using AccelOps Workbooks with Tableau Visual Analytics Desktop and Server

You can use any of the workbooks provided by AccelOps, which are attached to this page, to create visualizations of AccelOps data.

1. Download a workbook attached to this page to your local device where Tableau Visual Analytics Desktop is installed.
2. In Visual Analytics Desktop, go to File > Open….
3. Browse to the file you downloaded and open it.
4. You can make any changes you want to the workbook, but you can upload it to the server and start using it as is. Follow the instructions in the Publish the Workbook section of Creating a Single Sheet Workbook to publish to the Tableau Visual Analytics Sever, and add user permissions as described in Adding Users to Workbooks.

Drag and drop to upload or browse for files

Adding Users to Workbooks

Only the workbook publisher can give access to specific users during report creation time. As the AccelOps Visual Analytics Server Administrator, you can add users to the system and view which workbooks users can access.

Adding Users to Visual Analytics Server

Viewing User Access to Workbooks

Adding Users to Visual Analytics Server

1. Log in to AccelOps Visual Analytics Server.
2. In the Admin tab click Users.
3. Click Add.
4. Enter the user name as it appears in Active Directory.
5. Select the License Level for the user and assign User Rights as necessary.
6. Click OK.

Viewing User Access to Workbooks

1. Log in to Visual Analytics Server.
2. In the Admin tab click Users.
3. Select a user name to see the workbooks that the user can access.

Creating and Managing Workbooks

This section contains information on using Visual Analytics Desktop to create sheets and workbooks that are based on AccelOps reports, and then publishing them for others to use.

Viewing Workbooks

Creating and Publishing Workbooks

Creating a Single Sheet Workbook

Creating a Multiple Sheet Workbook

Using AccelOps Workbooks with Tableau Visual Analytics Desktop and Server Adding Users to Workbooks

Viewing Workbooks

1. Log in to Visual Analytics Server.
2. Click the Content tab and select Workbooks.
3. Click on a workbook.

The workbook along with the various worksheets are displayed.

4. Select a workbook or worksheet.
5. You will be prompted for credentials that will allow the workbook or worksheet to access database information. Enter the Admin credential that you used to set up Accelops Report Server and click OK.
6. When your credential is accepted, the chart associated with the selected workbook or worksheet will be displayed.

Creating and Publishing Workbooks

Workbooks are collections of AccelOps reports that have been synced to AccelOps Report Server, and which are then the basis for charts and dashboards that can be published to Visual Analytics Server for access by other users. Information in this section describes how to create single and multiple sheets of report information, and then make them accessible to other users.

Creating a Single Sheet Workbook

Creating a Multiple Sheet Workbook

Using AccelOps Workbooks with Tableau Visual Analytics Desktop and Server

Creating a Single Sheet Workbook

These instructions demonstrate how to create a single-sheet workbook that will chart the CPU and memory utilization trend for various servers. This example uses the Servers by CPU, Memory report and its associated table, but any report with a table in the reportdb database can also be used. The Tableau Desktop online Help also contains extensive information about building sheets and workbooks with the Tableau Desktop editor, which powers the AccelOps Visual Analytics Desktop.

Prerequisites

Procedure

Create the Sheet

Create the Workbook

Publish the Workbook

Prerequisites

Follow the instructions in Syncing an AccelOps Report with Report Server to sync the report you want to use for your worksheet.

You will need to know the name of the parent table for your synced report. Follow the instructions in Viewing reportdb Organization to find the table that corresponds to your report.

Procedure

Create the Sheet

1. Launch Tableau Visual Analytics Desktop.
2. Connect to AccelOps Report Server with the Username and Password that you used during Report Server installation. For Database, enter reportdb. For Port, enter 30000.

Connecting to Port 30000

It’s important to make sure you enter the correct port to connect to the reportdb database. If you leave this option blank you will connect to the default PostgreSQL database port, which will connect you with phoenixdb instead of reportdb. For more information about the databases contained in Report Server, see Report Server Architecture: phoenixdb and reportdb.

3. Under Tables, select the parent table for your report.

For the steps following, we will use the Servers by CPU, Memory table and its associated columns.

4. Drag the table to the View pane and click Update Now.

The data in the table will load into the pane below. Note that the table columns match closely to the Report Display Columns in AccelOps.

5. For Connection, select Live.
6. Click Go to Worksheet.

In the worksheet view you will see that a set of Dimensions and Measures are populated for the table.

7. Under Measures, select Report Time and drag it to the Dimensions section to create Report Time as a calculated measurement.
8. Under Dimensions, right-click on Report Time to edit the calculation formula and convert it to a human-readable format from UNIX time. The formula should look like DATEADD(‘second’,INT([Report Time]),#1969-12-31 16:00:00#)
9. Drag Report Time from Dimensions to Columns.
10. Under Columns, right-click on Report Time and select Exact Date.

You should now see dates and time increments in your chart as the X-axis.

11. Under Measures, select and drag AVG(cpuUtil) and AVG(memUtil) to Rows.
12. Set the aggregation of both AVG(cpuUtil) and AVG(memUtil) to AVG. For example, AVG(AVG(cpuUtil)) and AVG(AVG(memUtil)).

You should now see both measures on the Y-axis of your chart.

13. Under Dimensions, drag Host Name to the Color section under Marks. Each host will be assigned a color and added to the chart.
14. Change the chart display name for AVG(cpuUtil) and AVG(memUtil) by clicking on each in the Y-axis to launch the Edit Y-Axis dialog.

You can now edit the Title and Range, as well as other attributes, for each measure.

15. Under Data, click on the data source to open the Options menu, then click Refresh.
16. Rename the sheet by clicking on the data source to open the Options menu, then select Rename and enter a new name.

Your sheet is now complete. Hover your mouse over a trend line to view information about a specific host.

Create the Workbook

1. Click the Dashboard tab on the bottom of the Sheet editor to open the Dashboard
2. Under Dashboard, select an appropriate Size and screen resolution.
3. Under Dashboard, select the sheet and drag it into the display pane.
4. Open the Dashboard options menu and select Rename.

Change the name of the dashboard from Server CPU/Memory Trend to Server Performance.

5. In the File menu, select Save. Publish the Workbook
6. In the Server menu, select Sign In…
7. Enter the IP address and port number for the Visual Analytics Server.
8. Enter the Username and Password for the Visual Analytics Server admin user, and then click Sign In.
9. In the Server menu, select Publish Workbook.
10. Enter attributes for the workbook, such the associated Project, Name, View Permissions, and Views to Share.

See Adding Users to Workbooks for more information about user permissions for workbooks.

6. Click Publish.

Creating a Multiple Sheet Workbook

These instructions demonstrate how to create a multiple-sheet workbook that will contain a set of charts related to Network Health. This example uses the Network Devices by Ping RTT, Network Interfaces By Utilization, and Network Devices By CPU, Memory reports, but any report with an associated table and views in the reportdb database could be used. The Tableau Desktop online Help also contains extensive information about building sheets and workbooks with the Tableau Desktop editor, which powers the AccelOps Visual Analytics Desktop.

Prerequisites

Procedure

Create a View

Create a Workbook that Uses the View

Create the Workbook

Publish the Workbook

Prerequisites

Follow the instructions in Syncing an AccelOps Report with Report Server to sync the reports you want to use for your worksheet. You will need to know the name of the parent table for your synced reports. Follow the instructions in Viewing reportdb Organization to find the table that corresponds to your report.

Procedure

Create a View

Each report you want to include in your workbook corresponds to a table in the AccelOps reportdb. These tables need to be joined to cross-link the information that will appear in your workbook. In the case of a Network Health workbook that includes the sheets Network Devices by Ping RTT, Network Interfaces By Utilization, and Network Devices By CPU, Memory, the joining keys are host name and time.

1. Follow the instructions in Viewing reportdb Organization to find the parent tables for the reports you want to join.

For each report there is one parent table and multiple child tables containing data for a particular month.

2. Create a SQL statement in pgAdmin to join the tables.

In this example data is captured for one day. This enables quick generation of the data visualization.

SELECT cpu.report_time, cpu.”hostName”, cpu.”hostIpAddr”, cpu.”AVG(cpuUtil)”, cpu.”AVG(memUtil)”,        uptime.”SUM(sysDownTime)”, uptime.”AVG(avgDurationMSec)”, uptime.”LAST(sysUpTime)”,        uptime.”SUM(pollIntv)”, util.”intfName”, util.”intfAlias”,        util.”AVG(inIntfUtil)” AS “totalAvgInIntfUtil”, util.”AVG(outIntfUtil)” AS “totalAvgOutIntfUtil”,        util.”AVG(recvBitsPerSec)” AS “totalAvgRecvBitsPerSec”,        util.”AVG(sentBitsPerSec)” AS “totalAvgSentBitsPerSec”,        util.”AVG(outQLen)”, util.”AVG(intfSpeed64)”

FROM “Network Devices By CPU, Memory_1278492569_1” cpu,

“Network Devices by Ping RTT_2021056235_1” uptime,

“Network Interfaces By Utilization_382117475_1″ util

 

WHERE ((cpu.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND ((uptime.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND ((util.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND cpu.report_time = uptime.report_time AND cpu.”hostName” = uptime.”hostName” AND uptime.report_time = util.report_time AND uptime.”hostName” = util.”hostName”;

 

3. Click the Play icon in pgAdmin to execute the query.

Make sure the output pane contains data that is the result of the query execution.

4. Modify the SQL statement to create a view.

Add this command at the top of the SQL statement:

Add this command at the bottom of the SQL statement:

Your complete SQL statement should look like this:

CREATE OR REPLACE VIEW ph_network_health_view AS

SELECT cpu.report_time, cpu.”hostName”, cpu.”hostIpAddr”, cpu.”AVG(cpuUtil)”, cpu.”AVG(memUtil)”,        uptime.”SUM(sysDownTime)”, uptime.”AVG(avgDurationMSec)”, uptime.”LAST(sysUpTime)”,        uptime.”SUM(pollIntv)”, util.”intfName”, util.”intfAlias”,        util.”AVG(inIntfUtil)” AS “totalAvgInIntfUtil”, util.”AVG(outIntfUtil)” AS “totalAvgOutIntfUtil”,        util.”AVG(recvBitsPerSec)” AS “totalAvgRecvBitsPerSec”,        util.”AVG(sentBitsPerSec)” AS “totalAvgSentBitsPerSec”,        util.”AVG(outQLen)”, util.”AVG(intfSpeed64)”

FROM “Network Devices By CPU, Memory_1278492569_1” cpu,

“Network Devices by Ping RTT_2021056235_1” uptime,

“Network Interfaces By Utilization_382117475_1″ util

 

WHERE ((cpu.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND ((uptime.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND ((util.report_time * 1000)::double precision * ’00:00:00.001′::interval + ‘1969-12-31 16:00:00-08’::timestamp with time zone) >= (now() – 1::double precision * ‘1 day’::interval)      AND cpu.report_time = uptime.report_time AND cpu.”hostName” = uptime.”hostName” AND uptime.report_time = util.report_time AND uptime.”hostName” = util.”hostName”;

grant select on ph_network_health_view TO public;

 

5. In pgAdmin, click the Play icon to execute the statement.
6. Using pgAdmin, navigate to the Views and make sure the ph_network_health_view has been created.
7. Right-click on ph_network_health_view to open the Options menu, then select View Data > View Last 100 Rows to make sure the view contains data.

Create a Workbook that Uses the View

1. Launch AccelOps Visual Analytics Desktop.
2. Connect to AccelOps Report Server with the Username and Password that you used during Report Server installation. For Database, enter reportdb. For Port, enter 30000.
3. Under Tables, enter the name of the view you created in the search box to locate the view.

 

4. Drag the view into the Join pane and click Update Now. The data in the view will load into the pane below.

 

5. For Connection, select Live.
6. Click Go to Worksheet.

In the worksheet view you will see that a set of Dimensions and Measures are populated for the view.

An example worksheet showing CPU and Memory Utilization with several Dimensions and Measures populated from the original table.

 

7. For each report in your workbook you can now create an individual sheet, as described in Creating a Single Sheet Workbook.

Create the Workbook

1. Click the Dashboard tab on the bottom of the Sheet editor to open the Dashboard
2. Drag each sheet you’ve created into the Join

 

An example of three worksheets loaded into the Dashboard Join pane.

3. Under Dashboard, select an appropriate Size and screen resolution.
4. Open the Dashboard Options menu and select Rename.
5. In the File menu, select Save. Publish the Workbook
6. In the Server menu, select Sign In…
7. Enter the IP address and port number for the Visual Analytics Server.
8. Enter the Username and Password for the Visual Analytics Server admin user, and then click Sign In.
9. In the Server menu, select Publish Workbook.
10. Enter attributes for the workbook, such the associated Project, Name, View Permissions, and Views to Share.

See Adding Users to Workbooks for more information about user permissions for workbooks.

 

6. Click Publish.