-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Add /deep-dependencies
endpoint
#7399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add /deep-dependencies
endpoint
#7399
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7399 +/- ##
==========================================
- Coverage 96.46% 96.46% -0.01%
==========================================
Files 375 377 +2
Lines 22951 23071 +120
==========================================
+ Hits 22140 22255 +115
- Misses 613 617 +4
- Partials 198 199 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This commit introduce new endpint with fake deep dependencies data. Resolves jaegertracing#6606. Signed-off-by: Sujal Shah <sujalshah28092004@gmail.com>
0237520
to
44388c7
Compare
This commit updates the Deep Dependency Graph UI logic to use the correct backend API endpoint for fetching data. Resolves [#6606](jaegertracing/jaeger#6606). Part of [#7399](jaegertracing/jaeger#7399). Signed-off-by: Sujal Shah <sujalshah28092004@gmail.com>
Signed-off-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
/deep-dependencies
endpoint/deep-dependencies
endpoint
@@ -876,6 +877,21 @@ func TestGetQualityMetrics(t *testing.T) { | |||
require.Contains(t, resp.TraceQualityDocumentationLink, "github.com/jaegertracing") | |||
} | |||
|
|||
func TestGetDeepDependenciesData(t *testing.T) { | |||
handler := &APIHandler{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test creates an empty APIHandler
without initialization, which may cause failures when writeJSON()
is called in the deepDependencies
handler. Consider using initializeTestServer()
(as used in other tests) or initializing the handler with required dependencies like a logger. This would better match the production environment and ensure all handler dependencies are properly satisfied.
handler := &APIHandler{} | |
handler := initializeTestServer(nil) |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
This commit introduce new endpint with fake
deep dependencies data.
Part of #6606.
Screenshots and Screencaptures
output.mov
NOTE: The above graph shown in the visuals will only be shown after UI changes(See PR ). This PR only focuses on the backend level change.
Checklist
jaeger
:make lint test
jaeger-ui
:npm run lint
andnpm run test