This message was deleted.
# supports
Slackbot
03/02/2022, 2:22 PMThis message was deleted.
a
Ankit Nayan
03/02/2022, 2:24 PM
are you seeing dataloss? data might have been successfully sent after automatic retry
Ankit Nayan
03/02/2022, 2:25 PM
also can you show output of
docker stats --no-streamz
Zaid Khan
03/02/2022, 2:30 PM@User Data is their in the traces. i am sending the stats output
Zaid Khan
03/02/2022, 2:33 PM@Ankit Nayan Please find this attached stats of docker
a
Ankit Nayan
03/02/2022, 2:39 PM
this error will be intermittent and dataloss should not be there
z
Zaid Khan
03/02/2022, 2:40 PM@User No, it's occurring continuously.
Zaid Khan
03/02/2022, 2:43 PMeven after server restart, it's giving me this exception
a
Ankit Nayan
03/02/2022, 2:44 PM
the otel-collector has maxed out on the memory allocated
Ankit Nayan
03/02/2022, 2:44 PM
that is the RAM available at the machine
Ankit Nayan
03/02/2022, 2:46 PM
and which version of SigNoz are you using v0.6.2 or earlier?
z
Zaid Khan
03/02/2022, 2:56 PMI have installed it on 10th February, 2022. Can you please guide me how to verify the version? I am unable to find it
Zaid Khan
03/02/2022, 2:59 PMI think I will be on v0.6.0 or v0.6.1
Zaid Khan
03/02/2022, 3:01 PMAlso, can you please tell me how to check the otel-collector memory?
a
Ankit Nayan
03/02/2022, 3:06 PM
docker stats --no-streamclickhouse-setup_otel-collector_1Ankit Nayan
03/02/2022, 3:07 PM
how urgent is the issue...we are making a new release tomorrow with new otel-collector image...currently checking the memory issue
Ankit Nayan
03/02/2022, 3:08 PM
if you can't wait till tomorrow, I can help you to do manual changes after updating to v0.6.2
z
Zaid Khan
03/02/2022, 3:09 PMok sure I can wait it till tomorrow. But can I pause the signoz (open telemetry)? As it's running on our internal server and I can get back to you by tomorrow for the update.
a
Ankit Nayan
03/02/2022, 3:12 PM
You don't need to stop signoz. The timeout shouldn't affect your application latency. Sending telemetry data is async and maintains a buffer after which it drops telemetry data if the application is not able to reach otel-collector and hence RAM usage also should not increase.
Ankit Nayan
03/02/2022, 3:13 PM
if you must, you would need to change the run command of your application by removing the
opentelemetry-instrumentAnkit Nayan
03/02/2022, 3:14 PM
I can get back to you by tomorrow for the update.that would be awesome
z
Zaid Khan
03/02/2022, 3:15 PMNo, actually it's printing exception in tomcat catalina logs as my application uses cron jobs in regular interval. That's why sometimes it's giving 504 even server is not used up. Also, in our catalina file, there's no exception except this one.
Zaid Khan
03/02/2022, 3:15 PMCan it will be paused by removing the settings from setenv.sh file?
a
Ankit Nayan
03/02/2022, 3:17 PM
yes..
Ankit Nayan
03/02/2022, 3:17 PM
removing
export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/path/opentelemetry-javaagent.jar"Ankit Nayan
03/02/2022, 3:18 PM
or you can just add
OTEL_JAVAAGENT_ENABLED=falsez
Zaid Khan
03/02/2022, 6:22 PMI have currently disabled it. Thanks for your help 🙂
a
Ankit Nayan
03/02/2022, 6:51 PM
Cool
Ankit Nayan
03/04/2022, 8:48 AM
hey @User you can install the latest version
v0.7.1 Copy code
git checkout main
git pull origin mainsignoz/deploy Copy code
./install.shAnkit Nayan
03/04/2022, 8:49 AM
checkout the release features at https://github.com/SigNoz/signoz/releases
z
Zaid Khan
03/09/2022, 6:19 AMHey @User Thanks for the update. I will update it soon and will let you know
271 Views