dillu24 comments

Results 57 comments of


                                            dillu24

Deployed but no Data is visible

Could it be there is something wrong with the database?

Deployed but no Data is visible

Any news?

Implement the Strategy Pattern for the SubstrateNodeMonitor

@simplyrider Also suggested another approach for implementing the Monitors architecture: To make sure that the system never runs out of memory and CPU processing power is kept to a low...

Implement MonitorsManagers' functionality to start the GitHubMonitor

@simplyrider Also suggested another approach for implementing the Monitors architecture: To make sure that the system never runs out of memory and CPU processing power is kept to a low...

Implement Strategy Pattern for the ChainlinkContractStore

Another option is to implement the Strategy Pattern on the Existing `ChainlinkContractStore` and implement two abstract algorithms for the context class, `store_metric_state` and `store_metric_value`

Implement MonitorsManagers' functionality to start the ChainlinkNodeMonitor

@simplyrider Also suggested another approach for implementing the Monitors architecture: To make sure that the system never runs out of memory and CPU processing power is kept to a low...

Implement Strategy Pattern for the CosmosNetworkStore

Another option is to implement the Strategy Pattern on the Existing `CosmosNetworkStore` and implement two abstract algorithms for the context class, `store_metric_state` and `store_metric_value`

Implement the Strategy Pattern for the DockerHubMonitor

@simplyrider Also suggested another approach for implementing the Monitors architecture: To make sure that the system never runs out of memory and CPU processing power is kept to a low...

Implement the Strategy Pattern for the CosmosNetworkMonitor

@simplyrider Also suggested another approach for implementing the Monitors architecture: To make sure that the system never runs out of memory and CPU processing power is kept to a low...

Update managers to index sources by chain_id not chain name

The issue is that if we allow the user to change the sub-chain name, the alerter would not be able to delete the configs belonging to the old sub-chain, thus...