Timeline for Mysql slow query log always include "# Time:"
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:20 | history | edited | CommunityBot |
added [slow-log] to 102 questions - Shog9 (Id=1924)
|
|
| Apr 27, 2015 at 8:45 | vote | accept | aland | ||
| Apr 26, 2015 at 17:43 | answer | added | Rick James | timeline score: 1 | |
| Apr 26, 2015 at 14:12 | answer | added | aland | timeline score: 0 | |
| Apr 26, 2015 at 12:18 | comment | added | aland | @jynus yes I had based my config from that blog and I'm using timestamp for a timestamp, I'm using the line 'Time' as an anchor to mark the start of a new log event - but it seems he has recently edited it so that the pattern is based on the 'User' line rather than 'Time'. | |
| Apr 26, 2015 at 12:15 | history | edited | aland | CC BY-SA 3.0 |
Include logstash config
|
| Apr 26, 2015 at 11:48 | comment | added | jynus | @aland Have you tried tutorials like phase2technology.com/blog/… already? The idea is to use the timestamp, and not the time the query was logged. | |
| Apr 26, 2015 at 11:46 | history | edited | aland | CC BY-SA 3.0 |
clarity
|
| Apr 26, 2015 at 11:44 | comment | added | aland | Logstash is mainly using regex - elastic.co/guide/en/logstash/current/… | |
| Apr 26, 2015 at 11:38 | comment | added | Philᵀᴹ | Not hard to keep a running variable in your parser with the current value of time. I guess it depends on what your parser is written in. | |
| Apr 26, 2015 at 11:12 | history | asked | aland | CC BY-SA 3.0 |