Installing and Configuring Tableau Server

Prerequisites

Installation

Activation

Configuration

 

Prerequisites

Before you begin installing Tableau Server, make sure you have read the section on Tableau Server in Requirements for Visual Analytics Report Server. This contains information on the Administrator Account and Ports that you will need during the configuration process. You may want to also consult the Tableau Server Administration Guide before you begin the installation process.

Installation

1. Download the installation file from Tableau Software.
2. Double-click the installation file to launch the Setup Wizard.
3. When the Setup Wizard launches, click Next to begin the installation process.
4. Enter a Destination Location where you want to install the server files, and then click Next.
5. When the system verification process completes, click Next.
6. Enter a location for the Start Menu folder, or use the default location, and then click Next.
7. Click Install to complete the installation process.
8. Click Next to begin the server activation process.

Activation

1. If you are evaluating Tableau Server, click Start trial now. Otherwise, click Activate the product to enter a license key.
2. If you enter a license key, click Activate.
3. Click Continue to launch the Tableau Server configuration process.

Configuration

1. In the Configuration dialog, enter a User Name and Password for the domain admin account that you will use to administer the Tableau Server.
2. If necessary, enter a Gateway port through which you will connect to the server over HTTP.
3. Click OK.

The initialization process will launch and complete within several minutes.

4. Click Finish to complete the configuration process.
5. Launch the Tableau Server user interface by entering the URI for the server in a browser window.

The URI will be be in the format of http://<Windows_Server_IP_Address>:<Port_Number_Used_In_Step_2> 6.  Sign in to the server by entering the credentials for the domain admin account that you created in Step 1, and then click Sign In.

7. Click the Admin tab and select Maintenance.
8. Under Status, check to make sure that all systems are up and running.

You are now ready to install Tableau Desktop. After you have completed the Desktop installation process and connect to Report Server for the first time to create a sheet, as described in Creating a Single Sheet Workbook, you will also establish the connection between AccelOps Report Server and Tableau Server.

 

 

Working with the Report Server

This section contains information on AccelOps Report Server architecture, viewing and querying CMDB and Event data in contained in the Report Server databases, and database maintenance.

Report Server Architecture: phoenixdb and reportdb

Working with CMDB Data in AccelOps Report Server

Viewing phoenixdb Organization

Querying Incident Data in AccelOps Report Server

Reference: Attribute Columns in the ph_incident_view Table

Sample Incident Queries

Querying Other CMDB Tables in AccelOps Report Server

Querying Device Vendor and Model Distribution for Discovered Devices Querying Discovered Devices

Working with Event Data in AccelOps Report Server

Viewing reportdb Organization

Syncing an AccelOps Report with Report Server

Deleting a Report from AccelOps Report Server

Modifying an Existing Report in AccelOps Report Server

Report Server Architecture: phoenixdb and reportdb

AccelOps Report Server contains two databases:

phoenixdb

This database contains the entire AccelOps CMDB and is populated via asynchronous PostgreSQL replication (slony) in near-real time.

reportdb

This database contains the results of event queries.

Topics in this section describe how to view the tables in these databases, and how those tables are organized. For viewing the tables, we recommend using the pgAdmin PostgreSQL database utility, which you can download from the pgAdmin website.

Working with CMDB Data in AccelOps Report Server

Data from the AccelOps CMDB database is populated to the AccelOps Report Server and stored in the Report Server phoenixdb. This section contains information on how to view the organization of phoenixdb, and write queries against the data it contains.

Viewing phoenixdb Organization

Querying Incident Data in AccelOps Report Server

Reference: Attribute Columns in the ph_incident_view Table Sample Incident Queries

Querying Other CMDB Tables in AccelOps Report Server

Querying Device Vendor and Model Distribution for Discovered Devices Querying Discovered Devices

Viewing phoenixdb Organization

This database contains the contents of the entire AccelOps CMDB database, including incidents.

1. In the pgAdmin utility, go to File > Add Server.
2. In the New Server Registration dialog, enter connection details for AccelOps Report Server.

For Maintenance DB, select phoenixdb.

For Username and Password, use the read-only user name and password that you created when you provisioned the Report Server.

3. Click OK.

When the connection to the AccelOps Report Server is established, phoenixdb will load in the Object browser. There are approximately

