Skip to content
This repository has been archived by the owner on Dec 19, 2020. It is now read-only.

getting a response 400 from plugin #3

Open
whitty69 opened this issue Mar 8, 2016 · 3 comments
Open

getting a response 400 from plugin #3

whitty69 opened this issue Mar 8, 2016 · 3 comments

Comments

@whitty69
Copy link

whitty69 commented Mar 8, 2016

Hi,

Great plugin :-) however ........

I'm getting the following error in graylog when the callback is called.

any ideas why?

Peter.

2016-03-08 10:46:21,665 ERROR: org.graylog2.shared.rest.exceptionmappers.AnyExceptionClassMapper - Unhandled exception in REST resource java.lang.RuntimeException: [JIRA] Unexpected HTTP response status 400 at com.tjackiw.graylog2.plugin.jira.callback.JiraAlarmCallback.call(JiraAlarmCallback.java:76) at org.graylog2.rest.resources.streams.alerts.StreamAlertReceiverResource.sendDummyAlert(StreamAlertReceiverResource.java:168) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source)

@magicdude4eva
Copy link

I had similar issues - make sure that your plugin defaults match your Jira setup. In my case the default for issue-priority "P1" needed to change to "Minor". You might also have a different issue-type to the default of being "Bug".

@whitty69
Copy link
Author

whitty69 commented Mar 9, 2016

thanks.. finally got it work, but I to do as you mention, but I had to set values for all fields (even optional ones)

:-)

@magicdude4eva
Copy link

I reworked this plugin in another project - perhaps some of the new features will work for you - https://github.com/magicdude4eva/graylog-jira-alarmcallback

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants