Correct error logging format in InitMonitor function

[BruceAko]

Description

Correct error logging format in InitMonitor function.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 34.43%. Comparing base (ae76b12) to head (474223f).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/dependency/dependency.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4046      +/-   ##
==========================================
+ Coverage   34.40%   34.43%   +0.02%     
==========================================
  Files         343      343              
  Lines       40211    40211              
==========================================
+ Hits        13835    13845      +10     
+ Misses      25459    25453       -6     
+ Partials      917      913       -4     

Flag	Coverage Δ
unittests	34.43% <0.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
cmd/dependency/dependency.go	0.00% <0.00%> (ø)

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Liam-Zhao]

LGTM

[gaius-qi]

LGTM