Standalone Logsearch

Deploying Logsearch

The steps for deploying Logsearch on its own node and connecting it to the Pulse-core server are as follows:

[root@pulse2:~ (ad-default)]$ accelo deploy addons
INFO: Active Cluster: pulse_demo
? Select the SA components you would like to install: [Use arrows to move, space to select, type to filter]
[ ] FS Elastic
> [x] LogSearch
[ ] STANDALONE TSDB
[ ] FS Analytics V2
[ ] STANDALONE DB
[ ] HA GraphQL
[ ] LDAP

1. Login to Pulse server and update main Pulse configuration file present at ACCELO_HOME/config/acceldata_cluster_name.conf.

elastic = [
{
name = "default"
host = "<ES_HOST_NAME>"
port = 19013
},
{
name = "fsanalytics"
host = "<ES_HOST_NAME>"
port = 19013
},
{
name = "nifi"
host = "<ES_HOST_NAME>"
port = 19013
}
],

1. Create or update the existing ad-fsanalyticsv2-connector.yml file with the following properties:
   1. ES_HOST=<host_running_ES>
   2. ES_PORT=19013
2. Override the properties present in ACCELO_HOME/work/cluster_name/vars.yml file to override.yml .

base:
logstash_url: <LOG_SEARCH_HOSTNAME>:19012
yarn_app_es_urls: http://<LOG_SEARCH_HOSTNAME>:19013

1. On Pulse-core server run the following command to apply the configuration changes.

accelo reconfig cluster -a

1. Run the push config command on Pulse core server to push the updated config changes in application config file. Press Y on any prompts.

accelo admin database push-config -a

1. Restart all the Pulse services.

accelo restart all

1. Once data is available on Logsearch Pulse UI, unselect the Logsearch component running on Pulse-core to reduce overhead.

[root@pulse2:acceldata (ad-default)]$ accelo deploy addons
INFO: Active Cluster: pulse_demo
? Select the components you would like to install: [Use arrows to move, space to select, type to filter]
[ ] Kafka 0.10.2 Connector
[ ] Kafka Connector
[ ] LDAP
> [ ] LogSearch
[ ] Memsql Connector
[x] Notifications
[ ] Proxy
You have now successfully deployed Logsearch in its node and have connected it to the Pulse core sever.