Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

In Ops Genie alert query underscore character fails match

I have alerts with the "_" character in the description.  But these are not matching when I query something of this form:


If I use any section it will match but the entire pattern fails to match.

1 answer

0 votes

Hi @Jeffery Caldwell ,

"Wildcards can only be used after characters and will only match from the start of character sequences. Character sequences need to be separated by a space for the wildcard to try and match to each sequence of characters."

So if the string in your description is actually something like "XXXX-AAAA_BBBB_FAILURE" - Opsgenie is not gonna be able to query using that since the string starts with something else.

We have an open feature request for this additional functionality you can follow here:

I don't believe that bug fully matches the issue being described. I have encountered the same issue.

If you search for any text before an underscored you will find your alert.


If you search for any text after an underscore you will not find your alert.afterunderscore.PNGIf you search for any text before and after the underscore, but include the literal text surrounding the underscore, you will find your alert.workaround.PNG

Based on this behavior I can surmise that whatever is processing the string will only process the literal underscore character if it is wrapped by other literal characters. This means that something is processing the underscore symbolically. So I believe this should be a new bug to allow the use of the literal underscore in the search string.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events