-
Notifications
You must be signed in to change notification settings - Fork 480
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 loki parser to parse servicePort from config #2437
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.
the formatting here is a bit odd... why have another {
?
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 is where the actual for loop begins. Before that, it was only the array definition.
It is the same formatting as in the OTLP receiver
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.
ah i see, yeah i usually have only seen this in the test blocks so my brain didn't parse that correctly. Thanks for explaining!
Co-authored-by: Jacob Aronoff <[email protected]>
Description:
Add
LokiReceiverParser
to parseservicePort
from config.By default, only the Otel ports are extracted, parsed, then configured into the collector container's list of service ports.
This feature allows extracting loki ports (grpc:9095/http:3100, see default values) into the container's port list.
Link to tracking Issue:
Resolves #1825