AnsweredAssumed Answered

Setting add-on components to autostart at runlevel 3 on API GW appliance

Question asked by pwhelan81 on Jun 8, 2017
Latest reply on Aug 3, 2017 by Stephen_Hughes

Have installed filebeat and metricbeat on API GW 9.2 virtual appliance to feed an ELK environment according to document shared in How to implement ELK with API Gateway .  HINT use newer versions of filebeat and metricbeat than are specified in the doc....seems silly that I did not do this at first...but knowing nothing about elasticsearch I followed the doc and had several problems resolved by going to newer versions of the agents

 

Now my question:

 

 I want to set filebeat and metricbeat to start automatically when the appliance is rebooted.  I can see via the runlevel command that the default runlevel for the appliance is 3.  I also can see that mysql and SSG starts up at level 2 and that nothing starts up a runlevel 3. (see table below)

 

Assume it would be ok to have filebeat and  metricbeat (and any other add-on) start at level 3.

 

This would allow me to take the server down to level 2 and stop any/all add-ons while still leaving the gateway running. 

 

Looking for advice on this or confirmation I am thinking correctly about it?

 

 

Run level 1       
blk-availability0:off1:on2:off3:off4:off5:off6:off
lvm2-monitor0:off1:on2:off3:off4:off5:off6:off
udev-post0:off1:on2:off3:off4:off5:off6:off
Run level 2       
auditd0:off1:off2:on3:on4:on5:on6:off
crond0:off1:off2:on3:on4:on5:on6:off
foundation-services0:off1:off2:on3:on4:on5:on6:off
ip6tables0:off1:off2:on3:on4:on5:on6:off
iptables0:off1:off2:on3:on4:on5:on6:off
jytter0:off1:off2:on3:on4:on5:on6:off
mysql0:off1:off2:on3:on4:on5:on6:off
nc_hardserver0:off1:off2:on3:on4:on5:on6:off
nc_ncsnmpd0:off1:off2:on3:on4:on5:on6:off
nc_raserv0:off1:off2:on3:on4:on5:on6:off
network0:off1:off2:on3:on4:on5:on6:off
nslcd0:off1:off2:on3:on4:on5:on6:off
ntpd0:off1:off2:on3:on4:on5:on6:off
postfix0:off1:off2:on3:on4:on5:on6:off
rsyslog0:off1:off2:on3:on4:on5:on6:off
snmpd0:off1:off2:on3:on4:on5:on6:off
ssg0:off1:off2:on3:on4:on5:on6:off
ssg-dbstatus0:off1:off2:on3:on4:on5:on6:off
ssgsysconfig0:off1:off2:on3:on4:on5:on6:off
sshd0:off1:off2:on3:on4:on5:on6:off
tcp_tune0:off1:off2:on3:on4:on5:on6:off
vmware-tools0:off1:off2:on3:on4:off5:on6:off
Run level 3       

Outcomes