Configuration¶
Overview¶
The Insights Dashboard Configuration Settings page provides several options to configure and administer functions of the Dashboard application.
Note
To access the Configuration Settings page, click the profile menu, then select Configuration.
You can select the following tabs on this page:
Archive¶
The Archive tab configures archiving (backup) settings for the Insights Dashboard application.
You can select the following tabs on this page:
Remote Storage¶
This tab configures backup settings, including storage type (standard or nfs), remote location (for nfs), and allows you to view the list of archive files and non-SCP’d files.
You can choose to mount an NFS drive to the system. All archived files will then be archived to the NFS mounted drive.
Note
Removing the NFS mount will not copy the NFS contents back to local storage.
Only NFS v3 mounts are currently supported.
The system does a backup daily. For the most part, there is nothing for the user to configure. All data and configuration that exists on the system are archived automatically on a daily basis. Archived data are logically grouped together and by default stored into separate archived files locally on the server.
Analytix Backup¶
This tab displays the Dashboard backup settings. The settings are read-only, for informational purposes only.
This Archive group contains the Dashboard configuration settings (assets, licensing), user permissions settings (LDAP), and NDX files.
The backup excludes data from the specific Broadsoft data store, along with definition data and files. Broadsoft definitions and definition files each have their own separate Archive group.
Dashboard Files¶
Read-only, Dashboard files archive group settings. This archive group will archive all Dashboard settings. This includes all user created definition files, mappings, color palettes, user configs, schedules, and dashboards.
Definitions Data¶
Read-only, Dashboard definitions archive group settings. This archive group backs up all User Search Definitions data in the database tables. This is the data that drives the widgets.
Remote Storage¶
This tab allows you to configure remote archiving of the system backup files, if you’ve chosen standard / local storage in the setup.
Each archive group produces one or many archive files. The system can be configured to scp these archive files to a backup location or to another VOSS Insights system.
The archives can be sent to a separate backup location (SFTP-server, SCP or remote synced to another Dashboard).
The table describes settings on this tab:
archive_interval |
Choose a schedule, either Daily, Weekly, or Monthly. |
method |
Choose a method. Either of the following:
|
IP location |
The IP address. Also add username and password. |
destination |
The path on the remote server to the folder where backups are to be stored. |
DS9¶
This tab configures settings for DS9.
The NetFlow definitions data archive group backs up all Netflow Definitions data, which is the data that drives the widgets. These are read-only settings, for information purposes only.
Related Topics
DS9 Flow Summary¶
This tab displays and configures DS9 NetFlow summary status, options for detection of applications, internal subnets, and NetFlow, and port filtering.
Import¶
This tab allows you to import data into the system from a .csv file. There are specific
instructions on this page that need to be followed on how to format the .csv. This functionality will
allow you to manually add data that can be utilized in different contexts within the VOSS Insights
platform. An example could be specific costs associated with calling functions.
Import- Date Range Mapping
This setting allows you to import in a list of named date ranges (for example: Fiscal Quarters that may not align to standard calendar quarters, etc.).
If a date range mapping is imported, the Dashboard GUI allows you to change the Dashboard calendar by the imported date range name. Multiple named date ranges may be provided. Only dates are currently supported. The times for the entire day will be used (midnight to midnight).
Select a file to be imported then click IMPORT.
CSV format requirements described on this page must be followed:
CSV file to import. The CSV should adhere to the CSV RFC https://www.ietf.org/rfc/rfc4180.txt. Additionally, there are two more requirements. First, the first line of the CSV must contain the desired names for each CSV placement. Secondly, the second line of the CSV must contain the desired types for each CSV placement. Use 'integer', 'float', or 'string'. The normal CSV data can then start on lines 3 and above. Inherently a CSV file does not describe the names or types of each CSV placement. This is required so the system can create the proper database table and store the data appropriately. Failure to include these two lines will result in a failure to import in the CSV data.
Once imported, you can use the date range drop down to cycle through and select the custom dates.
LDAP¶
The system uses a local LDAP server to store user information. The system also supports authenticating with an external Microsoft Active Directory server. If an external Microsoft AD is used, the system will automatically sync all users locally. Local user accounts are necessary to set specific system privileges. Please note that Microsoft AD passwords are never stored locally. Authentication always occurs with external Microsoft AD. Once authenticated, the system allows the user access based on the user’s local system privileges. In order to properly configure this screen, the customer administrator must have an in-depth knowledge of the customer’s Microsoft AD architecture. Improper configuration may cause too little or too many users in the system.
The auto_sync_always_clean option can be set to clear user dashboards before sync.
Sendmail¶
Although the system has Sendmail built in, this tab allows for specific configuration changes to allow the system to interface with specific customer mail functions. All settings on this tab are optional settings.
SNMP¶
This tab allows the system to be configured to work with SNMP v3. It allows you to select the specific authentication and encryption methods to be utilized.
Syslog¶
This tab configures the IP address of your central syslog server.
The system can send out syslog messages about several of the internal functions, including backup and archival success.
This is a system-wide setting. If an IP address is specified, the system will send any internal messages onto the specified syslog server. Only one central syslog server can be specified at this time. Please validate firewall settings are open to allow incoming messages on the specified IP address and port.
VPN¶
The system can be connected to another Dashboard/Reporting platform, an Arbitrator Correlation platform, a Windows Forwarder or other client that supports the connectivity. Utilize this screen to set up automated connections to a server or client. The default port utilized is port 1194. Note that the screen selections will change based on the context selected (server or client).
VPN Manual¶
Configuration: Client - Add Server Config: The system allows you to enter a VPN configuration file directly into the system. Just paste the config directly into the bar under the label vpn_config.
Configuration: Server – Add Client: This screen is used to obtain a VPN Client Configuration file. This will allow connectivity from the Windows Forwarder directly to this server utilizing OpenVPN. There are a few prerequisites:
There must be network connectivity between the Windows Forwarder machine to this server.
The specified OpenVPN port (default port 1194) must be opened on the firewall between this server and the Windows Forwarder IPs.
This server VPN Configuration screen should be configured for server mode.
Widget Resources¶
This tab allows the auto-creation of a dashboard widget’s resource
description for a new table. At a minimum, the IP address and table name should be provided to
fetch/create the lxtapi_* definitions. This functionality may also be used to generate dashboards
for generic Postgres databases, if the database’s security information is known.
