How to disable CasMetricsConfiguration in CAS 5.2.3?

[Mr Rao]

Hi,

We have decided to  disable  CasMetricsConfiguration  I couldn't find property in cas.properties file to disable this?

I do not want any perfStatsLogger at all. Any help is greatly appreciated. This is filling up log files/disk space.

Thanks

Rao

018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.non-heap.used, value=105554216

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Code-Cache.committed, value=11108352

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Code-Cache.init, value=163840

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Code-Cache.max, value=33554432

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Code-Cache.usage, value=0.1809825897216797

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Code-Cache.used, value=6072768

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.committed, value=143130624

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.init, value=4521984

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.max, value=143130624

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.usage, value=0.34437706356956843

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.used, value=49290904

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Eden-Space.used-after-gc, value=0

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Metaspace.committed, value=100773888

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Metaspace.init, value=0

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Metaspace.max, value=-1

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Metaspace.usage, value=0.9871748522791935

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Metaspace.used, value=99481448

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.committed, value=17891328

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.init, value=524288

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.max, value=17891328

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.usage, value=0.20750611692994506

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.used, value=3712560

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Survivor-Space.used-after-gc, value=3712560

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.committed, value=357957632

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.init, value=11206656

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.max, value=357957632

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.usage, value=0.9090788710994714

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.used, value=325411720

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.pools.Tenured-Gen.used-after-gc, value=301383952

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.total.committed, value=630861824

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.total.init, value=16941056

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.total.max, value=518979583

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=jvm.memory.total.used, value=483969400

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.blocked.count, value=0

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.count, value=81

2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.daemon.count, value=71

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.deadlock.count, value=0

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.deadlocks, value=[]

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.new.count, value=0

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.runnable.count, value=25

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.terminated.count, value=0

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.timed_waiting.count, value=30

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=GAUGE, name=thread-states.waiting.count, value=26

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.CREATE_PROXY_GRANTING_TICKET_COUNTER, count=0

2018-12-11 18:22:13,667 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.CREATE_TICKET_GRANTING_TICKET_COUNTER, count=1

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.DELETE_TICKET_COUNTER, count=0

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.DESTROY_TICKET_GRANTING_TICKET_COUNTER, count=2

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.GET_TICKETS_COUNTER, count=0

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.GET_TICKET_COUNTER, count=5

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.GRANT_PROXY_TICKET_COUNTER, count=0

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.GRANT_SERVICE_TICKET_COUNTER, count=1

2018-12-11 18:22:13,668 severity=INFO, class=perfStatsLogger, type=COUNTER, name=org.apereo.cas.DefaultCentralAuthenticationService.VALIDATE_SERVICE_TICKET_COUNTER, c

[Ray Bon]

Rao,

You can comment it out in log4j2.xml:

<!-- Log perf stats only to perfStats.log -->

        <!-- <AsyncLogger name="perfStatsLogger" level="info" additivity="false" includeLocation="true">

            <AppenderRef ref="casPerf"/>

        </AsyncLogger> -->

Ray

-- 
Ray Bon
Programmer analyst
Development Services, University Systems
2507218831 | CLE 019 | rb...@uvic.ca

[Jon Anderson]

I fought with the same issue a few months ago, and I did not figure out how to suppress that log. I'm pretty sure that I tried commenting out the log4j entry as well as other tweaks, but nothing worked for me. If it works I'll have to try again...

Jon

---

From: cas-...@apereo.org [cas-...@apereo.org] on behalf of Ray Bon [rb...@uvic.ca]
Sent: Wednesday, December 12, 2018 11:10 AM
To: cas-...@apereo.org
Subject: Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1544634634.2733.3.camel%40uvic.ca.

[Mr Rao]

Thanks for your response.   I tried commenting out and it started routing the logs to application log files which didn't solve the issue.

[Ray Bon]

By 'application log files', do you mean catalina.out?

First make sure you are editing the correct file. You can force a particular file with a setting like this in cas.properties:

logging.config: file:/home/uvtomcat/config/log4j2.xml

Perhaps there is a more general logger that picks up the perStatsLogger. In the logger definition 'additivity="false"' prevents other loggers from also processing the messages. _BUT_ you must have an AppenderRef defined; if not the root logger (typically console => catalina.out) will take over.

In other words, you have to comment out the logger, as below, not just the appender ref.

Ray

[Mr Rao]

Thanks, Ray.

Rao.