https://prefect.io
Join Slack
We recently updated an automation to use <composite-triggers> in order to send out a Pager Duty inci...
# ask-community
c
We recently updated an automation to use composite-triggers in order to send out a Pager Duty incident, and we're seeing a change in behavior. 🧵
Our previous trigger was:
Copy code
{
  "type": "event",
  "match": {
    "prefect.resource.id": "prefect.flow-run.*"
  },
  "match_related": {
    "prefect.resource.id": [
      "prefect.tag.tag1",
      "prefect.tag.tag2"
    ],
    "prefect.resource.role": "tag"
  },
  "after": [],
  "expect": [
    "prefect.flow-run.TimedOut",
    "prefect.flow-run.Crashed",
    "prefect.flow-run.Failed"
  ],
  "for_each": [
    "prefect.resource.id"
  ],
  "posture": "Reactive",
  "threshold": 1,
  "within": 0
}
With an action that looks like what's shown in the screenshot; previously, the PD incidents it created had a title like shown in the screenshot.
We've since updated to the composite trigger:
Copy code
{
  "type": "compound",
  "triggers": [
    {
      "type": "event",
      "match": {
        "prefect.resource.id": "prefect.flow-run.*"
      },
      "match_related": {
        "prefect.resource.id": [
          "prefect.tag.tag1"
        ],
        "prefect.resource.role": "tag"
      },
      "after": [],
      "expect": [
        "prefect.flow-run.TimedOut",
        "prefect.flow-run.Failed",
        "prefect.flow-run.Crashed"
      ],
      "for_each": [
        "prefect.resource.id"
      ],
      "posture": "Reactive",
      "threshold": 1,
      "within": 0
    },
    {
      "type": "event",
      "match": {
        "prefect.resource.id": "prefect.flow-run.*"
      },
      "match_related": {
        "prefect.resource.id": [
          "prefect.tag.tag2"
        ],
        "prefect.resource.role": "tag"
      },
      "after": [],
      "expect": [
        "prefect.flow-run.TimedOut",
        "prefect.flow-run.Failed",
        "prefect.flow-run.Crashed"
      ],
      "for_each": [
        "prefect.resource.id"
      ],
      "posture": "Reactive",
      "threshold": 1,
      "within": 0
    }
  ],
  "require": "all",
  "within": 0
}
same action, same notification block, however the PD incident now look like what's shown in the screenshot. That is, it doesn't look like the body of the Action is getting the jinja vars materialized?
w
Thanks @Constantino Schillebeeckx - this does seem to be a regression - sorry about that! Would you mind filing an issue here and we can get this fixed asap?
c
will do
w
thanks so much
c
w
thanks!
4 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by