Heka decoder and filter metrics aren't collected
Bug #1550229 reported by
Simon Pasquier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Confirmed
|
Medium
|
LMA-Toolchain Fuel Plugins |
Bug Description
This is a follow up of https:/
It can happen that the message injected by the heka_monitoring filter exceeds the maximum message size limit. A typical scenario is when the logstreamers match hundreds of files because Heka will create 1 decoder per file.
In that situation, no Heka metric are emitted and the related Grafana panels show no data.
There are (at least) 2 options to fix this issue:
- Increase the max message size limit.
- Strip down the number of collected metrics.
Changed in lma-toolchain: | |
milestone: | 1.0.0 → 0.10.0 |
Changed in lma-toolchain: | |
milestone: | 0.10.0 → none |
Changed in lma-toolchain: | |
milestone: | none → 0.10.1 |
Changed in lma-toolchain: | |
milestone: | 0.10.1 → 0.11.0 |
Changed in lma-toolchain: | |
milestone: | 0.11.0 → 1.0.0 |
milestone: | 1.0.0 → none |
To post a comment you must log in.
A third option would be to split the "bulk metric" message in smaller pieces: /github. com/openstack/ fuel-plugin- lma-collector/ blob/master/ deployment_ scripts/ puppet/ modules/ lma_collector/ files/plugins/ filters/ heka_monitoring .lua#L83
https:/