Don't start performance tracing if transaction is not sampled

Open on Drupal.org →

Created on 29 August 2023, 10 months ago

Problem/Motivation

If the transaction is not sampled, then as an optimization, we don't really need to start performance tracing.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Fixed

Version

4.0

Component

Code

Created by

🇺🇸United States mfb San Francisco

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Open in Jenkins → Open on Drupal.org →
Core: 10.1.x + Environment: PHP 8.2 & MySQL 8
last update 10 months ago
29 pass
Issue created by @mfb

Comment 10 months ago →

mfb → committed c6f8c0b7 on 4.x

Issue #3384104 by mfb: Don't start performance tracing if transaction is...

Comment 10 months ago →

mfb → committed 9c394b0f on 3.x

Issue #3384104 by mfb: Don't start performance tracing if transaction is...

Status changed to Fixed 10 months ago6:59pm 29 August 2023
Comment 10 months ago →
🇺🇸United States mfb San Francisco
Comment 10 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024