NullPointerException in org.graylog2.outputs.GelfOutput

[razvanphp]

Hello,

Today I just noticed those errors in our logs, graylog v1.2.2

2015-11-05T11:35:58.212+01:00 ERROR [OutputBufferProcessor] Error in output [class org.graylog2.outputs.GelfOutput].
java.lang.NullPointerException
    at org.graylog2.outputs.GelfOutput.extractLevel(GelfOutput.java:195)
    at org.graylog2.outputs.GelfOutput.toGELFMessage(GelfOutput.java:213)
    at org.graylog2.outputs.GelfOutput.write(GelfOutput.java:176)
    at org.graylog2.buffers.processors.OutputBufferProcessor$1.run(OutputBufferProcessor.java:189)
    at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)

We have a lot of those, and anything else in the logs what we had for some time are some of those:

2015-11-05T11:37:07.915+01:00 ERROR [Messages] Failed to index [8] messages. Please check the index error log in your web interface for the reason. Error: failure in bulk execution:
[127]: index [graylog2_623], type [message], id [27cdf976-83a9-11e5-9ee7-00163e7a938a], message [MapperParsingException[failed to parse [ctxt_otl_markup_value]]; nested: NumberFormatException[For input string: "null"]; ]
2015-11-05T11:36:27.231+01:00 ERROR [Messages] Failed to index [1] messages. Please check the index error log in your web interface for the reason. Error: failure in bulk execution:
[904]: index [graylog2_623], type [message], id [103af882-83a9-11e5-9ee7-00163e7a938a], message [IllegalArgumentException[Document contains at least one immense term in field="context" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped.  Please correct the analyzer to not produce such terms.  The prefix of the first immense term is: '[123, 39, 105, 109, 97, 103, 101, 115, 39, 58, 32, 91, 39, 104, 116, 116, 112, 58, 47, 47, 109, 99, 45, 112, 114, 111, 100, 117, 99, 116]...', original message: bytes can be at most 32766 in length; got 42608]; nested: MaxBytesLengthExceededException[bytes can be at most 32766 in length; got 42608]; ]

I found no way to fix this null thing with an extractor, I already mentioned we need a replace extractor in ticket #1469

Thank you!