$ docker logs sentry_web 19:02:57 [WARNING] sentry.utils.geo: settings.GEOIP_PATH_MMDB not configured. 19:03:01 [INFO] sentry.plugins.github: apps-not-configured /usr/local/lib/python3.8/site-packages/memcache.py:1303: SyntaxWarning: "is" with a literal. Did you mean "=="? if key is '': /usr/local/lib/python3.8/site-packages/memcache.py:1304: SyntaxWarning: "is" with a literal. Did you mean "=="? if key_extra_len is 0: !! Configuration error: ConfigurationError("sentry.tsdb service failed to call validate()\nmodule 'sentry.tsdb.redis' has no attribute 'RedisSnubaTSDB'")
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 13 2023
Twitter support discontinuation
Twitter support discontinuation
Twitter support discontinuation
Twitter support discontinuation
Mar 12 2023
Empty log, container running.
s/volumes/binds
image ; uid/gid - symbolicator:x:10021:10021::/home/symbolicator:/bin/sh
+ image
So we decided to run each time bootstrap/migrate to ensure we're up-to-date.
Reconsolidate snuba and snuba_api: that will be less confusing to maintain if snuba is only snuba.
All containers are up:
Use full snuba command with docker exec
Nightly image
Not sure the network parameter works, as container _consumer wasn't connected:
$ snuba_containers="sentry_snuba_api sentry_snuba_consumer sentry_snuba_outcomes_consumer sentry_snuba_sessions_consumer sentry_snuba_transactions_consumer sentry_snuba_replays_consumer sentry_snuba_replacer sentry_snuba_subscription_consumer_events sentry_snuba_subscription_consumer_sessions sentry_snuba_subscription_consumer_transactions" $ docker stats $snuba_containers CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS d7fb9bf79329 sentry_snuba_api 0.00% 0B / 0B 0.00% 0B / 0B 0B / 0B 0 0ca62382910e sentry_snuba_consumer 0.45% 92.93MiB / 31.09GiB 0.29% 21.1kB / 10.9kB 0B / 0B 11 b01ba3b46457 sentry_snuba_outcomes_consumer 0.10% 92.27MiB / 31.09GiB 0.29% 8.08kB / 3.76kB 0B / 0B 5 30fcc4b9374d sentry_snuba_sessions_consumer 0.14% 92.26MiB / 31.09GiB 0.29% 10.2kB / 5.66kB 0B / 0B 5 fdabe0103fcf sentry_snuba_transactions_consumer 0.18% 92.23MiB / 31.09GiB 0.29% 10.2kB / 5.14kB 0B / 0B 8 d67d7260ab3e sentry_snuba_replays_consumer 0.11% 92.5MiB / 31.09GiB 0.29% 7.46kB / 3.4kB 0B / 0B 5 7b5920f801d8 sentry_snuba_replacer 0.10% 92.45MiB / 31.09GiB 0.29% 7.75kB / 3.56kB 0B / 0B 5 8a16768ac8a2 sentry_snuba_subscription_consumer_events 0.28% 93.58MiB / 31.09GiB 0.29% 11.7kB / 5.81kB 0B / 0B 9 0f043aee7ce5 sentry_snuba_subscription_consumer_sessions 0.00% 0B / 0B 0.00% 0B / 0B 0B / 0B 0 1686aea3ef0c sentry_snuba_subscription_consumer_transactions 0.24% 93.42MiB / 31.09GiB 0.29% 10.3kB / 5.14kB 0B / 0B 9
Remove port bindings
Mar 11 2023
$ geoipupdate […] # STATE: Creating configuration file at /etc/GeoIP.conf # STATE: Running geoipupdate $ docker ps -a | grep geoipupdate [nothing]
Renewed by @Sandlayth. DNS resolution works again.
Mar 10 2023
Wrappers part is omnipotent:
Linux capabilities (not required by Snuba, but nice to have for ClickHouse features)
2023.03.10 01:21:37.512800 [ 1 ] {} <Information> Application: It looks like the process has no CAP_NET_ADMIN capability, 'taskstats' performance statistics will be disabled. It could happen due to incorrect ClickHouse package installation. You could resolve the problem manually with 'sudo setcap cap_net_admin=+ep /usr/bin/clickhouse'. Note that it will not work on 'nosuid' mounted filesystems. It also doesn't work if you run clickhouse-server inside network namespace as it happens in some containers.
Current status