gjjjj0101 commented on issue #2053: URL: https://github.com/apache/hertzbeat/issues/2053#issuecomment-2146347597
hi, I have some thoughts on your ideas：If we want to get the actual status immediately, we may need to send a one-time monitoring task to the collector, so that it can immediately return the results and display them to the user. However, this may cause a problem that if the user frequently refreshes immediately, many one-time collection tasks will be generated, causing or increasing the pressure on the collected service. > > hi, welcome. btw, what the refresh time is if we config, suggest not too short > > Hello, I have some ideas: > > 1. When a user creates a new monitor, its actual status should be displayed directly in the monitoring center. Currently, even if the monitor is unavailable, its status will only be updated after a monitoring cycle has passed. > 2. Users likely want to quickly know about changes in the status of a monitor. However, configuring a refresh time for each monitor individually is obviously impractical. If we set the automatic refresh time for all monitor statuses to be close to the most common monitoring cycle, such as 2 minutes, this seems a bit short. What negative impacts might this have? -- 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]
