# Flow processor to output writer is 90% full while Monitor Output: decoding rate: 0 records/second

**URL:** <https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347>\
**Category:** ElastiFlow Community\
**Created:** [November 12, 2025, 10:20am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347 "2025-11-12T10:20:57Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 12, 2025, 10:20am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/1 "2025-11-12T10:20:57Z")

</div>

Hi Everyone, i’m newer to flowcoll, i getting a problem when start the flowcoll progress. The elk look only receive totally 256 flow record everytime the flowcoll service start. I’m have try 8C16G, 16C32G for my ubuntu 2404 system, but the phenomenon still same. I have install the basic license for the flowcoll.

How can i continue check, if anyone could point it out it will be really appreciate!

On the Kibana, i can see 2 time of 256 record for sflow after i mannually restart the flowcoll service twice.

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/2ac1841ae4cbae90009e40b6dfa60a86d74bc6fc.png)

tail -f /var/log/elastiflow/flowcoll/flowcoll.log

{“level”:“info”,“ts”:“2025-11-12T10:07:26.705Z”,“logger”:“flowcoll.elasticsearch\_output[default]”,“caller”:“httpoutput/healthcheck\_runner.go:70”,“msg”:“healthcheck success; connection is available”,“address”:“x.x.x.x:9200”}  
{“level”:“info”,“ts”:“2025-11-12T10:07:32.884Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:07:52.884Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:07:56.702Z”,“logger”:“flowcoll.monitor\_pool”,“caller”:“monitor/pool.go:54”,“msg”:“Monitor Output: decoding rate: 8 records/second”}  
{“level”:“info”,“ts”:“2025-11-12T10:08:12.885Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:08:26.702Z”,“logger”:“flowcoll.monitor\_pool”,“caller”:“monitor/pool.go:54”,“msg”:“Monitor Output: decoding rate: 0 records/second”}  
{“level”:“info”,“ts”:“2025-11-12T10:08:32.885Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:08:52.885Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:08:56.702Z”,“logger”:“flowcoll.monitor\_pool”,“caller”:“monitor/pool.go:54”,“msg”:“Monitor Output: decoding rate: 0 records/second”}  
{“level”:“info”,“ts”:“2025-11-12T10:09:12.884Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:09:26.702Z”,“logger”:“flowcoll.monitor\_pool”,“caller”:“monitor/pool.go:54”,“msg”:“Monitor Output: decoding rate: 0 records/second”}  
{“level”:“info”,“ts”:“2025-11-12T10:09:32.885Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:09:52.885Z”,“logger”:“flowcoll”,“caller”:“metrics/queuegauge.go:88”,“msg”:“flow processor to output writer is 90% full. This is normal when the collector is starting. If it persists for hours, it may indicate that you are at your license threshold or your system is under-resourced.”}  
{“level”:“info”,“ts”:“2025-11-12T10:09:56.702Z”,“logger”:“flowcoll.monitor\_pool”,“caller”:“monitor/pool.go:54”,“msg”:“Monitor Output: decoding rate: 0 records/second”}

more /etc/elastiflow/flowcoll.yml  
EF\_LOGGER\_LEVEL: ‘info’  
EF\_LOGGER\_ENCODING: ‘json’  
EF\_LOGGER\_FILE\_LOG\_ENABLE: true  
EF\_LOGGER\_FILE\_LOG\_FILENAME: ‘/var/log/elastiflow/flowcoll/flowcoll.log’  
EF\_LOGGER\_FILE\_LOG\_MAX\_SIZE: 100  
EF\_LOGGER\_FILE\_LOG\_MAX\_AGE: 7  
EF\_LOGGER\_FILE\_LOG\_MAX\_BACKUPS: 4  
EF\_LOGGER\_FILE\_LOG\_COMPRESS: false  
EF\_LICENSE\_ACCEPTED: true  
EF\_ACCOUNT\_ID: “xxxx”  
#EF\_LICENSE\_FLOW\_RECORDS\_PER\_SECOND: 4000  
EF\_LICENSE\_KEY: “”  
EF\_INSTANCE\_NAME: xxxx  
EF\_API\_IP: 0.0.0.0  
EF\_API\_PORT: 8080  
EF\_API\_TLS\_ENABLE: false  
#EF\_API\_TLS\_CERT\_FILEPATH:  
#EF\_API\_TLS\_KEY\_FILEPATH:  
#EF\_API\_BASIC\_AUTH\_ENABLE: false  
#EF\_API\_BASIC\_AUTH\_USERNAME:  
#EF\_API\_BASIC\_AUTH\_PASSWORD:  
EF\_FLOW\_SERVER\_UDP\_IP: 10.x.x.x  
EF\_FLOW\_SERVER\_UDP\_PORT: 6343,9995  
EF\_FLOW\_SERVER\_UDP\_READ\_BUFFER\_MAX\_SIZE: 33554432  
EF\_FLOW\_PACKET\_STREAM\_MAX\_SIZE: 8192

