-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add reserve logs #505
Labels
feature
New functionality
Comments
callmevladik
added a commit
that referenced
this issue
Nov 28, 2024
callmevladik
added a commit
that referenced
this issue
Nov 28, 2024
MykolaMarusenko
pushed a commit
that referenced
this issue
Nov 28, 2024
callmevladik
added a commit
that referenced
this issue
Nov 29, 2024
callmevladik
added a commit
that referenced
this issue
Nov 29, 2024
SergK
pushed a commit
that referenced
this issue
Nov 29, 2024
callmevladik
added a commit
that referenced
this issue
Dec 3, 2024
MykolaMarusenko
pushed a commit
that referenced
this issue
Dec 3, 2024
SergK
added a commit
that referenced
this issue
Jan 28, 2025
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
11 tasks
SergK
added a commit
that referenced
this issue
Jan 28, 2025
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jan 28, 2025
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The task involves investigating an approach to retrieve and display logs directly from OpenSearch in scenarios where Tekton pipelines are unavailable for log provision. This includes enabling and configuring log retrieval using the OpenSearch approach, ensuring comprehensive log coverage and accessibility for debugging and monitoring purposes.
Acceptance Criteria
A detailed investigation on the feasibility of using OpenSearch for log retrieval without Tekton pipelines.
Recommendations and potential configurations for enabling log retrieval through OpenSearch.
Documentation of the process and configurations needed to implement this approach.
Identify any limitations or considerations when using OpenSearch for log management in this context.
The idea from Tekton Pipelines https://github.com/tektoncd/dashboard/blob/main/docs/walkthrough/walkthrough-logs.md
curl -X GET "https://vpc-k8s-logs-sandbox-euc1-jpyn55j6qjx75tobqi7hgbvgrq.eu-central-1.es.amazonaws.com/logstash-dev-krci-*/_search" -H 'Content-Type: application/json' -d'
{
"_source": ["log"],
"query": {
"bool": {
"must": [
{
"match_phrase": {
"kubernetes.namespace_name": "krci"
}
},
{
"match_phrase": {
"kubernetes.labels.tekton_dev/pipelineRun": "ctp-frontend-main-review-rx8ms"
}
},
{
"range": {
"@timestamp": {
"gte": "now-2d",
"lte": "now"
}
}
}
]
}
},
"sort": [
{
"@timestamp": {
"order": "asc"
}
}
],
"size": 200
}' --insecure --user 'username:password'
The text was updated successfully, but these errors were encountered: