Anything with a response time logged as “0ms” in the dispatcher.log was served from cache, whilst anything else would have been served from the publish backend. This is a fairly inefficient search (I’ll get around to improving it) but it gets the job done. | appendcols [search(index=aem source=/var/log/httpd/dispatcher.log host=aem-prd*) NOT 0ms (index=aem source=/var/log/httpd/dispatcher.log host=aem-prd*) 0ms Graphing Dispatcher Cache Hit RatioĪn easy way to get a running graph of your cache hit ratio on the AEM Dispatcher / Publisher tier is to analyze your dispatcher.log to find out how many requests the dispatcher serves out of cache vs the number of requests that it serves after requesting the resource from the backend publisher. When Response time is being extracted from your request logs, use the above to get a chart of average response times by host for the publish tier. Sourcetype=aem_request_log | timechart avg(responsetime)span=5m by host Graph of Author/Publish Average Response Time #Splunk Search Make sure to extract just the number from the responsetime so that you can do mathmatical functions like averages, most/least/etc against the responsetime.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |