Heka configuration for Elasticsearch is missing

Bug #1634225 reported by Christian Berendt on 2016-10-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Undecided
Unassigned

Bug Description

Heka configuration for Elasticsearch is missing

Changed in kolla:
status: New → Confirmed
importance: Undecided → Medium
Jeffrey Zhang (jeffrey4l) wrote :

So heka do not collect ES's logging, right?

Changed in kolla:
milestone: none → ocata-3

Heka is not used anymore, fluentd is used instead.
Maybe we can close this bug?

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: Medium → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers