Manually prepare mysql package (alpha)#323
Conversation
| description: Collect logs and metrics from MySQL instances | ||
| inputs: | ||
| - type: logs | ||
| description: Collecting MySQL logs |
There was a problem hiding this comment.
I think it would be nice to also have a title for the logs and metrics input
| default: 10s | ||
| - name: raw | ||
| type: bool | ||
| title: Raw (all fields from "SHOW /*!50002 GLOBAL */ STATUS;") |
There was a problem hiding this comment.
Should we put this into the description?
| default: | ||
| - /var/log/mysql/mysql-slow.log* | ||
| - /var/lib/mysql/{{.builtin.hostname}}-slow.log | ||
| os.darwin: |
There was a problem hiding this comment.
The platform flags will not work yet but please keep them in as we plan to support them later.
There was a problem hiding this comment.
I adjusted all config properties with path variables.
| show_user: true | ||
| default: | ||
| - /var/log/mysql/mysql-slow.log* | ||
| - /var/lib/mysql/{{.builtin.hostname}}-slow.log |
There was a problem hiding this comment.
Not supported yet, but we plan to add it: elastic/beats#17340 As soon as we add it we need to adjust this the way we need it. Best keep it as is for now.
There was a problem hiding this comment.
I adjusted all config properties with path variables.
335e9c8 to
b4ffdfb
Compare
|
Also, screenshot updated. |
|
After fixing the issue with merging vars, I managed to install the package flawlessly. Dashboard: |
| - name: thread_id | ||
| type: alias | ||
| path: mysql.thread_id | ||
| migration: true |
There was a problem hiding this comment.
Should the migration field be removed?
There was a problem hiding this comment.
Hmm, I'm not sure. If so, then probably that field should disappear at all from all entries?
There was a problem hiding this comment.
Sorry, I meant here thread_id, the full block. I assume mysql.error.thread_id does not exist anymore.
There was a problem hiding this comment.
Ok, so this change will affect fields.yml and exported fields in README. I will work on this then, but it may take some time.
|
There was an issue with stream generation found last week: elastic/kibana#62330 . Once it's fixed, I will re-verify the integration and re-generate events (leaving it here for visibility). |
|
Hi @mtojek just checking in, is this still blocked? is there anything else pending to have MySQL package ready? |
In the mean time, I've prepared a tutorial how to build a package (#330). |
|
@ruflin I verified all bugfixes, merged changes from the master branch, installed the package in the testing environment. It works fine. Switching to a ready PR. |
|
I look at this in the UI and created the config. The part I didn't test was if it ingests data after shipping it to the agent but the config looks good. One thing I stumbled over is we should have status and galera status both enabled by default? |
I like this one. The dataset |
|
Tried this locally and it seems it is still enabled in the UI. If you can reproduce it on your end, this sounds more like a bug in Kibana. The other part I stumbled over is that I think quite a few fields in error are not documented. But lets move forward here and get this and follow up with iterations. Great job! |
|
Haha, already merged. Seems like we agree :-D |

I'm opening this as draft to present all manual changes that were applied.
Changes:
Action items:
Closes: #317
Closes: #318
Closes: #319
Closes: #320
Screenshot:
