Skip to content

Latest commit

 

History

History
57 lines (36 loc) · 2.35 KB

README.md

File metadata and controls

57 lines (36 loc) · 2.35 KB
Raw

Babl Quality Assurance Service

Initial draft: https://docs.google.com/babl-qa

How to test babl-qa in the local dev-env

In order to test babl-qa locally it is required to launch 4 additional services/modules:

  • logstash
  • supervisor2
  • babl-server
  • babl (cli)

babl + supervisor2 + babl-server will use queue.babl.sh:9092 kafka pub-sub service, logstash will receive STDOUT/STDERR output log messages from supervisor2 + babl-server and will forward the logs into kafka logs.qa topic.

babl-qa will be working independently and consuming data from kafka logs.qa topic.

Launch 6 terminal sessions in $GOPATH/src/github.com/larskluge/babl-qa/DEVENV and run:

T1: $ ./logstash_start.sh && ./logstash_attach.sh

T2: $ ./supervisor2.sh

T3: $ ./babl-server.sh

T4: $ ./babl-qa.sh

T5: $ ./kafka-listen-logsqa.sh

T6: $ ./babl-cli.sh

TODO:

  1. Babl module request history view

    • Track request Start/Stop(Duration) from kafka logs.qa topic and write to logs.history

  2. Babl module request details view

    • Track request full details from kafka logs.qa topic and write to logs.details
    • Send babl events (Telegram/Slack notifications) when the request details is not completed within the expected time limit.

  3. babl-qa core modules

    • Listen to kafka logs.qa topic and parse JSON log messages
    • Create a request details manager (receive messages and groups by requestid, should contain the 6 different details messages to assure the request was successfully completed)
    • Create a REST api module
    • Create internal request timeout monitor (in some conditions supervisor2 does not timeout)
    • Create an internal request monitor that triggers an event error when it's only receiving messages from the supervisor2 or only from babl-server
    • Add websockets support for UI Live Update
    • Add Dashboard to count Success/Errors per minute and per hour rates
    • Add Histogram graph (time vs requests, similar to logmatic top view)
    • Add flag to adjust qa-service internal timeout
    • Add flag to adjust cache timeout
    • Add flag to silence kafka write (useful to test locally)
    • Create a go routine to parse logs.raw data into logs.qa (removing logstash dependency)