Data Sources
The Data Sources page enables you to configure the datasources.
From the left navigation bar, click Configure and select Data Sources. You are now on Datasource Manager page.
The left-panel provides the list of active datasources available along with its health check. indicates that the datasource is healthy. indicates that the datasource is experiencing some issues. It provides the search capability to search for the datasource(s).
You may click an active datasource in the left-panel to Modify Selected Datasource. By default, the right-panel provides you an option to Create Datasource.
Modify Selected Datasource
The left-panel provides the list of datasources available. It provides the search capability to search for the datasource you need to modify.
If a datasource is selected in the left-panel, the right-panel provides you with the datasource details for the datasource selected. You can view the datasource details or modify the configuration of the selected datasource.
Associate Tenants
- In the bottom panel, Associated Tenants lists the tenants associated with the selected datasource, if any.
- Click Associate tenants button to associate a tenant to the selected datasource. When you click this button, you are navigated to section Tenant Administration page.
Create Datasource
From the drop-down list , select the datasource type from the following options.
-
Datasources Elasticsearch and Splunk are used by the Logs Widget.As you enter the information in the fields, real-time health checks are performed.
Elasticsearch
Elasticsearch is a third-party datasource used by the Logs Widget. To install and configure elasticsearch, please refer to https://www.elastic.co/guide/en/elastic-stack-get-started/current/get-started-elastic-stack.html
- Name - enter a unique name of the datasource you want to create for Elasticsearch.
- API Server - enter the Elasticsearch URL.
- Authentication
- Token - enter the API Token from your elasticsearch logging datasource.
- Credentials - enter elasticsearch username and password in the following fields.
- Username - enter the elasticsearch username.
- Password - enter the elasticsearch password.
- None - authentication type is not required.
- Column Mappings
- Device - enter the field for the host name in elasticsearch. For example, it can be host or reported_hostname.
- Severity ID - enter the severity Id. For example, severity_id.
- Timestamp - enter the Elasticsearch timestamp. For example, @timestamp.
This must be an Elasticsearch date type field.
- Select Test connection button to confirm you can connect to the server.
- Click Add Datasource button in the upper-right corner to add the datasource.
NMS
- Name - enter a unique name of the datasource you want to create.
- API Server - enter the SevOne NMS URL.
- Authentication
- Token - enter the generated API token from REST API. Please refer to section Generate API Key.
- Type - metrics can be METRICS/FLOW or FLOW.
- Select Test connection button to confirm you can connect to the server.
- Click Add Datasource button in the upper-right corner to add the datasource.
Splunk
Splunk is a third-party datasource used by the Logs Widget.
Prerequisites
To validate Splunk configuration, execute the steps below.
- Launch Splunk from your web browser.
http://<enter Splunk IP address>:8000
- From Settings drop-down, under DATA, select Data Inputs.
- Under Local inputs, select UDP.
- Choose the UDP port to configure. For example, port 514 (for syslog) in the screenshot above.
- Enter the source name to override in field Source name override. For example, Syslog in screenshot below.
- Enable check box More settings.
- In field Host, validate DNS is selected. If not, please verify that Host can be changed to DNS before continuing with the steps below. Field Host must be DNS.
- Click Save.
- Run a query in Splunk to verify if the devices are in the host or the reported_host field. Click Search & Reporting in the left navigation bar.
- Click Data Summary button.
- In Data Summary pop-up, click the Sources tab and then, click udp:514 for Syslog.
- In the left navigation bar under SELECTED FIELDS, click host or reported_hostname to obtain the values. From SevOne Data Insight, when creating a Splunk datasource, under Column Mappings > Device field, use host or reported_hostname.
Create Splunk Datasource
- Name - enter a unique name of the datasource you want to create for Splunk.
- API Server - enter the Splunk URL. For example, example.com/api or
/api . - Authentication
- Credentials
- Username - enter the Splunk username.
- Password - enter the Splunk password.
- None - authentication type is not required.
- Credentials
- (optional) Port - default port is 8089.
Column Mappings- Device - enter the field for the host name in SPLUNK. For example, it can be host or reported_hostname. For details on how to obtain this information, please refer to SPLUNK Column Mappings.
- Severity ID - enter the severity Id. For example, severity_id.
- Timestamp - enter the Splunk timestamp. For example, _time.
- Select Test connection button to confirm you can connect to the server.
- Click Add Datasource button in the upper-right corner to add the datasource.
Generate API Key
To generate an API Key, please execute the steps below.
- From you web browser, enter URL http://
/api/v3/docs/ . Please replacewith the hostname or IP address of your SevOne NMS appliance. - Select sevone.api.v3.Users.
- Select POST /api/v3/users/signin.
- Under Parameters, all the way to the right, locate the Model Schema field. Click on the field to copy its content to the body field.
- On the left side of the Parameters section, you will notice that the content now appears in the body field. Perform the following actions in the body field:
- After "password":, replace string with SevOne NMS password . Make sure to enter it within the quotes.
- After "username":, replace string with SevOne NMS username . Make sure to enter it within the quotes.
- At the bottom of the POST section, click the Try it out! button.
- Scroll down to the Response Body field. You should see a long alphanumeric string after "token". This is the token that you need to sign in. Copy it without the quotes.
- In the upper-right corner, locate bearer token field. Paste the token into this field. You should now have permissions to perform the operations.
- Scroll-up to POST /api/v3/users/apikey and select it.
- Under Parameters, all the way to the right, locate the Model Schema field. Click on the field to copy its content to the body field.
- On the left side of the Parameters section, you will notice that the content now appears in the body field. Perform the following actions in the body field: * After "application":, replace string with the name of the key. For example, SevOneKey. Make sure to enter it within the quotes.
- At the bottom of the POST section, click the Try it out! button.
- Scroll down to the Response Body field. You should see a long alphanumeric string after "apiKey". This is the API Key. Copy it without the quotes.
- Enter the API key in field API Token.