Update diesel-dtrace, fix transaction depth predicate in probe

oxidecomputer · Dec 13, 2024 · c371852 · c371852
1 parent 7b99029
commit c371852
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 9 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/tools/dtrace/nexus/trace-transactions.d b/tools/dtrace/nexus/trace-transactions.d
@@ -33,15 +33,9 @@ diesel_db$target:::query-start
 /*
  * As transactions complete, print the number of statements we ran and the
  * duration.
- *
- * NOTE: The depth, arg1, is intentionally 1 here. When we first enter a
- * non-nested transaction, the depth is 0, because there is no outer
- * transaction. However, when the `transaction-done` probe fires, we are still
- * in a transaction, in which case the depth is currently 1. It's decremented
- * _after_ the transaction itself is committed or rolled back.
  */
-diesel_db$targe:::transaction-done
-/arg1 == 1 && ts[copyinstr(arg0)]/
+diesel_db$target:::transaction-done
+/arg1 == 0 && ts[copyinstr(arg0)]/
 {
     this->key = copyinstr(arg0);
     this->conn_id = json(this->key, "ok");