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

Fix: fix http status code parsing for publish #279

Merged
merged 1 commit into from
Apr 21, 2022

Conversation

electron0zero
Copy link
Member

@electron0zero electron0zero commented Apr 20, 2022

We had a temporary fix where we were looking at error string to check if we were getting 401 from server.

sm_agent_publisher_push_errors_total metric is still broken after the temporary fix, and it was reporting 0 as status for all errors.

In this change, I am fixing the status code parsing code, and getting rid of temporary fix.

@electron0zero electron0zero requested a review from a team as a code owner April 20, 2022 19:12
Copy link
Contributor

@thepalbi thepalbi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@electron0zero electron0zero merged commit 0f758a3 into main Apr 21, 2022
@electron0zero electron0zero deleted the suraj/fix_http_code_check branch April 21, 2022 13:07
electron0zero added a commit that referenced this pull request Apr 26, 2022
* Bump kernel.org/pub/linux/libs/security/libcap/cap from 1.2.63 to 1.2.64
* Chore(deps): Bump google.golang.org/grpc from 1.45.0 to 1.46.0
* Bump github.com/miekg/dns from 1.1.47 to 1.1.48 (#277)
* Fix linter errors
* Fix build error
* Add metric to track prometheus client retries (#282)
* dialer for grpc?
* feat: Add a metric for failure to publish data (#280)
* Fix: fix http status code parsing for publish (#279)

Signed-off-by: Suraj Nath <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants