Logs are not being indexed
alertname: LogCollectionBroken
The end-to-end log testing system has detected that logs are not reaching the Elasticsearch index. Something must be broken either with Elasticsearch itself, or with the log-collector service (rsyslog)
in our deployment, we have since the very first successful lilypad run, this alarm firing.
this alarm does seem correct (unlike false-positive #45 (closed)) since kibana / elasticsearch appears empty.
i'm unsure if this is expected to work, or maybe in development. just reporting it, in case it's relevant for anyone. after all, we prefer logs to be discarded.