Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cant get a falmegraph due to error Cannot read properties of undefined (reading 'length') #29

Open
soanni86 opened this issue Feb 6, 2025 · 6 comments
Assignees

Comments

@soanni86
Copy link

soanni86 commented Feb 6, 2025

hello, i set up perforator on one of our clusters but i cant see the flamegraph seeing error below

Image

and then error

Image

what could be wrong ?

below are the console logs

Image Image

Thanks

@gearoffortune gearoffortune self-assigned this Feb 6, 2025
@gearoffortune
Copy link
Contributor

gearoffortune commented Feb 6, 2025

Judging by the fact that error takes place inside the component, I think it is this line, but the reasons are unclear for now

Thank you for providing the devtools screenshot, that does help with debugging.
What looks suspicious is the fact that the json response is 466 bytes (the last network request). That sounds a little bit small.
Could you take a look what is inside of it?

@soanni86
Copy link
Author

soanni86 commented Feb 6, 2025

yeah , its empty . 466 bytes thats only headers i guess

Image

@soanni86
Copy link
Author

soanni86 commented Feb 6, 2025

what backend is supposed to populate the data for these frontend requests ? dont see anything specifically wrong in backend services logs however

@gearoffortune
Copy link
Contributor

It seems that the proxy have rendered the json successfully and uploaded it into storage.
The proxy prerenders json to show by the UI.
It expects an absolute path to the storage.
Try checking that it is making a request to somewhere you expect.
Hover your mouse over the 0194dbbd-*.json line and check the domain. If there is no domain then check what is inside the rendered_profiles.url_prefix field in the proxy config
It is empty by default.
If it is empty you should swap it with a domain prefix or with an IP, something like http://[%IP_V6_IP]/ if you're using ip v6

@soanni86
Copy link
Author

soanni86 commented Feb 6, 2025

great, thank now i see 500 while accessing directly the flamegraph https://perforator.dev-***.com/task/0194dce2-dace-7501-b3e2-fc5dbac9b3ea.json

Image

in my logging system i see this error from postgres side

Image

@gearoffortune
Copy link
Contributor

gearoffortune commented Feb 6, 2025

I'm sorry, by "absolute path to storage" I meant, the path to this bucket, not "storage" microservice.

From what I understand the request is somehow reaching the postgres, and it really shouldn't. It takes the bucket link with the id and downloads it. So no postgres involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants