Is your feature request related to a problem? Please describe.
With the yaml based config and options inherited from cortex etc its easy to make mistakes in the loki config file that don't manifest until runtime. Right now the only way to test the config, per the team on Slack, is to run loki on it. This is fine for a manual check but it becomes difficult to work with in CI environments.

I want to reduce the amount of log-spam in the DB logs. Is there a better way of executing the CREATE DATABASE queries? Postgres doesn't have the WHERE NOT EXISTS clause - but it's still possible to check if tables are already present.

I'm not sure where these originate from - heplify-server, homer-app, or some other script.

2020-05-29 04:54:15.076 UTC [1] LOG:  received sm

i see there is anew feature there, to export the call flow as a PNG, which is great. However the exported PNG does not include the IP address in the top of the call flow tab. can you have a look into that?

thanks again :)

The Loki API has changed: https://github.com/grafana/loki/blob/master/docs/api.md

PR #4 included (among other changes) the removal of ipinfo.io as a geolocation provider. We had several reasons for this:

• We are able to get the country data even without any additional provider thanks to Cloudflare.
• ipinfo.io required a subscription which meant one additional step for potential users.

With this change, the README needs to be updated.

TODO:

• Remove the IPINFO l

There's a bunch of tests that don't work, mostly because the fixtures in ./test/fixtures.json are invalid. This is because there's less data processing happening in 6.0.0 before sending than before. Logs in this version only get formatted and stringified just before sending out for easier processing.