Page History

...

• Same as Management Server: Each management server will be configured to run as a elasticsearch node. This particular configuration though simple can impact the management server as the elasticsearch service can be memory and cpu intensive. One of the management servers will be configured as the master node. The same node  will also run the amqp instance.
• Seperate Elasticsearch nodes: In this configuration the systemvm template can be used to spawn elasticsearch nodes. The number of such nodes should be configurable via a global parameter. One of the  node will be designated as the master node, which will also run the amqp instance.

TODO: Details on using Using systemvm for elasticsearch nodes:

Currently cloudstack does not allow deployment of default system vms. The only supported types are (virtual router, secondary storage, consoleproxy, internal and external load balancer). These specifc types are handle in their specific Manager code. To enable systemvms to be started by admin, Default System VM manager and VO class will require to be implemented.

Logstash Configuration on the log shipping layer.

...

A new API will introduced which can be accessed as
http://<host>:8080/client/api?command=extractLogByJobId&jobid=<jobid>

UI flow

None

IP Clearance

• Logstash which is an opensource log management tool and is covered under Apache 2.0 license
• Elasticsearch which is a search and analytics tool and is again covered under Apache 2.0 license. 

...