Use nagios Field Processor in combination with Project Mappings

Charlie Misonne Community Champion Jul 14, 2016

Is it possible to use the Nagios Field Processor in JEMH together with Project Mappings?

I want to add a component to some Nagios alerts based on a keyword in the subject.
When the Project Mappings are configured the correct component is added but the description of the issue is empty and the cutom Nagios fields (host, state, ...) are also missing

 

I'm leaving the project blank in the Nagios configuration
Which shows a red error. I would expect it to fall back to the default project

image2016-7-14 17:7:33.png

1 answer

This widget could not be displayed.

Hi Charlie,

It appears that currently, while the project mapping works, the nagios field processor does not extract the field values from the email when the nagios configuration does not have a project set.

I am looking into what it would take for the processing behaviour to allow your scenario to work.

Mike

Charlie Misonne Community Champion Jul 18, 2016

Hi Mike

Thanks for looking into this!

Does that mean I should be able to set up different mappings with other components while using the same project? And defining the project in the the Nagios field processor? I don't think that works either. I'll try again tomorrow to be sure

Charlie Misonne Community Champion Jul 19, 2016

Tested today.

I set a project in the Nagios configuration and I am using the same project in the project mapping with 2 different components using keyword mapping

It creates the tickets without component. Probably because no Nagios Components are defined?

image2016-7-20 11:55:0.png

Charlie Misonne Community Champion Aug 10, 2016

Hi @Mike Harrison. Should I create a ticket in your JIRA for this?

Hello Charlie,

If component(s) are selected in the project mapping rule level, and that rules criteria are the first to be met, then the components should be added to the created issue. If the components are instead set at the project mapping level it should also work. The nagios field processor is still chosen as the field processor by JEMH.

There are however bigger current problems with using this processor without a specified project in the config: missing custom field mappings (as mentioned before) and issue association not being possible (so it will always create instead of comment, and resolving when a "resolve" email comes in will not work as it does normally).

Please follow https://thepluginpeople.atlassian.net/browse/JEMH-4351 for future updates on the improvements necessary to allow project mappings to work with the nagios field processor.

Regards,

Mike

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in Teamwork

What teamwork quotes inspire you?

Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork?  We've compiled a list here, along with...

151 views 16 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you