About Lyra

Growing up, my parents would always tell me to figure things out on my own (I’m sure my fellow first-gen readers can relate). Both of them immigrated to the US during the 1979 Iranian Revolution, so self sufficiency was their only option, and it was a value they wanted to impart on me. I don’t blame them for it - if anything it made me stronger! But it also prevented me from ever seeking out a mentor.
Instead, I turned to books & the internet. The author or protagonist of every book, blogpost, video, or podcast became manifestations of the mentors I had always wanted. While I’ve never actually spoken to the majority of these "mentors," they have resided in my mind, guiding decisions and choices that I make on a day-to-day basis.

Summary

If you’ve got a lot of alerting rules set up from different services across your organization, they won’t
all have the same metadata or labels attached to them, which can make extracting “which team is
responsible for this?” or “which service does this relate to?” tricky.
For example, some alerts might include a team=payments label directly, but others might instead have service=banking. With fallback expressions you can now consistently assign a team to these alerts no matter what they look like. For example:

1. If there is a team attribute on the metadata of the payload, use that to notify a team

2. Otherwise, if there is a service on the payload, use that to point to a service, then navigate to the owning team via Catalog