Fix _entities Apollo Error Metrics Missing Service Attribute (backport #8153)#8172
Fix _entities Apollo Error Metrics Missing Service Attribute (backport #8153)#8172
Conversation
|
Cherry-pick of 78d22ee has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 7 changed, 0 removedBuild ID: 31ad78888bcdbd944c1ed8c6 URL: https://www.apollographql.com/docs/deploy-preview/31ad78888bcdbd944c1ed8c6 |
|
@mergify rebase |
✅ Branch has been successfully rebased |
910fd1e to
b969b7b
Compare
|
going to try a fresh PR because i backported this wrong. |
b969b7b to
d18a9d8
Compare
d18a9d8 to
3d9f962
Compare
|
@rregitsky This is my cherrypicking of your #8153 onto our upcoming 2.6.1. I know you can't approve your own PRs, but if you could make sure this still looks right and give your written LGTM, I'm happy to green-light it and land it myself. |
@abernix LGTM. I successfully tested the branch out locally as well. |
Error counting #7712 introduced a bug where
_entitieserrors from a subgraph fetch no longer reported a service (subgraph or connector) attribute. This erroneously categorized these errors as from the Router rather than their originating service in the Studio UI.The attribute has been re-added, fixing this issue.
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
[ROUTER-1424]: https://apollographql.atlassian.net/browse/ROUTER-1424?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
This is an automatic backport of pull request #8153 done by Mergify.
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
A lot of (if not most) features benefit from built-in observability and
debug-level logs. Please read this guidance on metrics best-practices. ↩Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