Page History

...

Glossary

Feature Specifications

Use cases

1. Root Admin users can use this API to quickly identify the sequence of steps related to a particular Job.
2. QA can use this api to link the log messages related to automated test failures.

...

• 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 systemvm for elasticsearch nodes.

Logstash Configuration on the log shipping layer.

input {
  file {    

type => "apache"    

Wiki Markuppath => \ [ "/var/log/cloudstack/management/management-server.log" \]   \} } output {   amqp \{     host => "myamqpserver"     exchange_type => "fanout"     name => "rawlogs"   \} ]
  }
}
output {
  amqp {
    host => "myamqpserver"
    exchange_type => "fanout"
    name => "rawlogs"
  }
}

Logstash configuration on the index/search layer.

input {
  amqp {
    type => "all"
    host => "<host>"
    exchange => "rawlogs"
    name =>  "<name>"
  }
}unmigrated-wiki-markup

filter { &nbsp; &nbsp;grok \{ &nbsp; &nbsp; &nbsp;type => "apache" &nbsp; &nbsp; &nbsp;pattern => "%\{YEAR\}-%\{MONTHNUM\}-%\{MONTHDAY\}\[T \]%\{HOUR\{
   grok {
     type => "apache"
     pattern => "%{YEAR}%{MONTHNUM}%{MONTHDAY}[T ]%{HOUR}\:?%\{MINUTE\}\:?%\{SECOND\}\[T \ ]INFO%\{GREEDYDATA\}job\[-\]+%\{INT\:jobid\}\s*=\s*\[\s*%\{UUID\:uuid\}\s\* \\ \
]%\{GREEDYDATA\}" &nbsp; \}
  }
}

output {
  elasticsearch {
    host => "<elasticsearch_master>"
  }
}

...