标签扩展 about hertzbeat HOT 9 CLOSED

这两天又进一步用了用，深切喜欢这个软件 🥰🥰～

哦对了，前面提到的 tdengine 是说我本地 macOS 没有用 docker 的情景下，没能跑起来，最终还是在我私人 linux 服务器上跑的 tdengine（可能我不懂这个 tdengine），怪我前面没有描述清楚～😅😅，不过这个不重要了～

我的搭建环境，除了 tdengine 没在本地，其余都在本地

另一个不好意思的地方，是过滤条件我发现咱其实也有，只是在最上方，之前没注意到

不过，我觉得该功能还是可以再优化的，详情见下属建议第 1 点。

但是根据我个人的使用，我又想提出几点建议，也希望作者能考虑考虑 🤞。

1. 页面全局监控搜索：比如我的资源名称：TELNET_10.10.10.100_随便节点服务器_8088 ，我搜索中文“随便”等，可能没有结果，搜索“8088” 也没有结果 😔

2. 列表种时间展示问题，最好标准成： yyyy-MM-dd HH:mm:ss 这样的格式（年月日 时分秒，24 小时制），当前的展示确实不利于查看，诺：
   

3. 数据库监控，总会超时，探测都是 OK 的
   这个情景是由于我使用了公司的 VPN，本地直接连接公司数据库都是走 VPN 的，当然我本地通过数据库可视化工具连接什么的都没问题，这个应该是我这边的问题，不过这个超时时间，如果长点会不会解决我这个情景的问题呢？ 🤔

Emmmm， 监测 本地 127.0.0.1 数据库也会超时。。。😢

有时候它又会恢复，如下图：

from hertzbeat.

哈哈感谢🙏这些建议，很开心能得到这样的评价。

1. 页面全局监控搜索：比如我的资源名称：TELNET_10.10.10.100_随便节点服务器_8088 ，我搜索中文“随便”等，可能没有结果，搜索“8088” 也没有结果 😔

这个看样子是个BUG 我后面修复下。

2. 列表种时间展示问题，最好标准成： yyyy-MM-dd HH:mm:ss 这样的格式（年月日 时分秒，24 小时制），当前的展示确实不利于查看

get 这个要改下 现在是直接用的UTC时间 不便于查看。

4. 数据库监控，总会超时，探测都是 OK 的.

这个我去复现下看是不是BUG或者其它配置原因。 目前time-out是写死的，那我下一版本把timeout暴露出来让可配置

from hertzbeat.

哈哈 给这么详细的体验描述点赞，tdengine我本地可以docker起来，谢谢监控列表那块的建议，后面把查询过滤条件功能加上，tag的这个建议可以有，我在其它系统也看到过。👍👍

from hertzbeat.

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

I have used it further in the past two days, I really like this software 🥰🥰～

Oh, by the way, the tdengine mentioned above means that I couldn't run it when I didn't use docker on my local macOS, and I ended up running tdengine on my private linux server (maybe I don't I understand this tdengine), blame me for not describing it clearly before😅😅, but this is not important

My build environment, except tdengine is not local, the rest are local

Another embarrassing place is that I found that we actually have the filter conditions, but they are at the top, I didn't notice it before

However, I think this function can still be optimized. For details, see point 1 of the subordinate's suggestion.

But according to my personal use, I would like to make a few more suggestions, and I hope the author will consider it 🤞.

1. Global monitoring search on the page: For example, my resource name: TELNET_10.10.10.100_any node server_8088, I search for Chinese "casual", etc., there may be no results, search for "**8088 **” also no results 😔

2. List time display problems, the best standard is: yyyy-MM-dd HH:mm:ss format (year, month, day, hour, minute, second, 24-hour format), the current display is indeed not conducive to viewing, promise:
   

3. Database monitoring always times out, and the detection is OK
   This scenario is due to the fact that I use the company's VPN, and the local direct connection to the company's database is through VPN. Of course, I can connect locally through the database visualization tool. This should be the problem on my side, but this timeout period, Would it solve the problem for my scenario if it was longer? 🤔

from hertzbeat.

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

Haha thanks 🙏 for these suggestions, I am very happy to get such a review.

1. The global monitoring search of the page: For example, my resource name: TELNET_10.10.10.100_any node server_8088, I searched for Chinese "casual", etc., there may be no results, and there is no result for "8088" 😔

This seems to be a bug, I will fix it later.

2. List time display problems, the best standard is: yyyy-MM-dd HH:mm:ss format (year, month, day, hour, minute, second, 24-hour format), the current display is indeed not conducive to viewing

get This needs to be changed. Now it is the UTC time directly used, which is not easy to view.

4. Database monitoring always times out, and the detection is OK.

I will reproduce this to see if it is a bug or other configuration reasons. At present, the time-out is hard-coded, so I will expose the timeout in the next version so that it can be configured.

from hertzbeat.

我觉得如果是vpn链接的话 这种的我们可以提供一个范围值，做成一个可接受的ping值范围

from hertzbeat.

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

I think if it is a vpn link, we can provide a range value to make an acceptable ping value range

from hertzbeat.

support #111 next version v1.0.beat.8

from hertzbeat.

hi tags manage support with v1.0-beat.8 https://github.com/dromara/hertzbeat/releases/tag/v1.0-beta.8

from hertzbeat.