I know this has probably been covered somewhere, but I can’t seem to be able to find it in any documentation.
How do I handle wildcards?
I need a regular expression that will find this is:
The previous system shutdown at 12:24:41 AM on ?2/?2/?2025 was unexpected. for MDO-SQL
I want it to ignore 12:24:41 AM and ?2/?2/?2025 and MDO-SQL
I just cannot seem to be able to find this most simplest of tasks.
Thank you,
Sid
Hi @spayne ,
I’ll be glad to generate a regular expression for you.
Given this string, please tell me what text you would like extracted:
The previous system shutdown at 12:24:41 AM on ?2/?2/?2025 was unexpected. for MDO-SQL
I appreciate the help.
What I want to do is ignore the Time, date, and name of the server.
I want those to be all wildcards.
Not sure why I having a hard time figuring that out.
Try this:
The previous system shutdown at [\w\s\-:\?\d\/]* was unexpected. for \S*
I use Regex101.com to verify and test expressions I build. Here’s a link to that if you want to play with it:
If you have any other questions, let me know.
So, you would enter it exactly like this in the scheduled task?
I get no results even though I have a ticket with this in the title:
The previous system shutdown at 6:17:34 AM on ?1/?29/?2025 was unexpected. for KML-DC
Please send the URL to the history in MSPintegrations and I’ll check it out.
Thanks, that’s helpful.
For the sake of anyone else following along, here is the action step in the Scheduled Task. You are querying for Autotask tickets using the Autotask API:
The Autotask API doesn’t support sending a regular expression through the query. The query configured above will search for a ticket where the title is the literal value of The previous system shutdown at [\w\s\-:\?\d\/]* was unexpected. for \S*.
Since you can’t submit a regular expression to the Autotask API, I recommend you query the API to find a ticket where the title contains The previous system shutdown at and the title also contains was unexpected.. This may return other results, but it may be good enough for your purpose (only you will know that).
To configure the action to query this way, configure it like this:
Let me know how that goes.
Okay, so we can’t have wildcards in the query. That is unfortunate.
I will give your solution a try.
