-
Notifications
You must be signed in to change notification settings - Fork 89
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
feat(telemetry): track local payments #2610
Conversation
* ci: WIP new integration test workflow no idea what the docker command will do... * fix: deps not found, add debug step * ci: add debug step * ci: use docker compose (v2) instead of docker-compose (v1) * chore: add setup from seed debug logs * ci: rework jobs into steps * chore: rm todo comment * chore: rm debug log * chore: shorten timeout in integration test * refactor: move integreation test job to lint_test_build * chore: test hostile cmd in ci, no setup host step * Revert "chore: test hostile cmd in ci, no setup host step" This reverts commit 5f529b2.
✅ Deploy Preview for brilliant-pasca-3e80ec ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
What would you like to do re: 'transactions_total' metric? Should we only call it if the receiver is at a remote rafiki?
packages/backend/src/payment-method/ilp/connector/core/middleware/telemetry.ts
Outdated
Show resolved
Hide resolved
Based on these changes, @mkurapov also brought up having 4 metrics, 2 for local and 2 for remote. |
packages/backend/src/payment-method/ilp/connector/core/test/middleware/telemetry.test.ts
Outdated
Show resolved
Hide resolved
packages/backend/src/payment-method/ilp/connector/core/test/middleware/telemetry.test.ts
Show resolved
Hide resolved
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.
Looks good, just some test comments.
packages/backend/src/payment-method/ilp/connector/core/test/middleware/telemetry.test.ts
Outdated
Show resolved
Hide resolved
packages/backend/src/payment-method/ilp/connector/core/test/middleware/telemetry.test.ts
Outdated
Show resolved
Hide resolved
packages/backend/src/payment-method/ilp/connector/core/test/middleware/telemetry.test.ts
Outdated
Show resolved
Hide resolved
const collectAmountSpy = jest | ||
.spyOn(telemetry, 'collectTelemetryAmount') | ||
.mockImplementation(() => { | ||
expect(nextCalled).toBe(true) |
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.
Ah, I understand, this ensures that next was called before the collectTelemetryAmount
👍
I was looking at some more of this, and this is something that exists in jest-extended, but not in the standard jest lib unfourtunately.
We can keep this test as is.
7095b15
to
566e1be
Compare
closed in favor of #2626 (which is a fresh duplicate). Will delete this source branch once that one gets merged |
Changes proposed in this pull request
This PR moves the amount metrics collection from the accounting service back to the ILP connector, as an extra middleware.
Context
All context is provided in the linked issue
fixes #2531 #2505
Checklist
Note
if you enable telemetry on the playground containers, you should be able to see the metrics output of your transactions here