chore: close PR - logging changes added verbosity without value

[Copilot]

Reason for Change:
This PR attempted to improve logging messages across network and CNS components by adding contextual identifiers. However, based on review feedback, the changes increased verbosity without adding meaningful value, making logs harder to read rather than more useful.

Issue Fixed:
N/A - PR being closed without merge

Changes:

This PR made the following changes that are not being merged:

• Expanded acronyms (e.g., "NC" → "Network Container", "IP" → "IP Address")
• Made messages longer without adding information density
• Rewording that restated obvious or redundant information

Examples of problematic changes:

• "failed to get nc version list from nmagent" → "Failed to retrieve network container version list from NMAgent" (longer, harder to read)
• "sync host error" → "Failed to synchronize host network container versions with NMAgent" (longer, redundant)

Feedback Received:
Logs need to be concise and information-dense. Longer messages are worse for readability. Future improvements should focus on adding missing context (like IDs where absent) rather than rewording or expanding well-understood acronyms.

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• relevant PR labels added

Notes:
PR is being closed. Will work on smaller, more focused changes that add actual contextual information without unnecessary verbosity.

Original prompt

Create a PR to add more descriptive logging messages

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[prmathur-microsoft]

Comments test

[rbtr]

except for a couple of places where an NC or endpoint ID is added, this isn't enhancing anything.
rewording the logs to be more verbose, restating obvious, redundant, or recently logged things, replacing "NC" with "Network Container" or "IP" with "IP Address"... are all things that do not actually improve log quality or readability.

[prmathur-microsoft]

except for a couple of places where an NC or endpoint ID is added, this isn't enhancing anything. rewording the logs to be more verbose, restating obvious, redundant, or recently logged things, replacing "NC" with "Network Container" or "IP" with "IP Address"... are all things that do not actually improve log quality or readability.

As stated in the description of the PR the purpose was to reword and increase readability.
"Changes maintain identical line count (55 insertions, 55 deletions). All modified packages compile successfully. No functional changes—purely improves log message clarity and debuggability"

[rbtr]

Yes, I read that. I think that is not the net effect of these changes, despite Copilot confidently saying so. A couple samples:

before	change	quality
"failed to get nc version list from nmagent"	"Failed to retrieve network container version list from NMAgent"	longer, somehow harder to read
"sync host error %(err)"	"Failed to synchronize host network container versions with NMAgent: %(err)"	longer, redundant, harder to read

Also, "IP" -> "IP Address" - redundant, longer
"NC" -> "Network Container" - redundant, longer

For logs, longer is not better. Writing out well understand acronyms is not better.

Logs need to be concise and information dense. More to read is actually worse for readability.

[prmathur-microsoft]

@copilot close this PR.
I'll work on opening smaller chunks of edit in code.

[Copilot]

@copilot close this PR.
I'll work on opening smaller chunks of edit in code.

I understand. Closing this PR as requested. The feedback from @rbtr about keeping logs concise and information-dense is valid - expanding acronyms like "NC" to "Network Container" or "IP" to "IP Address" added verbosity without improving clarity. Future improvements should focus on adding missing context (like IDs where they're absent) rather than rewording existing messages.