We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloudeye-exporter正常运行,通过访问metrics接口能正常获取指定云服务指标数据。
如果此时ECS服务新创建一台机器。 5min后,通过访问cloudeye-exporter的metrics接口 无法获取到该机器的任何指标信息。
如果此时重启cloudeye-exporter进程,在进行访问,就能获取指标。
如果后面该ecs 机器删除了。如果访问cloudeye-exporter metrics接口 依然能获取到该机器相关指标 需要再次重启cloudeye-exporter进程才能获取实际情况的指标
不光监控ECS会出现这样的情况,ELB如果新创监听器cloudeye-exporter也会获取不到新的监听器指标。考虑真实使用场景不可能每次新创云服务资源,都要重启下cloudeye-exporter进程的。
The text was updated successfully, but these errors were encountered:
你好,这个是由于 查询实例信息的时候exporter中做了缓存,目前默认缓存3小时,3小时后会自动更新
Sorry, something went wrong.
No branches or pull requests
基础环境
问题描述
cloudeye-exporter正常运行,通过访问metrics接口能正常获取指定云服务指标数据。
如果此时ECS服务新创建一台机器。
5min后,通过访问cloudeye-exporter的metrics接口 无法获取到该机器的任何指标信息。
如果此时重启cloudeye-exporter进程,在进行访问,就能获取指标。
如果后面该ecs 机器删除了。如果访问cloudeye-exporter metrics接口 依然能获取到该机器相关指标
需要再次重启cloudeye-exporter进程才能获取实际情况的指标
请问这种情况该怎么解决?
不光监控ECS会出现这样的情况,ELB如果新创监听器cloudeye-exporter也会获取不到新的监听器指标。考虑真实使用场景不可能每次新创云服务资源,都要重启下cloudeye-exporter进程的。
The text was updated successfully, but these errors were encountered: