Description:

In the current LMOS Operator implementation, a Channel may enter an unresolved state when its required capabilities cannot be matched with the available Agent resources. While the runtime still allows communication through unresolved Channels, there is no alerting mechanism to notify users or administrators about this unresolved state.

Problem:

• When a Channel becomes unresolved, there is currently no way to easily monitor or detect that the Channel's required capabilities cannot be met.
• This could lead to unnoticed issues where Channels may not function properly or may miss important capabilities.

Proposed Solution:

• Implement an alerting mechanism that triggers when a Channel is in an unresolved state.
• Alerts can be sent to a monitoring system, log, or notification service to inform the relevant stakeholders about the unresolved Channel.
• The alert should include details such as:
  • The Channel name
  • The capabilities that couldn't be resolved
  • The reason for the unresolved state (e.g., missing Agent or incompatible capability versions)

Impact:

• Provides visibility into unresolved Channels, enabling quicker detection and resolution of potential issues.
• Ensures that administrators or users are alerted when critical Channels are not meeting their requirements.
• Improves monitoring and observability of the LMOS Operator and its interactions with Channels and Agents.

Expected Behavior:

• When a Channel enters an unresolved state, an alert should be triggered and delivered to the configured monitoring or notification system.
• The alert should contain sufficient information to help diagnose the root cause of the unresolved state.