[jira] [Commented] (WICKET-6120) Wicket Metrics

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192541#comment-15192541 ] 

ASF GitHub Bot commented on WICKET-6120:
----------------------------------------

Github user klopfdreh commented on the pull request:

    https://github.com/apache/wicket/pull/164#issuecomment-196058123
  
    Ticket is created: https://issues.apache.org/jira/browse/WICKET-6120
    
    I choose this way of API because it actually not able to configure metrics from start (if available in the class path), because AspectJ is started before the init method is executed. But you can deactivate the JMX functionality and the measurement with meta data keys:
    
    ```java
    WicketMetricsSettings settings = 
    Application.get().getMetaData(WicketMetrics.METRIC_SETTINGS);
    settings.startJmxReporter();
    settings.stopJmxReporter();
    settings.setEnable(bool);
    ```
    



> Wicket Metrics
> --------------
>
>                 Key: WICKET-6120
>                 URL: https://issues.apache.org/jira/browse/WICKET-6120
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>    Affects Versions: 8.0.0-M1
>            Reporter: Tobias Soloschenko
>            Assignee: Tobias Soloschenko
>              Labels: features
>             Fix For: 8.0.0-M1
>
>
> As mentioned in confluence, it would be nice Wicket to collect data about the lifecycle of components and other useful metric data:
> https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0
> Mailing list:
> http://apache-wicket.1842946.n4.nabble.com/wicket-metrics-statistics-for-wicket-td4673887.html
> Pull request:
> https://github.com/apache/wicket/pull/164?_pjax=%23js-repo-pjax-container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)