balanced / balog Goto Github PK

Should run tests on git push.

If there is a new tag and the tests pass then publish to pypi. Same as sterling https://github.com/balanced/sterling/blob/balanced/.travis.yml#L19

schema (required)
The integer number indicates the version of schema.

I propose we use semver instead. The benefit of a semver version indicator is that it makes it clear what is a breaking change, and what is just additional.

What does the basic payload look like?

Open company etc etc etc. It's much easier to start a repo as public and make it private later if required than the other way around.

mentioned here 25131ee#commitcomment-7740436

and the reason JSON handler is not suitable is, if it is datetime, it's fine since json handler knows how to deal with it, but if it's a string like

/uri/{id}

in this case, id is the only meaningful part, so we will certainly extract that as in object. But when we are going to serialize it, json handler cannot know this.

balog consume <app_initialization options> -- options options

e.g. balog consume balanced_service.init -s /etc/balanced/balanced.conf -- -ldebug

right now if i want to integrate a consumer for the service i need to write a small script to scan the consumers and instantiate an engine and begin consumption of events.

what i'd like to be able to do is not write that runner but instead specify the init function that can be called, pass it some parameters and let balog write the runner for me.

Colander does not support serializing an object to its json representation

Maybe pez, schematics or marshmallow

When I run pip install -e .[tests] in justitia, and I run the justitia command

justitia

error

pkg_resources.DistributionNotFound: balog==0.0.3

will be raised. I see this line in the pip installation log. My bet is the setup.py version number reading is broken or what

Requested balog==0.0.3 (from justitia==0.0.0), but installing version 0.0.0

• https://www.loggly.com/blog/what-60000-customer-searches-taught-us-about-logging-in-json/

https://magnum.travis-ci.com/balanced/balanced/builds/6696671

Downloading/unpacking balog[kafka]>=1.2,<1.3 (from balanced-service==1.8.23)
  Downloading balog-1.2.3.tar.gz
  Running setup.py (path:/home/travis/virtualenv/build/balog/setup.py) egg_info for package balog

    The required version of setuptools (>=3.5.1) is not available,
    and can't be installed while this script is running. Please
    install a more recent version first, using
    'easy_install -U setuptools'.

    (Currently using setuptools 2.2 (/home/travis/virtualenv/lib/python2.7/site-packages))
    Complete output from command python setup.py egg_info:

The required version of setuptools (>=3.5.1) is not available,
and can't be installed while this script is running. Please
install a more recent version first, using

What does this requirement give us?

be good to enforce coverage and keep track of it.

source (optional)
Source of this event, usually a FQDN of host. Since this might not given by application when the event is generated, it could be attached by fluented or other log processor, so it should be optional.

Rather than a single field for the FQDN of the host, how about a context field that allows specifying many attributes about when the message was generated?

E.g.

• FQDN
• versions of various installed libraries
• logged in user
• time taken to process
• application - e.g. balanced, precog, knox
• application_version - e.g. 1.8.0

these are just example fields, i'm not advocating for them, rather suggesting that a field that can contain more information that just a single item (FQDN) would be more suitable.