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.

Sign up for GitHub

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

Jump to bottom

fortio shows 503s as warning immediately using fast client but not using stdclient (https) #489

Closed
ldemailly opened this issue Oct 19, 2021 · 0 comments · Fixed by #490
Closed

fortio shows 503s as warning immediately using fast client but not using stdclient (https) #489

ldemailly opened this issue Oct 19, 2021 · 0 comments · Fixed by #490

Comments

@ldemailly
Copy link
Member

No description provided.

ldemailly added a commit that referenced this issue Oct 19, 2021
@ldemailly
Now both the fastclient (like before) and the std client will log non
fb38c12 
ok http error codes as they occur. You can also turn off these warnings
using -log-errors=false

Fixes #489
@ldemailly ldemailly mentioned this issue Oct 19, 2021
Merged
ldemailly added a commit that referenced this issue Oct 20, 2021
@ldemailly
Now both the fastclient (like before) and the std client will log htt…
033287c 
…p errors (#490)

Now both the fastclient (like before) and the std client will log non #490
ok http error codes (codes not 2xx or not 418) as they occur. 
You can also turn off these warnings using -log-errors=false

Also log an id 0-n number of runners/connection for these messages (this is a log change
fast client logs look like
```
16:35:41 W http_client.go:806> [0] Non ok http code 503 (HTTP/1.1 503)
```
and std client:
```
16:35:25 W http_client.go:401> [0] Non ok http code 503
```


Fixes #489

Also use latest go 1.16 (1.16.9) in  rev'ed up build image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Now both the fastclient (like before) and the std client will log http errors fortio/fortio
1 participant
@ldemailly