Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
This PR is a prof-of-concept to send "availability" log to ElasticSearch.
It's complementary with module "mod-elastic-logs" because this module send only "Shinken logs" from broker to ElasticSearch (Nagios logs).
With all logs (Shinken log+Availability log), you will be able to create lots of nice graphs with Grafana or Kibana:
Example of uses with Grafana:
->Show SLA for each hosts/services on period chosen by user.
eg: Pie chart:
->Have a historic of availability for each hosts/services per day
->Timeline of states for each hosts/services (Critical/Warning/OK/...)
->Count of Critical services each hour
Everything is possible...
I'm not an expert in programming, so i think some impovements could be done. For example to add possibility to enable/disable sending logs to ElasticSearch in mongo-logs.cfg