Prashant Shahi

Hey @KR-Ravindra! Thanks for the PR however I am getting error while loading the SigNoz UI. Have you tested this locally? `*http://localhost:3301*`  `*http://localhost:3301/signozui/*` 

@bmike78 Thanks for raising this PR! There are other places as well where you would have to make changes for example, in other Alertmanager data and SQLite data in Query-service...

@bmike78 Unfortunately, this change is specific to very small number of scenario. While it might be relevant for your use case, most users might require the data to be persisted...

Hi @rinshadka :wave: It is not mandatory for running SigNoz. We mainly use it to tail and parse logs from all containers and send it to SigNoz OtelCollector running locally....

Not able to replicate the issue in EKS with K8s version

@lazywei I suppose it's the latter one using headless service. The first one will make sense when only one instance of keeper is being used.

We have Ingestion Token for SigNoz Cloud user, which is used to send telemetry data. That is often referred as SigNoz API Key in docs (that will be updated to...

@kcns008 Thanks for creating this issue. We will be looking into it.

Meanwhile, can you check the log path of containers on host machine itself? It should be in pattern something like this `/var/log/pods/*/*/*.log`. How did you confirm this path`/app/resources/logs/${HOSTNAME}.log`?

From the shared screenshot, I see there is no container for signoz-otel-collector. Do check why that container is not up.