• Can you please provide command line args to override config params for the timeline? I will invoke this tool periodically, and changing config file programmatically each time is less than ideal. Doable, of course. But ugly.
• Can you please make the output name configurable via command line? Current way of auto-creating filenames is not very programmer friendly.

I want to be able to know the relays for an specific block height, so now because it is reusing the timeline idea, start is X and end should be X+1, but when X is the latest block height this throw errors so is not usuable.

type NodeReport struct {
	Service              []ServiceReport  `json:"serviced"`
	TotalRelays          int64            `json:"total_relays"`
	ServiceReportByChain map[string]int64 `json:"service_by_chain"`
}

type AppReport struct {
	ServicedBy            []ServiceReport  `json:"serviced_by"`
	TotalRelays           int64            `json:"total_relays"`
	ServicedReportByChain map[string]int64 `json:"serviced_by_chain"`
}

Make them the same to allow for easy parsing

After playing with it a bit.. I kinda think that it really needs to accept absolute block numbers in addition to relative to current block time periods. as well as printing same in the report file.

I would find it much easier to run batches and keep them organized by month or week or whatever if the header info contained min and max height.
Thank you.

Do I need to run a downgraded version? or Am I doing something else wrong?

$ go get github.com/pokt-network/relay_counter

github.com/pokt-network/pocket-core/types

go/pkg/mod/github.com/pokt-network/[email protected]/types/config.go:130:20: c.TendermintConfig.LevelDBOptions undefined (type config.Config has no field or method LevelDBOptions)
go/pkg/mod/github.com/pokt-network/[email protected]/types/config.go:130:38: undefined: config.DefaultLevelDBOpts
go/pkg/mod/github.com/pokt-network/[email protected]/types/config.go:173:3: t.LevelDBOptions undefined (type *config.Config has no field or method LevelDBOptions)
go/pkg/mod/github.com/pokt-network/[email protected]/types/config.go:173:21: undefined: config.DefaultLevelDBOpts
go/pkg/mod/github.com/pokt-network/[email protected]/types/context.go:271:3: unknown field 'NumTxs' in struct literal of type "github.com/tendermint/tendermint/abci/types".Header
go/pkg/mod/github.com/pokt-network/[email protected]/types/context.go:272:3: unknown field 'TotalTxs' in struct literal of type "github.com/tendermint/tendermint/abci/types".Header
go/pkg/mod/github.com/pokt-network/[email protected]/types/indexer.go:192:81: undefined: query.Page
go/pkg/mod/github.com/pokt-network/[email protected]/types/indexer.go:200:81: undefined: query.Page
go/pkg/mod/github.com/pokt-network/[email protected]/types/indexer.go:208:84: undefined: query.Page
go/pkg/mod/github.com/pokt-network/[email protected]/types/indexer.go:216:69: undefined: query.Page
go/pkg/mod/github.com/pokt-network/[email protected]/types/context.go:272:3: too many errors

I am receiving this error on healthy nodes, completely up to speed with current block height and with bunch of relays and rewards.

This error doesn't happen if I use blocks as timeline unit vs. days. Perhaps a bug in binary search logic?

go run ./ ...
2021/02/23 04:03:48 Attempting to read Config file:
2021/02/23 04:03:48 Config File Processed:
2021/02/23 04:03:48 {{-4 -1 days} http://localhost:8082/v1 3 {15 4}}
2021/02/23 04:03:48 Testing Pocket Endpoint
2021/02/23 04:03:48 Converting Timeline To Block Heights
2021/02/23 04:03:48 Getting the latest height
2021/02/23 04:03:48 Getting the latest block
2021/02/23 04:03:48 Latest height is 19243 and latest time is: 2021-02-23 03:41:33.185792419 +0000 UTC
2021/02/23 04:03:48 Timeline unit is days
2021/02/23 04:03:48 Calclating the approximate start and end times
2021/02/23 04:03:48 Target start: 2021-02-19 03:41:33.185792419 +0000 UTC
Target End: 2021-02-22 03:41:33.185792419 +0000 UTC
2021/02/23 04:03:48 Begin Closest Height Operations
2021/02/23 04:03:48 Performing a binary search for the closest height to the target time: 2021-02-19 03:41:33.185792419 +0000 UTC
2021/02/23 04:03:48 min:  0 max 19243 try height 18859 closest height 18859
2021/02/23 04:03:48 min:  18859 max 19243 try height 19051 closest height 18859
2021/02/23 04:03:48 RPC failure for block by height: Unregistered interface types.Evidence
Trying to retry. Retry count is: 0/3
2021/02/23 04:03:53 min:  18859 max 19243 try height 19051 closest height 18859
2021/02/23 04:03:54 RPC failure for block by height: Unregistered interface types.Evidence
Trying to retry. Retry count is: 1/3
2021/02/23 04:03:59 min:  18859 max 19243 try height 19051 closest height 18859
2021/02/23 04:03:59 RPC failure for block by height: Unregistered interface types.Evidence
Trying to retry. Retry count is: 2/3
2021/02/23 04:04:04 min:  18859 max 19243 try height 19051 closest height 18859
2021/02/23 04:04:04 After 3 retries, unable to get block for height: 19051, with error: Unregistered interface types.Evidence
exit status 1

Finally got caught up enough to look at this relay counter.
running a 5 block sample but not succeeding.
here's the config
{
"timeline": {
"start": -5,
"end": 0,
"unit": "blocks"
},
"endpoint": "http://localhost:8082/v1",
"http_retry": 3,
"params": {
"blocks_per_session": 4,
"approx_block_time_in_min": 15
}
}

Thoughts?