<commit_before>* Welcome to Sensu
  Sensu is a monitoring system framework, handling the remote execution of checks.

* License
  Sensu is released under the MIT license.

* Contributing
  - [[http://help.github.com/fork-a-repo/][Fork]] [[https://github.com/sonian/sensu][Sensu]]
  - Use a [[https://github.com/dchelimsky/rspec/wiki/Topic-Branches][topic branch]]
  - Create a [[http://help.github.com/send-pull-requests/][pull request]]

  Keep it simple.

** Readme Driven Development
*** A Client Will
  - Have a set of attributes to describe it, including its responsibilities
  - Send keep-alives to a server
  - Subscribe to a set of queues bound to a set of fanout exchanges, determined by its responsibilities
  - Substitute tokens in check commands with their matching client attribute
  - Receive checks from subscriptions, execute them, and publish the results to a queue with its client name
  - Not allow overlapping check executions of the same name
  - Report when it is unaware of a check it received from a subscription

*** A Server Will
  - Subscribe to a queue for check scheduling, another for check results
  - Populate the check scheduling queue using a JSON config file
  - Pull a check from the check scheduling queue and push it onto its associated fanout exchanges
  - Pull check results, storing the latest events for clients, a good result will flush a previous event for that client<commit_msg>update the readme<commit_after>* Welcome to Sensu
  Sensu is a monitoring system framework, handling the remote execution of checks.

* License
  Sensu is released under the [[https://github.com/sonian/sensu/blob/master/MIT-LICENSE.txt][MIT license]].

* Contributing
  - [[http://help.github.com/fork-a-repo/][Fork]] [[https://github.com/sonian/sensu][Sensu]]
  - Use a [[https://github.com/dchelimsky/rspec/wiki/Topic-Branches][topic branch]]
  - Create a [[http://help.github.com/send-pull-requests/][pull request]]

  Keep it simple.

** Readme Driven Development
*** A Client Will
  - Have a set of attributes to describe it, including its responsibilities
  - Send keep-alives to a server
  - Subscribe to a set of queues bound to a set of fanout exchanges, determined by its responsibilities
  - Substitute tokens in check commands with their matching client attribute
  - Receive checks from subscriptions, execute them, and publish the results to a queue with its client name
  - Not allow overlapping check executions of the same name
  - Report when it is unaware of a check it received from a subscription

*** A Server Will
  - Subscribe to a queue for check scheduling, another for check results
  - Populate the check scheduling queue using a JSON config file
  - Pull a check from the check scheduling queue and push it onto its associated fanout exchanges
  - Pull check results, storing the latest events for clients, a good result will flush a previous event for that client
{'fraction_non_alphanumeric': 0.07233459033253342, 'fraction_numerical': 0.0, 'mean_word_length': 3.920741989881956, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 5, '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': '1810554', 'n_tokens_mistral': 783, 'n_tokens_neox': 757, 'n_words': 373}