Files
kubeshark/agent
M. Mert Yıldıran 145e7cda01 Add OAS contract monitoring support (#325)
* Add OAS contract monitoring support

* Pass the contract failure reason to UI

* Fix the issues related to contract validation

* Fix rest of the issues in the UI

* Add documentation related to contract monitoring feature

* Fix a typo in the docs

* Unmarshal to `HTTPRequestResponsePair` only if the OAS validation is enabled

* Fix an issue caused by the merge commit

* Slightly change the logic in the `validateOAS` method

Change the `contractText` value to `No Breaches` or `Breach` and make the text `white-space: nowrap`.

* Retrieve and display the failure reason for both request and response

Also display the content of the contract/OAS file in the UI.

* Display the OAS under `CONTRACT` tab with syntax highlighting

Also fix the styling in the entry feed.

* Remove `EnforcePolicyFileDeprecated` constant

* Log the other errors as well

* Get context from caller instead

* Define a type for the contract status and make its values enum-like

* Remove an unnecessary `if` statement

* Validate OAS in the CLI before passing it to Agent

* Get rid of the `github.com/ghodss/yaml` dependency in `loadOAS` by using `LoadFromData`

* Fix an artifact from the merge conflict
2021-10-19 14:24:22 +03:00
..
2021-08-15 14:22:49 +03:00

mizu agent

Agent for MIZU (API server and tapper) Basic APIs:

  • /stats - retrieve statistics of collected data
  • /viewer - web ui

Remote Debugging

Setup remote debugging

  1. Run go get github.com/go-delve/delve/cmd/dlv
  2. Create a "Go Remote" run/debug configuration in Intellij, set to localhost:2345
  3. Build and push a debug image using docker build . -t gcr.io/up9-docker-hub/mizu/debug:latest -f debug.Dockerfile && docker push gcr.io/up9-docker-hub/mizu/debug:latest

Connecting

  1. Start mizu using the cli with the debug image mizu tap --set agent-image=gcr.io/up9-docker-hub/mizu/debug:latest {tapped_pod_name}
  2. Forward the debug port using kubectl port-forward -n default mizu-api-server 2345:2345
  3. Run the run/debug configuration you've created earlier in Intellij.

Do note that dlv won't start the api until a debugger connects to it.