Hi Steven, there's no fixed release date for Graylog 1.1.0 (and the first version of the Graylog Agent) yet, but it should be soonish.
There are multiple types of logs that MySQL can write to disk, most of them only into plain text files. To get those to another host (and possibly add some useful meta information) you should take a look at nxlog or logstash which both support tailing files and sending their contents via GELF into Graylog. There are also additional interesting information in MySQL which aren't directly written into log files but which are for example available in the information_schema database (see https://dev.mysql.com/doc/refman/5.7/en/information-schema.html). I'm not aware of any off-the-shelf software which would grab this information and send it to another system like Graylog, so you will probably need to write a custom script for this, if you're interested in that information. Cheers, Jochen On Thursday, 7 May 2015 09:16:40 UTC+2, Steven Broschat wrote: > > re: Graylog Agent, Yes that will be nice, When will I get my hands on > that? Im using 1.0.2 I believe. > So based on this answer, Should I even bother with syslog-ng? I have > Syslog-NG > 3.2.5 in a webmin interface and While I believe I understand how source, > target, destination, filters work, I am still wrapped around the axle on > how to tail the general query log into graylog. I imagine I could generate > a lot of useful information for apps using mysql like, opencart, or > anything else that uses the database. Should I consider using something > else for log data transport? > I have been successful with --syslog via plain udp but I want to have a > way to track employee logins and transactions within the apps backends. > > On Wednesday, May 6, 2015 at 5:58:11 AM UTC-10, Jochen Schalanda wrote: >> >> Hi Steven, >> >> you can have MySQL log errors into syslog via the --syslog options for >> mysqld, see >> https://dev.mysql.com/doc/refman/5.7/en/mysqld-safe.html#option_mysqld_safe_syslog >> and >> http://mysqlserverteam.com/logging-with-mysql-error-logging-to-syslog-eventlog/ >> . >> >> If you want to additionally send the slow query logs of MySQL, you'll >> need to tail the file MySQL writes the slow query log into (see >> https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html) and send it >> to Graylog via GELF. You can use nxlog, logstash, or our very own and shiny >> Graylog Agent (to be released together with Graylog 1.1.0) for this. >> >> For configuring your syslog daemon to send log messages to Graylog, >> please refer to our documentation at >> http://docs.graylog.org/en/1.0/pages/sending_data.html#syslog. >> >> >> Cheers, >> Jochen >> >> On Wednesday, 6 May 2015 13:59:40 UTC+2, Steven Broschat wrote: >>> >>> This request for help is specific to sending log data to graylog using >>> syslog-ng then analyzing the mysql servers logs from within graylog. >>> Primary Question is, How can I achieve this? FYI, I do have a running >>> stack just not logging any mysql data such as user data, queries data yet. >>> >>> Please offer constructive and helpful suggestions, Thank You, >>> P.S. I have been researching this for a few days and have not found any >>> conclusive instructions.. >>> >> -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
