I now have both servers using the same mongo, and as far as I can tell everything works. But I'm back to the same problem with an admin logged into the slave having the ability to accidentally or intentionally delete indices. The reader account is pretty much useless. I realize it's possible to create dashboards and streams to return some functionality. Up to now I had no reason or desire to do so. I have no reason to limit anyone from what they can search, and I want them to see the sources and stats. I would much prefer an account that looks almost identical to admin, but prevents one from changing various inputs/settings or deleting indices. I think we need a third superuser account type. I have seen similar feedback from others here.
What to do? On Thursday, May 12, 2016 at 3:50:28 PM UTC-7, Mark Moorcroft wrote: > > > I'm having a similar issue. I have things to a point where neither > instance sees more than one "node". Both are seeing the elasticsearch > indicies (one local, one not). The master node seems mostly operational. I > set up a "slave" node for only one reason. The Graylog user levels made it > necessary to add another instance so users have full search capability but > no way to delete an index by mistake. It appears things have changed and > that strategy won't work anymore. The only step you mention that I haven't > done is clone the mongo. Right now my slave instance sees the indices, but > none of the searches ever load, and I see errors that no master is > selected, along with can't retrieve retention or rotation config. I presume > I'm reaching elasticsearch, but not the master graylog? I see no connection > errors in either mongo log. > >> >> -- 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/75475c80-4734-4a44-bb49-64946014901f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
