Weekly Sync - 10 October 2023

[github-actions[bot]]

Please add agenda items below and give your weekly update in a comment. Thank you!

Agenda

• @dragosp1011 @raducristianpopa : Payments for really small amounts as well for example 0.01 testnet#828
• @Tymmmy : testnet WM accounting
• @sabineschaller : Progress and priorities
• @JoblersTune : Telemetry status update

If we have time:

• @sabineschaller : Adjustable streaming outgoing payments #2014

[Tymmmy]

• Quite a few stories were picked up by #hacktoberfest devs so I organized the stories, feedback for PRs, help for local instalation, already 2 PRs approved and merged
• Help other people from IL community handle local testnet environment
• Finish up Websocket story, added notifications when user receives money
• Further testing Boutique and OP snipets
• Continue exchange button story, find out if we can make it different from Send money to yourself
• Many org stuff

[beniaminmunteanu]

Working on telemetry:
Progress:

• Current experimental dashboards:

• Managed to get transactions based on different asset codes in the same graphic (top-right)
  any new asset code will show up with a different color in the graphic.
  Legend indicates asset_code
• Managed to get transaction counts of different rafiki instances and their total in the same graph (top-left)
• Managed to use rate-of-change operators in order to get time-series graphics
  also just found this video discussing the issue of ever increasing counters and how the PromQL rate of change operators work

Issues:
It's not smooth sailing.

• Counters are cumulative
  Using counter for metrics, we get cummulative value for each metric.

  Example:
  If 4 transactions of 250 eur happen, the counter will reach the value of 1000.
  If next transaction is 100 eur, the sent metric will be 1100.

  Solution
  We must use derivatives, and create the graphic based on the rate of change, not on actual values.
  Still experimenting and researching on PromQL operators in order to achieve this.

• OTEL collector periodically sends same metric
  Another issue I'm looking for a solution for is also related to the dashboard graphic:
  Our opentelemetry collector pushes metrics every 1 minute (configurable period). But each time it send metrics, it sends the current counters even if they haven't increased.
  As such, if our last transaction was of value 100, that will be sent every minute (which is also another factor for going for rates of changes instead of actual values in the dashboards)

  Currently, the graphics end up looking like this (after sending some transactions, the last one being of 100 USD, and then halting transactions):
  
  In the bottom-left graphic for example, I want to make the bar drop to 0. I'm still trying to figure this out and fix it by using PromQl operations

• Cumulating metrics from multiple rafiki instances

  Even though all rafiki instances can have their own OTEL collector exporters, their counters will only have knowledge on what is happening in that specific rafiki instance. One instance can reach X value on transactions, while another will reach Y.
  Given the example dashboard for average of transactions, this can become an issue, as the rate of change is PER instance, and not per whole network.

  Still looking into this as well.

[dragosp1011]

• investigated and opened a PR for the issue with depositing additional funds to rapyd if there are no enough funds in settlement account
• investigated the issue why 0.01 transactions are failing for asset 2
• continued testing the autopeering stuff and added a few scripts to run everything in one command
  In the next days will work on generating unique ilp addresses for each device so the peering won't be overwritten and on adding the necessary description in documentation

[raducristianpopa]

• OP snippets feedback
• PR Reviews
• Released the VSCode extension
  • workflows/scripts for auto-release and generating the snippets table in the README
  • fixed a minor issue for the extension - it was not working with older versions of VSCode
• Started working on One click buy for Boutique
• WM Diagrams for Ionut

Will continue to work on:

• One click buy feature
• Prep for Hackathon

[domin191013]

• resolved comments on quote unit tests
• created a PR for user unit tests
• will work on new ticket related to not sending notification for exchange events

[JoblersTune]

I've been working on making our Grafana dashboard publicly viewable. The two options I've seen are to either set the dashboard to be public and we could then use a CNAME to redirect one of our subdomains there or to enable emedding so we could add the dashboard to an iframe. However both options require access to Grafana configuration files which we cannot access directly using Amazon managed Grafana. Looking into using grafana.net instead to see if that will still work with our Amazon managed Prometheus and if that will solve our problems.
Also updated the telemetry code so that all transaction amounts are collected at a scale of 4. This way we can display total amounts over the network or average amounts in a sensible way per asset code.

[sabineschaller]

I did a bunch of PR reviews, worked on my PR, which is up for review now

• feat: add AWS lambda for https signatures #1964

and worked with Max to create our talk for the ILP summit.

[njlie]

• Added wallet address parameter to resource requests (feat: add wallet address to subresource requests open-payments#305)
• Fixed issue creating noninteractive grants in AS (fix(auth): fix noninteractive grant creation #2003)
• Contributed more work to renaming 'payment pointer' to 'wallet address' (feat(backend): rename "payment pointer" tables & columns to use "wallet address" #1937 & docs: replace payment pointer with wallet address #1951).
• Will work on getting PRs over finish line, and implementing code changes in Rafiki to reflect the new wallet address request parameter & ILP summit talk.

[mkurapov]

• Working with Sabine on our presentation for the ILP summit last week
• Merged in the start of decoupling payment method changes: feat: payment method handler service (quoting) #1974 as well as decoupling ILP from the quoteService: feat: use payment manager handler in quote service #1994
• Will continue this week with trying to help get open payment changes over the line as well as continuing with the Payment Method story: Mojaloop as a payment method #1965

[BlairCurrey]

• merged open-payments client public incoming-payment get feat(open-payment): add unauthenticated payment get open-payments#307
• working on connection removal changes from rafiki work week: Implement payment methods and finish removing connections #1962