Fix the issue of duplicate traceId and spanId caused by RandomIdGenerator

[lyred193]

Description

Fix the issue of duplicate traceId and spanId when the user sets the global random operator seed.

Fixes #4376

Type of change

Please delete options that are not relevant.

• Bug fix

How Has This Been Tested?

• test_id_generator.py

Does This PR Require a Contrib Repo Change?

No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lyred193 / name: Lurious (22a5a84, de0cc5b, 0a6bb4f)

[xrmx]

Could you please add an explanation on why this fixes things?

[lyred193]

Could you please add an explanation on why this fixes things?

In some scenarios, such as model performance evaluation, we prefer the split between training and testing data to be random. By setting a fixed random seed, we can ensure that each model uses the same dataset for training and validation, enabling fair comparisons.

In this context, integrating OpenTelemetry can lead to the duplication of traceId and spanId if the application is restarted.

Here’s a demo:

import uvicorn
from fastapi import FastAPI, HTTPException
from logging import getLogger

_logger = getLogger(__name__)

def init():
    import random
    random.seed(10)

app = FastAPI()

@app.get("/health")
async def health_check():
    return {"data": "ok"}

@app.get("/evaluation")
async def evaluation():
    # Randomly generate a list of test numbers
    random_numbers = random.sample(range(1, 101), 10)
    '''
    Other operations
    test model 1
    test model 2
    '''
    return {"data": {"score": 0.6}}

if __name__ == "__main__":
    init()
    uvicorn.run(app, host="0.0.0.0", port=8000)

In this demo, when accessing the /evaluation endpoint, the generated traceId is 164207228320579316746596838417247989971, and the spanId is 273610340023782072, with the span name being /evaluation.

After restarting the application (due to an update or a manual restart), accessing the /health endpoint generates the same traceId 164207228320579316746596838417247989971 and spanId 273610340023782072. However, the span name has changed to /health, which is clearly incorrect.