Closed debajyoti-truefoundry closed 7 months ago
Hi this is definitely reasonable, we just need to be sure that we don't break setup for existing users.
@debajyoti-truefoundry are you willing to contribute this feature?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to inactivity.
I think this should not be closed as its still a valid issue
Proposal
Right now, the Consumer metrics are fetched using the direct URL of the NATS Consumer Leader Node.
Considering a situation where Keda ScaledObject and NATS are in two different K8s clusters, it may not be possible to expose the individual Nodes over the internet.
In the above scenario, it will try to get the metrics from
https://nats-1.nats-metrics.example.org/jsz?acc=example&consumers=true&config=true
URL, assumingnats-1
is the Consumer Leader.The above API call fails as I only have
https://nats-metrics.example.org
exposed.I see that with the following patch, I can get the Consumer metrics directly from the
natsServerMonitoringEndpoint
.I understand that the Consumer Leader will have the most up-to-date metrics information. But is it possible to add a configuration in the Trigger Metadata, forcing the scaler code to use the
natsServerMonitoringEndpoint
directly? I would also like to know if this is a bad idea.Use-Case
No response
Is this a feature you are interested in implementing yourself?
Maybe
Anything else?
No response