-
Notifications
You must be signed in to change notification settings - Fork 140
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
LOG-2811: Add lokistack output type to cluster forwarder #2483
Conversation
@Clee2691: This pull request references LOG-2811 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.8.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
/test all |
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.
Apart from a comment on the auth debate, this looks good.
Generating extra outputs and pipelines is somewhat complex but I think it is the only option right now - vector doesn't support any way to vary the base URL per message.
I'd like the code to be simpler, but I don't have any good idea how to do that right now....
/hold |
/retest |
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.
2 small nits othewise lgtm
api/observability/v1/output_types.go
Outdated
// to allow dynamic per-event values. Defaults to the log type (i.e. application, audit, infrastructure) | ||
// | ||
// +kubebuilder:validation:Required | ||
// +kubebuilder:default:={{.log_type}} |
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.
I think we discovered this needs quote? Is that right?
} | ||
|
||
// hasLokiStackOutput checks if a pipeline includes a lokistack output | ||
func hasLokiStackOutput(outputMap map[string]*obs.OutputSpec, outputRefs []string) *sets.String { |
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. since we need to change the other thing maybe make this plural?
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.
I changed the name of this function to better represent what it does: findLokiStackOutputs()
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Clee2691, jcantrill 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 |
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
@Clee2691: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Loki
to use observability APILoki
output to APILokiStack
output toLoki
outputs crafting the URL with the tenant (current behavior of LokiStack)/cc
/assign
Links