[database watcher] Pad time interval to include a successful probe #2854
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Problem
When all connectivity probes in a time range have failed, no data is displayed on the Connectivity dashboards. This happens because the SQL target identifiers such as logical server name and database name are not available in the failed probe data.
Solution
Expand (pad) the time range to increase the probability of finding a successful probe with the required SQL target identifiers.
Validation
Checklist
When done correctly, this means that from then on your team does reviews of your things, not the workbooks team.