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: Log request body (#6404) #6536

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

achave11-ucsc
Copy link
Member

@achave11-ucsc achave11-ucsc commented Aug 31, 2024

Connected issues: #6404

Checklist

Author

  • PR is a draft
  • Target branch is develop
  • Name of PR branch matches issues/<GitHub handle of author>/<issue#>-<slug>
  • On ZenHub, PR is connected to all issues it (partially) resolves
  • PR description links to connected issues
  • PR title matches1 that of a connected issue or comment in PR explains why they're different
  • PR title references all connected issues
  • For each connected issue, there is at least one commit whose title references that issue

1 when the issue title describes a problem, the corresponding PR
title is Fix: followed by the issue title

Author (partiality)

  • Added p tag to titles of partial commits
  • This PR is labeled partial or completely resolves all connected issues
  • This PR partially resolves each of the connected issues or does not have the partial label

Author (chains)

  • This PR is blocked by previous PR in the chain or is not chained to another PR
  • The blocking PR is labeled base or this PR is not chained to another PR
  • This PR is labeled chained or is not chained to another PR

Author (reindex, API changes)

  • Added r tag to commit title or the changes introduced by this PR will not require reindexing of any deployment
  • This PR is labeled reindex:dev or the changes introduced by it will not require reindexing of dev
  • This PR is labeled reindex:anvildev or the changes introduced by it will not require reindexing of anvildev
  • This PR is labeled reindex:anvilprod or the changes introduced by it will not require reindexing of anvilprod
  • This PR is labeled reindex:prod or the changes introduced by it will not require reindexing of prod
  • This PR is labeled reindex:partial and its description documents the specific reindexing procedure for dev, anvildev, anvilprod and prod or requires a full reindex or carries none of the labels reindex:dev, reindex:anvildev, reindex:anvilprod and reindex:prod
  • This PR and its connected issues are labeled API or this PR does not modify a REST API
  • Added a (A) tag to commit title for backwards (in)compatible changes or this PR does not modify a REST API
  • Updated REST API version number in app.py or this PR does not modify a REST API

Author (upgrading deployments)

  • Ran make docker_images.json and committed the resulting changes or this PR does not modify azul_docker_images, or any other variables referenced in the definition of that variable
  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading deployments
  • Added u tag to commit title or this PR does not require upgrading deployments
  • This PR is labeled upgrade or does not require upgrading deployments
  • This PR is labeled deploy:shared or does not modify docker_images.json, and does not require deploying the shared component for any other reason
  • This PR is labeled deploy:gitlab or does not require deploying the gitlab component
  • This PR is labeled deploy:runner or does not require deploying the runner image

Author (hotfixes)

  • Added F tag to main commit title or this PR does not include permanent fix for a temporary hotfix
  • Reverted the temporary hotfixes for any connected issues or the none of the stable branches (anvilprod and prod) have temporary hotfixes for any of the issues connected to this PR

Author (before every review)

  • Rebased PR branch on develop, squashed old fixups
  • Ran make requirements_update or this PR does not modify requirements*.txt, common.mk, Makefile and Dockerfile
  • Added R tag to commit title or this PR does not modify requirements*.txt
  • This PR is labeled reqs or does not modify requirements*.txt
  • make integration_test passes in personal deployment or this PR does not modify functionality that could affect the IT outcome

Peer reviewer (after approval)

  • PR is not a draft
  • Ticket is in Review requested column
  • PR is awaiting requested review from system administrator
  • PR is assigned to only the system administrator

System administrator (after approval)

  • Actually approved the PR
  • Labeled connected issues as demo or no demo
  • Commented on connected issues about demo expectations or all connected issues are labeled no demo
  • Decided if PR can be labeled no sandbox
  • A comment to this PR details the completed security design review
  • PR title is appropriate as title of merge commit
  • N reviews label is accurate
  • Moved connected issues to Approved column
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Checked reindex:… labels and r commit title tag
  • Checked that demo expectations are clear or all connected issues are labeled no demo
  • Squashed PR branch and rebased onto develop
  • Sanity-checked history
  • Pushed PR branch to GitHub
  • Ran _select dev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select dev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Ran _select anvildev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select anvildev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Checked the items in the next section or this PR is labeled deploy:gitlab
  • PR is assigned to only the system administrator or this PR is not labeled deploy:gitlab

System administrator

  • Background migrations for dev.gitlab are complete or this PR is not labeled deploy:gitlab
  • Background migrations for anvildev.gitlab are complete or this PR is not labeled deploy:gitlab
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Ran _select dev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Ran _select anvildev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Added sandbox label or PR is labeled no sandbox
  • Pushed PR branch to GitLab dev or PR is labeled no sandbox
  • Pushed PR branch to GitLab anvildev or PR is labeled no sandbox
  • Build passes in sandbox deployment or PR is labeled no sandbox
  • Build passes in anvilbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in sandbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in anvilbox deployment or PR is labeled no sandbox
  • Deleted unreferenced indices in sandbox or this PR does not remove catalogs or otherwise causes unreferenced indices in dev
  • Deleted unreferenced indices in anvilbox or this PR does not remove catalogs or otherwise causes unreferenced indices in anvildev
  • Started reindex in sandbox or this PR is not labeled reindex:dev
  • Started reindex in anvilbox or this PR is not labeled reindex:anvildev
  • Checked for failures in sandbox or this PR is not labeled reindex:dev
  • Checked for failures in anvilbox or this PR is not labeled reindex:anvildev
  • The title of the merge commit starts with the title of this PR
  • Added PR # reference to merge commit title
  • Collected commit title tags in merge commit title but only included p if the PR is also labeled partial
  • Moved connected issues to Merged lower column in ZenHub
  • Moved blocked issues to Triage or no issues are blocked on the connected issues
  • Pushed merge commit to GitHub

Operator (chain shortening)

  • Changed the target branch of the blocked PR to develop or this PR is not labeled base
  • Removed the chained label from the blocked PR or this PR is not labeled base
  • Removed the blocking relationship from the blocked PR or this PR is not labeled base
  • Removed the base label from this PR or this PR is not labeled base

Operator (after pushing the merge commit)

  • Pushed merge commit to GitLab dev
  • Pushed merge commit to GitLab anvildev
  • Build passes on GitLab dev
  • Reviewed build logs for anomalies on GitLab dev
  • Build passes on GitLab anvildev
  • Reviewed build logs for anomalies on GitLab anvildev
  • Ran _select dev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Ran _select anvildev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Deleted PR branch from GitHub
  • Deleted PR branch from GitLab dev
  • Deleted PR branch from GitLab anvildev

Operator (reindex)

  • Deindexed all unreferenced catalogs in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed all unreferenced catalogs in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Deindexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Indexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Indexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Started reindex in dev or this PR does not require reindexing dev
  • Started reindex in anvildev or this PR does not require reindexing anvildev
  • Checked for, triaged and possibly requeued messages in both fail queues in dev or this PR does not require reindexing dev
  • Checked for, triaged and possibly requeued messages in both fail queues in anvildev or this PR does not require reindexing anvildev
  • Emptied fail queues in dev or this PR does not require reindexing dev
  • Emptied fail queues in anvildev or this PR does not require reindexing anvildev

Operator

  • Propagated the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels to the next promotion PRs or this PR carries none of these labels
  • Propagated any specific instructions related to the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels, from the description of this PR to that of the next promotion PRs or this PR carries none of these labels
  • PR is assigned to no one

Shorthand for review comments

  • L line is too long
  • W line wrapping is wrong
  • Q bad quotes
  • F other formatting problem

@github-actions github-actions bot added the orange [process] Done by the Azul team label Aug 31, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch 5 times, most recently from f7083d1 to 2246652 Compare October 1, 2024 21:01
Copy link

codecov bot commented Oct 1, 2024

Codecov Report

Attention: Patch coverage is 97.87234% with 2 lines in your changes missing coverage. Please review.

Project coverage is 85.58%. Comparing base (93637ff) to head (1c2f71b).

Files with missing lines Patch % Lines
src/azul/logging.py 87.50% 1 Missing ⚠️
test/service/test_app_logging.py 98.50% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #6536      +/-   ##
===========================================
+ Coverage    85.57%   85.58%   +0.01%     
===========================================
  Files          154      154              
  Lines        20915    20932      +17     
===========================================
+ Hits         17897    17915      +18     
+ Misses        3018     3017       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@coveralls
Copy link

coveralls commented Oct 1, 2024

Coverage Status

coverage: 85.621% (+0.03%) from 85.587%
when pulling 1c2f71b on issues/achave11-ucsc/6404-log-req-body
into 93637ff on develop.

Copy link
Contributor

@dsotirho-ucsc dsotirho-ucsc left a comment

Choose a reason for hiding this comment

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

Currently the logging tests only cover GET requests. Consider adding a logging test of a PUT or POST request with a body. Maybe this can be done in IT when a manifest request is made, or against a dummy endpoint like in TestAppLogging.test

Comment on lines 397 to 398
else:
if config.debug == 2:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
else:
if config.debug == 2:
elif config.debug == 2:

@dsotirho-ucsc dsotirho-ucsc removed their assignment Oct 2, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch 7 times, most recently from 2395ab7 to 6d3f998 Compare October 17, 2024 07:24
test/service/test_app_logging.py Outdated Show resolved Hide resolved
Comment on lines 57 to 38
def test_request_logs(self):
for level in INFO, DEBUG:
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of having two loops for level and azul_debug, how about you only loop over the three values of azul_debug:

    def test_request_logs(self):
        for azul_debug in (0, 1, 2):
            for authenticated in False, True:
                for request_body in False, True:
                    headers = {'authorization': 'Bearer foo_token'} if authenticated else {}
                    if request_body:
                        request_body = json.dumps({'filters': json.dumps({'organ': {'is': ['foo']}})})
                        headers = {
                            'content-length': str(len(request_body)),
                            'content-type': 'application/json',
                            **headers,
                        }
                    with mock_patch.object(Config,
                                           'debug',
                                           new=PropertyMock(return_value=azul_debug)):
                        self._assert_request_logs(authenticated, request_body, headers, azul_debug)

then in _assert_request_logs you can set level based on azul_debug:

level = [INFO, DEBUG, DEBUG][azul_debug]

Copy link
Member Author

Choose a reason for hiding this comment

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

Great idea, ty!

@@ -3,15 +3,22 @@
DEBUG,
INFO,
)
from unittest.mock import (
PropertyMock,
patch as mock_patch,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
patch as mock_patch,
patch,

What's wrong with patch?

Copy link
Member Author

Choose a reason for hiding this comment

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

I felt compelled to denote the mock relationship to patch.

Copy link
Member

Choose a reason for hiding this comment

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

We don't do that anywhere else and I see no good reason to start now.

body = json.dumps(body, cls=self._LogJSONEncoder)
msg = f' ({len(body)} characters)'
else:
msg = f' (first {str(n := 1024)} characters)'
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
msg = f' (first {str(n := 1024)} characters)'
n = 1024
msg = f' (first {str(n)} characters)'

The walrus operator can be useful in an if condition, but here seems unnecessary and the code is easier to read without it.

dsotirho-ucsc
dsotirho-ucsc previously approved these changes Oct 21, 2024
Copy link
Contributor

@dsotirho-ucsc dsotirho-ucsc left a comment

Choose a reason for hiding this comment

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

Approved.

@dsotirho-ucsc dsotirho-ucsc marked this pull request as ready for review October 21, 2024 16:39
@hannes-ucsc hannes-ucsc removed their assignment Oct 29, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch 4 times, most recently from cc35a8b to 730d487 Compare October 31, 2024 18:10
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

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

We should discuss in PL how we can match up the different levels of detail logged at which log level for the request and response. Currently these two methods look worryingly dissimilar.

body = self.current_request.json_body
if body is None:
len_msg = ''
elif config.debug == 2:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
elif config.debug == 2:
elif config.debug > 1:

If we ever add a fourth level m we would want this condition to be True there as well.

n = 1024
len_msg = f' (first {str(n)} characters)'
body = json_head(n, body) if not isinstance(body, str | bytes) else body[:n]
log.info('%s', http_body_log_message('request', body, verbatim=True) + len_msg)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
log.info('%s', http_body_log_message('request', body, verbatim=True) + len_msg)
log.info(http_body_log_message('request', body, verbatim=True) + len_msg)

len_msg = f' ({len(body)} characters)'
else:
n = 1024
len_msg = f' (first {str(n)} characters)'
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
len_msg = f' (first {str(n)} characters)'
len_msg = f' (first {n} characters)'

@hannes-ucsc hannes-ucsc removed their assignment Nov 2, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch 3 times, most recently from 2abc349 to c7030a5 Compare November 20, 2024 18:17
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch from c7030a5 to 98b64f4 Compare November 20, 2024 19:00
@achave11-ucsc
Copy link
Member Author

Re-requesting peer review since previously approved changes were mostly removed.

response.status_code,
json.dumps(response.headers, cls=self._LogJSONEncoder),
n, body)
log.info('With %s body size of %i bytes.', body_type, len(body))
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
log.info('With %s body size of %i bytes.', body_type, len(body))
log.info('… with %s body size of %i bytes.', body_type, len(body))

Consider modifying http_body_log_message() so that it can return this message, perhaps by adding a include_body: bool = True parameter. This would keep all the different … with message strings in the same place.

}
}
}
)[:1024] # … upto the first 1024 characters.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
)[:1024] # … upto the first 1024 characters.
)

Consider returning the full value here, then slicing at the call sites where a comment won't be necessary since it'll be clear from the nearby log lines why the value is sliced.

@dsotirho-ucsc dsotirho-ucsc removed their assignment Nov 20, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6404-log-req-body branch from 98b64f4 to 0defdbd Compare November 21, 2024 17:30
json_head,
)
from azul.logging import (
http_body_log_message,

Check failure

Code scanning / CodeQL

Module-level cyclic import Error

'http_body_log_message' may not be defined if module
azul.logging
is imported before module
azul.chalice
, as the
definition
of http_body_log_message occurs after the cyclic
import
of azul.chalice.
Copy link
Member Author

Choose a reason for hiding this comment

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

@dsotirho-ucsc, note this is likely a false positive finding.

Copy link
Contributor

@dsotirho-ucsc dsotirho-ucsc left a comment

Choose a reason for hiding this comment

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

Approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 reviews [process] Lead requested changes thrice orange [process] Done by the Azul team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants