Layer7 API Management

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?

Good afternoon,

The normal way that services are setup to auto-start on the Gateway is using the "chkconfig <service> on" command. Any third party application on the gateway appliance needs to be fully tested in your lab as CA Support does not support the installation and maintenance of these applications. If you don't see anything amiss with the operation then promote it through the environment. While during troubleshooting any issue, we may ask for them to be disabled to eliminate them as being factors in an issue.

Sincerely,

Stephen Hughes

Director, CA Support

To document how I ended up setting this:

The following command will cause the filebeat and metricbeat agents to start automatically

[root@servername init.d]# chkconfig --add metricbeat

[root@servername init.d]# chkconfig --add filebeat

And shows that they are now set to start at level 2

[root@servername init.d]# chkconfig --list filebeat

filebeat        0:off   1:off   2:on    3:on    4:on    5:on    6:off

[root@servername init.d]# chkconfig --list metricbeat

metricbeat      0:off   1:off   2:on    3:on    4:on    5:on    6:off

The following command sets the runlevel to level 3 for both

[root@servername init.d]# chkconfig --level 2  filebeat off

[root@servername init.d]# chkconfig --list filebeat

filebeat        0:off   1:off   2:off   3:on    4:on    5:on    6:off

[root@servername init.d]# chkconfig --level 2  metricbeat off

[root@servername init.d]# chkconfig --list metricbeat

metricbeat      0:off   1:off   2:off   3:on    4:on    5:on    6:off