Quick start guide issues

[mark-emc]

I'm trying to test out the stack but not having much luck. I'm wanting to run the docker compose setup on a windows 10 host, then run another native scollector instance on the same windows 10 host and query the data via Bosun.

The docker stack builds fine and the embedded scollector is working and I can query this data via both Bosun and OpenTSDB.

The guide says I can point scollector directly at the Bosun host. This doesn't seem to be the case for both versions of scollector:

container version

bash-5.1# ./scollector -version 2021/05/13 02:33:08 error: log_unix.go:13: Unix syslog delivery error 2021/05/13 02:33:08 info: log_unix.go:15: starting scollector version 0.9.0-preview-dev last modified 2021-05-12T01:08:32Z scollector version 0.9.0-preview-dev last modified 2021-05-12T01:08:32Z

bash-5.1# ./scollector -h bosun:8070 2021/05/13 02:28:46 error: log_unix.go:13: Unix syslog delivery error 2021/05/13 02:28:46 info: log_unix.go:15: starting scollector version 0.9.0-preview-dev last modified 2021-05-12T01:08:32Z 2021/05/13 02:28:46 info: elasticsearch.go:74: Using default IndexInterval: 15m0s for localhost_9200 2021/05/13 02:28:46 info: elasticsearch.go:83: Using default ClusterInterval: 15s for localhost_9200 2021/05/13 02:28:46 info: main.go:251: OpenTSDB host: http://bosun:8070 2021/05/13 02:28:46 error: interval.go:65: bosun.org/cmd/scollector/collectors.c_iostat_linux: cannot parse 2021/05/13 02:28:46 error: interval.go:65: bosun.org/cmd/scollector/collectors.c_dfstat_blocks_linux: exit status 1 2021/05/13 02:28:46 error: interval.go:65: bosun.org/cmd/scollector/collectors.c_dfstat_inodes_linux: exit status 1 2021/05/13 02:28:47 error: queue.go:123: 502 Bad Gateway 2021/05/13 02:28:47 info: queue.go:139: restored 500, sleeping 5s 2021/05/13 02:28:52 error: queue.go:123: 502 Bad Gateway 2021/05/13 02:28:52 info: queue.go:139: restored 500, sleeping 5s

windows version

C:\repos>scollector.exe -version scollector version 0.8.0 (67a8ce416becdbeaa9328ad2abafb3b2161a28df) built 2018-10-10T14:02:00Z

C:\repos>scollector.exe -h localhost:8070 2021/05/13 12:34:05 info: elasticsearch.go:74: Using default IndexInterval: 15m0s for localhost_9200 2021/05/13 12:34:05 info: elasticsearch.go:83: Using default ClusterInterval: 15s for localhost_9200 2021/05/13 12:34:08 info: main.go:256: OpenTSDB host: http://localhost:8070 2021/05/13 12:34:08 error: queue.go:123: 502 Bad Gateway 2021/05/13 12:34:08 info: queue.go:139: restored 5, sleeping 5s 2021/05/13 12:34:13 error: queue.go:123: 502 Bad Gateway 2021/05/13 12:34:13 info: queue.go:139: restored 191, sleeping 5s

If I use the docker OpenTSDB host instead with the windows scollector it works, but the data is only available via OpenTSDB, not Bosun. Could someone explain this behaviour? Does Bosun poll data from OpenTSDB directly or does scollector supply data to both systems via tsdbrelay?

[mark-emc]

I've modified the docker-compose.yml file to expose the tsdbrelay port (5252) on the bosun container. Pointing scollector at tsdbrelay results in the data being available in both Bosun and OpenTSDB.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.