<div dir="ltr">Let me step back a bit...<div><br></div><div>I really think that for the embedded Wildfly agent, it makes total sense and is preferable to use standalone.xml for the reasons mentioned above. The user is primarily a Wildfly user and he "just" wants to monitor it.</div><div><br></div><div>Now, even though I see the benefits in some agent that can support many things (with or without plugins), I am not fully convinced that it's the right approach. <br></div><div><br></div><div>- For the docker/kubernetes/cAdvisor/heapster world, it would be more natural to run a Go-lang client with a yaml descriptor, this is kinda the "standard" there. That agent could be in charge of reading metrics for the kubernetes infrastructure + application metrics (through JMX/Jolokia and Prometheus) (admittedly, the language itself may somehow be hidden if it can run in a small container)</div><div>- At the OS/linux level, python seems to be a preferred solution (To be verified).</div><div>- ...</div><div><br></div><div>(In that case, I would trim down the Wildfly agent for DMR and embedded + domain scenarios.)</div><div><br></div><div>To some extend it would simplify some aspects ("no write-back" issue for instance), I understand it adds some duplication + requires a team to become polyglot.</div><div><br></div><div>Would we ever need to support 2 same protocoles for 2 different agents, very likely. Even though we seem to have some preferences according to the environment, WF is exposing its DMR interface in "standard" deployments, while it's exposing Jolokia in OpenShift environment.</div><div><br></div><div>In nothing else, I think it would help adoption + contributions.</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 7, 2016 at 5:58 AM, Josejulio Martinez Magana <span dir="ltr"><<a href="mailto:jmartine@redhat.com" target="_blank">jmartine@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Sep 6, 2016 at 8:27 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>> What about an utility to export/import that yaml from/to the standard<br>
> configuration file (standalone.xml) ?<br>
<br>
</span>That is one idea. However, note there still would be issues that need to be solved:<br>
<br>
1) Any change you make to the yaml file would require the user to run the export/import tool again - is that going to be annoying to the user? Are they even going to know they have to run a tool after editing a configuration file? That seems to be annoying to add a second step (1. modify the yaml file 2) run a tool to export the config into standalone.xml). People will most likely forget to do 2.<br></blockquote></span><div>Yep, I would indeed forget to do it. </div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2) This means our export/import tool needs to be smart enough to know how to transform the standalone.xml when the agent configuration is not there yet AND when there is already agent configuration there. We'd need to do something similar to what the agent installer does, which is not trivial.<br>
<br>
3) Still doesn't solve the security problems (passwords unencrypted, how to define and reference security realms) - unless we add the security realms in the yaml and have the export/import tool modify the standalone.xml so it modifies the proper security-realms section in standalone xml, too.<br>
<br>
4) Still doesn't solve the "no write-back" to the yaml. If you change or add a config setting via the JBoss CLI, it will get persisted to standalone.xml, but it will NOT be persisted to the yaml file. The yaml file essentially becomes stale and you can no longer refer to it and be guaranteed it contains the most up-to-date config. If you run the export/import tool on the stale yaml, you have essentially overwritten the current config in standalone.xml with stale config.<br></blockquote></span><div>I was thinking, what if instead of having a yaml file, you do something like git. </div><div>e.g. $ hawkular-agent-config path-to-standalone.xml</div><div>It would parse standalone.xml and create and open (with vim or some other editor) a yaml file (or some other easy to read/edit format) with the current configuration, you edit, save and close and all the changes go back to the standalone.xml file.</div><div>or some other way to actually make it easier to modify agent configuration (like a GUI or command line tool) without having a second configuration file that might be out-of-sync.</div><span class=""><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/hawkular-dev</a><br>
</div></div></blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div>