MySQL Client integration reference

To get started with the Aspire MySQL integrations, follow the Get started with MySQL integrations guide.

This article includes full details about the Aspire MySQL Client integration, which allows you to connect to and interact with MySQL databases from your Aspire consuming projects.

Installation

To get started with the Aspire MySQL client integration, install the 📦 Aspire.MySqlConnector NuGet package in the client-consuming project, that is, the project for the application that uses the MySQL client. The MySQL client integration registers a MySqlConnector.MySqlDataSource instance that you can use to interact with MySQL.

dotnet add package Aspire.MySqlConnector

Add a MySQL data source

In the Program.cs file of your client-consuming project, call the AddMySqlDataSource extension method to register a MySqlDataSource for use via the dependency injection container:

builder.AddMySqlDataSource(connectionName: "mysqldb");

You can then retrieve the MySqlConnector.MySqlDataSource instance using dependency injection:

public class ExampleService(MySqlDataSource dataSource)
{
    // Use dataSource...
}

Add keyed MySQL data source

There might be situations where you want to register multiple MySqlDataSource instances with different connection names. To register keyed MySQL data sources, call the AddKeyedMySqlDataSource method:

builder.AddKeyedMySqlDataSource(name: "mainDb");
builder.AddKeyedMySqlDataSource(name: "loggingDb");

Then you can retrieve the MySqlDataSource instances using dependency injection:

public class ExampleService(
    [FromKeyedServices("mainDb")] MySqlDataSource mainDataSource,
    [FromKeyedServices("loggingDb")] MySqlDataSource loggingDataSource)
{
    // Use data sources...
}

For more information on keyed services, see .NET dependency injection: Keyed services.

Properties of the MySQL resources

When you use the WithReference method to pass a MySQL server or database resource from the AppHost project to a consuming client project, several properties are available to use in the consuming project.

Aspire exposes each property as an environment variable named [RESOURCE]_[PROPERTY]. For instance, the Uri property of a resource called mysqldb becomes MYSQLDB_URI.

MySQL server resource

The MySQL server resource exposes the following connection properties:

MySQL database resource

The MySQL database resource inherits all properties from its parent MySqlServerResource and adds:

Configuration

The MySQL database integration provides multiple options to configure the connection based on the requirements and conventions of your project.

Use a connection string

When using a connection string from the ConnectionStrings configuration section, you can provide the name of the connection string when calling AddMySqlDataSource:

builder.AddMySqlDataSource(connectionName: "mysql");

Then the connection string is retrieved from the ConnectionStrings configuration section:

{
  "ConnectionStrings": {
    "mysql": "Server=mysql;Database=mysqldb"
  }
}

For more information on how to format this connection string, see MySqlConnector: ConnectionString documentation.

Use configuration providers

The MySQL database integration supports Microsoft.Extensions.Configuration. It loads the MySqlConnectorSettings from configuration using the Aspire:MySqlConnector key. Example appsettings.json:

{
  "Aspire": {
    "MySqlConnector": {
      "ConnectionString": "YOUR_CONNECTIONSTRING",
      "DisableHealthChecks": true,
      "DisableTracing": true
    }
  }
}

For the complete MySQL client integration JSON schema, see Aspire.MySqlConnector/ConfigurationSchema.json.

Use inline delegates

You can pass the Action<MySqlConnectorSettings> delegate to set up some or all the options inline:

builder.AddMySqlDataSource(
    "mysql",
    static settings => settings.DisableHealthChecks = true);

Client integration health checks

By default, Aspire integrations enable health checks for all services. The MySQL database integration:

• Adds the health check when DisableHealthChecks is false, which verifies that a connection can be made and commands can be run against the MySQL database
• Integrates with the /health HTTP endpoint, which specifies all registered health checks must pass for app to be considered ready to accept traffic

Observability and telemetry

Aspire integrations automatically set up Logging, Tracing, and Metrics configurations, which are sometimes known as the pillars of observability. Depending on the backing service, some integrations may only support some of these features. For example, some integrations support logging and tracing, but not metrics. Telemetry features can also be disabled using the techniques presented in the Configuration section.

Logging

The MySQL integration uses the following log categories:

• MySqlConnector.ConnectionPool
• MySqlConnector.MySqlBulkCopy
• MySqlConnector.MySqlCommand
• MySqlConnector.MySqlConnection
• MySqlConnector.MySqlDataSource

Tracing

The MySQL integration emits the following tracing activities using OpenTelemetry:

• MySqlConnector

Metrics

The MySQL integration will emit the following metrics using OpenTelemetry:

• MySqlConnector
  • db.client.connections.create_time
  • db.client.connections.use_time
  • db.client.connections.wait_time
  • db.client.connections.idle.max
  • db.client.connections.idle.min
  • db.client.connections.max
  • db.client.connections.pending_requests
  • db.client.connections.timeouts
  • db.client.connections.usage