[BUG] Why does "NO DATA" appear in some DNS service monitors?
- Dominant language
- Java
- Stars
- 7.4k
- Forks
- 1.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 32
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current Behavior
It seems that the monitoring job is not running!
It feels like there is a very significant delay in the monitoring job.
It's not just DNS; other services like Prometheus monitoring also frequently show "NO DATA", and it takes a long time before data becomes visible.
We are currently downloading the source code and compiling it ourselves.
### Expected Behavior
_No response_
### Steps To Reproduce
_No response_
### Environment
```markdown
HertzBeat version(s):1.7.3+
```
### Debug logs
_No response_
### Anything else?
_No response_
Contributor guide
Research direction
Start by reproducing the delayed or missing data behavior on HertzBeat 1.7.3+ and inspect the monitoring job and available logs. Compare DNS and Prometheus monitors to determine whether the job is running; done means monitoring data appears reliably without the reported delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100