<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:56:12 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[JAVA-2057] Custom logging implementation</title>
                <link>https://jira.mongodb.org/browse/JAVA-2057</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;The Java driver currently assumes that logging will be done through SLF4J or java.util.logging.&lt;/p&gt;

&lt;p&gt;There doesn&apos;t appear to be a way to integrate the driver with a custom logging framework, making it difficult to integrate logging in middleware libraries that supply their own logging.&lt;/p&gt;

&lt;p&gt;The MongoDB C Driver allows for library users to specify logging callbacks.&lt;/p&gt;</description>
                <environment></environment>
        <key id="243174">JAVA-2057</key>
            <summary>Custom logging implementation</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jamesd">James Duong</reporter>
                        <labels>
                    </labels>
                <created>Thu, 10 Dec 2015 08:19:47 +0000</created>
                <updated>Fri, 8 Dec 2017 21:57:09 +0000</updated>
                            <resolved>Fri, 8 Dec 2017 21:57:09 +0000</resolved>
                                                                    <component>Monitoring</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="1747464" author="jeff.yemin" created="Fri, 8 Dec 2017 21:57:09 +0000"  >&lt;p&gt;As there have been no other requests for this feature, and there are workarounds available (though none were seen as acceptable by the reporter), I&apos;m closing this as Won&apos;t Fix.&lt;/p&gt;</comment>
                            <comment id="1111189" author="jeff.yemin" created="Thu, 10 Dec 2015 19:44:11 +0000"  >&lt;p&gt;If SLF4J is not on the classpath, the driver defaults to JUL (java.util.logging), so it logs to wherever JUL is configured to log.  There is no way to completely turn off logging except via configuration of the logging implementation itself.&lt;/p&gt;</comment>
                            <comment id="1111182" author="jamesd" created="Thu, 10 Dec 2015 19:36:54 +0000"  >&lt;p&gt;Hi Jeff,&lt;/p&gt;

&lt;p&gt;We won&apos;t be able to use solution 1, since we don&apos;t want to add an SLF4J dependency in our JDBC Driver (we wouldn&apos;t want to conflict with the calling application&apos;s version of SLF4J if it has one). &lt;/p&gt;

&lt;p&gt;Command Monitoring lloks like it might be a viable solution.&lt;/p&gt;

&lt;p&gt;In the meantime, is there an easy way to shut off logging in the 3.0.0 Driver, regardless of if SLF4J appears in the class path? It seems to log to STDERR by default.&lt;/p&gt;</comment>
                            <comment id="1111036" author="jeff.yemin" created="Thu, 10 Dec 2015 18:11:43 +0000"  >&lt;p&gt;In that case, you have a couple of workarounds using the currently released driver&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;Build an SLF4J bridge to your logging API&lt;/li&gt;
	&lt;li&gt;Add your own logging via &lt;a href=&quot;http://mongodb.github.io/mongo-java-driver/3.2/driver/reference/management/monitoring/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Command Monitoring&lt;/a&gt;, introduced in the 3.1 driver.  This doesn&apos;t get you everything you might want, but we will be adding more event types in future versions that will provider fuller coverage of any events that an application might want to log.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;We will also consider your request to make logging pluggable.  But note that the C driver does this because there is no equivalent to SLF4J in C.  The whole point of SLF4J is so that every library doesn&apos;t have to invent its own pluggable logging API.&lt;/p&gt;
</comment>
                            <comment id="1111001" author="jamesd" created="Thu, 10 Dec 2015 17:52:44 +0000"  >&lt;p&gt;Hi Jeff,&lt;/p&gt;

&lt;p&gt;We are using our own SDK to build a JDBC driver on top of the Mongo Java Driver. It has its own logging API that isn&apos;t tied to SL4J or java.util.logging.&lt;/p&gt;</comment>
                            <comment id="1110671" author="jeff.yemin" created="Thu, 10 Dec 2015 14:51:16 +0000"  >&lt;p&gt;Hi James,&lt;/p&gt;

&lt;p&gt;Can you tell me what middleware libraries you&apos;d like to integrate with?&lt;/p&gt;
</comment>
                            <comment id="1110466" author="jamesd" created="Thu, 10 Dec 2015 09:44:44 +0000"  >&lt;p&gt;This was encountered in the 3.0.0 build.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hsewn3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>