-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[opampsupervisor] Add HealthCheckPort configuration parameter #34704
[opampsupervisor] Add HealthCheckPort configuration parameter #34704
Conversation
e5ebe01
to
4a8e195
Compare
if a.HealthCheckPort > 65535 { | ||
return errors.New("agent::health_check_port must be a valid port number") | ||
} | ||
|
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.
Let's also check that the port is not negative
a1a5237
to
5b54cb6
Compare
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 works great for me.
@tigrannajaryan Do you have any objections to this feature in general? I know you were discussing ways to mitigate issues with the random port allocation, but I think this is a good practical solution to the problem for now.
No objections. |
80eddf4
to
03dc166
Compare
03dc166
to
bb67282
Compare
…elemetry#34704) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add a new configuration parameter to `agent` called `health_check_port`. If this is set, then the supervisor will configure the agent's healthcheck extension to use the given port. If it is unset, then we will grab a random port same as before. **Link to tracking Issue:** open-telemetry#34643 **Testing:** <Describe what testing was performed and which tests were added.> - Updated config validation tests - Verified that healthcheck extension is configured with the correct port and works as expected
Description:
Add a new configuration parameter to
agent
calledhealth_check_port
. If this is set, then the supervisor will configure the agent's healthcheck extension to use the given port. If it is unset, then we will grab a random port same as before.Link to tracking Issue: #34643
Testing: