Add configurable alert to print log statement warning of missing TIMs deposits

[mcook42]

PR Details

Description

We have added support for logging WARN level messages to indicate when we have not received any TIMs messages through our TimDepositController. The monitoring and the interval at which the monitor runs are both configurable via environment variables. I have also marked the executable scripts (like mvnw) as executable in the git index so that developers don't need to chmod +x the scripts whenever they want to run them.

Related Issue

No relevant GitHub Issue, but there is one for CDOT:

Modify ODE to log warning upon not receiving data for a configurable duration
https://dev.azure.com/SOC-OIT/CDOT/_workitems/edit/229495

Motivation and Context

As developers and maintainers of the ODE systems, we want a way to detect when we have lost connectivity or are not receiving data via the TimsDepositController. This will help us identify connectivity issues with WZDX and be proactive about resolving these issues.

How Has This Been Tested?

Unit tests were added where feasible to confirm code functions as intended. Where unit tests were not feasible, like in the case of log messages being emitted, local tests were run to simulate TIMs deposits and view the appropriate log messages. See the following screenshots of logs for more information:

• No TIMs ingested scenario (first screenshot is the environment variable settings):
  

• TIMs ingested for 30 seconds then not ingested for 15 to show changing states over time are still tracked and alerted on (DEBUG level so these messages are not written to logs in production unless configured):

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  ODE Contributing Guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[dmccoystephenson]

Looks good, just a few questions!

[mwodahl]

This all looks great! I just had a couple of questions

[dmccoystephenson]

The solution looks good overall, and the unit tests are passing! I just left a comment about a mismatch between the environment variable names in sample.env and docker-compose.yml, along with a suggestion to handle the empty string case for the variable.

[mwodahl]

Looks good!

[dmccoystephenson]

Looks good to me!