Hi #C01HWQ1R0BC, could you please help? Our log search is not functioning anymore. Issue: key

k8s.namespace.name

not found Supposed root cause: some log records do not have this field and got this error. Expected behavior: default value for the key is empty and perform search on record that match key and value. Reference: https://signoz.io/docs/userguide/search-troubleshooting/#key-fieldname-not-found

@Dang Huy Nguyen What version are you running on? There was a bug on 0.92.x series. I believe it was fixed in the 0.93.x series onward. So if you're running an earlier version, it might pay to update.

@Kieran Pilkington Thanks for your response. I use version 0.92.1. Is there any discussion/issue link for this issue?

@Dang Huy Nguyen the bug @Kieran Pilkington was referring to was very specific and not the same as yours. It was about

log.file_path

not working. In your case, there is no data with the key

k8s.namespace.name

. This is why you are getting the error.

default value for the key is empty and perform search on record that match key and value

Since there is no such key in the data, it won't even perform search. It the past we used perform search and silently return no data even if the key doesn't exist. That was not a good choice because it hides the problems. We want to solve the "telemetry drift" and this is the first step.

Hi @Srikanth Chekuri, there are ~58M records of my data have field `k8s.namespace.name`: Query:

SELECT COUNT(*)
FROM signoz_logs.distributed_logs_v2
WHERE resources_string['k8s.namespace.name'] != '';

Response:

58432117

The upgrade is completely unrelated to the issue. Check you

distributed_attribute_keys

and

distributed_resource_keys

table, they should contain all the keys. If a key is not present there then it will throw error.

distributed_resource_keys

table contains all key now. I will monitor behavior to see if the issue happens again

Hi @Dang Huy Nguyen, restart the collector

It works. Why is that ?