-
Notifications
You must be signed in to change notification settings - Fork 79
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
Optimise GetLog API query in v1alpha3 Logs API #808
Conversation
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.
/kind cleanup
/assign @enarha @vdemeester |
The following is the coverage report on the affected files.
|
/test pull-tekton-results-unit-tests |
01b031f
to
6696d8d
Compare
/test pull-tekton-results-integration-tests |
The following is the coverage report on the affected files.
|
6696d8d
to
9f45fd7
Compare
/test pull-tekton-results-build-tests |
The following is the coverage report on the affected files.
|
9f45fd7
to
5183e44
Compare
/hold retesting after rebase. |
The following is the coverage report on the affected files.
|
5183e44
to
59c2952
Compare
The following is the coverage report on the affected files.
|
59c2952
to
fdb7359
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-results-integration-tests |
fdb7359
to
3a34003
Compare
/test pull-tekton-results-unit-tests |
The following is the coverage report on the affected files.
|
/hold cancel |
3a34003
to
725ed66
Compare
/test pull-tekton-results-integration-tests |
I have added the documentation for new parameter. |
The following is the coverage report on the affected files.
|
docs/logging-support.md
Outdated
@@ -25,5 +25,4 @@ These are the common configuration options for all third party logging APIs. | |||
- `LOGGING_PLUGIN_PROXY_PATH`: The path to the proxy to use for the third party logging API. (optional) | |||
- `LOGGING_PLUGIN_CA_CERT`: The CA certificate to use for the third party logging API. This should ideally be passed as environment variable in the deployment spec of the results-api pod. (optional) | |||
- `LOGGING_PLUGIN_TLS_VERIFICATION_DISABLE`: Set to `true` to disable TLS verification for the third party logging API. (optional) | |||
|
|||
Also, `MAX_RETENTION` is passed to the results API from the Retention Policy ConfigMap. | |||
- `LOGGING_PLUGIN_FORWARDER_BUFFER_DURATION`: Buffer Duration is the max duration taken by third party logging system to forward and store the logs after completion of taskrun and pipelinerun. This is used to search between start time of runs and completion plus buffer duration. |
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.
The explanation is good. Maybe you can add the type e.g in minutes. The name LOGGING_PLUGIN_FORWARDER_DELAY_DURATION
makes more sense to me.
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.
Changed to LOGGING_PLUGIN_FORWARDER_DELAY_DURATION
.
The following is the coverage report on the affected files.
|
In logql queries, optimised the following: * Duration where we search should be small. * Searching for uid(TaskRun/PipelineRunUID) after parsing data. Also, we are caching Token.
79c2888
to
33890fd
Compare
/hold |
The following is the coverage report on the affected files.
|
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
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enarha The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
In logql queries, optimised the following:
Also, we are caching Token.
Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes