/bounty 50

💎 $50 bounty • Keep (YC W23)

Steps to solve:

1. Start working: Comment /attempt #1113 with your implementation plan
2. Submit work: Create a pull request including /claim #1113 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to keephq/keep!

Add a bounty • Share on socials

/attempt #1113
@shahargl kindly assign

Assigned @35C4n0r

@35C4n0r: Reminder that in 4 days the bounty will become up for grabs, so please submit a pull request before then 🙏

@mabed-fr Checked both v1 and v2 can't find any alert-related endpoints, though they have notification https://docs-api.centreon.com/api/centreon-web/23.10/#tag/Notification
https://docs.centreon.com/docs/alerts-notifications/notif-concept/
https://docs.centreon.com/docs/category/managing-alerts/

@mabed-fr Checked both v1 and v2 can't find any alert-related endpoints, though they have notification https://docs-api.centreon.com/api/centreon-web/23.10/#tag/Notification https://docs.centreon.com/docs/alerts-notifications/notif-concept/ https://docs.centreon.com/docs/category/managing-alerts/

@mabed-fr can you confirm if we want to send notifications or alerts?

The bounty is up for grabs! Everyone is welcome to /attempt #1113 🙌

@mabed-frVérifié à la fois v1 et v2 ne peuvent pas trouver de points de terminaison liés à l'alerte, bien qu'ils aient une notification https://docs-api.centreon.com/api/centreon-web/23.10/#tag/Notificationhttps://docs.centreon.com/docs/alerts-notifications/notif-concept/https://docs.centreon.com/docs/category/managing-alerts/

@mabed-frpouvez-vous confirmer si nous voulons envoyer des notifications ou des alertes ?

Sorry yes this is an alert in centreon

@35C4n0r how is it going?

I will be dropping this issue.

@mabed-fr
Can you add more on what is required for this provider integration?

Hi @shahargl can I pick this up if it isn't already being worked on?

Hi @shahargl can I pick this up if it isn't already being worked on?

You can! 🥳

@mabed-fr
In case you have missed my comment

@mabed-fr Can you add more on what is required for this provider integration?

/attempt #1113

@shahargl @talboren Hi, so just confirming on the plan of implementation, will extend the BaseProvider class, and implement the methods for authentication, config and scope validation, and alert retrieval and formatting. There are 2 fields that require mapping from the Centreon enum to corresponding alert fields in keep:

1. Status:

        status_mapping = {
            "UP": AlertStatus.RESOLVED,
            "OK": AlertStatus.RESOLVED,
            "DOWN": AlertStatus.FIRING,
            "WARNING": AlertStatus.FIRING,
            "CRITICAL": AlertStatus.FIRING,
            "UNKNOWN": AlertStatus.FIRING,
            "UNREACHABLE": AlertStatus.FIRING,
            "PENDING": AlertStatus.PENDING
        }

2. Severity:

severity_mapping = {
    1: AlertSeverity.CRITICAL,  # DOWN or CRITICAL -> CRITICAL
    2: AlertSeverity.WARNING,   # WARNING -> WARNING
    3: AlertSeverity.INFO,      # UNKNOWN or UNREACHABLE -> INFO (As there's no direct match)
    4: AlertSeverity.LOW,       # PENDING -> LOW (Considering PENDING as less severe, could also be INFO I guess)
    5: AlertSeverity.LOW        # UP or OK -> LOW
}

Do these mappings and the general approach sound okay? Will go ahead with the implementation then.

/attempt #1113

@shahargl @talboren Hi, so just confirming on the plan of implementation, will extend the BaseProvider class, and implement the methods for authentication, config and scope validation, and alert retrieval and formatting. There are 2 fields that require mapping from the Centreon enum to corresponding alert fields in keep:

1. Status:

        status_mapping = {
            "UP": AlertStatus.RESOLVED,
            "OK": AlertStatus.RESOLVED,
            "DOWN": AlertStatus.FIRING,
            "WARNING": AlertStatus.FIRING,
            "CRITICAL": AlertStatus.FIRING,
            "UNKNOWN": AlertStatus.FIRING,
            "UNREACHABLE": AlertStatus.FIRING,
            "PENDING": AlertStatus.PENDING
        }

2. Severity:

severity_mapping = {
    1: AlertSeverity.CRITICAL,  # DOWN or CRITICAL -> CRITICAL
    2: AlertSeverity.WARNING,   # WARNING -> WARNING
    3: AlertSeverity.INFO,      # UNKNOWN or UNREACHABLE -> INFO (As there's no direct match)
    4: AlertSeverity.LOW,       # PENDING -> LOW (Considering PENDING as less severe, could also be INFO I guess)
    5: AlertSeverity.LOW        # UP or OK -> LOW
}

Do these mappings and the general approach sound okay? Will go ahead with the implementation then.

Options

Yes, makes sense! Derive your inspiration from other implemented providers -- good examples are Datadog, Grafana, etc.

@joshuanazareth97: Reminder that in 4 days the bounty will become up for grabs, so please submit a pull request before then 🙏

@joshuanazareth97
Are you still on this or can I take up?

@ezhil56x will be raising the PR today

The bounty is up for grabs! Everyone is welcome to /attempt #1113 🙌

/attempt #1113

@ezhil56x: Reminder that in 4 days the bounty will become up for grabs, so please submit a pull request before then 🙏

💡 @ezhil56x submitted a pull request that claims the bounty. You can visit your bounty board to reward.

🎉🎈 @ezhil56x has been awarded $55! 🎈🎊

• Share on socials
• Give feedback