You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/10/08 10:24:20 UTC
[jira] [Resolved] (SLING-6120) Collect logger names which get hit
for a given request thread
[ https://issues.apache.org/jira/browse/SLING-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved SLING-6120.
------------------------------------
Resolution: Fixed
Now a {{loggerNames}} array would be part of recording which would have name of loggers
{code:javascript}
"loggerNames": [
"org.apache.jackrabbit.oak.cache.CacheLIRS",
"org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate",
"org.apache.jackrabbit.oak.jcr.operations.query",
"org.apache.jackrabbit.oak.jcr.operations.reads",
"org.apache.jackrabbit.oak.jcr.operations.writes",
"org.apache.jackrabbit.oak.plugins.index.lucene.IndexPlanner",
"org.apache.jackrabbit.oak.plugins.index.property.PropertyIndex",
"org.apache.jackrabbit.oak.query.QueryEngineImpl",
"org.apache.jackrabbit.oak.query.QueryImpl",
"org.apache.jackrabbit.oak.query.SQL2Parser",
"org.apache.jackrabbit.oak.security.authentication.LoginContextProviderImpl",
"org.apache.jackrabbit.oak.security.authorization.composite.CompositeAuthorizationConfiguration",
"org.apache.jackrabbit.oak.security.authorization.permission.PermissionStoreImpl",
"org.apache.sling.adapter.internal.AdapterManagerImpl",
"org.apache.sling.commons.compiler.impl.EclipseJavaCompiler",
"org.apache.sling.commons.fsclassloader.impl.FSClassLoaderProvider",
"org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter",
"org.apache.sling.engine.impl.request.RequestData",
"org.apache.sling.i18n.impl.JcrResourceBundle",
"org.apache.sling.i18n.impl.JcrResourceBundleProvider",
"org.apache.sling.jcr.resource.internal.JcrSystemUserValidator",
"org.apache.sling.jcr.resource.internal.helper.jcr.JcrItemResourceFactory",
"org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator",
"org.apache.sling.resourceresolver.impl.ResourceResolverImpl",
"org.apache.sling.resourceresolver.impl.helper.ResourceResolverControl",
"org.apache.sling.rewriter.impl.PipelineImpl",
"org.apache.sling.scripting.core.impl.BindingsValuesProvidersByContextImpl",
"org.apache.sling.scripting.core.impl.DefaultSlingScript",
"org.apache.sling.scripting.jsp.jasper.compiler.Compiler",
"org.apache.sling.scripting.jsp.jasper.compiler.SmapUtil$SDEInstaller",
"org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper",
"org.apache.sling.scripting.jsp.taglib.AbstractDispatcherTagHandler",
"org.apache.sling.servlets.resolver.internal.SlingServletResolver",
"org.eclipse.jetty.io.ChannelEndPoint",
"org.eclipse.jetty.server.HttpConnection"
]
{code}
Done with r1763885
> Collect logger names which get hit for a given request thread
> -------------------------------------------------------------
>
> Key: SLING-6120
> URL: https://issues.apache.org/jira/browse/SLING-6120
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: Log Tracer 1.0.2
>
>
> To allow better discovery to determine logger names to enabled it would be good to collect name of loggers which get invoked as part of given request processing.
> These loggers need not log but they might be just check if given logging level is enabled or not. We can collect such logger names and report back as part of recording to allow end user an option to enable "interesting ones"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)