Open davidd8 opened 2 years ago
@davidd8 Looking at the logs no publication failure,query:(match_phrase:(cluster:mainnet-us-east-1-eks))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'logzioCustomerIndex',key:kubernetes.namespace,negate:!f,params:(query:ntwk-mainnet-dealbot),type:phrase),query:(match_phrase:(kubernetes.namespace:ntwk-mainnet-dealbot))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'logzioCustomerIndex',key:kubernetes.container.name,negate:!f,params:(query:dealbot-controller),type:phrase),query:(match_phrase:(kubernetes.container.name:dealbot-controller))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'logzioCustomerIndex',key:logger,negate:!f,params:(query:controller),type:phrase),query:(match_phrase:(logger:controller)))),index:'logzioCustomerIndex',interval:auto,query:(language:lucene,query:'%22Failed%20to%20publish%22'),sort:!(!('@timestamp',desc)))&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30d,to:now))&discoverTab=logz-logs-tab&accountIds=true&switchToAccountId=104138) is occurring.
It seems no data is being produced at all to be published in the first place.
Can you point me to logs that suggest otherwise please?
Right. the dealbot model is that data is only propagated to pando when a dealbot daemon is 'finalized' / rotated. This is so that the active IPs / identities of daemons still doing in-process work are not exposed publicly until that bot has been swapped out.
We'll need to continue understanding usage by data programs, which has stopped rotated daemon processes regularly unless we ask them to because disks fill up.
Investigate reports that dealbot data is not propagating to the Pando service.