Hi Werner, i was doing this, like you said:
> use graylog2 switched to db graylog2 > db.index_failures.dataSize() > db.dead_letters.dataSize() > db.notifications.dataSize() The output was always nothing! I didn't miss any log messages, so this is NOT the problem. I would understand better, how can I plan the disk space for a bigger environment like the actual on, so I have to know how is the balanace between the Elasticsearch space and the MongoDB space on disk. Thank you! Klaus. Am Donnerstag, 5. November 2015 21:20:16 UTC+1 schrieb Werner van der Merwe: > > Interesting - that ratio seems a little out of balance. 15M for ES for 13 >> servers sounds quite light. >> > You can maybe get some more info on what is using space in Mongo doing the >> following: >> > > On the server hosting mongodb: > mongo (This will enter the mongo > shell from where you can navigate the db) > use graylog2 > db.index_failures.dataSize() (This will give you the size of the > failures collection) > db.dead_letters.dataSize() (This will give you the size of the > dead_letters collection) > db.notifications.dataSize() (This will give you the size of > the notifications collection) > > If none of those are taking up the space, do the same for system_messages. > > Might be helpful to see what is using the bulk of the mongo space? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/50aa1670-77d5-41e4-9fc4-19ae2141a93f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
