Skip to content

Background Service: Workload Node Monitoring #1031

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zaelgohary opened this issue May 21, 2025 · 2 comments
Open

Background Service: Workload Node Monitoring #1031

zaelgohary opened this issue May 21, 2025 · 2 comments
Assignees
Milestone

Comments

@zaelgohary
Copy link
Contributor

as a user I'd like to know if any of my workloads' VMs went offline

@zaelgohary zaelgohary self-assigned this May 21, 2025
@zaelgohary zaelgohary added this to the 4.4.x milestone May 21, 2025
@zaelgohary
Copy link
Contributor Author

WIP:

Did changes in grid proxy in contract params to be a list of contract state instead of a string. Applied changes in the app and created getWorkloadNodesState in the check node service. Also, did some refactors.

@zaelgohary
Copy link
Contributor Author

zaelgohary commented May 22, 2025

Work Completed:

Key Features & Enhancements:

  • Wallet & User ID:
    • Integrated twinId into the Wallet.
    • Made twinId a required field.
  • Workload Node Monitoring & Notifications:
    • Added notifications for workload node status. 🔔
    • Implemented _checkWorkloadNodesAndNotify for background monitoring.
    • Added pingWorkloadNodes functionality.
  • Refactoring & Internal Improvements:
    • Renamed several background task methods for better clarity.
    • Refactored the NotificationService.
    • Updated the Grid Proxy reference.

UI Changes:

  • Updated the icon for workload-related elements.

Bug Fixes:

  • Addressed a null error.
  • Fixed notifications dismissal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant