https://signoz.io logo
#support
Title
# support
h

Henri Ropponen

11/17/2023, 8:48 AM
Hi, Logs explorer no longer shows any logs in the list view. Currently have installed v0.34.0. I believe this was happening already in v0.33.1. We see this happening in the developer tools console. @Yunus M
Copy code
Error: API responded with 400 -  encountered multiple errors: error in query-A: code: 47, message: Missing columns: 'attributes_bool_key' 'attributes_bool_value' while processing query: 'SELECT timestamp, id, trace_id, span_id, trace_flags, severity_text, severity_number, body, CAST((attributes_string_key, attributes_string_value), 'Map(String, String)') AS attributes_string, CAST((attributes_int64_key, attributes_int64_value), 'Map(String, Int64)') AS attributes_int64, CAST((attributes_float64_key, attributes_float64_value), 'Map(String, Float64)') AS attributes_float64, CAST((attributes_bool_key, attributes_bool_value), 'Map(String, Bool)') AS attributes_bool, CAST((resources_string_key, resources_string_value), 'Map(String, String)') AS resources_string FROM signoz_logs.distributed_logs WHERE (timestamp >= 1700208960000000000) AND (timestamp <= 1700210760000000000) ORDER BY timestamp DESC LIMIT 0, 100', required columns: 'trace_id' 'span_id' 'attributes_bool_value' 'timestamp' 'id' 'body' 'trace_flags' 'severity_number' 'attributes_int64_key' 'attributes_float64_value' 'resources_string_value' 'resources_string_key' 'severity_text' 'attributes_string_key' 'attributes_int64_value' 'attributes_string_value' 'attributes_float64_key' 'attributes_bool_key', maybe you meant: 'trace_id', 'span_id', 'attributes_int64_value', 'timestamp', 'id', 'body', 'trace_flags', 'severity_number', 'attributes_int64_key', 'attributes_float64_value', 'resources_string_value', 'resources_string_key', 'severity_text', 'attributes_string_key', 'attributes_string_value' or 'attributes_float64_key'
    at src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:15653
    at p (src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:9155)
    at Generator.<anonymous> (src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:10501)
    at Generator.next (src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:9584)
    at f (src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:15070)
    at i (src_lib_dashboard_getQueryResults_ts.8141b02d95bd8fc761e7.js:2:16239)
n

nitya-signoz

11/17/2023, 9:01 AM
This means your otel collector migrator didn’t run successfully and the corresponding migration was not complete. https://github.com/SigNoz/signoz/blob/31b5635339560d01bedb2a6f724f4ccddb91fb99/deploy/docker/clickhouse-setup/docker-compose.yaml#L217
Are you running on docker or kubernetes.
h

Henri Ropponen

11/17/2023, 9:02 AM
Docker
n

nitya-signoz

11/17/2023, 9:02 AM
can you check logs of
otel-collector-migrator
? and try rerunning the container as well ?
h

Henri Ropponen

11/17/2023, 9:04 AM
I see now that we do not have the migrator. Was this added recently? We'll add it and report back. Thanks for the quick response! 🙂
n

nitya-signoz

11/17/2023, 9:04 AM
yeah it was added recently.
h

Henri Ropponen

11/17/2023, 11:24 AM
That was it! Now I see the logs again 🙏