197 tables in phoenixdb, which are replicated from the AccelOps cluster.

4. Select a table to view, then right-click to open the Options
5. In the Options menu, select View Data, and then select an option for which rows you want to view.

For example, to view the contents of the ph_device table, which contains CMDB information about discovered devices, you would select and then right click on ph_device, then select View Data > View All Rows.

You can also use this method to examine Views and other objects in the phoenixdb database.

Querying Incident Data in AccelOps Report Server

There are two ways to look at the incident data inside AccelOps Report Server:

Incident Tables (ph_incident and ph_incident_detail)

Contains the incidents

Incident View (ph_incident_view)

This is a database view that adds other context to the incident tables by joining with other tables in the database. Added information includes location and business service. Some information is parsed out for easier query, such as host names and IP address fields from incident_source, and incident_target fields in ph_incident are parsed out as separate fields in ph_incident_view.

This topic describes how to view the data contained in Incident View.

1. Follow the instructions in Viewing phoenixdb Organization to access the phoenixdb database in AccelOps Report Server.
2. Go to Views > ph_incident_view > Columns to view the table columns.
3. Go to Views > ph_incident_view > View Data > View Last 100 Rows to view the incidents.

 

Reference: Attribute Columns in the ph_incident_view Table

Column Name	Format	Description
incident_id	integer	Unique id for an incident
cust_org_id	integer	Customer Id (for AO-SP)
first_seen_time	integer	The time when the incident was first seen. The format is UNIX time but with milliseconds granularity. It is defined as the number of milliseconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970
last_seen_time	integer	The time when the incident was last seen. The format is UNIX time but with milliseconds granularity. It is defined as the number of milliseconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970
incident_et	string	Incident event type id e.g. PH_RULE_SERVER_HW_CRITICAL
incident_status	integer	0: Active 1: Auto Cleared 2: Manually Cleared 3: System Cleared
incident_count	integer	The number of times this exact incident (with the same parameters: source, destination etc has happened)
biz_name	string	Associated business service name
severity	integer	Numerical severity of the incident – range 0-10
severity_cat	string	Incident severity category: 0-4: LOW, 5-8: MEDIUM and 9-10: HIGH
orig_device_ip	string	IP address of the device that reported the incident
ph_incident_category	string	Category of infrastructure affected by this incident: possible valies: Network, Server, Storage, Virtualization, Application, Internal
incident_src	string	Incident Source string formatted as a list of <Attribute>:Value; e.g. srcIpAddr:10.1.1.1,srcName:JoeLaptop
src_ip_addr	string	Source IP parsed out from incident_src field
src_name	string	Source Name parsed out from incident_src field
src_device_location	string	(Geo) Location display name string for the object specified in incident_src
src_country	string	(Geo) Country name string for the object specified in incident_src
src_state	string	(Geo) State name for the object specified in incident_src
src_building	string	(Geo) Building name for the object specified in incident_src
src_floor	string	(Geo) Floor for the object specified in incident_src
src_latitude	double	(Geo) Latitude for the object specified in incident_src
src_longitude	double	(Geo) Latitude for the object specified in incident_src
incident_target	string	Incident Destination string formatted as a list of <Attribute>:Value; e.g. “destIpAddr:10.1.1.1,destName:JoeLaptop” or “hostIpAddr:10.1.1.1,hostName:JoeLaptop”
dest_ip_addr	string	Destination IP parsed out from incident_target field
dest_name	string	Destination Name parsed out from incident_target field
dest_device_location	string	(Geo) Location display name string for the object specified in incident_target
dest_country	string	(Geo) Country name string for the object specified in incident_target
dest_state	string	(Geo) State name for the object specified in incident_target
dest_building	string	(Geo) Building name for the object specified in incident_target
dest_floor	string	(Geo) Floor for the object specified in incident_target
dest_latitude	double	(Geo) Latitude for the object specified in incident_target

 

