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

docs(log) http-log authentication and retries logging #408

Merged
merged 1 commit into from
Apr 30, 2017

Conversation

Tieske
Copy link
Member

@Tieske Tieske commented Apr 28, 2017

Deals with Kong issue Kong/kong#2429: logging retries and failure info
and Kong/kong#2430 for adding a basic auth header with the http log plugin

This documents the additional changes in Kong/kong#2467.

@Tieske Tieske self-assigned this Apr 28, 2017
@Tieske Tieske added this to the 0.10.2 milestone Apr 28, 2017
@Tieske Tieske force-pushed the docs/retries-log branch from c6bc0e4 to fc85974 Compare April 28, 2017 15:13
@@ -77,9 +77,21 @@ Every request will be logged separately in a JSON object separated by a new line
"access-control-allow-origin": "*"
}
},
"tries": [
Copy link
Contributor

Choose a reason for hiding this comment

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

this is valid for the file-log plugin?

Copy link
Member

Choose a reason for hiding this comment

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

Curious: why not? It should use the same serializer as the other ones, so yes. Maybe your understanding of the file-log plugin is that it doesn't log requests/response info?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yep, misread this. Thought this had to do with the log plugin retrying, not the retries in the serialized data. My bad!

@@ -40,11 +40,15 @@ form parameter | default | description
--- | --- | ---
`name` | | The name of the plugin to use, in this case: `http-log`
`consumer_id`<br>*optional* | | The CONSUMER ID that this plugin configuration will target. This value can only be used if [authentication has been enabled][faq-authentication] so that the system can identify the user making the request.
`config.http_endpoint` | | The HTTP endpoint (including the protocol to use) where to send the data to
`config.http_endpoint` | | The HTTP endpoint (including the protocol to use) where to send the data to.
Copy link
Contributor

Choose a reason for hiding this comment

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

The HTTP endpoint (including the protocol) to which the data will be sent.

`config.method`<br>*optional* | `POST` | An optional method used to send data to the http server, other supported values are PUT, PATCH
`config.timeout`<br>*optional* | `10000` | An optional timeout in milliseconds when sending data to the upstream server
`config.keepalive`<br>*optional*| `60000` | An optional value in milliseconds that defines for how long an idle connection will live before being closed

**NOTE:** If the `config.http_endpoint` contains a username and password, then
Copy link
Member

@thibaultcha thibaultcha Apr 29, 2017

Choose a reason for hiding this comment

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

I think we should make clear where exactly in the URL that username and password should be to be taken into consideration:

contains a username and password in the authentication section of the URL.
Ex: http://bob:[email protected]/logs

@@ -112,6 +124,7 @@ A few considerations on the above JSON object:

* `request` contains properties about the request sent by the client
* `response` contains properties about the response sent to the client
* `tries` contains the information of the successive (re)tries, the upstream address and failure information
Copy link
Member

@thibaultcha thibaultcha Apr 29, 2017

Choose a reason for hiding this comment

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

I think a bit more context here wouldn't hurt:

contains the list of (re)tries (successes and failures) made by
the load balancer for this request

Deals with Kong issue 2429: logging retries and failure info
and 2430 for adding a basic auth header with the http log plugin
@Tieske Tieske force-pushed the docs/retries-log branch from fc85974 to d7be0cb Compare April 30, 2017 06:45
@Tieske Tieske merged commit bdfd094 into 0.10.2 Apr 30, 2017
@Tieske Tieske deleted the docs/retries-log branch April 30, 2017 07:05
lena-larionova added a commit that referenced this pull request Apr 10, 2020
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.

4 participants