<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 09:01:47 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-4323] Migrate uses of json.send to perf.send in Evergreen project YAML</title>
                <link>https://jira.mongodb.org/browse/JAVA-4323</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;div class=&quot;panel&quot; style=&quot;background-color: #fafbfc;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelContent&quot; style=&quot;background-color: #fafbfc;&quot;&gt;
&lt;h3&gt;&lt;a name=&quot;Summary&quot;&gt;&lt;/a&gt;&lt;b&gt;Summary&lt;/b&gt;&lt;/h3&gt;

&lt;p&gt;As of PM-2172, the TIPS team would like to remove its legacy performance gathering and analysis API in favor of a new, more robust option. In order to migrate to the new API, uses of &lt;tt&gt;json.send&lt;/tt&gt; in Evergreen project YAML should be removed in favor of using &lt;tt&gt;perf.send&lt;/tt&gt; (assuming it is desirable to continue to maintain / run the testing that uses &lt;tt&gt;json.send&lt;/tt&gt;) . The following &lt;a href=&quot;https://github.com/10gen/performance-tooling-docs/blob/main/getting_started/performance_monitoring_setup.md&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;instructions&lt;/a&gt; describe how to use &lt;tt&gt;perf.send&lt;/tt&gt;. We have also added &lt;a href=&quot;https://github.com/10gen/performance-tooling-docs/blob/main/getting_started/performance_monitoring_setup.md#legacy-data-migration&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;docs&lt;/a&gt; for migrating away from &lt;tt&gt;json.send&lt;/tt&gt; and onto &lt;tt&gt;perf.send&lt;/tt&gt;.&lt;/p&gt;
&lt;h3&gt;&lt;a name=&quot;Motivation&quot;&gt;&lt;/a&gt;&lt;b&gt;Motivation&lt;/b&gt;&lt;/h3&gt;
&lt;h4&gt;&lt;a name=&quot;Whoistheaffectedenduser%3F&quot;&gt;&lt;/a&gt;Who is the affected end user?&lt;/h4&gt;

&lt;p&gt;This ticket tracks the mongo-python-driver-perf change specifically.&lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;Howdoesthisaffecttheenduser%3F&quot;&gt;&lt;/a&gt;How does this affect the end user?&lt;/h4&gt;

&lt;p&gt;The trend charts UI will continue to display any legacy performance data that had previously been gathered with &lt;tt&gt;json.send&lt;/tt&gt; even after migration to &lt;tt&gt;perf.send&lt;/tt&gt;. Additionally, it appears that change points are not presently being detected for these projects even in cases where performance data is being collected; migration to &lt;tt&gt;perf.send&lt;/tt&gt; should avoid these sorts of errors.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Howlikelyisitthatthisproblemorusecasewilloccur%3F&quot;&gt;&lt;/a&gt;How likely is it that this problem or use case will occur?&lt;/h4&gt;

&lt;p&gt;N/A&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Iftheproblemdoesoccur%2Cwhataretheconsequencesandhowseverearethey%3F&quot;&gt;&lt;/a&gt;If the problem does occur, what are the consequences and how severe are they?&lt;/h4&gt;

&lt;p&gt;N/A&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisissueurgent%3F&quot;&gt;&lt;/a&gt;Is this issue urgent?&lt;/h4&gt;

&lt;p&gt;TIPS would like to remove the &lt;tt&gt;json.send&lt;/tt&gt; tooling as part of PM-2172, which we are working on this quarter. If all the usages could be removed or migrated to the new tooling by October 25th, that would be great.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisticketrequiredbyadownstreamteam%3F&quot;&gt;&lt;/a&gt;Is this ticket required by a downstream team?&lt;/h4&gt;

&lt;p&gt;Yes. It is required by TIPS for PM-2172.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisticketonlyfortests%3F&quot;&gt;&lt;/a&gt;Is this ticket only for tests?&lt;/h4&gt;

&lt;p&gt;Yes. This is specific to gathering and analyzing performance data.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="1888114">JAVA-4323</key>
            <summary>Migrate uses of json.send to perf.send in Evergreen project YAML</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="13201">Fixed</resolution>
                                        <assignee username="jeff.yemin@mongodb.com">Jeffrey Yemin</assignee>
                                    <reporter username="maria.vankeulen@mongodb.com">Maria van Keulen</reporter>
                        <labels>
                            <label>internal-user</label>
                    </labels>
                <created>Fri, 1 Oct 2021 18:25:00 +0000</created>
                <updated>Sat, 28 Oct 2023 11:21:01 +0000</updated>
                            <resolved>Thu, 7 Oct 2021 18:41:44 +0000</resolved>
                                                    <fixVersion>4.4.0</fixVersion>
                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="4111138" author="xgen-internal-githook" created="Thu, 7 Oct 2021 18:41:22 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Jeff Yemin&apos;, &apos;email&apos;: &apos;jeff.yemin@mongodb.com&apos;, &apos;username&apos;: &apos;jyemin&apos;}
&lt;p&gt;Message: Update performance benchmarks to use perf.send (#797)&lt;/p&gt;

&lt;p&gt;Evergreen has deprecated json.send in favor of perf.send. See&lt;br/&gt;
&lt;a href=&quot;https://github.com/evergreen-ci/evergreen/wiki/Project-Commands#perf-send&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/evergreen-ci/evergreen/wiki/Project-Commands#perf-send&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-4323&quot; title=&quot;Migrate uses of json.send to perf.send in Evergreen project YAML&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-4323&quot;&gt;&lt;del&gt;JAVA-4323&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/ea1ae2422f73a1da2c2dd7d3964c847b995f99d2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/ea1ae2422f73a1da2c2dd7d3964c847b995f99d2&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4097257" author="dbeng-pm-bot" created="Fri, 1 Oct 2021 18:28:34 +0000"  >&lt;p&gt;Moving this issue to Needs Triage because DRIVERS-1892 moved to Implementing.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10620">
                    <name>Issue split</name>
                                                                <inwardlinks description="split from">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <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|hr3nbb:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_21457" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Upstream Changes Summary</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p&gt;DRIVERS-1892:&lt;br/&gt;
As of PM-2172, the TIPS team would like to remove its legacy performance gathering and analysis API in favor of a new, more robust option. In order to migrate to the new API, uses of json.send in Evergreen project YAML should be removed in favor of using perf.send (assuming it is desirable to continue to maintain / run the testing that uses json.send) . Please see the linked DRIVERS ticket for detailed information about how to use perf.send. We have also added docs for migrating away from json.send and onto perf.send.&lt;/p&gt;
</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>