[graylog2] Re: Quick Values not working

2017-02-03 Thread Bill Murrin
Hi Steve,

I changed the field name to something else (rcode). I am shipping my logs 
via GELF from a logstash processing instance so I edited my logstash config 
file to parse it as a different field name.

-Bill

On Friday, February 3, 2017 at 10:28:08 AM UTC-10, Steve Kuntz wrote:
>
> What 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. 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 was greater than 0.
>>
>> -Bill
>>
>> On Friday, February 3, 2017 at 5:08:14 AM UTC-10, Steve Kuntz wrote:
>>>
>>> I'm having a new issue getting quick values since I modified some 
>>> fields. This is just to get the HTTP status codes but there is some issue. 
>>> All values are being converted to numeric but I'm getting an error. I've 
>>> attached the error and the stats to show what the data is.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/f3fd7b94-9e08-479e-a20a-c3eb7317db92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
What 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. 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 was greater than 0.
>
> -Bill
>
> On Friday, February 3, 2017 at 5:08:14 AM UTC-10, Steve Kuntz wrote:
>>
>> I'm having a new issue getting quick values since I modified some fields. 
>> This is just to get the HTTP status codes but there is some issue. All 
>> values are being converted to numeric but I'm getting an error. I've 
>> attached the error and the stats to show what the data is.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/1da31c69-1dfe-4520-9b37-43f8fae81641%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
Unfortunately not, it's the only log message that shows when trying to do a 
quick value on the field.

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/d5b87637-a46b-4bbf-b742-7514637a0069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Jochen Schalanda
Hi Steve,

On Friday, 3 February 2017 18:05:26 UTC+1, Steve Kuntz wrote:
>
> There is an error in the graylog.log
>
> WARN  [SearchResource] Unable to execute search: [reduce]  
>

Is there more context around that warning message?

Cheers,
Jochen 

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/790e896c-0f15-4e54-b9e8-2b12e3f7e05b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
Same here but I wasn't sure it was related to the update.

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/19e68697-b13a-47a4-8aa7-63fcf22f2087%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Bill Murrin
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 was greater than 0.

-Bill

On Friday, February 3, 2017 at 5:08:14 AM UTC-10, Steve Kuntz wrote:
>
> I'm having a new issue getting quick values since I modified some fields. 
> This is just to get the HTTP status codes but there is some issue. All 
> values are being converted to numeric but I'm getting an error. I've 
> attached the error and the stats to show what the data is.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/586d1c58-2702-4a46-b4be-b0ddbce365d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
There is an error in the graylog.log

WARN  [SearchResource] Unable to execute search: [reduce]  

Any and All help is appreciated.

On Friday, February 3, 2017 at 11:59:34 AM UTC-5, Steve Kuntz wrote:
>
> Also Field Statistics and Generate Chart work on this same data set as 
> well and I think they require Numeric values as well. 
>
> On Friday, February 3, 2017 at 11:44:44 AM UTC-5, Steve Kuntz wrote:
>>
>> As a test my search is 
>>
>> _exists_:http_response_code AND http_response_code:[200 TO 503]
>>
>> And I"m still getting the same error.
>>
>> On Friday, February 3, 2017 at 10:53:04 AM UTC-5, Jochen Schalanda wrote:
>>>
>>> Hi Steve,
>>>
>>> the "quick values" functionality only works if the field is numeric in 
>>> all messages of the queried time range. If there are some non-numeric 
>>> values for that message field within the queried time range, you'll receive 
>>> the error message you've already mentioned.
>>>
>>> Cheers,
>>> Jochen
>>>
>>> On Friday, 3 February 2017 16:08:14 UTC+1, Steve Kuntz wrote:

 I'm having a new issue getting quick values since I modified some 
 fields. This is just to get the HTTP status codes but there is some issue. 
 All values are being converted to numeric but I'm getting an error. I've 
 attached the error and the stats to show what the data is.

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/474c4b05-c4e8-47ca-ac2d-ae14976be486%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
Also Field Statistics and Generate Chart work on this same data set as well 
and I think they require Numeric values as well. 

On Friday, February 3, 2017 at 11:44:44 AM UTC-5, Steve Kuntz wrote:
>
> As a test my search is 
>
> _exists_:http_response_code AND http_response_code:[200 TO 503]
>
> And I"m still getting the same error.
>
> On Friday, February 3, 2017 at 10:53:04 AM UTC-5, Jochen Schalanda wrote:
>>
>> Hi Steve,
>>
>> the "quick values" functionality only works if the field is numeric in 
>> all messages of the queried time range. If there are some non-numeric 
>> values for that message field within the queried time range, you'll receive 
>> the error message you've already mentioned.
>>
>> Cheers,
>> Jochen
>>
>> On Friday, 3 February 2017 16:08:14 UTC+1, Steve Kuntz wrote:
>>>
>>> I'm having a new issue getting quick values since I modified some 
>>> fields. This is just to get the HTTP status codes but there is some issue. 
>>> All values are being converted to numeric but I'm getting an error. I've 
>>> attached the error and the stats to show what the data is.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/4faf9447-7e01-4a98-83f6-b1e1d0cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Steve Kuntz
As a test my search is 

_exists_:http_response_code AND http_response_code:[200 TO 503]

And I"m still getting the same error.

On Friday, February 3, 2017 at 10:53:04 AM UTC-5, Jochen Schalanda wrote:
>
> Hi Steve,
>
> the "quick values" functionality only works if the field is numeric in all 
> messages of the queried time range. If there are some non-numeric values 
> for that message field within the queried time range, you'll receive the 
> error message you've already mentioned.
>
> Cheers,
> Jochen
>
> On Friday, 3 February 2017 16:08:14 UTC+1, Steve Kuntz wrote:
>>
>> I'm having a new issue getting quick values since I modified some fields. 
>> This is just to get the HTTP status codes but there is some issue. All 
>> values are being converted to numeric but I'm getting an error. I've 
>> attached the error and the stats to show what the data is.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/f0e66a72-1bd7-4f28-adfe-3efee2a4b4c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Re: Quick Values not working

2017-02-03 Thread Jochen Schalanda
Hi Steve,

the "quick values" functionality only works if the field is numeric in all 
messages of the queried time range. If there are some non-numeric values 
for that message field within the queried time range, you'll receive the 
error message you've already mentioned.

Cheers,
Jochen

On Friday, 3 February 2017 16:08:14 UTC+1, Steve Kuntz wrote:
>
> I'm having a new issue getting quick values since I modified some fields. 
> This is just to get the HTTP status codes but there is some issue. All 
> values are being converted to numeric but I'm getting an error. I've 
> attached the error and the stats to show what the data is.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/33c4642f-6ead-4b30-9e20-63b0e97ffead%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.