loggregator.dropsonde_incoming_port is not defined in manifest diego.yml

[ramelito]

loggregator.dropsonde_incoming_port is not defined in manifest diego.yml, this leads metron_agent to use default loggregator dropsonde incoming port 3457 not 3459 (from CF). As metron uses wrong port operator or developer can not get metrics from garden containers.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/105087208.

[emalm]

Hi, @ramelito,

Thanks for reporting this issue. Just to clarify, you're overriding that value to 3459 in your CF deployment manifest, but the spiff-based manifest-generation tooling in diego-release isn't propagating it correctly into the separate Diego deployment manifest? And you're referring to the loggregator.dropsonde_incoming_port value, and not metron_agent.dropsonde_incoming_port?

Thanks,
Eric, CF Runtime Diego PM

[ramelito]

Hi, @ematpl
that's correct, this value is not propagating to diego
i am using loggregator.dropsonde_incoming_port as it's defined in job spec

[emalm]

Thanks for the confirmation, @ramelito. I've created https://www.pivotaltracker.com/story/show/105646774 in the Diego tracker for the spiff-based manifest-generation system to respect this value from the CF deployment manifest.

Best,
Eric

[emalm]

Hi, @ramelito, this should be corrected with https://www.pivotaltracker.com/n/projects/1003146/stories/105646774 in Diego 0.1443.0. Closing.