Goal: Get Usage Metrics From TSN

[outerlook]

Tasks

• Problem: Missing Vector config to consume KGW metrics #377
• Problem: Missing Vector config to consume KGW metrics locally #447
• Problem: Missing SQS queues for KGW metrics #378
• Problem: Missing destination to SQS KGW Analytics #379
• Problem: KGW is outdated #437

Kwil Tasks

• Problem: Enable OTel Compatible Metrics from KGW #383

Blocked By

• Kwil DB v0.9

[outerlook]

Hey @markholdex, I see you previously converted #383 to a goal, but I'm structuring it slightly differently as there are other sub-tasks which #383 is also part of

does this make sense?

[outerlook]

@zolotokrylin @markholdex

Does this goal's inclusion on the TSN project's "TODO" list mean I can work on it if I'm blocked by other tasks?

[zolotokrylin]

@outerlook deffinatly. Are requirements already 100% clear/specified?

[markholdex]

@zolotokrylin @markholdex

Does this goal's inclusion on the TSN project's "TODO" list mean I can work on it if I'm blocked by other tasks?

Pretty much. As long as the specs/requirements are clear and defined. However, always check with other priorities on the roadmap.

This metrics are more oriented for the consumer. Think about the fact that we might need metrics related to the nodes

• Goal: onboard Kwil as Node Operator #393

that we are deploying soon (runtime, fails, response time, etc.). It might be a separate Goal but I wanted to mention here so you can consider the right priority.

[markholdex]

@outerlook is this Goal a duplicate of

• Goal: 99.9% TSN Reliability #415 ?

[outerlook]

Not exactly, but there is some overlap. I previously asked something similar here: https://docs.google.com/document/d/1-yxCyunqLhIHqLGJrIqScqRduo_lB3Ee6LGyeyY4B3A/edit?pli=1&disco=AAABUTVC6wo

However, this goal was previously more targetted at getting through KGW to serve the billing spec

the plan was just knowing how was the network being queried, with no intention to know what is happening at node level.

However, the new goal was raised more target at knowing what is going on specifically with nodes, how they are behaving if they are answering and participating the network.

The metrics are very similar, but the mechanism may be different, and the #415 results may impact this present goal, while using some of its same subset of problems (or mechanics)

I think we should reevaluate this one after #415 gets merged, since we may have easier ways to observe what we need

[MicBun]

log: added blocked by Kwil DB v0.9 to the issue description

[markholdex]

@outerlook feel free to wrap things up here as your next priority. Thank you!

[markholdex]

@outerlook have you started on this Goal? Do you have any ETA in mind?

[outerlook]

hey @markholdex

no I didn't, I'm tackling these which appeared to be prioritized:

• Problem: Network halted with lack of consensus truf-node-operator#34
• https://github.com/truflation/chainlink-config/issues/4
• https://github.com/truflation/index-creator/issues/75