You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a need to monitor our Splitter and Factory deployments on testnet/mainnet and integration with various protocols on Dune. Analyzing these elements is essential but often challenging because of the immense amount of data and the various metrics that need to be presented.
🛠️ Proposed solution
To address the problem, the following steps can be taken to build a dashboard to monitor Splitter and Factory deployments and integration with various protocols:
Identifying the Metrics: Determine what to analyze and the metrics to present.
Utilizing Pre-Built Dashboards: Leverage existing community-contributed guides and dashboards and analyze existing metrics and trends
Creating Custom Dashboards: Utilize Dune's platform to create custom charts and dashboards using plain SQL, leveraging decoded Ethereum smart contract data
Connecting and Integrating Protocols: Consider the mix of on-chain events happening and ensure integration trends are incorporated into the dashboard.
Sharing and Collaborating: Once the dashboard is complete, share the work in communities, get feedback, and make necessary improvements.
Continuous Monitoring and Updates: Keep the dashboard up-to-date and adjust as new information and changes occur within the web3 data analytics space.
The text was updated successfully, but these errors were encountered:
🎯 Problem to be solved
There is a need to monitor our Splitter and Factory deployments on testnet/mainnet and integration with various protocols on Dune. Analyzing these elements is essential but often challenging because of the immense amount of data and the various metrics that need to be presented.
🛠️ Proposed solution
To address the problem, the following steps can be taken to build a dashboard to monitor Splitter and Factory deployments and integration with various protocols:
The text was updated successfully, but these errors were encountered: