zxh326/clash-exporter

A prometheus exporter for clash

It's showtime, folks 👋

clash-exporter's Issues

read limited at 1048577 bytes

完整log

2023-06-27 13:37:07 2023/06/27 05:37:07 Listening on : 2112
2023-06-27 13:37:07 2023/06/27 05:37:07 starting collector: tracing
2023-06-27 13:37:07 2023/06/27 05:37:07 starting collector: connections
2023-06-28 02:01:59 2023/06/27 18:01:59 collector: connections failed, retry after 10s error: failed to read JSON message: failed to read JSON message: failed to read: read limited at 1048577 bytes
2023-06-28 02:02:09 2023/06/27 18:02:09 starting collector: connections
2023-06-28 11:44:08 2023/06/28 03:44:08 collector: connections failed, retry after 20s error: failed to read JSON message: failed to read JSON message: failed to read: read limited at 1048577 bytes
2023-06-28 11:44:28 2023/06/28 03:44:28 starting collector: connections
2023-06-28 16:25:56 2023/06/28 08:25:56 collector: connections failed, retry after 30s error: failed to read JSON message: failed to read JSON message: failed to get reader: failed to read frame header: EOF
2023-06-28 16:25:56 2023/06/28 08:25:56 collector: tracing failed, retry after 10s error: failed to read JSON message: failed to read JSON message: failed to get reader: failed to read frame header: EOF

clash重启后统计数据出现错乱

目前主要观察到总下载量的问题。
下午重启clash后，总下载量重新计数，不知道有没有办法解决？

clash exporter如何使用？

请问这里clash exporter和clash是怎么关联起来的呢，它是如何拿到clash的数据的？

Some data appears to be missing?

startup error in pve debian12

I get the following error in the boot log, can you help me take a look?

failed to dial: failed to WebSocket dial: expected handshake response status code 101 but got 404

grafana 无法连接 prometheus

除了前面的问题，我在docker 中运行的clash-exporter 会连接不上。release 的连接没有出现错误

..[$] <()> ./clash-exporter-v0.0.1-darwin-arm64
2023/06/26 16:42:41 Listening on : 2112
2023/06/26 16:42:41 starting collector: connections

高CPU占用

运行时发现CPU占用极高，同时带着clash的CPU占用上升

疑似是collector.Start有一个循环不断去收集数据，但该循环在部分情况下没有阻塞在 c.Collect，导致循环空转CPU占用极高

• 未开启 collectTracing 时，tracing.Collect 直接返回 nil
• info.Collect 请求版本信息后就返回 nil 了，导致一直在循环请求版本信息，clash本身的CPU占用也因此升高