logstash: almost all logs aren't properly processed
Bug #1403890 reported by
Jesse Pretorius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Invalid
|
High
|
Jesse Pretorius | ||
Icehouse |
Fix Released
|
High
|
Jesse Pretorius | ||
Juno |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
It would appear that most logs are either dropped or not being properly processed by logstash. When all the filters are removed then the logs show properly in Kibana when the correct query is used.
It may be best to go back to basics in the log processing and refactor it to ensure that absolutely all logs are pushed into Elasticsearch and shown in Kibana.
Some inspiration:
https:/
https:/
Changed in openstack-ansible: | |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
Changed in openstack-ansible: | |
status: | Confirmed → In Progress |
Changed in openstack-ansible: | |
status: | Fix Committed → Invalid |
To post a comment you must log in.
This is actually a known issue ever since and based on the github issue #530. /bugs.launchpad .net/openstack- ansible/ +bug/1399410
Here the based launchpad issue: https:/