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

Missing "response-time-ms" when querying check api #74

Open
akrzos-bw opened this issue Jan 3, 2020 · 0 comments
Open

Missing "response-time-ms" when querying check api #74

akrzos-bw opened this issue Jan 3, 2020 · 0 comments

Comments

@akrzos-bw
Copy link

Describe the bug
Running curl $IP:8080/check on a goldpinger pod some of the returned results are missing field "response-time-ms". Are values less than 1ms just missing?

To Reproduce
Steps to reproduce the behavior:
on a kube cluster with a sufficently low enough network latency you'll see statuc-code 200s returned but no "response-time-ms" field:

# curl 172.20.0.221:8080/check | python -mjson.tool
...
    "podResults": {
        "x.x.x.x": {
            "HostIP": "x.x.x.x",
            "OK": true,
            "response": {
                "boot_time": "2020-01-03T20:51:07.082Z"
            },
            "status-code": 200
        },
...

Expected behavior
The field "response-time-ms" to exist when status-code 200 is returned

Environment (please complete the following information):

  • OpenShift 3.11
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

1 participant