search

openclarity / apiclarity

An API security tool to capture and analyze API traffic, test API endpoints, reconstruct Open API specification, and identify API security risks. 
https://apiclarity.io
Apache License 2.0
498 stars 64 forks source link

no monitored traffic on the UI #366

Closed jpgong closed 8 months ago

jpgong commented 9 months ago

APIclarity has been deployed correctly in the sock-shop demo application, why is there no monitored traffic on the UI?

image

image

kubectl logs -f apiclarity-apiclarity-7c96cc5c87-kd2md -n apiclarity，and reports warning: level=warning msg="External trace server not started because TLS is not enabled" func=github.com/openclarity/apiclarity/backend/pkg/backend.Run file="/build/backend/pkg/backend/backend.go:237"

Is it because of this reason? image

jpgong commented 9 months ago

apiclarity can run normally, but the namespace traffic cannot be monitored in the Istio Service Mesh module. and, Tap via a DaemonSet module also can not monitor normal traffic, and error reports as follow in taper pod: image

Yeatesss commented 1 month ago

apiclarity can run normally, but the namespace traffic cannot be monitored in the Istio Service Mesh module.

Please ask if you have solved this problem, I am also encountering this problem, in the deployment of istio kubernetes using apiclarity, open the ui interface of apiclarity did not get the api request, but the same deployment process I can get the api request in kind, I would like to get your reply!

amanhigh commented 1 week ago

Even i am not clear how to enable Capture. Istio is already deployment but no Traffic. Is there any further guide on this ?