Shazzam Parser V2

[doug_schulze]

Some might remember I created and posted an update set that would parse the Shazzam result. I did this because many of my friends here would just dread having to parse through the Shazzam port scan return to better identify what IPs were active and alive and what responses they were returning in an easy-to-read table. For some reason, the community rulers have since deleted/archived that post, and is no longer found, but hopefully this in a blog will keep it around for a while

While I was quite proud of it there was one fatal flaw that I didn't address, and that was the parsing of a return when the values were in an attachment to the record over just a straight XML file. I'll just mark it up to our good friend JED (Just Enough Development) but the concept was there and it worked, but it needed to be better.

Enter my awesome friend and fellow ITOM Ranger @Yew Hoong Ng 

He took the original work fixing some of my Crayola-level scripting and addressed the attachment limitations, its much better. So with him, I offer to you, our friends the Shazzam parser v2.  Hope you find some good joy in using it to help make your discovery troubleshooting even easier.

ShazzamStatusv2.xml

[Cedric LORIN1]

Hello,

Thank you for your sharing.

It's very cool and this simply. 

Great job 😀

[Jimbo2]

Yes I found this really useful in particular where shazzam DNS is resolvable on a failed discovery attempt, I can quickly see the hostname has resolved rather than having to try nslookup from mid server myself.

[CBartram]

I LOVE this extension! Tested it in our lower environments where I had admin access and it's been a wonderful tool - but when we installed it in production we get this error when we open the tab:

shazam plugin: Number of rows removed from this list by Security constraints: #

Any hints at the table/role we need to fix so our discovery admins can use the plugin?

Thanks!!!