<commit_before># Flapjack

[![Travis CI Status][id_travis_img]][id_travis_link]

[id_travis_link]: https://secure.travis-ci.org/#!/flpjck/flapjack
[id_travis_img]: https://secure.travis-ci.org/flpjck/flapjack.png

Flapjack is a highly scalable and distributed monitoring notification system.

Flapjack provides a scalable method for dealing with events representing changes in system state (OK -> WARNING -> CRITICAL transitions) and alerting appropriate people as necessary.

At its core, flapjack process events received from external check execution engines, such as Nagios. Nagios provides a 'perfdata' event output channel, which writes to a named pipe. `flapjack-nagios-receiver` then reads from this named pipe, converts each line to JSON and adds them to the events queue. Flapjack's `executive` component picks up the events and processes them -- deciding when and who to notifify about problems, recoveries, acknowledgements etc. Additional check engines can be supported by adding additional receiver processes similar to the nagios receiver.


# Using Flapjack

TODO (link to doc/USING.md)


# Developing Flapjack

TODO (link to doc/DEVELOPING.md)<commit_msg>test wiki links in README<commit_after># Flapjack

[![Travis CI Status][id_travis_img]][id_travis_link]

[id_travis_link]: https://secure.travis-ci.org/#!/flpjck/flapjack
[id_travis_img]: https://secure.travis-ci.org/flpjck/flapjack.png

Flapjack is a highly scalable and distributed monitoring notification system.

Flapjack provides a scalable method for dealing with events representing changes in system state (OK -> WARNING -> CRITICAL transitions) and alerting appropriate people as necessary.

At its core, flapjack process events received from external check execution engines, such as Nagios. Nagios provides a 'perfdata' event output channel, which writes to a named pipe. `flapjack-nagios-receiver` then reads from this named pipe, converts each line to JSON and adds them to the events queue. Flapjack's `executive` component picks up the events and processes them -- deciding when and who to notifify about problems, recoveries, acknowledgements etc. Additional check engines can be supported by adding additional receiver processes similar to the nagios receiver.


# Using Flapjack

## Quickstart

TODO numbered list for simplest possible Flapjack run

For more information, including full specification of the configuration file and the data import formats, please refer to the [Flapjack Wiki](wiki/USING).

# Developing Flapjack

Information on developing more Flapjack components or contributing to core Flapjack development can be found in the [Flapjack Wiki](wiki/DEVELOPING).
{'fraction_non_alphanumeric': 0.062242219722534686, 'fraction_numerical': 0.0, 'mean_word_length': 5.322274881516588, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5156646', 'n_tokens_mistral': 729, 'n_tokens_neox': 716, 'n_words': 322}