Re: Parfait agent, docs, rpm updates

Hi,

On 2016-10-28 11:04, Marko Myllynen wrote:
> On 2016-10-28 10:28, Nathan Scott wrote:
>>
>> I've fixed up a bunch of things in parfait-agent land, added
>> several example code projects and documentation, and I built
>> new Fedora 23/24 RPMs for those who don't even maven...
>>
>> $ sudo dnf install dnf-plugins-core
>> $ sudo dnf copr enable nathans/pcp.io
>> $ sudo dnf install parfait parfait-agent parfait-examples
>>
>> (there's a new -examples RPM and parfait(1) man page is new.)
> 
> Thanks, but I don't see any new RPMs in your Copr repo except for a new
> build of the parfait.rpm:
> 
> https://copr.fedorainfracloud.org/coprs/nathans/pcp.io/packages/

Nevermind, the above page is still not showing it but dnf(1) found it.

>> 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.

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).

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.

...
Caused by: java.lang.IllegalStateException: updateInterval is too short.
...

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.

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.

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"


Thanks,

-- 
Marko Myllynen

-=-=-=-=-=-=-=-=-=-=-=-
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 (#14627): https://groups.io/g/pcp/message/14627
View All Messages In Topic (3): 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
-=-=-=-=-=-=-=-=-=-=-=-