-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mysql] add dbms_flavor tag to tell if the database is mysql or mariadb #18950
Conversation
return dbm_instance.get('tags', []) + [ | ||
'server:{}'.format(common.HOST), | ||
'port:{}'.format(common.PORT), | ||
'dbms_flavor:{}'.format(MYSQL_FLAVOR.lower()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it better to use f"" formatting? it's a little bit less verbose.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
f""
is more concise. i use the same .format
syntax for consistency. we used .format
in the past because f""
is python3 only. it's no longer a concern now.
What does this PR do?
This PR adds
dbms_flavor
tag to the mysql integration metrics and events. The tag can better support explain parsing due to different explain plan format between mysql and mariadb.Motivation
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged