Re: Parfait agent, docs, rpm updates

Hi Marko,

----- Original Message -----
> [...]
> >> Please give it a whirl - incremental improvement, and there's
> >> still lots to do of course.  I'll be away for the better part
> >> of the next two weeks, so wont be hacking on it for a bit.
> 
> It's starting to look very nice! With -Dparfait.name=foo the namespace
> issue is more or less solved (ok, if we'd be splitting hairs making sure
> nobody overrides others' metrics perhaps it could combine name and
> cluster id to make the files unique but perhaps this is now more in the
> "don't do it if it hurts" category). The mmv directory is still being
> created with different permissions by Install and parfait, though.

Yes, I'm not sure of a better strategy there yet though.  parfait doesn't
have the same permissions (it's running as regular user) and the Install
script wants to assist with providing MMV back-compatibility.  Ho-hum.

> JMX mode also worked just fine except with interval. I would perhaps
> change the man example not to enable unauthenticated JMX remote access
> by default (i.e., use -Dcom.sun.management.jmxremote.local.only=true
> instead of =false).

+1  - done.

> With java -Dparfait.name=foobar -Dparfait.interval=60 -jar ... I get an
> exception, with interval=60000 it works, I think the unit should be
> spelled out. Btw, -connect is used in the examples but it is not
> mentioned anywhere else in the man page.

Fixed.

> Defining the same cluster ID for two different agents using different
> name seems to work, it should probably fail to prevent accidents as
> their PMID is the same in this case.

pmdammv is actually capable of stitching together metrics from multiple
files - people even use this to provide different instances of a metric
from different applications for example.  So, its not necessarily an
accident when it happens, which makes guarding against accidents tricky.

> Not sure whether the Spring XML files would be better under /etc than
> /usr on a typical installation given that they might need changes every
> now and then, I'd probably move them under /etc.

+1  - done.

> With WildFly (10.1.0.Final) I still see the same logging related
> exception when trying to start it up after adding this to start script:
> 
> JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager
> -Dparfait.name=wildfly -javaagent:/usr/share/java/parfait/parfait.jar
> $JAVA_OPTS"

Not sure this is going to be fixable ... still looking for solutions, but
its Wildfly being really paranoid about logging.  This may end up being a
case where the proxy mode has to be used I guess, good thing we have that
solution up our sleeve now.

cheers.

--
Nathan

-=-=-=-=-=-=-=-=-=-=-=-
pcp mailing list
[email protected]
https://groups.io/g/pcp/messages
-=-=-
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#14813): https://groups.io/g/pcp/message/14813
View All Messages In Topic (4): https://groups.io/g/pcp/topic/2984744
Mute This Topic: https://groups.io/mt/2984744?uid=174580
New Topic: https://groups.io/g/pcp/post

Change Your Subscription: https://groups.io/g/pcp/editsub?uid=174580

Group Home: https://groups.io/g/pcp
Contact Group Owner: [email protected]

Terms of Service: https://groups.io/static/tos

Unsubscribe: https://groups.io/g/pcp/leave/354243/563757577/xyzzy
-=-=-=-=-=-=-=-=-=-=-=-