Yes the logs are the only way to find out which port the reporter is
bound to.
We may be able to display this information in the web-UI, but it isn't
very high on my list and will probably require
modifications to the reporter interface.
On 21.12.2017 09:41, Piotr Nowojski wrote:
> I am not sure (and because of holiday season you might not get an answer quickly), however I do not see a way to obtain this port other then by looking into the log files. On the other hand, I have an impression, that intention of this feature was that if you must execute N reporters on one single machine, you configure port range to the size of N. That way you can just assume that each port was taken and used.
>
> Maybe Chesnay will be able to answer this question better once he is back from the holidays.
>
> Piotrek
>
>> On 20 Dec 2017, at 17:57, Jared Stehler <
[hidden email]> wrote:
>>
>> The prometheus metric reporter allows for a specification of a port range; is there a way I can find out which actual port it found to bind to?
>>
>> Also, there doesn’t seem to be a way to reserve an extra port for task managers in mesos to assign to a metric reporter, is that a roadmap item? I’m able to override the port for the app master (-Dmetrics.reporter.prom_reporter.port=$PORT1) but this carries over to the task managers and can collide with the assigned data port, etc.
>>
>>
>>
>> --
>> Jared Stehler
>> Chief Architect - Intellify Learning
>> o: 617.701.6330 x703
>>
>>
>>
>
Locked
