Sn0rt commented on issue #9627: URL: https://github.com/apache/apisix/issues/9627#issuecomment-1868853210
> @Sn0rt > > 1. I feel that if we ignore this problem, it also means that the problem that the metrics data keeps increasing cannot be solved. If the metrics are too large, there is still the problem that the privileged worker calculates the CPU time. Before this, our online environment (before APISIX transferred the Metrics computation to a special privileged worker) would restart APISIX every once in a while > 2. If it's not easy to introduce the TTL mechanism in the current APISIX, is it possible to dynamically delete the relevant Metrics when upstream and route are deleted? Thank you for your continued attention. After discussion with @membphis, I found that my previous understanding of metrics was wrong. We use the TTL scheme to recycle metrics that have not been reset for a long time, which has no impact on grafana's display. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
