loki

We have a promtail configured with two scrape configs: consulagent_sd_configs & systemd-journal
Inspecting the output from the metrics at /metrics, it seems that Promtail only exposes data relevant to file-based log tailing.

There is no data about metrics that were collected via the systemd-journal target at all.
I'm not even sure if the total metrics such as

• `promtail_targets_a

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem

The kiali-operator may require higher memory limits for clusters with bigger a mount of nodes. Thus resource limits shall be configurable via values.

Describe the solution you'd like A clear and concise description of what you want to happen.
Enrich schema for Kiali-operator

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

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.