<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 4, 2017 at 2:00 PM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Why don't just upload the agent with the config of the new slaves ?<br>
><br>
> Today, when an agent is added/modified (is the same use case in practical<br>
> terms), the p8s are generated.<br>
><br>
> So, if we know we have a modification, just add the slave endpoints into<br>
> the agent config, and just let the inventory re-create them.<br>
<br>
</span>Hmm.. that's possible. We would have to change the way the "Metrics Endpoint" resource config property is processed. Today it is assumed to be a single value ("host:port")... we would need it to be a comma-separate list (e.g. "host:8787,host:8787/slave1/<wbr>metrics,host:8787/slave2/<wbr>metrics" or something like that. The server would then have to parse it out and create multiple endpoints. Note that it would also be nice to DELETE files if they did exist before but now no longer do exist.<br>
<br>
Like if the agent originally was<br>
<br>
"host:8787,host:8787/slave1/<wbr>metrics,host:8787/slave2/<wbr>metrics"<br>
<br>
but is now<br>
<br>
"host:8787,host:8787/slave1/<wbr>metrics"<br>
<br>
the slave2 file should be deleted so P doesn't try to scrape it anymore.<br></blockquote><div><br></div><div>It's doable, let's collect requeriments about if we would need additional info perform those changes once we have a picture more or less drafted.</div><div><br></div><div>I mean, if we need to have a map to easy identify slave or something similar (well, this is more implementation detail).</div><div><br></div><div> </div></div><br></div></div>