[Question] Are these errors coming from the api or from the pewpew client or the api ?

[abhijeetkushe]

I am using the below config file

{
  "Count": 500,
  "Concurrency": 100,
  "Quiet": false,
  "Compress": true,
  "UserAgent": "pewpewpewpewpew",
  "Timeout": "5s",
  "DNSPrefetch": true,
  "Headers": "Accept-Encoding:gzip",
  "Targets": [
        {
            "URL": "http://localhost:9080/metrics/1100690469415/events/flow/4b140825-5e7b-4b9b-9415-192904f42525/count",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100690469415/events/flow/302e184f-25fe-4361-b610-2976486fa839/count",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100675341239/events/flow/e0ea5d4f-12d6-4c6b-8142-b3324f0332aa/count",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100690469415/events/flow/ac1e088e-e76f-45cd-99fb-7353c5054627/count",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100702411342/events/flow/80bf2d18-23d2-4089-9d67-f5dbb6517de5/count",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100675341239/events/query",
            "Method": "POST",
            "Headers": "Content-Type:application/json",
           "Body": "{ \"count\": [\"cid\",\"sid\"], \"groupby\": [\"aType\", \"aid\"] }",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100690469415/events/query",
            "Method": "POST",
            "Headers": "Content-Type:application/json",
            "Body": "{ \"count\": [\"cid\",\"sid\"], \"groupby\": [\"aType\", \"aid\"] }",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100604762927/events/query",
            "Method": "POST",
            "Headers": "Content-Type:application/json",
            "Body": "{ \"count\": [\"cid\",\"sid\"], \"groupby\": [\"aType\", \"aid\"] }",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100702411341/events/query",
            "Method": "POST",
            "Headers": "Content-Type:application/json",
            "Body": "{ \"count\": [\"cid\",\"sid\"], \"groupby\": [\"aType\", \"aid\"] }",
            "Timeout": "1.75s"
        },
        {
            "URL": "http://localhost:9080/metrics/1100703561903/events/query",
            "Method": "POST",
            "Headers":"Content-Type:application/json",
            "Body": "{ \"count\": [\"cid\",\"sid\"], \"groupby\": [\"aType\", \"aid\"] }",
            "Timeout": "1.75s"
        }
  ]
}

I get these errors Are coming from the api or from the pewpew client

Failed to make request: Post "http://localhost:9080/metrics/1100604762927/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100604762927/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100690469415/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100702411341/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100604762927/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100604762927/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Get "http://localhost:9080/metrics/1100690469415/events/flow/ac1e088e-e76f-45cd-99fb-7353c5054627/count": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100675341239/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100703561903/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Get "http://localhost:9080/metrics/1100702411342/events/flow/80bf2d18-23d2-4089-9d67-f5dbb6517de5/count": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Get "http://localhost:9080/metrics/1100690469415/events/flow/302e184f-25fe-4361-b610-2976486fa839/count": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100703561903/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100702411341/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Post "http://localhost:9080/metrics/1100703561903/events/query": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Failed to make request: Get "http://localhost:9080/metrics/1100675341239/events/flow/e0ea5d4f-12d6-4c6b-8142-b3324f0332aa/count": context deadline exceeded (Client.Timeout exceeded while awaiting headers```

I get the following output global

----Global----

Timing
Mean query speed: 320 ms
Fastest query speed: 0 ms
Slowest query speed: 1737 ms
Mean RPS: 607.62 req/sec
Total time: 2065 ms

Data Transferred
Mean query: 2.8 kB
Largest query: 41 kB
Smallest query: 312 B
Total: 3.5 MB

Response Codes
200: 432 responses (34.42%)
302: 428 responses (34.10%)
400: 395 responses (31.47%)

200: 432 responses (34.42%)
302: 428 responses (34.10%)
400: 395 responses (31.47%)

[bengadbois]

This will be an issue with the local server running/listening on http://localhost:9080. You can try increasing the timeout beyond your configured 5s as it seems like some number of responses are coming through, so it's not a total connectivity failure.