Fix environment for browser traces (#25)

Author: petyosi

backend/api.py

@@ -94,9 +94,10 @@ async def game_move(db: Annotated[DB, Depends(DB.get_dep)], game_id: UUID4, colu
 async def client_traces(request: Request):
     httpx_client: httpx.AsyncClient = request.app.state.httpx_client
 
-    response = await httpx_client.post('v1/traces', json=await request.json())
-    if not response.is_success:
-        logfire.warn('prox failed {status=}', status=response.status_code, response=response.text)
+    with logfire.suppress_instrumentation():
+        response = await httpx_client.post('v1/traces', json=await request.json())
+        if not response.is_success:
+            logfire.warn('prox failed {status=}', status=response.status_code, response=response.text)
 
     return {
         'status_code': response.status_code,

backend/server.py

@@ -47,7 +47,7 @@ async def lifespan(app: fastapi.FastAPI):
 
 
 app = fastapi.FastAPI(lifespan=lifespan)
-logfire.instrument_fastapi(app, capture_headers=True)
+logfire.instrument_fastapi(app, capture_headers=True, excluded_urls=['client-traces'])
 logfire.instrument_pydantic_ai()
 logfire.instrument_asyncpg()
 logfire.instrument_httpx(capture_all=True)

frontend/src/Instrumentation.tsx

@@ -15,6 +15,7 @@ export const ClientInstrumentationProvider: Component<ClientInstrumentationProvi
     logfire.configure({
       traceUrl: url.toString(),
       serviceName: 'frontend',
+      environment: import.meta.env.MODE === 'development' ? 'dev' : 'prod',
       serviceVersion: '0.1.0',
       // for development purposes, we want to see traces as soon as they happen, so maxExportBatchSize is set to 1.
       // in production, we want to batch traces and send them in batches
@@ -25,6 +26,7 @@ export const ClientInstrumentationProvider: Component<ClientInstrumentationProvi
         getWebAutoInstrumentations({
           '@opentelemetry/instrumentation-fetch': {
             propagateTraceHeaderCorsUrls: /.*/,
+            ignoreNetworkEvents: true,
           },
           // disable user interaction instrumentation, clicks are not relevant for us
           '@opentelemetry/instrumentation-user-interaction': {