-
Notifications
You must be signed in to change notification settings - Fork 519
[AWS] [API Gateway] Add custom access logging fields #7151
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
[AWS] [API Gateway] Add custom access logging fields #7151
Conversation
🌐 Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should expand this section.
Here's the information we should convey to the users:
- the API Gateway offers a wide array of additional fields you can pick from
- you can leverage the custom pipeline to process the field names or values
- you can leverage the custom mapping to store data efficiently
zmoog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is looking good; I have a few minor suggested changes.
|
It seems changing my github username finally caught up to me (resigned the CLA). What's your opinion on the new docs @zmoog ? |
|
💚 CLA has been signed |
|
@lucian-ioan, do you still have problems with CLA? |
|
/test yes @zmoog, apparently so, I believe there need to be some signatures on the other end as well for it to be in effect. Can the PR not be merged without the CLA passing? |
No. We need to sort this out. |
0da8058 to
144af0f
Compare
|
cla/check |
1 similar comment
|
cla/check |
|
cla/check |
134917a to
5e32eba
Compare
zmoog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: tiny suggestion on the wording.
Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
packages/aws/changelog.yml
Outdated
| @@ -1,4 +1,9 @@ | |||
| # newer versions go on top | |||
| - version: "1.52.2" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be a minor version bump here as we are adding the fields and it is an enhancement
bhapas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Package aws - 1.53.0 containing this change is available at https://epr.elastic.co/search?package=aws |
Urgency
Activity Type
What does this PR do?
Adds
apiId,domainNameandstagefields which need Custom Access Logging enabled in the AWS API Gateway settings and to be added to the default log format via context variables. Also enhances current tests.These fields are common between all API types supported by AWS and provide value in filtering data/enhancing dashboards.
apiId -> unique identifier for the API
domainName -> full URL path to the API, easier to identify with than apiId
stage -> environment typically used as a step in the lifecycle of the API (ex. dev/beta/prod/)
Documentation for context variables based on API type:
Checklist
changelog.ymlfile.How to test this PR locally
{"apiId": "$context.apiId", "domainName": "$context.domainName", "stage": "$context.stage"}Related issues