ADO.NET Backends
The .NET Agent automatically discovers ADO.NET data providers implementing standard Microsoft interfaces as database backends. See .NET Supported Environments.
Because the ADO.NET API is interface-based, Splunk AppDynamics instruments all ADO.NET database providers that implement these interfaces by default.
Splunk AppDynamics uses database identification information from the ADO.NET connection string. The connection string specifies the server address and schema, or the local file name. Most connection strings are formatted based on common rules that you can parse and distill to a database name. However because no standards exist for the connection string, the ADO.NET provider implementer determines the format.
For some providers, Splunk AppDynamics may fail to parse the connection string. In these cases, the .NET Agent uses the complete connection string minus any user password. The property is labeled ADO.NET connection string, and the value shows the connection string minus any user password.
For example, the .NET Agent names this database backend using the connection string pattern <datasource name>-<database name>
.
.\SQLEXPRESS-HowdyWorldDB
ADO.NET Configurable Properties
You can enable or disable the use of these properties for ADO.NET exit points:
Configurable Properties | Default Detection and Naming Property? | Description |
---|---|---|
Vendor | No | Type of client-side ADO.NET library |
Connection String | No | Full connection string with password filtered out |
Port | No | Port number |
Host | Yes | Data source or database server |
Database | Yes | Database name |