Tony Choe

Results 15 comments of Tony Choe

We have the use cases to collect logs with Vector and send them to various sinks including OTLP-compatible endpoints. Vector's support for OTLP would be fantastic. :)

@kakkoyun sorry I have been busy; will get back after trying v.04.0 and/or collecting any evidences.

@kakkoyun I did some tests today and here's the summary. - Parca agent v0.4.0 didn't make a difference. - So, I've tested total three version of agent (0.4.0, 0.3.0, 0.1.0)....

@kakkoyun Thank you. I've been using the debug mode but couldn't find some clues. All errors I got look normal - the agent complained about not finding symbols, etc. I've...

That's a good theory. @kakkoyun I was continuing the experiment (3). The app I was profiling (Jaeger hotrod demo) moved to the surviving node. I could see profiling working with...

Experiment (1) - running parca agent/server on non-K8S, regular VM w/ OL 8.4 - went with zero issue almost 1 day. Experiment (4) - started running parca agent/server on K8S,...

Hi @kakkoyun I tested the latest Parca agent in the same Kubernetes cluster. This time the nodes were alive more than a day over the weekend, but sadly this morning,...

@kakkoyun thank you. This is the test i did after my previous post: (1) Ran parca-agent to profiling just one microservice, went fine for the past 7 days (2) Last...

@kakkoyun This is the warning message I often see. ``` level=warn ts=2022-04-12T18:45:30.544771804Z caller=extract.go:125 component=debuginfo component=extractor msg="failed to remove temporary file" file=48596f474f6344753477517958586169745036382f756549645875676a687a314672715079657945302f4d4f716931767a69746e7633732d47724c4c2d792f3461706a37692d707a7565433044674865643877.stripped err="remove 48596f474f6344753477517958586169745036382f756549645875676a687a314672715079657945302f4d4f716931767a69746e7633732d47724c4c2d792f3461706a37692d707a7565433044674865643877.stripped: read-only file system" ``` It's weird. parca-agent...

@kakkoyun I've tested the agent v0.8.0 and unfortunately the issue is still there - the K8S nodes went unresponsive quickly.