GitHub user funky-eyes added a comment to the discussion: seata 事务的 metrics 是否会有以下问题；seata版本1.5.2
This is not an issue with Seata but rather with Prometheus. Prometheus does not use a push-based monitoring approach; instead, it collects data at regular intervals. When a restart occurs, monitoring data will inevitably be lost. You can mitigate this issue by adjusting Prometheus's scraping frequency, but it cannot be completely resolved. To achieve almost no data loss, you would need to use a time-series database like InfluxDB to store metrics and combine it with a graceful shutdown process. However, Seata does not support this. GitHub link: https://github.com/apache/incubator-seata/discussions/7555#discussioncomment-13884231 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