#EF\_INPUT\_FLOW\_BENCHMARK\_ENABLE: false  
#EF\_INPUT\_FLOW\_BENCHMARK\_PACKET\_FILEPATH: /etc/elastiflow/benchmark/flow/packets.txt

EF\_PROCESSOR\_DECODE\_IPFIX\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_NETFLOW1\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_NETFLOW5\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_NETFLOW6\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_NETFLOW7\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_NETFLOW9\_ENABLE: false  
EF\_PROCESSOR\_DECODE\_SFLOW5\_ENABLE: true  
#EF\_PROCESSOR\_DECODE\_SFLOW\_FLOWS\_ENABLE: true  
#EF\_PROCESSOR\_DECODE\_SFLOW\_FLOWS\_KEEP\_SAMPLES: true  
#EF\_PROCESSOR\_DECODE\_SFLOW\_COUNTERS\_ENABLE: true  
EF\_PROCESSOR\_DECODE\_MAX\_RECORDS\_PER\_PACKET: 8192  
EF\_PROCESSOR\_ENRICH\_ASN\_PREF: flow  
EF\_PROCESSOR\_ENRICH\_JOIN\_ASN: true  
EF\_PROCESSOR\_ENRICH\_JOIN\_GEOIP: true  
EF\_PROCESSOR\_ENRICH\_JOIN\_SUBNETATTR: true  
EF\_PROCESSOR\_ENRICH\_JOIN\_SEC: true  
EF\_PROCESSOR\_EXPAND\_CLISRV: true  
EF\_PROCESSOR\_EXPAND\_CLISRV\_NO\_L4\_PORTS: true  
#EF\_PROCESSOR\_IFA\_ENABLE: false  
#EF\_PROCESSOR\_IFA\_WORKER\_SIZE: 4000

EF\_PROCESSOR\_ENRICH\_APP\_ID\_ENABLE: true  
EF\_PROCESSOR\_ENRICH\_APP\_ID\_PATH: /etc/elastiflow/app/appid.yml  
EF\_PROCESSOR\_ENRICH\_APP\_ID\_TTL: 7200  
EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_ENABLE: false  
EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PATH: /etc/elastiflow/app/ipport.yml  
EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_TTL: 7200  
EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PRIVATE: true  
EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PUBLIC: false  
EF\_PROCESSOR\_ENRICH\_APP\_REFRESH\_RATE: 15

EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_ENABLE: false  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_NAMESERVER\_IP: 8.8.8.8  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_NAMESERVER\_TIMEOUT: 3000  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_RESOLVE\_PRIVATE: true  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_RESOLVE\_PUBLIC: true  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_USERDEF\_PATH: /etc/elastiflow/hostname/user\_defined.yml  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_USERDEF\_REFRESH\_RATE: 15  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_INCLEXCL\_PATH: /etc/elastiflow/hostname/incl\_excl.yml  
EF\_PROCESSOR\_ENRICH\_IPADDR\_DNS\_INCLEXCL\_REFRESH\_RATE: 15

EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_ASN\_ENABLE: true  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_ASN\_PATH: /etc/elastiflow/maxmind/GeoLite2-ASN.mmdb  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_ENABLE: true  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_PATH: /etc/elastiflow/maxmind/GeoLite2-City.mmdb  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_VALUES: city,country,country\_code,location,timezone  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_LANG: en  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_INCLEXCL\_PATH: /etc/elastiflow/maxmind/incl\_excl.yml  
EF\_PROCESSOR\_ENRICH\_IPADDR\_MAXMIND\_GEOIP\_INCLEXCL\_REFRESH\_RATE: 15

EF\_PROCESSOR\_ENRICH\_NETIF\_FLOW\_OPTIONS\_ENABLE: true  
EF\_FLOW\_DATA\_PATH: /var/lib/elastiflow/flowcoll

EF\_PROCESSOR\_ENRICH\_SAMPLERATE\_CACHE\_SIZE: 65535  
#EF\_PROCESSOR\_ENRICH\_SAMPLERATE\_USERDEF\_ENABLE: false  
#EF\_PROCESSOR\_ENRICH\_SAMPLERATE\_USERDEF\_PATH: /etc/elastiflow/settings/sample\_rate.yml  
#EF\_PROCESSOR\_ENRICH\_SAMPLERATE\_USERDEF\_OVERRIDE: false

EF\_PROCESSOR\_POOL\_SIZE: 32  
EF\_PROCESSOR\_TRANSLATE\_KEEP\_IDS: all  
EF\_PROCESSOR\_DURATION\_PRECISION: ms  
#EF\_PROCESSOR\_DROP\_FIELDS:  
EF\_OUTPUT\_MONITOR\_ENABLE: true  
EF\_OUTPUT\_MONITOR\_INTERVAL: 30  
EF\_OUTPUT\_ELASTICSEARCH\_ENABLE: true  
EF\_OUTPUT\_ELASTICSEARCH\_ECS\_ENABLE: true  
EF\_OUTPUT\_ELASTICSEARCH\_BATCH\_DEADLINE: 2000  
EF\_OUTPUT\_ELASTICSEARCH\_BATCH\_MAX\_BYTES: 8388608  
EF\_OUTPUT\_ELASTICSEARCH\_TIMESTAMP\_SOURCE: collect #default is [end]  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_PERIOD: rollover  
#EF\_OUTPUT\_ELASTICSEARCH\_TSDS\_ENABLE:  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_SUFFIX: szho-elastiflow  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_TEMPLATE\_ENABLE: true  
#EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_TEMPLATE\_OVERWRITE: false  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_TEMPLATE\_SHARDS: 3  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_TEMPLATE\_REPLICAS: 1  
EF\_OUTPUT\_ELASTICSEARCH\_INDEX\_TEMPLATE\_REFRESH\_INTERVAL: 20s  
EF\_OUTPUT\_ELASTICSEARCH\_ADDRESSES: x.x.x.x:9200  
EF\_OUTPUT\_ELASTICSEARCH\_USERNAME: yyyyy  
EF\_OUTPUT\_ELASTICSEARCH\_PASSWORD: zzzzz  
#EF\_OUTPUT\_ELASTICSEARCH\_TLS\_ENABLE: false  
#EF\_OUTPUT\_ELASTICSEARCH\_TLS\_SKIP\_VERIFICATION: false  
#EF\_OUTPUT\_ELASTICSEARCH\_TLS\_CA\_CERT\_FILEPATH:  
#EF\_OUTPUT\_ELASTICSEARCH\_DROP\_FIELDS:

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 12, 2025, 10:27am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/2 "2025-11-12T10:27:34Z")

</div>

some output from the metric report

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/3af2ec47880d79c8556f452220b248393f7da5fe.png)

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [November 12, 2025, 2:33pm UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/3 "2025-11-12T14:33:33Z")

</div>

Based on the log sample I would say the flow collector is running normally and that the issue is with the device(s) sending flow data. You can collect a tcpdump on the flow collector server to see what is actually being received by doing the following:

_ **find the appropriate interface name** _

