FastNode SlowNode configuration, aging an index based off of time using 3
nodes
1. Edit elasticsearch.yml:
Node1 - node.box_type: Fastnode
Node2 - node.box_type: Fastnode
Node3 - node.box_type: Slownode
2. Configure Template so new indexes are created on FastNodes
curl
Im duplicating In production now, once its running there Ill respond with
how I accomplished everything.
--
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 graylo
I'm looking at the Graylog as possible solution for us and this was one of
my issues as well, can you share more details please. I'm a bash guy and
I'll like to understand the logic of this. (on a side note: I'm completely
green with greylog ;) )
On Tuesday, March 8, 2016 at 3:35:49 PM UTC, Mik
Ive got this all figured out. Is anyone interested in how to make a
configuration like this work? Im a windows guy so I scripted out the
moving indexes portion using powershell however someone who can parse json
in bash could replicate the same things fairly easy.
Anyways Im happy to help
Mi
which of the multiple time/date stamps does curator use when determining
how old an index is? Doesnt seems to be documented in an easy to find
place.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop re
not having any luck so far getting this to work
--
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 o
Hi Mike,
changing the index naming schema (except for the prefix) is currently not
supported in Graylog.
Cheers,
Jochen
On Monday, 22 February 2016 23:05:16 UTC+1, Mike Daoust wrote:
>
> prepend was the wrong word, sorry. I think what I meant is clear though.
>
> graylog2_date/time
>
> On Mond
* Mike Daoust [20160222 22:54]:
> prepend was the wrong word, sorry. I think what I meant is clear though.
>
> graylog2_date/time
>
> On Monday, February 22, 2016 at 4:03:51 PM UTC-6, Mike Daoust wrote:
> >
> > Is there a way to have the graylog index prepend the date/time instead of
> > just
prepend was the wrong word, sorry. I think what I meant is clear though.
graylog2_date/time
On Monday, February 22, 2016 at 4:03:51 PM UTC-6, Mike Daoust wrote:
>
> Is there a way to have the graylog index prepend the date/time instead of
> just iterating over numbers?
>
--
You received this
Is there a way to have the graylog index prepend the date/time instead of
just iterating over numbers?
--
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
Jochen,
It would be fantastic if that were added in.
If anyone else is interested in this type of setup I would be willing to
share my experiences.
thanks
Mike
On Friday, February 19, 2016 at 4:19:24 AM UTC-6, Jochen Schalanda wrote:
>
> Hi Mike,
>
> you could build something like this using a
Hi Mike,
you could build something like this using a Hot/Warm architecture in
Elasticsearch, see https://www.elastic.co/blog/hot-warm-architecture for an
example.
We might also add this directly into Graylog in a future release.
Cheers,
Jochen
On Thursday, 18 February 2016 21:31:31 UTC+1, Mi
12 matches
Mail list logo
