Hi,
The docs state that the k8s deployment automa...
# supports
Saajid Mohammed
03/08/2023, 6:21 PMHi,
The docs state that the k8s deployment automatically parses container_name and other relevant k8 fields, and I can see them within the log record. Do I have to do another step to make it a "suggested field" or should I be able to query it as is.
Side Question: Are there any k8 helm examples for modifying the collector for json parsing specifically?
Thanks in advance.
n
nitya-signoz
03/09/2023, 7:18 AMI don’t see k8s_container_name in selected or interesting fields, if it’s not present you won’t be able to query it.
Are your logs getting ingested? also where is your k8s cluster running can you provide some more info.
s
Saajid Mohammed
03/09/2023, 2:31 PMYep, all the logs are coming through as expected, and I can see the
resources_string.k8s_container_namen
nitya-signoz
03/09/2023, 3:37 PMIf thats the case then these should also appear as fields on the left side of the logs page.
can you share the output of the following commands.
Copy code
kubectl exec -n platform -it chi-my-release-clickhouse-cluster-0-0-0 -- sh
clickhouse client
use signoz_logs;
select distinct name from distributed_logs_resource_keys;s
Saajid Mohammed
03/09/2023, 3:40 PM Copy code
SELECT DISTINCT name
FROM distributed_logs_resource_keys
Query id: 02a3aa7e-bcc4-4b13-a527-0223530f3dd4
┌─name────────────────────────┐
│ host_name │
│ os_type │
│ signoz_component │
└─────────────────────────────┘Saajid Mohammed
03/09/2023, 3:42 PMI've deployed the helm to another environment with the same setup and it show and is queriable as expected... is it possible a redeployment should solve it?
n
nitya-signoz
03/09/2023, 3:42 PMOne more question how many shards of clickhouse do you have ?
s
Saajid Mohammed
03/09/2023, 3:46 PMIt should just be the one.
n
nitya-signoz
03/09/2023, 3:47 PMGot it then if your logs data is not important you can stop the otel collector pod, delete the
signoz_logsdrop database signoz_logss
Saajid Mohammed
03/09/2023, 3:48 PMAwesome, thank you. I'll give it a go and report back
Saajid Mohammed
03/09/2023, 7:00 PMReporting back, deleting the database broke things and signoz was unable to recover gracefully, no logs and was unable to get new logs even after rebooting all pods. I did however took everything down and redeployed and things seem to be working as the other environment now. Thanks for your time.
n
nitya-signoz
03/10/2023, 4:39 AMThat’s strange, did you stop the collectors before deleting the database?
And by broke can you share what happened exactly ?
s
Saajid Mohammed
03/10/2023, 2:31 PMyep, stop everything but the clickhouse pod.
And by broke I mean no logs after starting them back up and no errors in either the agents or the collectors.
2 Views