login::
pass::
name::
id::
node:
Server mail reports
template:
4
parent:
Vychytavky
owner:
wiro
viewed by:
created:
05.06.2015 - 19:48:50
cwbe coordinatez
:
101
63540
63542
1098481
7930864
ABSOLUT
K
YBERIA
permissions
you:
r,
system:
public
net:
yes
⠪
neurons
stats
|
by_visit
|
by_K
source
tiamat
K
|
my_K
|
given_K
last
commanders
polls
total descendants::3
total children::2
2
❤️
show[
2
|
3
]
flat
http://www.vojcik.net/how-to-handle-thousands-of-reports-from-servers-logstash-elasticsearch-kibana/
Kuk zijeme este ?
title/content
title
content
user
000001010006354000063542010984810793086408089218
nudzo
08.02.2016 - 22:33:38
, level: 1,
UP
NEW
Re: Server mail reports
New leader for time series DBs:
https://influxdata.com/
000001010006354000063542010984810793086407936289
semantic frequency
12.06.2015 - 11:24:58
, level: 1,
UP
NEW
Re: Server mail reports
http://prometheus.io/
viac
http://prometheus.io/docs/visualization/promdash/
myslim ze ELK ukazal spravny smer, zaroven LevelDB od googlu mi pride viac sympatisch (Elastic je derivat od Lucene nad JVM a na nod kde bezi ES okrem tej nenazranej JVM nic uz nepobezi)
00000101000635400006354201098481079308640793628907943145
wiro
21.06.2015 - 17:24:39
, level: 2,
UP
NEW
Re[2]: Server mail reports
Zaujimave tiez, pozriem sa na to podrobnejsie.
Inak ten elatic zalezi na velkosti DB a od operacii ktore od nej su pozadovane. Mam skusenost s tym ze viac sluzieb bezalo vsetko na jednom serveru bez problemov. Akonahle zacne narocnost DB rast tak ci tak sa presunie na cluster a teda uz ani nevada zmysel aby na jednom DB node bezalo cosi ine.