Saramanda9988 commented on issue #3765: URL: https://github.com/apache/hertzbeat/issues/3765#issuecomment-3575796774
Hi @tomsun28 , thanks again for your patience. Regarding duplicate monitoring: You're right that while it's technically possible to configure multiple monitors for a single instance <img width="2146" height="623" alt="Image" src="https://github.com/user-attachments/assets/686eced1-7b2a-4d13-9e04-1357fe3117ec" /> <img width="1060" height="839" alt="Image" src="https://github.com/user-attachments/assets/4dd9c0f4-6519-44dd-bacf-b018fe22ce8c" /> It's possible to add validation rules to prevent this case, although in real-world usage I don't think users would intentionally configure it this way 😂 For now, continuing to use instance for querying historical metric data seems like the most pragmatic approach. About the label mappings, I’d like to propose the following adjustments: 1. Rename the current `instance` field (used for label strings) to `metric_labels`, which better reflects its actual meaning. The `instance` field, instead of `monitorEd`, will continue to represent the IP address and port of the monitored target. 2. Remove the label-query logic for the other five TSDB implementations. For GreptimeDB and VictoriaMetrics datasource, this label field is not used for querying anyway. 3. VictoriaMetrics datasource will no longer return the host (instance) to the frontend by `metric_labels`, matching the behavior of GreptimeDB. Also, I noticed there isn’t any configuration or documentation regarding QuestDB and TDengine in the official docs.Are we still planning to maintain compatibility with these two data sources going forward? -- 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: notifications-unsubscr...@hertzbeat.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@hertzbeat.apache.org For additional commands, e-mail: notifications-h...@hertzbeat.apache.org
