Hey Jochen, another question:
In case the Graylog node ID was generated automatically from the docker configuration, but the graylog data and logs folder was mounted on the host machine. What is a good work around to find out the GRAYLOG_NODE_ID that was generated previously. My Plan is to to start the docker container again and set the previous generated GRAYLOG_NODE_ID as static node id to make graylog use the old configs. Thank you in advance Ivan Am Mittwoch, 9. September 2015 17:30:32 UTC+2 schrieb ivan morozov: > > Thank you Jochen! > > Am Mittwoch, 9. September 2015 17:18:29 UTC+2 schrieb Jochen Schalanda: >> >> Hi Ivan, >> >> extractors and Grok patterns are stored in MongoDB and at least >> extractors are linked to the inputs. Please make sure that you also use an >> external data volume for MongoDB's data files and that the Graylog node ID >> doesn't change with every start (see GRAYLOG_NODE_ID at >> http://docs.graylog.org/en/1.1/pages/installation/docker.html#additional-options >> ). >> >> >> Cheers, >> Jochen >> >> On Wednesday, 9 September 2015 16:44:57 UTC+2, ivan morozov wrote: >>> >>> Hi @all, >>> >>> im using graylog all in one docker. To ensure persistence i have >>> mounted data and log folder at my host machine... >>> after stop and restart docker the dashboards are still there (thats the >>> good news) but my extractors and grok patterns are not more inside. >>> >>> My question is how to keep extractors in this case because create them >>> again and again is really annoying. >>> >>> Best >>> Ivan >>> >> -- 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/f8984d5b-aad6-443d-964c-a51b31e52f66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
