Timezone conversion failed, falling back to UTC – OneAgent time‑zone handling

Error context

The OneAgent health log emits the warning "Timezone conversion failed, falling back to UTC" when the host’s IANA time‑zone database is missing or outdated. This causes the agent to treat all host timestamps as UTC, shifting metric timestamps relative to local time.

Goal: Ensure that metric timestamps remain accurate despite a missing or outdated zone file, while understanding whether the fallback behavior can be altered or escalated.

Constraints: The warning is only visible in agent logs; it does not automatically create a problem ticket in the default view, and there is no documented option to select an alternative fallback (e.g., retain local time or raise an alert).

• Is there a configuration setting to change the fallback behavior or to treat the warning as a problem?
• Can the warning be automatically escalated to a problem ticket via log monitoring?
• What verification steps confirm the impact on stored metric timestamps when the fallback occurs?