Duansg commented on issue #3904: URL: https://github.com/apache/hertzbeat/issues/3904#issuecomment-3646144011
@NewNimo Thanks, got it. > The first issue you are concerned about 1. Not necessarily; recovery notifications may be subject to the `group_interval` restriction. 2. If certain alarms exhibit jitter, it may generate a large number of real-time recovery alerts. Consider adding a configuration option in the future to allow users to choose whether to enable this behavior. 3. The determination of the same aggregation group is based solely on: label + label value 4. In the logic for group convergence, correlation processing has already been implemented for alarm recovery. 5. Ibid. > The second issue you raised What I mean is that the tags you see are merely the commonly used tags recommended by hzb. Regarding the example you provided, if you're monitoring tasks integrated via Prometheus, your understanding of the `job` label is correct. However, if the monitoring involves custom templates or other types of templates, the meaning of this `job` depends on the label configuration of the template or the labels of the collected metrics. For instance, in certain custom business metrics, `job` may also serve as the name of a scheduled task. The meaning of this label cannot be exhaustively defined for you; you must configure it as needed based on the current context. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
