We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue.
Which version of SkyWalking, OS and .NET Runtime? SkyWalking version : 9.4.0 OS: LINUX CentOS 7.9 .NET RUNTIME: 3.1
Which company or project?
What happen? If possible, provide a way for reproducing the error. e.g. demo application, component version.
The text was updated successfully, but these errors were encountered:
You could check docs linked from the top. There are required tags to build virtual services.
Sorry, something went wrong.
plz fix the bug in file src/SkyApm.Diagnostics.EntityFrameworkCore.Pomelo.MySql/MySqlEntityFrameworkCoreSpanMetadataProvider.cs as follow,
public bool Match(DbConnection connection) { var fullName = connection.GetType().FullName; return fullName == "MySql.Data.MySqlClient.MySqlConnection" || fullName == "MySqlConnector.MySqlConnection"; }
so that the Virtual Database can be retrieved correctly.
If you want to propose some changes, feel free to submit a pull request.
This is not a bug. The dot net agent exists before the virtual database/cache/queue concept. So, it may not be aligned with the newer concept.
Welcome to contribute to the project.
No branches or pull requests
Please answer these questions before submitting your issue.
Question
this is no service name display in Virtual Database
Bug
Which version of SkyWalking, OS and .NET Runtime?
SkyWalking version : 9.4.0
OS: LINUX CentOS 7.9
.NET RUNTIME: 3.1
Which company or project?
What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.
Requirement or improvement
The text was updated successfully, but these errors were encountered: