paulelong / windows-time-calibration-tools Goto Github PK

The output should include an IP address, expected name as columns for each record. This is important because IP addresses can change. The data can then be consumed by IP address or Friendly Name.

Additionally we should include the IP reversed lookup DNS name. This will help diagnose DNS issues when the data is collected.

I noticed I wasn't able to find records for servers we are monitoring. It would be useful to have more information to understand why there is not record recorded.

Reasons could be:

1. It didn't resolve to any IP address
2. Server didn't respond to NTP query

We should continue to keep the same format, perhaps adding another column with an error? Perhaps the start/end/time would all be zero as an indication?

Right now it shows MonitorService.exe which is generic.

Targeting an IP address is preferable in many instances. The friendly name might also be important, but there could be multiple addresses. This change is to allow the configuration to include:
[Name]
IPAddress : REG_SZ
Expected DNS Name: REG_SZ
Polling Frequency: REG_DWORD

Where [Name] is a friendly user defined name for the monitoring target.