Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Frontend requests correct span status but wrong http.status_code and two independent traces produced instead of one #749

Closed
devrimdemiroz opened this issue Feb 19, 2023 · 0 comments · Fixed by #810
Assignees
Labels
bug Something isn't working frontend

Comments

@devrimdemiroz
Copy link
Contributor

devrimdemiroz commented Feb 19, 2023

Bug Report

Version:
b2f729a56884e3b55e1e203897c9644d8d92a8a9
v 1.3.0 release

Symptom

See the screenshot attached.

1- Frontend request returns an error but sets http.status_code to 200 always. Following is the code segment.

frontend/pages/api/cart.ts
case 'POST': {
const { userId, item } = body as AddItemRequest;

  await CartGateway.addItem(userId, item!);
  const cart = await CartGateway.getCart(userId);

  return res.status(200).json(cart);
}

2- Two separate trace is observed, the second trace has reference spanid as FOLLOWS_FROM. Better (even async) to have one trace that starts from the loadgenerator until the end of the transaction.

Reproduce

When load generator runs, you can search "http.status_code=200" in traces and look into ones with "status=error"

Additional Context

Screenshot 2023-02-19 at 19 42 36

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working frontend
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants