Hi Rangarasan,
unfortunately we started archiving the old Graylog Omnibus packages only
with Graylog 1.2.0 (see https://packages.graylog2.org/omnibus), so there's
no way to easily rebuild the old Graylog 1.0.2 OVA, except for grabbing the
sources for the corresponding Omnibus package (
Thanks Jochen.
On Thursday, January 21, 2016 at 8:57:23 PM UTC+5:30, Jochen Schalanda
wrote:
>
> Hi Ranjith,
>
> you can use the typical log file collectors like nxlog (
> https://nxlog.co/products/nxlog-community-edition), logstash (
> https://www.elastic.co/products/logstash), Graylog
I require to dedup all values of one extracted field called "Employee ID".
Is there any way to do this on graylog. Any can help on this please.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop
I have experienced the same issue; I found if I delete the first stream and
create a new one just like it, the second one usually works. I don't know
why.
On Thu, Jan 28, 2016 at 10:33 AM, Mcfly ATL wrote:
> Good morning,
>I already posted about this a month ago and
Hi Mohana,
make sure that the system user who is running the Graylog server node(s)
has sufficient permissions to access the configured private key and
certificate files. The user must be able to descend into the
directory /opt/graylog/conf/nginx/ca/ and finally read the private key and
Hi there
I just had an event where I was looking at some data of interest via the
Search Histogram and all I could see was this big spike - looked like
there was nothing except for this spike. Threw me for a bit but I
figured out that the size of the spike was so large that the other data
points
Hej Skip,
just an idea - based on that what you have written.
If you change the timestamp in gelf, graylog is not able to parse this.
(Reference: https://www.graylog.org/resources/gelf/ )
*timestamp* number
Seconds since UNIX epoch with optional decimal places for milliseconds;
SHOULD be set
Hi,
there are no official startup scripts or packages/ports for Graylog on
FreeBSD at the moment, but there's a third party port for a slightly older
version of Graylog at https://github.com/tbartelmess/freebsd-port-graylog.
Cheers,
Jochen
On Thursday, 28 January 2016 08:06:44 UTC+1,
Thanks guys for your suggestion.
I am in progress of testing this upgrade. So, I am looking for graylog v1.0.2
OVA file. But, I don't see the old ova files in download section.
Could you please help me to get graylog v1.0.2 OVA file?
Thanks,
Rangarasan
--
You received this message because
Thanks
--
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
Hi Jan,
Thanks for the reply. The thing is, we are passing in the timestamp. Here
is a 'toString' of the GelfMessage:
GelfMessage{version="1.1" timestamp="1453388845999.000"
short_message="{timestamp=2016-01-21T10:07:25.999-05:00, level=DEBUG,
action=HTTP_REQUEST, user=hso_admin}",
Hi Jan,
Thanks for the reply. The thing is, we are passing in the timestamp. Here
is a 'toString' of the GelfMessage:
GelfMessage{version="1.1" timestamp="1453388845999.000"
short_message="{timestamp=2016-01-21T10:07:25.999-05:00, level=DEBUG,
action=HTTP_REQUEST, user=felixfrankfurter}",
Thank you
четверг, 28 января 2016 г., 17:18:51 UTC+8 пользователь Jochen Schalanda
написал:
>
> Hi,
>
> there are no official startup scripts or packages/ports for Graylog on
> FreeBSD at the moment, but there's a third party port for a slightly older
> version of Graylog at
Hi Rangarasan,
we currently do not provide downloads of old OVA versions.
Cheers,
Jochen
On Thursday, 28 January 2016 14:00:58 UTC+1, Rangarasan N wrote:
>
> Thanks guys for your suggestion.
>
> I am in progress of testing this upgrade. So, I am looking for graylog
> v1.0.2 OVA file. But, I
I have a server with 4x cores - 6Gb memory .. running graylog-server,
graylog-web, elasticsearch and mongodb same machine... average 50 messages
per minute... the server still have free memory using usually 4gb from
6gb... but graylog-server consume until "out of memory error - Java heap
:-)
Thanks for this information!
You have brightened my day.
Sincerely,
Skip
On Thu, Jan 28, 2016 at 8:46 AM, Jochen Schalanda
wrote:
> Hi,
>
> the value of the timestamp field in the actual GELF message
> (1453388845999.000) is invalid or rather translates to a date
Good call! I tried that on two streams and they are working fine. Odd is
true but glad it's working!
On Thursday, January 28, 2016 at 11:56:33 AM UTC-5, Joi Owen wrote:
>
> I have experienced the same issue; I found if I delete the first stream
> and create a new one just like it, the second
Thanks Jochen.
Is there any other way that I can test the upgrade v1.0.2 to v1.3.3?
I'm looking to test it before get into production upgrade. Can you please
suggest me?
Thanks,
Rangarasan
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To
Hi Jochen,
thanks. It solved ! the error is not intutive.
Can you also tell me which format the TLS client auth certs should be ?
PEM or PKCS?
On Thursday, 28 January 2016 03:20:43 UTC-6, Jochen Schalanda wrote:
>
> Hi Mohana,
>
> make sure that the system user who is running the Graylog
Hi All,
I have been using typesafe activator version 1.3.5 to compile Graylog Web
Component. But it is not working efficiently, sometime it compiles the file
and sometime it do not.
Form today I am facing this issue. Also can anyone please point me to any
other tool or method to compile
20 matches
Mail list logo