John Pereira
Has any one integrated Patrol Agent alerts with XMatters 5.x
0
Patrol integration with Xmatters 5x
Comments
Please sign in to leave a comment.
Hey John. I haven't personally heard of any customers who have tried this. But I poked around and found a couple of resources:
* Old PEM integration - The old integration, built for the java client
* Convert java-client integration to IA - Walks you through porting an integration to the IA.
Although, might not be a bad idea to take the logic in the java client integration and manually port it to javascript to make a native IA integration. You'll need to make sure you can install the IA on the PEM box, or somewhere PEM can reach the IA, and from there determine what mechanism to send the data to the IA (command line or HTTP POST). With the new 5.1.5 IA, you can throw pretty much anything at it and the payload can be consumed pretty easily.
Hi Travis, Do you know if 5.1.5 IA is supported with 5.1.3 xmatters server
Yep. That will work. You need a minimum of 5.1.1, so you're in the clear. Feel free to post any issues you run into while trying this. It would be a great example to have public, and I can help you as I get to it.
Travis, Thanks, ill keep you informed.
updated the IA to 5.1.5 today. Travis, is there any guide on how to make the data mapping work.
i do pass the values using APClient.bin, and i do get a notification from xmatters, but its all blank. can you help, ( i also
did ask the same question in another thread )
Hey John, apologies for the delayed response. That sounds like the mapped-input section might be wonky. What do you have entered there and how are you making the APClient.bin call?
You might also dump the incoming parameters to the log with this command:
IALOG.info( 'stuff to go to log here' );Travis, Kim Jue helped with fix the Patrol.xml file so that email notifications are correctly recieved. It is fixed now, however i could not clearly understand how it worked.
I mean, i was passing parameters to the APClient.bin file and there was a type format in the patrol.xml file. How is the APClient.bin parameters and xml file entries mapping with each other. Does this also require any more files information for it to work. I would like to create a new event domain and do some testing based on what you say.
Here is the case that was opened for the same issue : 101867
Thanks
John
(updated some formatting)
Ah, oh good. Glad to hear. That Kim guy knows his stuff.
To answer your question, I'll reference the ovens integration in that Getting Integrated Guid (part 6)
It has this section in the ovens.xml file:
<mapped-input method="add">
<parameter>recipients</parameter>
<parameter>Oven_Name</parameter>
<parameter>Timer_End_Time</parameter>
<parameter>Timer_Start_Time</parameter>
</mapped-input>
This tells APClient.bin that the first parameter will be recipients. The second parameter will be
Oven_Name, thirdTimer_End_Time... etc.So, the command to APClient.bin would be this:
./APClient.bin --map-data 'applications|ovens' '[{"targetName":"chef"}]' "oven1" "10:34 AM" "11:04 AM"Note that the 'applications|ovens' tells APClient.bin which integration to use.
If we wrote it like this:
Then Oven_Name would be the first parameter and our command would be:
./APClient.bin --map-data 'applications|ovens' "oven1" "10:34 AM" "11:04 AM" '[{"targetName":"chef"}]'Oh, note that the recipients part looks weird because that article was written for the xMatters On Demand engines, rather than the Event Domains it sounds like you are using. So, your recipients entry would just be "chef", or just the group/user name.
Anyway, behind the scenes, before the
apia_inputfunction is called, the IA will build the "apxml" so you can then reference the parameters by name inapia_inputand so that when the event is submitted to xMatters, it can sort out what values go where.Does that help?