You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enabling the carbon listener in a custom config map doesn't open the port in the service and container. Adding EnableCarbonIngester to the cluster spec, which then generate a config map with
carbon:
ingester:
listenAddress: "0.0.0.0:7204"
and opening the ports in the coordinator service and the m3dbnode containers, would be very helpfull.
The text was updated successfully, but these errors were encountered:
I am working on a PR for this. I just added a boolean flag to the cluster spec EnableCarbonIngester This will work only for custom config maps, as the listener doesn't start with an empty carbon: config. Does it make sense to generate the carbon rules based on the configured namespaces in the spec?
I am working on a PR for this. I just added a boolean flag to the cluster spec EnableCarbonIngester This will work only for custom config maps, as the listener doesn't start with an empty carbon: config. Does it make sense to generate the carbon rules based on the configured namespaces in the spec?
Just saw in the carbon listener code in the m3db, that if no rules supplied, default rules based on the namespaces will be generated. So no need in the operator to do so :-)
Enabling the carbon listener in a custom config map doesn't open the port in the service and container. Adding
EnableCarbonIngester
to the cluster spec, which then generate a config map withand opening the ports in the coordinator service and the m3dbnode containers, would be very helpfull.
The text was updated successfully, but these errors were encountered: