Change Details

[ENG-11111](https://linear.app/comm/issue/ENG-11111/implement-monitoring-for-farcaster-websocket-connection). Added some metrics to be able to monitor `TokenDistributor` mechanism, similar to how our telemetry for errors works. I deployed this on staging, and after going into `Cloudwatch -> Metrics`, I was able to see all the events. We can also create a dashboard for this using multi-source metrics, like this: {F12200283} I'll create a follow-up task for this, and another for configuring alarms if needed. Depends on D15231

[ENG-11111](https://linear.app/comm/issue/ENG-11111/implement-monitoring-for-farcaster-websocket-connection). Added some metrics to be able to monitor `TokenDistributor` mechanism, similar to how our telemetry for errors works. I deployed this on staging, and after going into `Cloudwatch -> Metrics`, I was able to see all the events. We can also create a dashboard for this using multi-source metrics, like this: {F12200283} I'll create a follow-up task for this ([link](https://linear.app/comm/issue/ENG-11163/implement-farcaster-tokens-dashboard-in-cloudwatch)), and another for configuring alarms if needed ([link](https://linear.app/comm/issue/ENG-11164/create-alarms-for-farcaster-tokens)). Depends on D15231

[ENG-11111](https://linear.app/comm/issue/ENG-11111/implement-monitoring-for-farcaster-websocket-connection). Added some metrics to be able to monitor `TokenDistributor` mechanism, similar to how our telemetry for errors works. I deployed this on staging, and after going into `Cloudwatch -> Metrics`, I was able to see all the events. We can also create a dashboard for this using multi-source metrics, like this: {F12200283} I'll create a follow-up task for this ([link](https://linear.app/comm/issue/ENG-11163/implement-farcaster-tokens-dashboard-in-cloudwatch)), and another for configuring alarms if needed ([link](https://linear.app/comm/issue/ENG-11164/create-alarms-for-farcaster-tokens)). Depends on D15231