Closed matchai closed 2 years ago
It looks like this is certainly caused by #76. Unfortunately, the disk I/O caused by cloudplow uploads is directly affecting my ability to run Plex streams. I would love to see the ability to configure the local check.
Merged.
Describe the bug Cloudplow always logs that there are "0 playing stream(s)" despite there being actively playing streams.
This occurs despite the logs saying that the "Plex Media Server URL + Token were validated":
To Reproduce Steps to reproduce the behavior:
plex.max_streams_before_throttle
to 1Expected behavior A clear and concise description of what you expected to happen.
Throttling begins to kick in at the increased thresholds, matching the number of Plex streams playing.
Logs
Despite there being active "playing" streams, they aren't being accounted for by Cloudplow:
System Information