Enum InstrumentationEvent

#[non_exhaustive]
pub enum InstrumentationEvent<'a> {
    #[non_exhaustive]
    StartEstablishConnection {
        url: &'a str,
    },
    #[non_exhaustive]
    FinishEstablishConnection {
        url: &'a str,
        error: Option<&'a ConnectionError>,
    },
    #[non_exhaustive]
    StartQuery {
        query: &'a dyn DebugQuery,
    },
    #[non_exhaustive]
    CacheQuery {
        sql: &'a str,
    },
    #[non_exhaustive]
    FinishQuery {
        query: &'a dyn DebugQuery,
        error: Option<&'a Error>,
    },
    #[non_exhaustive]
    BeginTransaction {
        depth: NonZeroU32,
    },
    #[non_exhaustive]
    CommitTransaction {
        depth: NonZeroU32,
    },
    #[non_exhaustive]
    RollbackTransaction {
        depth: NonZeroU32,
    },
}

This enum describes possible connection events that can be handled by an Instrumentation implementation

Some fields might contain sensitive information, like login details for the database.

Diesel does not guarantee that future versions will emit the same events in the same order or timing. In addition the output of the Debug and Display implementation of the enum itself and any of its fields is not guarantee to be stable.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

StartEstablishConnection

An event emitted by before starting establishing a new connection

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

url: &'a str

The database url the connection tries to connect to

This might contain sensitive information like the database password

FinishEstablishConnection

An event emitted after establishing a new connection

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

url: &'a str

The database url the connection tries is connected to

This might contain sensitive information like the database password

error: Option<&'a ConnectionError>

An optional error if the connection failed

StartQuery

An event that is emitted before executing a query

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

query: &'a dyn DebugQuery

A opaque representation of the query

This type implements Debug and Display, but should be considered otherwise as opaque.

The exact output of the Debug and Display implementation is not considered as part of the stable API.

CacheQuery

An event that is emitted when a query is cached in the connection internal prepared statement cache

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

sql: &'a str

SQL string of the cached query

FinishQuery

An event that is emitted after executing a query

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

query: &'a dyn DebugQuery

A opaque representation of the query

This type implements Debug and Display, but should be considered otherwise as opaque.

The exact output of the Debug and Display implementation is not considered as part of the stable API.

error: Option<&'a Error>

An optional error if the connection failed

BeginTransaction

An event that is emitted while starting a new transaction

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

depth: NonZeroU32

Transaction level of the newly started transaction

CommitTransaction

An event that is emitted while committing a transaction

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

depth: NonZeroU32

Transaction level of the to be committed transaction

RollbackTransaction

An event that is emitted while rolling back a transaction

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

depth: NonZeroU32

Transaction level of the to be rolled back transaction

Implementations

impl<'a> InstrumentationEvent<'a>

pub fn start_establish_connection(url: &'a str) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::StartEstablishConnection event

pub fn finish_establish_connection( url: &'a str, error: Option<&'a ConnectionError>, ) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::FinishEstablishConnection event

pub fn start_query(query: &'a dyn DebugQuery) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::StartQuery event

pub fn cache_query(sql: &'a str) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::CacheQuery event

pub fn finish_query(query: &'a dyn DebugQuery, error: Option<&'a Error>) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::FinishQuery event

pub fn begin_transaction(depth: NonZeroU32) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::BeginTransaction event

pub fn rollback_transaction(depth: NonZeroU32) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::RollbackTransaction event

pub fn commit_transaction(depth: NonZeroU32) -> Self

Available on crate feature i-implement-a-third-party-backend-and-opt-into-breaking-changes only.

Create a new InstrumentationEvent::CommitTransaction event

Trait Implementations

impl<'a> Debug for InstrumentationEvent<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.