You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue.
Why do you submit this issue?
Question or discussion
Bug
Requirement
Feature or performance improvement
Requirement or improvement
Please describe your requirements or improvement suggestions.
We were waiting for ShardingSphere's 5.0 release for a long time. Powered by that, we have the SQL parser compatibility across different SQL databases. So, we could run SQL parser at the backend in doing trace/span and ALS+SQL-log(in the future) analysis.
We should be able to get the metrics like
read/write latency/traffic for table and table set.
select/update metrics per database.
DDL detection. As normally, there should be no DDL in the product environment.
@tristaZero When your documentation is ready, please ping us. If you want to lead this, please let us know. @ascrutae@kezhenxu94@hanahmily We need to keep our eyes on this and add this into the OAP in the next several weeks, especially for trace analysis first.
The text was updated successfully, but these errors were encountered:
Hi everyone. I am glad to see this SQL-parsing feature of ShardingSphere can come into play in Skywalking community. :-)
We spent a lot of effort and time on this important feature, though it is the first time to present it an independent feature from ShardingSphere. Some interesting ideas are still in the incubator. Stayed tuned!
The additional doc is under review and will be merged soon I suppose. Please give it a watch. :)
I set up the benchmarks to test the performance, apache/shardingsphere#8208. We need a deeper discussion and maybe optimization as right now, it seems would cause a big impact to the OAP.
Please answer these questions before submitting your issue.
Requirement or improvement
We were waiting for ShardingSphere's 5.0 release for a long time. Powered by that, we have the SQL parser compatibility across different SQL databases. So, we could run SQL parser at the backend in doing trace/span and ALS+SQL-log(in the future) analysis.
We should be able to get the metrics like
@tristaZero When your documentation is ready, please ping us. If you want to lead this, please let us know.
@ascrutae @kezhenxu94 @hanahmily We need to keep our eyes on this and add this into the OAP in the next several weeks, especially for trace analysis first.
The text was updated successfully, but these errors were encountered: