Description:

The observation scope for "jdbc.connection" is opened when a DB connection is acquired and closes when the DB connection is closed.
When Open In View (OIV) is enabled, since it delays the DB connection close until after the view is rendered, it causes the "jdbc.connection" observation/scope to leak outside of the intended observation boundary.

Example

@GetMapping("/")
List<Car> cars() {
  // (1)
  return Observation.createNotStarted("my.observation", registry).observe(() -> {
    // (2)
    List<Car> cars = repository.findAll();  // DB access
    // (3)
    return cars;
  });
  // (4)
}

OIV disabled

At point (1), the active scope is "http.server.requests".
At point (2), the active scope is "my.observation".
At point (3), the active scope is "my.observation".
At point (4), the active scope should be "http.server.requests".

OIV enabled

At point (1), the active scope is "http.server.requests".
At point (2), the active scope is "my.observation".
At point (3), the active scope is "jdbc.connection". <==
At point (4), the active scope is "jdbc.connection". <==

Proposing Change

There is no good reason to keep the jdbc.connection scope open for the entire lifetime of the connection.
Closing the scope right after acquisition ensures observations do not leak into application logic and keeps scope boundaries consistent.

To keep the observation hierarchy, pass the jdbc.connection observation as the parent to the child observations(query, result-set, generated-keys).