Thread
#prefect-community
    c

    Charles Leung

    1 year ago
    Hey Team, When our agents go down due to a hosed host, we find that we can get an email notification via automations setup (agent is unhealthy). However, when we change it to pagerduty, we find we do not get alerts. How can we resolve this?
    Kevin Kho

    Kevin Kho

    1 year ago
    Hey @Charles Leung, was the schedule of these flows created before the pagerduty alert was created
    Wait, you work with Krapi right? Is it this same issue as this ?
    c

    Charles Leung

    1 year ago
    Hey Kevin this is not a flow alert, this is an unhealthy agent alert
    Jenny

    Jenny

    1 year ago
    Hi Charles - have you confirmed that the pagerduty action works with other automations or with the test_action mutation: Find action ID by running:
    query {
      action {
        id
        name
        action_type
      }
    }
    Then you can test the action by using:
    mutation {
      test_action (input: {action_id: ""}){
        success
      }
    }
    c

    Charles Leung

    1 year ago
    Hey Jenny! Yes we have pagerduty actions on our flows that work great
    Jenny

    Jenny

    1 year ago
    Hmmm... Are there any messages about that automation in your notifications tile on the dashboard?
    c

    Charles Leung

    1 year ago
    @Callum Okuefuna Hey Callum! Jenny is assisting us with this issue - could you provide detail if you've seen any notifications on this?
    c

    Callum Okuefuna

    1 year ago
    I haven't seen anything to do with unhealthy agent via pagerduty. The test I performed was to attach the agent to a config-group and bring it down, and we got no notifications through
    I also did the same with email alerts and it worked
    Jenny

    Jenny

    1 year ago
    hI @Callum Okuefuna - can you check the notifications tile on your dashboard - if there's an issue with an automation we send a message there. If there's a notification there it should give us more info to work from.
    Also can you confirm that the agent config connected to your pagerduty automation is correctly set on your agent - you can see that in the config tab on your agent page:
    c

    Charles Leung

    1 year ago
    Hey Jenny! Thanks this is resolved now - we are working on integrating it with our ansible roles.
    Jenny

    Jenny

    1 year ago
    Great. Thanks for the udpate!