`dxturner@mg-lab:~$ ip addr show`  
`1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000`  
`link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00`  
`inet 127.0.0.1/8 scope host lo`  
`valid_lft forever preferred_lft forever`  
`inet6 ::1/128 scope host noprefixroute`  
`valid_lft forever preferred_lft forever`  
`2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000`  
`link/ether b4:2e:99:f0:85:70 brd ff:ff:ff:ff:ff:ff`  
`altname enp3s0`  
`inet 192.168.1.10/24 brd 192.168.1.255 scope global eno1`  
`valid_lft forever preferred_lft forever`  
`inet6 fe80::b62e:99ff:fef0:8570/64 scope link`  
`valid_lft forever preferred_lft forever`  
`3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000`  
`link/ether 78:2b:46:2d:a3:ca brd ff:ff:ff:ff:ff:ff`  
`inet 192.168.1.164/24 metric 600 brd 192.168.1.255 scope global dynamic wlp4s0`  
`valid_lft 85675sec preferred_lft 85675sec`  
`inet6 fe80::7a2b:46ff:fe2d:a3ca/64 scope link`  
`valid_lft forever preferred_lft forever`

In this case, there are 3 interfaces … the loopback (lo), the wired interface (eno1), and the wireless interface (wlp4s0). Flow data will be received on the wired interface (192.168.1.10) so we will use eno1 in the tcpdump command.

**collect a packet capture using tcpdump**  
`sudo tcpdump -i eno1 -nn -s 0 -c 1000 -W 1 -G 300 -w netflow-packets.pcap ‘udp and (port 2055 or port 4739 or port 6343 or port 9995)’`

This will listen on interface eno1 (-i eno1), capture the entire packet (-s 0), stop collecting after 1000 packets (-c 1000), stop collecting after 5 minutes (-G 300), write the output to a file named ‘netflow-packets.pcap (-w) and only collect UDP packets on ports 2055,4739,6343, or 9995.

Once you collect the packet capture you can open it using Wireshark to see what is being received. If want to share it with me directly I’d be happy to review. The full flow collector logs would be helpful, too.

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 13, 2025, 10:16am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/4 "2025-11-13T10:16:37Z")

</div>

I can see the continually sflow data during the 5 mins packet cature. But the kibana still only seen 1 min for 256 record… Should I also capture the same at the ELK side?

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/e521fce834e8fbfb41401894ac74e92013763dba.png)

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 13, 2025, 10:18am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/5 "2025-11-13T10:18:57Z")

</div>

kibana

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/a3c04db287b7f8de5aad0c987f71bb4b4330060a.png)

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 13, 2025, 10:19am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/6 "2025-11-13T10:19:35Z")

</div>

![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/ff6c5c140850e24c60932ae17c4ad88068fd9290.png)

ip address and packet capture command

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 13, 2025, 10:43am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/7 "2025-11-13T10:43:36Z")

</div>

The full flowcoll log too large, how can i deliver to you if you want?

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 19, 2025, 1:33am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/8 "2025-11-19T01:33:32Z")

</div>

Hi Sir, would like to hear from you if any good news 🙂

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [November 19, 2025, 2:34pm UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/9 "2025-11-19T14:34:12Z")

</div>

I sent you a direct message here with my email address where you can send any compressed log files or pcaps.

---

<div class="post-metadata">

**Author:** ![vincenttt7](https://avatars.discourse-cdn.com/v4/letter/v/e99b99/32.png) [@vincenttt7](https://forum.elastiflow.com/u/vincenttt7)\
**Post date:** [November 24, 2025, 10:25am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/10 "2025-11-24T10:25:39Z")

</div>

I just upgrade the flow-collector from 7.19.0 to 7.19.2 and solve this issue. no change made to /etc/elastiflow/flowcoll.yml.

Now It’s collecting flow data normally. Thanks a lot 🙂

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/e4c7ab6f71f9c650e583ee7a7cbf54cd73bf54ee.png)

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.elastiflow.com/system/32/59_2.png) [@system](https://forum.elastiflow.com/u/system)\
**Post date:** [December 24, 2025, 10:26am UTC](https://forum.elastiflow.com/t/flow-processor-to-output-writer-is-90-full-while-monitor-output-decoding-rate-0-records-second/347/11 "2025-12-24T10:26:18Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.