dest_longitude	double	(Geo) Longitude for the object specified in incident_target
host_ip_addr	string	Host IP address parsed out from incident_target field
host_name	string	Host Name parsed out from incident_target field
host_device_location	string	(Geo) Location display name string for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_country	string	(Geo) Country name string for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_state	string	(Geo) State name for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_building	string	(Geo) Building name for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_floor	string	(Geo) Floor for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_latitude	double	(Geo) Latitude for the object specified in incident_target – populated if incident_target contains hostIpAddr
host_longitude	double	(Geo) Longitude for the object specified in incident_target – populated if incident_target contains hostIpAddr
vm_name	string	VM Name if incident involves a Virtual machine – populated if incident_target contains vmName
user_attr	string	User name if incident involves user, i.e. incident_target contains user
target_user_attr	string	Target user name if incident involves user, i.e. incident_target contains targetUser
ldap_domain	string	Domain if incident involves user, i.e. incident_target contains domain
computer	string	Computer name incident_target contains computer
target_computer	string	Target Computer name incident_target contains targetComputer
incident_details	string	Incident Details containing evidence on why the incident triggered e.g. Triggered Event Count = 90 or AVG(CPUUtil) = 90 etc

Sample Incident Queries

Show Incident Categories with Severity and Frequency Occurrence Show Incident Location

Show Incident Categories with Severity and Frequency Occurrence

This query will show which parts of the infrastructure are triggering events.

1. Follow the instructions in Viewing phoenixdb Organization to access the phoenixdb in AccelOps Report Server.
2. Under Views, select ph_incident_view.
3. In pgAdmin, click on the SQL icon in the menu bar to open the SQL query window.
4. Enter this SQL query:

 

SELECTph_incident category, incident_et, severity_cat, src_ip_addr, host_name, FROMph_incident_view GROUPBYph_incident category, incident_et, severity_cat, src_ip_addr, host_name ORDERBYCOUNT(*) DESC;

COUNT(*)

5. When the query executes, you will see a list of matching incidents in the Output Pane. Show Incident Location
6. Follow the instructions in Viewing phoenixdb Organization to access the phoenixdb in Accelops Report Server.
7. Under Views, select ph_incident_view.
8. In pgAdmin, click on the SQL icon in the menu bar to open the SQL query window.
9. Enter this SQL query:

 

COUNT(*)

SELECT host_device_location, severity_cat, ph_incident_category, FROM ph_incident_view GROUP BY host_device_location, ph_incident_category, severity_cat ORDER BY host_device_location ASC, severity_cat ASC COUNT

(*) DESC;

5. When the query executes, you will see a list of incidents and their locations in the Output Pane.

Querying Other CMDB Tables in AccelOps Report Server

Querying Device Vendor and Model Distribution for Discovered Devices Querying Discovered Devices

Querying Device Vendor and Model Distribution for Discovered Devices

Querying Discovered Devices

Working with Event Data in AccelOps Report Server

Data from the AccelOps EventDB database is populated to the AccelOps Report Server and stored in the Report Server reportdb. This section contains information on how to view the organization of reportdb, and write queries against the data it contains.

Viewing reportdb Organization

Syncing an AccelOps Report with Report Server

Deleting a Report from AccelOps Report Server

Modifying an Existing Report in AccelOps Report Server

Viewing reportdb Organization

This database contains the reports that are synched from the AccelOps cluster.

1. In the pgAdmin utility, go to File > Add Server.
2. In the New Server Registration dialog, enter connection details for AccelOps Report Server.

For Maintenance DB, select reportdb.

For the Port enter 30000 (default port used for the reported).

For Username and Password, use the read-only user name and password that you created when you provisioned the Report Server.

3. Click OK.

When the connection to the Report Server is established, reports will load in the Object browser.

4. Select a table to view, then right-click to open the Options
5. In the Options menu, select View Data, and then select an option for which rows you want to view.

Syncing an AccelOps Report with Report Server

1. Log in to AccelOps.
2. Go to Analytics > Reports.
3. Select a report.

Any reports with a Sync checkbox can be synced. Run the report to make sure it contains some data.

4. For each report you want to sync, select the Sync
5. Click OK.
6. After several minutes, follow the instructions in Viewing reportdb Organization to view the reportdb database.
7. Under Tables, you should now see the synced reports.

Table Structure for Synced Reports

When you sync an AccelOps report to AccelOps Report Server, two pairs of tables are created in reportdb, one pair for each organization in the case of AO-SP. For each organization, multiple tables are created:

1. A parent table containing data for all months: the table name is of the form <Report Name>_<ID>_<custId>
2. A child table for the current month: <Report Name>_<ID>_<custId>_<yYYYYmMM> where YYYY is the year and MM is the month.

