kolla

Heka configuration for Elasticsearch is missing

Bug #1634225 reported by Christian Berendt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned
kolla ocata-3 "o3"

Bug Description

Heka configuration for Elasticsearch is missing

Mauricio Lima (mliima) (mauricio-lima)
Changed in kolla:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

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

Jeffrey Zhang (jeffrey4l)
Changed in kolla:
milestone: none → ocata-3
Revision history for this message
Bertrand Lallau (bertrand-lallau) wrote :

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

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.