About M_L_A

M_L_A · ‎04-18-2023

Thank you for your assistance. This project got put on hold and I've just had a chance to look at it. I've changed the json to manually have a link of http://localhost:8000/en-US/app/search/search?sid=$results_sid$ and while the sid variable works, the resulting link when the alert goes through PagerDuty is http://localhost:8000/en-US/app/search/search?sid=schedulerusersearchnumbers_at_sid which does not work as the sid is incorrect I think I have concluded that the variable is simply bugged at the moment and will have to use a work around. Thanks for your assistance 🙂

M_L_A · ‎04-05-2023

We have recently switched from email alerts to PagerDuty alerting. With this switch, the link to search results has broken. When the alert comes in through email, it gives a link that includes ....scheduler__user__search__abc__at_123__ and the splunk query contains |loadjob scheduler__user__search__abc_at_123__ When the alert comes in through PagerDuty, using $results_link$ it gives a link that includes ...schedulerusersearchabc__at__123 and the splunk query contains |loadjob schedulerusersearchabc_at_123__ . When this search is ran it gives an error that the alphabet soup job ID couldnt be found Is there a way to adjust $results_link$ to insert the __ in between sections manually?

Posts	2
Solutions	0
Karma Given	2
Karma Received	0
Member Since	‎04-05-2023

Online Status	Offline
Date Last Visited	‎05-24-2023 05:32 AM

Why is $results_link$ giving a broken link?

Re: $results_link$ giving a broken link

Why is $results_link$ giving a broken link?