I also starting receiving errors for a Quick values on a field named
"status_code"; I only noticed it after the upgrade to 2.1.3. I changed the
name to something else and everything starting working again. I am
converting this field to an integer and was doing a search on if the field
value
at did you change in the name to make it work?
>
> On Friday, February 3, 2017 at 12:39:56 PM UTC-5, Bill Murrin wrote:
>>
>> I also starting receiving errors for a Quick values on a field named
>> "status_code"; I only noticed it after the upgrade to 2.1.3.
In the Getting Started section of the README on
https://github.com/Graylog2/graylog-plugin-map-widget, it says the
following:
Getting started
This project is using Maven 3 and requires Java 7 or higher.
- Clone this repository.
- Run mvn package to build a JAR file.
- Optional: Run
y 2017 13:00:19 UTC+1, Bill Murrin wrote:
>>
>> Any assistance you can provide would be appreciated. Here is a link to
>> the plugin to see if you guys might be able to help me figure out what is
>> causing it. Once we figure this out, I plan on sharing the plugin on the
.jar?dl=0
Thanks in advance,
-Bil
On Monday, January 30, 2017 at 7:46:54 PM UTC-10, Bill Murrin wrote:
>
> Hi everyone,
>
> I'm attempting to build a web plugin that will also act as a Field
> Analyzer.
>
> After much frustration and various undocumented errors, I've
ut the frustration you had when trying to
> build a plugin, so we can either improve the documentation or the build
> process?
>
> Kind regards,
> D.
>
> > On 31.01.2017, at 06:46, Bill Murrin <bill@gmail.com >
> wrote:
> >
> > Hi ever
Hi everyone,
I'm attempting to build a web plugin that will also act as a Field Analyzer.
After much frustration and various undocumented errors, I've been able to
build the package successfully! :-)
When I add the plugin, it shows up as a plugin, but does not act
accordingly.
When I look at
Nitzan,
When this was happening on my system it was related to the jvm garbage
collection (GC) on the elasticsearch cluster kicking in. When it does so,
it stops processing all messages until it is done. I got around the issue
by adding another node to my Elasticsearch instance.
You can check
Graylog Team,
Congratulations on the release of 2.2.0. Can't wait to take it for a spin!
:-)
-Bill
On Tuesday, February 14, 2017 at 5:07:13 AM UTC-10, Jochen Schalanda wrote:
>
> Hi everyone,
>
> I'm proud to announce the GA release of Graylog 2.2.0!
>
> We've put a lot of work into this
I am looking for assistance with a plugin I am trying to create for a
pipeline processor function.
I followed along with the tutorial
(https://www.graylog.org/blog/71-writing-your-own-graylog-processing-pipeline-functions)
and
also looked at source code for other pipeline processor functions.
10 matches
Mail list logo
