docs: filters: log_to_metrics: general doc updates and cleanup#2565
Conversation
Add an "Operational considerations" section covering long-running
pipeline behavior that isn't visible in short-lived tests:
- cardinality and process-lifetime state retention for counter/gauge,
with guidance to pre-aggregate high-cardinality fields upstream
- how to monitor the internal emitter via /api/v1/metrics and what a
stalled emitter looks like
- emitter_mem_buf_limit pause semantics and mitigation knobs
- counter reset behavior across restarts and how Prometheus consumers
should query counters
Fixes fluent#2551
Signed-off-by: Eric D. Schabell <eric@schabell.org>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 37 minutes and 3 seconds.Comment |
|
Merging as reviewer approved. |
Add an "Operational considerations" section covering long-running
pipeline behavior that isn't visible in short-lived tests:
Fixes #2551