2 unstable releases
0.2.0 | Nov 24, 2024 |
---|---|
0.1.0 | Nov 20, 2024 |
#1210 in Database interfaces
286 downloads per month
190KB
2K
SLoC
mysql-slowlog-parser - streaming slow query log parser
About
This library parsers MySQL slow query logs. While
certainly not the first slowlog parser written, this one attempts to extract a great deal more information than its
predecessors. The parsers extract nearly all the information about each line in an Entry
with plans to extract any
remaining values in the near future.
The query found within an entry is also parsed to extract query meta-information about the query (such as which tables and databases are accessed), what type of query and masking of parameters, primarily to normalize repeated calls of the same query.
Since it is a fairly common practice to include important information in the comment of a query. So, each of these comments are parsed to find key-value pairs and include values you can map to specific context about the software that ran the query.
This library is able to read streaming data from the slow logs from a variety of sources and can handle large logs without memory issues.
Limitations
- Currently, does not parse slow query logs generated when logged with the log-slow-extra set. This contains additional fields that aren't accounted for in the current parser and will likely cause parsing errors.
- Comment values that can't be mapped to one of the predetermined keys are lost, this can eventually be saved in a different Hashmap to ensure this information is never lost.
- Masked values are lost when masking parsed queries. The masked values are lost when the query is parsed. These should
be saved in a
Vec<Bytes>
to ensure the values are accessible.
Usage
The parser is built as a tokio codec and so can accept anything that FramedRead supports.
let fr = FramedRead::with_capacity(
File::open("mysql-slow-lobsters.log")
.await
.unwrap(),
EntryCodec::default(),
400000,
);
let future = fr.for_each(|re: Result<Entry, CodecError>| async move {
let _ = re.unwrap();
// do something here with each entry
});
future.await;
Entries
The parsers or codec will return an Entry struct for each object found which contains the following information. Most of the following information below can be accessed via functions on this struct.
Call Information
Information about the start and end time of the query run including the time period it held locks EntryCall
Session Information
Information about the user connection, contained in EntrySession
Query Stats
Details on how long and how often the query ran, contained in EntryStats.
Query Information
EntrySqlAttributes Contains information on the query the entry is about. You can find out the following information about a query:
- The query, with values (depending on settings). At the moment, the values that are masked aren't properly
stored in
EntrySqlAttributes
are lost. This problem will be fixed in an upcoming release. - An AST of the query if it was parseable by sql parser.
- Objects referred to in a parseable query.
- Database schema referred to in a parseable query.
- Mapped key-value pairs from the comment of the query.
Additional Information
In order to understand the data streaming back to you, see docs for the Entry
struct, which holds information returned from individual
in the docs
License
MIT Licensed. See LICENSE
Dependencies
~6–13MB
~153K SLoC