<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We expose the Monitor via and endpoint in saiku:<div><br></div><div><a href="http://dev.analytical-labs.com/saiku/rest/saiku/statistics/mondrian">http://dev.analytical-labs.com/saiku/rest/saiku/statistics/mondrian</a></div><div>admin / admin</div><div><br></div><div>Was useful to see how connections are opened but never closed (<a href="http://jira.pentaho.com/browse/MONDRIAN-1653">http://jira.pentaho.com/browse/MONDRIAN-1653</a>)</div><div>But so far I wasn't able to make much use of it myself.</div><div>Was planning on logging that info every x interval to view changes over time.</div><div><br></div><div>In any case it would be quite useful to know more about whats happening inside mondrian.</div><div><br></div><div>-Paul</div><div><br><div><div>On Apr 4, 2014, at 4:54 PM, "Wright, Jeff" <<a href="mailto:jeff.s.wright@truvenhealth.com">jeff.s.wright@truvenhealth.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">In addition to Bob's logging request, it definitely is also appealing to be able to see into what's happening right now. It seems like it would be easy and worthwhile for us to throw together a JSP or servlet to expose the Monitor info as a status page, until the JMX interface is available.<br><br>--jeff<br><br>-----Original Message-----<br>From: <a href="mailto:mondrian-bounces@pentaho.org">mondrian-bounces@pentaho.org</a> [mailto:mondrian-<a href="mailto:bounces@pentaho.org">bounces@pentaho.org</a>] On Behalf Of Matt Campbell<br>Sent: Friday, April 04, 2014 10:50 AM<br>To: Mondrian developer mailing list<br>Subject: Re: [Mondrian] Mapping user requests to mondrian MDX and SQL<br><br>The monitor has always seemed to me like something that could be incredibly useful for larger deployments, and it's a shame it hasn't gotten more usage. Because it hasn't been beat on much in the real world I know there are some cases where it gives incorrect numbers (e.g. MONDRIAN-1449), but I'd love to see some work to correct any issues.<br><br><br><br>________________________________________<br>From: <a href="mailto:mondrian-bounces@pentaho.org">mondrian-bounces@pentaho.org</a> [<a href="mailto:mondrian-bounces@pentaho.org">mondrian-bounces@pentaho.org</a>] On Behalf Of Wright, Jeff [<a href="mailto:jeff.s.wright@truvenhealth.com">jeff.s.wright@truvenhealth.com</a>]<br>Sent: Friday, April 04, 2014 10:32 AM<br>To: Mondrian developer mailing list<br>Subject: Re: [Mondrian] Mapping user requests to mondrian MDX and SQL<br><br>Luc, the monitor API sounds like a window into what’s going on right now. I think the spirit of Bob’s request is for analysis after the fact. We have Mondrian embedded in an application, and would like to correlate the Mondrian logs to the specific report request in the surrounding app, and to have that in an slf4j log.<br><br>The JIRA for JMX has 14 votes right now ☺<br><a href="http://jira.pentaho.com/browse/MONDRIAN-1448">http://jira.pentaho.com/browse/MONDRIAN-1448</a><br><br>--jeff<br><br>From: mondrian-bounces@pentaho.org [mailto:mondrian-bounces@pentaho.org] On Behalf Of Baldwin, Bob<br>Sent: Friday, April 04, 2014 10:28 AM<br>To: Mondrian developer mailing list<br>Subject: Re: [Mondrian] Mapping user requests to mondrian MDX and SQL<br><br>Thanks Luc for the quick response!<br><br>I’ll investigate the monitor and see if it fits our needs. We would also be interested in the JMX support if that feature were to be resurrected.<br><br>Bob<br><br>From: mondrian-bounces@pentaho.org<mailto:mondrian-bounces@pentaho.org> [mailto:mondrian-bounces@pentaho.org] On Behalf Of Luc Boudreau<br>Sent: Friday, April 04, 2014 10:22 AM<br>To: Mondrian developer mailing list<br>Subject: Re: [Mondrian] Mapping user requests to mondrian MDX and SQL<br><br>There's an easier way to track them.<br><br>In Mondrian 3.3.X, we have introduced the Mondrian monitor API.<br><br> final Monitor monitor =<br> MondrianServer.forConnection(rolapConnection)<br> .getMonitor();<br>Through the monitor, you can get all sorts of interesting metrics, like the MDX queries running, which SQL statements they have created, how many cells from the cache were hits & misses, and much more. Would that be of help?<br>We also have a branch with JMX support, but we haven't had much traction for that feature so it stayed on the back burner for a while now. Maybe now's the time to resurrect it.<br>Luc<br><br>On Fri, Apr 4, 2014 at 10:02 AM, Baldwin, Bob <robert.w.baldwin@truvenhealth.com<mailto:robert.w.baldwin@truvenhealth.com>> wrote:<br>We are currently trying to map a user request for a report to the MDX and the SQL generated by Mondrian.<br><br>To do this we are intercepting the “mondrian.mdx” and “mondrian.sql” loggers with a new slf4j appender (we are bridging log4j to slf4j) to write the MDX and subsequent SQL to a database log. In an attempt to map the MDX and SQL to a specific request by user, we are setting MDC values to be used by the appender when Mondrian kicks off the log. This works fine if enough time occurs between requests to Mondrian as a new executor thread is created.<br><br>The problem, for us, occurs when a the executor thread is reused. Instead of the new MDC values being propagated to the executor, they are persisting because it’s the same thread, instead of a new one which would inherit the new MDC properties from the parent thread.<br><br>Is there a way to accurately track the MDX and SQL ran per request to Mondrian and map that back to the requesting thread? I suspect forcing a new executor thread every time would solve this (if possible) but I worry about the performance implications of doing that.<br><br>Thanks for any help/direction.<br><br>Truven Health Analytics<br>Bob Baldwin<br>Software Engineer<br><br>Truven Health Analytics<br>O: 734.786.5365<tel:734.786.5365><br>robert.w.baldwin@truvenhealth.com<mailto:robert.w.baldwin@truvenhealth.com><br>truvenhealth.com<http://truvenhealth.com><br><br>[cid:image001.gif@01CF4FF1.309138D0]<br><br><br>_______________________________________________<br>Mondrian mailing list<br>Mondrian@pentaho.org<mailto:Mondrian@pentaho.org><br>http://lists.pentaho.org/mailman/listinfo/mondrian<br>_______________________________________________<br>Mondrian mailing list<br>Mondrian@pentaho.org<br>http://lists.pentaho.org/mailman/listinfo/mondrian<br>_______________________________________________<br>Mondrian mailing list<br>Mondrian@pentaho.org<br>http://lists.pentaho.org/mailman/listinfo/mondrian<br></blockquote></div><br></div></body></html>