Queries should be written using the parent table. To see data in the parent table, follow the instructions in  Viewing reportdb Organization . The re portdb database fields are generated from the display fields in AccelOps report definitions. Only the field report_time is added to the Report Server table definitions to capture the time when the particular report is generated. For example, if you synced the report Network Devices by CPU, Memory, you would see these fields:

Field	Description
report_time	UNIX time at which the report is generated. Unix time (or POSIX time or Epoch time) is a system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970 not counting leap seconds.
hostName	Host Name of the device for which CPU and memory are being measured
hostIpAddr	Access IP of the device for which CPU and memory are being measured
AVG(cpuUtil)	Average of all the CPU utilization metrics within the last 5 minutes ending with report_time
AVG(memUtil)	Average of all the CPU utilization metrics within the last 5 minutes ending with report_time

Deleting a Report from AccelOps Report Server

1. Log in to AccelOps.
2. In Analytics > Reports > Synced Reports, select the report you want to delete.
3. In the Sync Details dialog, clear the Sync option for the report, and then click OK.

The report will no longer be synced with Report Server. You can verify this by making sure the Sync option is not selected for the report on the Analytics > Reports > Synced Reports page. You can now delete the report from AccelOps Report Server.

4. Log in to AccelOps Report Server via SSH and navigate to the directory /opt/phoenix/deployment/jumpbox.
5. Run the py command, along with the table name and date as arguments, to delete the report.
6. After you have deleted the table containing the report information, you will need to delete the parent table, which will now be empty of content, using the same py command.

Modifying an Existing Report in AccelOps Report Server

Suppose a system report is synced and exported to AccelOps Report Server. When you modify that report in AccelOps, you must rename it, at which point it becomes a user report. When you then sync that report for Accelops Report Server, a new table is created on the AccelOps Report Server.

Suppose now that you have a user-defined report that is already synced to the AccelOps Report Server, but you modify it inline in AccelOps, which means that you have changed the report conditions without changing the report name. This will cause a change in the table, but a new table will not be created. Here are some examples of inline modifications, and how they affect the structure of the table as well as the data collected in the table:

Modification	Effect
GROUP BY field added	The corresponding table has the new GROUP BY field, but only newer data populates the field
GROUP BY field removed	There is no change in the corresponding table, and newer data does not populate the field
GROUP BY field changed	For example, the field srclpAddr is changed to destlpAddr. Both fields are retained, but newer data populates d estlpAddr.
Aggregated fields added	The corresponding table has the new field, but only newer data populate that field
Aggregated field removed	There is no change in the corresponding table, and newer data does not populate the field
Aggregated Field Changed	For example, AVG(cpUutil) is changed to MAX(cpuUtil). Both fields are retained, but newer data populates MA X(cpuUtil).

 

 

Registering Report Server

1. In the Admin tab, select License Management.
2. Under Report Server Information, click Add.
3. Enter the Report Server IP Address, and the Database Username and Password you want to use to administer Report Server.

These are also the credentials that you will use when you set up the Visual Analytics Server to read data from Report Server.

4. Click Run in Background if you want Report Server registration to run in the background for larger installations.

When CMDB size is under 1GB, registration takes approximately 3 minutes to complete.

5. When registration completes, click OK in the confirmation dialog.
6. Under the Admin tab, select Cloud Health and make sure Report Server is up and running.

Syncing with the Report Server

Using AccelOps Visual Analytics involves first syncing reports contained in the primary AccelOps application to the AccelOps Report Server.

1. Log in to your Supervisor node.
2. Go to Analytics > Reports > Synced Reports.
3. Select a report.

Currently only reports that contain a Group By condition can be synced. Both system and user-created reports can be synched as long as the contain a Group By condition.

4. Select Sync.

When the sync process initiates, the Supervisor node dynamically creates a table within the Report Server reportdb database. When the sync is established, it will run every five minutes, and the last five minutes of data in the synced report will be pushed to the corresponding table. This lets you run Visual Analytics on event data stored in the Report Server reportdb database.

Hypervisor Installations for Report Server

These topics cover the installation of Report Server in various hypervisor enviroments.

Installing and Registering AccelOps Report Server in Amazon Web Services

Installing and Registering AccelOps Report Server in KVM

Installing and Registering AccelOps Report Server in Microsoft Hyper-V Installing and Registering AccelOps Report Server in VMware ESX

Installing and Registering AccelOps Report Server in Amazon Web Services

Follow the instructions for setting up an AccelOps virtual appliance as described in Setting Up Supervisor, Worker and Collector Nodes in AWS, and then register the Report Server to the Supervisor as described in Installing and Registering AccelOps Report Server in VMware ESX.

Turn on archive mode for Report server CMDB replication

1. Mount a NFS shared directory on both Super and report server and make sure that this mount can survive system reboot. For example:

/data/replication/archive

2. Make this shared directory own by postgres.postgres
3. On Super, edit postgresql.conf under /cmdb/data to turn on archive mode by uncommenting (removing # in the first column) the following lines and make sure archive_command points to the correct directory which is created in step 1
4. On Report Server, edit /cmdb/data/recovery.conf and uncomment the following lines and make sure restore_command and archive_cleanup_command are pointing to the directory created in step 1:
5. On Super, restart postgresql DB ‘service postgresql-9.1 restart’
6. On Super, restart App Server (Glassfish)
7. On Report Server, restart postgresql DB ‘service postgresql-9.1 restart’

Registering Report Server

1. In the Admin tab, select License Management.
2. Under Report Server Information, click Add.
3. Enter the Report Server IP Address, and the Database Username and Password you want to use to administer Report Server.

These are also the credentials that you will use when you set up the Visual Analytics Server to read data from Report Server.

4. Click Run in Background if you want Report Server registration to run in the background for larger installations.

When CMDB size is under 1GB, registration takes approximately 3 minutes to complete.

5. When registration completes, click OK in the confirmation dialog.
6. Under the Admin tab, select Cloud Health and make sure Report Server is up and running.

Installing and Registering AccelOps Report Server in KVM

Follow the instructions for installing an AccelOps virtual appliance as described in Importing a Supervisor, Collector, or Worker Image into KVM, and then register the Report Server with the Supervisor as described in Installing and Registering a Report Server Node in ESX.

Turn on archive mode for Report server CMDB replication

1. Mount a NFS shared directory on both Super and report server and make sure that this mount can survive system reboot. For example:

/data/replication/archive

2. Make this shared directory own by postgres.postgres
3. On Super, edit postgresql.conf under /cmdb/data to turn on archive mode by uncommenting (removing # in the first column) the following lines and make sure archive_command points to the correct directory which is created in step 1
4. On Report Server, edit /cmdb/data/recovery.conf and uncomment the following lines and make sure restore_command and archive_cleanup_command are pointing to the directory created in step 1:
5. On Super, restart postgresql DB ‘service postgresql-9.1 restart’
6. On Super, restart App Server (Glassfish)
7. On Report Server, restart postgresql DB ‘service postgresql-9.1 restart’

Registering Report Server

1. In the Admin tab, select License Management.
2. Under Report Server Information, click Add.
3. Enter the Report Server IP Address, and the Database Username and Password you want to use to administer Report Server.

These are also the credentials that you will use when you set up the Visual Analytics Server to read data from Report Server.

4. Click Run in Background if you want Report Server registration to run in the background for larger installations.

When CMDB size is under 1GB, registration takes approximately 3 minutes to complete.

5. When registration completes, click OK in the confirmation dialog.
6. Under the Admin tab, select Cloud Health and make sure Report Server is up and running.

Installing and Registering AccelOps Report Server in Microsoft Hyper-V

Follow the virtual appliance installing instructions in Installing in Microsoft Hyper-V, and then register the Report Server node with the Supervisor as described in Installing and Registering AccelOps Report Server in VMware ESX.

Turn on archive mode for Report server CMDB replication

1. Mount a NFS shared directory on both Super and report server and make sure that this mount can survive system reboot. For example:

/data/replication/archive

2. Make this shared directory own by postgres.postgres
3. On Super, edit postgresql.conf under /cmdb/data to turn on archive mode by uncommenting (removing # in the first column) the following lines and make sure archive_command points to the correct directory which is created in step 1
4. On Report Server, edit /cmdb/data/recovery.conf and uncomment the following lines and make sure restore_command and archive_cleanup_command are pointing to the directory created in step 1:
5. On Super, restart postgresql DB ‘service postgresql-9.1 restart’
6. On Super, restart App Server (Glassfish)
7. On Report Server, restart postgresql DB ‘service postgresql-9.1 restart’

Registering Report Server

1. In the Admin tab, select License Management.
2. Under Report Server Information, click Add.
3. Enter the Report Server IP Address, and the Database Username and Password you want to use to administer Report Server.

These are also the credentials that you will use when you set up the Visual Analytics Server to read data from Report Server.

4. Click Run in Background if you want Report Server registration to run in the background for larger installations.

When CMDB size is under 1GB, registration takes approximately 3 minutes to complete.

5. When registration completes, click OK in the confirmation dialog.
6. Under the Admin tab, select Cloud Health and make sure Report Server is up and running.

Installing and Registering AccelOps Report Server in VMware ESX

These instructions are for installing Report Server on VMWare ESX, and assume that you have already installed and configured an AccelOps environment. For instructions for a complete AccelOps install, see the topics under Installation.

Installing Report Server

Follow the instructions for installing an AccelOps virtual appliance as described in the topics under Installing a Supervisor, Worker, or Collector Node in ESX and in Configuring the Supervisor, Worker, or Collector from the VM Console.

Turn on archive mode for Report server CMDB replication

1. Mount a NFS shared directory on both Super and report server and make sure that this mount can survive system reboot. For example:

/data/replication/archive

2. Make this shared directory own by postgres.postgres
3. On Super, edit postgresql.conf under /cmdb/data to turn on archive mode by uncommenting (removing # in the first column) the following lines and make sure archive_command points to the correct directory which is created in step 1
4. On Report Server, edit /cmdb/data/recovery.conf and uncomment the following lines and make sure restore_command and archive_cleanup_command are pointing to the directory created in step 1:
5. On Super, restart postgresql DB ‘service postgresql-9.1 restart’
6. On Super, restart App Server (Glassfish)
7. On Report Server, restart postgresql DB ‘service postgresql-9.1 restart’

Installation and Configuration of AccelOps Visual Analytics

Installation and configuration of AccelOps Visual Analytics involves setting up AccelOps Report Server, and then integrating it with Tableau Server and Desktop from Tableau Software. Topics in this section contain setup and configuration instructions for Report Server. For information on setting up and configuring Tableau Server and Desktop, see the online Tableau Software documentation.

Requirements for Visual Analytics Report Server

Setting Up Visual Analytics

Hypervisor Installations for Report Server

Syncing with the Report Server

 

Requirements for Visual Analytics Report Server

You install Visual Analytics Report Server as an AccelOps node, and these requirements assume that you have already set up and installed AccelOps. If you are working with a fresh install of AccelOps that includes Report Server, see the topics under Installation for complete requirements and installation instructions for the AccelOps Virtual Appliance.

Hardware Requirements for Report Server Nodes

Component	Quantity	Host SW	Processor	Memory	OS/App Storage	Reports Data Storage (1 year)
Report Server	1	ESX	8 Core 3 GHz, 64 bit	16 GB	200GB (80GB OS/App, 60GB CMDB, 60GB SVN)	See recommendations under Hardware Requirements for Supervisor and Worker nodes

 

 

Setting Up Visual Analytics

There are three components to Accelops Visual Analytics:

1. Accelops Report Server
2. Tableau Server
3. Tableau Desktop

Setting up Visual Analytics involves setting up each of those components in order, and establishing the relationship between them.

1. You must first install Report Server as described in Installing and Registering AccelOps Report Server in VMware ESX.
2. After installing Tableau Server on a Windows server, and installing Tableau Desktop on a Windows or Mac OS X device, you then connect the two systems as described in the Tableau Software product documentation.
3. When this connection is established, it automatically triggers the remote registration and configuration of the AccelOps Report Server, including replication of the CMDB and EventDB data from the AccelOps Cluster to the AccelOps Report Server, as well as the user account required for access to the original databases.

Registration of the Report Server and replication of the AccelOps database data may take some time depending on the size of the original CMDB. Registration is complete when the replication process catches up with the latest data in the system. From that point on, replication from the CMDB to Accelops Report Server takes place in near real time, letting you run Visual Analytics queries against CMDB data that has been replicated to the Report Server’s phoenixdb.

You can find full information about setting up all components of AccelOps Visual Analytics in the section Installation and Configuration of

AccelOps Visual Analytics

Visual Analytics

Visual Analytics is an add-on for AccelOps that lets you create custome visualizations of AccelOps report data, as well as dashboards containing multiple visualization charts. AccelOps Visual Analytics has three components:

1. The AccelOps Report Server, which syncs with and replicates AccelOps reports in near-real time.
2. Tableau Server from Tableau Software, which enables the publication and distribution of your visualizations.
3. Tableau Desktop, also from Tabeleau Software, which is your primary tool for creating visualizations.

See Installation and Configuration of AccelOps Visual Analytics for information about setting up AccelOps Report Server. For more detailed information about Tableau Server and Desktop, including installation, configuration, and examples of creating sheets and workbooks, you should consult the Product Support section of the Tableau Software website.

 

AccelOps Visual Analytics Architecture

Overview and Report Server Architecture

Using AccelOps Report Server with Tableau Software

Overview and Report Server Architecture

With AccelOps Visual Analytics, you can now create visual representations of the data that is stored in AccelOps. This includes:

Structured data stored in the AccelOps CMDB relational PostgreSQL database, such as: Discovered information about devices, systems, applications and users

Identity and location information

Incidents and notifications

Unstructured data such as logs, events, performance metrics etc. that are monitored by AccelOps and stored in the EventDB NoSQL database, which is accessible by Supervisors and Workers over NFS.

In order to provide near real-time visual analytics without compromising the performance of your AccelOps deployment, both structured and unstructured data is exported to a separate virtual machine, the AccelOps Report Server, running PostgreSQL. The Report Server contains two databases that are queried by AccelOps Visual Analytics:

phoenixdb

This database contains the entire AccelOps CMDB and is populated via asynchronous PostgreSQL replication (slony) in near-real time.

reportdb

This database contains the results of event queries

You can find more information about AccelOps Report Server in the topic Report Server Architecture: phoenixdb and reportdb and its related topics.

Using AccelOps Report Server with Tableau Software

AccelOps Report Server integrates with Tableau Software to provide the interface for creating and publishing your data visualizations. Workbooks containing visualizations based on AccelOps data are created using Tableau Desktop, and then are published to Tableau server, where they can be accessed on any Windows or OS X device by users how have been granted permission for viewing or editing them. AccelOps provides some workbooks for visualizations, but you can construct others for custom analytics. You can find more information about workbooks in the section Cre ating and Managing Workbooks.

 

 

 

Audit

Audit Reports can be used to determine if a device is running the recommended OS and installed software versions, performance metrics are within bounds and harmful events have not triggered.

Creating Audit Report

Running an Audit

Exporting Audit Results

Scheduling an Audit

 

Creating Audit Report

To create an Audit Report

1. Go to Analytics tab
2. Expand Audit node on the left tree and go to the folder to which the new report will belong. You can also create a new folder first by clicking on the + on top of the left tree.
3. Click New.
4. Enter the following information for an Audit Report
   1. Name: Name of the Audit Report
   2. Description: Description of the Audit Report
   3. Vendor: Select a specific device vendor from the drop down list. The Audit Report will be specific to the chosen device vendor and model
   4. Model: Select a vendor specific model from the drop down list. The Audit Report will be specific to the chosen device vendor and model
   5. Specify Failed Criteria for the Audit Report. A device will fail the audit if any of the specified criteria is matched. i. OS Version Condition:
      1. Choose an operator: possible choices are IN, NOT IN, CONTAINS, NOT CONTAINS
      2. Specify value to be matched: this can be a comma separated list ii. Install Software Condition:
      3. Specify Condition name. This is just for reference purposes.
      4. Specify Install software name – the name has to be exactly identical to the discovered installed software in CMDB > Devices > Installed Software > Name
      5. Choose an operator: possible choices are IN, NOT IN, CONTAINS, NOT CONTAINS
      6. Specify value to be matched: this can be comma separated list

• Rules Condition:
  1. Click … and the Rule selector dialog appears
  2. Select the appropriate Rule folder from the left most tree. If you do not know the specific folder, then choose the top level Rules folder.
  3. Select the rules from the middle section. You can also type a search string. You can expand the window and shrink the left most section to see more of the rule descriptions. The rules in the selected folder will appear in the middle section.
  4. Click Items >> to place the selected rules on the rightmost section 5. Click

1. Report Condition:
   1. Click … and the Report selector dialog appears
   2. Select the appropriate Report folder from the left most tree. If you do not know the specific folder, then choose the top level Reports folder. The reports in the selected folder will appear in the middle section.
   3. Select the reports from the middle section. You can also type a search string. You can expand the window and shrink the left most section to see more of the report descriptions.
   4. Click Items >> to place the selected reports on the rightmost section 5. Click OK.

 

Audit Policy Criteria Matching Notes

1. For each criteria, only devices in CMDB with vendor and model specified in the Audit Report is considered
2. If any of the criteria matches, then the device fails the audit
3. IN and NOT IN are exact match while CONTAINS and NOT CONTAINS are case insensitive sub-string match
4. For OS Version match, the entered value is compared with the Version column in CMDB > Device.
5. For Installed Software Version match, the entered value is compared with the Version column in CMDB > Device > Installed Software
6. For Rule match, the specified rule must trigger during the time interval specified in the Audit Report. Organization id and access IP of the device is compared to the Organization Id and Host IP in an incident.
7. For Report match, the specified reports run for the time duration specified in Audit Report must have data.

Running an Audit

To run an Audit,

1. Select an Audit Policy
2. Click Run Now
3. In the follow up dialog,
   1. Select the organizations for which to run the audit (meaningful for Service Provider version)
   2. Choose a time window – absolute or relative
   3. Click OK

The Audit Policy check results are displayed in the right bottom pane.

Summary tab shows a high level overview of the Audit Policy check.

 Audit Result Distribution chart shows the device pass/fail distribution for every selected organization.

Failed Criteria distribution chart shows the contribution of each audit criteria to the devices that failed the audit.

Detail tab shows the Audit Policy check for each device matching the vendor, model specified in the policy.

Organization specifies the entity to which the device belongs

Device Name is the host name of the device in CMDB

Audit Status is the Pass/Fail flag

Details specifes the reasons for Audit Policy check failure

Exporting Audit Results

To export an Audit Report,

1. Select an Audit Policy
2. Run the Audit Policy Check. The results will be shown in the bottom right pane.
3. Click Export
   1. Add User Notes
   2. Choose Output Format – PDF or CSV
   3. Click Generate Report – the PDF file will be stored in local disk

Scheduling an Audit

To schedule a report to run at a later time

1. Choose between one of two options
   1. Run this report for – If the ‘Run this report for’ button is selected, a report will be scheduled for the super user, containing data from the organizations selected. The super user will be the owner of the report. The recipients of the report may be defined in the ‘Send Notifications’ section below or in Admin -> General Settings -> Analytics.
   2. Schedule this report for – If the ‘Schedule this report for’ button is selected, multiple reports will be scheduled — one for each selected organization — and containing only that organization’s data. The reports will be owned by the respective organizations. The recipients of the report are taken from Admin -> General Settings -> Analytics. When multiple reports are run in this way the notification recipients cannot be indicated in the ‘Send Notifications’ section below.
2. Select all the Organizations for which to run the Audit Report
3. Select the Report time range
4. Specify Schedule settings – when to run this report
5. Choose Output Format – PDF or CSV
6. Select notification – report recipients and method
   1. If you choose Send default notification, then the settings in Admin > General Settings > Analytics > Alerts to be sent when scheduler runs any REPORT, is used
   2. If you choose Specify custom notifications, then you can specify email addresses
   3. If you choose Copy to a remote directory, then the settings in Admin > General Settings > Analytics > Reports to be copied to this remote location when scheduler runs any REPORT, is used

Viewing Available Reports

1. Log in to your Supervisor node.
2. Go to Analytics > Reports.
3. For multi-tenant deployments, select the Organization for which you want to view the available reports.
4. Expand the Reports list, and select the subcategory of report you want to view.
5. Select the report you want to view information about. Each report has four information tabs:

Report Tab	Description
Summary	Includes the Filter and Group By conditions for the report, and the report’s Display attributes
Schedule	Information about when the report is scheduled to run. See Scheduling Reports for more information. You can click the + icon to set a schedule for the report to run.
Results	The results from any scheduled runs of the report, or results you have saved from running the report.
Definition	The XML definition of the report.