[UI]: Performance Testing - URL to test in invalid (for valid Linkerd main application URL)

[bluedog13]

Current Behavior

Does not take a valid URL to run the performance test. It is treating valid URLs as invalid.

Below is for the Linkerd emojivoto example and the URL one uses to votes for the emojis ex: http://localhost:8888/api/vote?choice=:joy:

Desired Behavior

Should take the URL

Screenshots/Logs

---

Works in Chrome

---

Works with CURL

Environment

• Browser: Chrome
• Host OS: Mac
• Meshery Server Version: v0.6.49 460e9bd4
• Meshery Client Version: v0.6.49 460e9bd43
• Platform: Kubernetes

---

Contributor Guides and Handbook

• 🎨 Wireframes and designs for Meshery UI in Figma
• 🖥 Contributing to Meshery UI
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[github-actions[bot]]

This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests Using Cypress.

---

        Be sure to join the community, if you haven't yet and please leave a :star: star on the project :smile:

[leecalcote]

Thanks for opening this issue, @bluedog13 👍

One common pitfall that folks stumble into is that depending upon your deployment model, Meshery Server (where the load generator is) resides on a network disconnected from (without route) to the endpoint under test. There are a number of scenarios in which this occurs. Will you confirm that localhost:8888 is accessible by Meshery Server?

It shouldn't be, but it's possible that URL validation in the endpoint input field is bothered by the ?, which would certainly be a bug.

[bluedog13]

Yes, localhost:8888 is accessible by meshery server. The above seems very strictly related to some UI validation and I highly doubt it's related to localhost:8888 being accessible. I don't think the UI bothers to check the connection at this step.

I am able to run the performance tests using mesheryctl as an alternative. Below commands work and I also see the profile being created in the meshery UI as well.

mesheryctl perf apply local-perf-linkerd2 \
    --duration 60s \
    --qps 10 \
    --url http://localhost:8888/api/vote?choice=:joy: \
    --mesh linkerd

mesheryctl perf result local-perf-linkerd2 --page 1

Accessing the profile and the test results created from above in the UI

[bluedog13]

In the newer version of mesheryctl the command fails now. Link to this issue is here

I am seeing other issues after upgrading.