Merge pull request #8641 from newrelic/daily-release/07-27-2022-evening

daily-release/07-27-2022-evening

Author: barbnewrelic

package.json

@@ -9,7 +9,7 @@
     "@github-docs/frontmatter": "^1.3.1",
     "@mdx-js/mdx": "^2.0.0-next.8",
     "@mdx-js/react": "^2.0.0-next.8",
-    "@newrelic/gatsby-theme-newrelic": "6.8.0",
+    "@newrelic/gatsby-theme-newrelic": "6.9.2",
     "@splitsoftware/splitio-react": "^1.2.4",
     "cockatiel": "^3.0.0-beta.0",
     "common-tags": "^1.8.0",

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx

@@ -53,20 +53,6 @@ For how to find billing and usage information in the UI, see [Billing-related UI
   If you're on our [original user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-user-models), see [some considerations for managing billable users](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#managing-billable-users).
 </Callout>
 
-## Tiered pricing [#tiered-pricing]
-
-Some Pro and Enterprise edition organizations have access to tiered pricing for data and/or billable users. The prices and tier levels will vary depending on an organization's specific contract. 
-
-Here's an example of how tiered pricing might work for an organization that has tiered pricing for full platform users:
-
-* Users #1-10 at price x
-* Users #11-20 at price y (lower than x)
-* Users #21-30 at price z (lower than y)
-
-Note that the billable users in lower tiers remain billable at that tier's cost, regardless of how many other, less expensive tiers are unlocked for subsequent users. In the example above, if the customer has 29 full platform users for the month, then the billable full platform users for the month would be the sum of: a) 10 users multiplied by price x, b) 10 users multiplied by price y, and c) 9 users multiplied by price z. 
-
-If you want access to tiered pricing, talk to your account representative. 
-
 ## Data ingest calculation [#usage-calculation]
 
 Want to understand how data ingest is calculated? See [Data ingest calculation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing).
@@ -86,6 +72,20 @@ A New Relic organization can have one of several types of plans that govern how
 
 For more about how these options can affect your user downgrade rules, see [Downgrade rules](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing#user-downgrade-rules).
 
+## Tiered pricing [#tiered-pricing]
+
+Some Pro and Enterprise edition organizations have access to tiered pricing for data and/or billable users. The prices and tier levels will vary depending on an organization's specific contract. 
+
+Here's an example of how tiered pricing might work for an organization that has tiered pricing for full platform users:
+
+* Users #1-10 at price x
+* Users #11-20 at price y (lower than x)
+* Users #21-30 at price z (lower than y)
+
+Note that the billable users in lower tiers remain billable at that tier's cost, regardless of how many other, less expensive tiers are unlocked for subsequent users. In the example above, if the customer has 29 full platform users for the month, then the billable full platform users for the month would be the sum of: a) 10 users multiplied by price x, b) 10 users multiplied by price y, and c) 9 users multiplied by price z. 
+
+If you want access to tiered pricing, talk to your account representative. 
+
 ## Announcement: removal of estimated cost in May of 2022 [#estimated-cost-removal]
 
 In May of 2022, we removed the current month's estimated cost from the usage UI and from usage-related events. For details, see the [release notes](/docs/release-notes/org-user-mgmt-release-notes/org-users-22-05-01).

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -484,6 +484,23 @@ Here's a detailed comparison of capabilities by user type. For tips on why you'd
       </td>
     </tr>
 
+    <tr>
+      <td>
+        [Service level management](/docs/service-level-management/intro-slm/)
+      </td>
+
+      <td style="text-align:center"/>
+
+      <td/>
+
+      <td style="text-align:center">
+        <Icon
+          style={{color: '#328787'}}
+          name="fe-check"
+        />
+      </td>
+    </tr>
+
     <tr>
       <td>
         [Infinite Tracing](/docs/distributed-tracing/infinite-tracing/introduction-infinite-tracing) (Pro & Enterprise editions only)

src/content/docs/accounts/original-accounts-billing/original-users-roles/user-migration.mdx

@@ -89,7 +89,7 @@ Before you start, be sure you've read [the requirements](#requirements) and the
   src={userMigrationPage1}
 />
 
-On this page, you'll select the admins you want to migrate. This step will create user records on the new model for the chosen admins and assign them to the **Admin** group. Once done, the chosen admins will have a new user record available upon logging in to New Relic (see image below), and will have access to both the old and new user records until the migration wizard process is completed. The admins you choose here will have the ability to use the migration wizard from their new user record: this may be helpful if you want to choose other team members to finish the migration for you. 
+On this page, you'll select the admins you want to migrate. This step will create user records on the new model for the chosen admins and assign them to the **Admin** group. Once that's done, those admins will have a new user record available upon logging in to New Relic (see image below), and will have access to both the old and new user records until the migration wizard process is completed. Any admin you migrate at this stage can help you complete the migration wizard: that's one benefit to having the admins migrated first. For any user to access the migration wizard after this step is completed, they must sign in with their new user record: this may require signing out of New Relic and re-accessing the log-in screen so that you can see all the log-in options. 
 
 Note that you can always add more admins, or remove and edit existing admins, after you complete the migration process. This may be a reason to bring over many or all your admins now and adjust settings later.  
 

src/content/docs/apis/nerdgraph/examples/async-queries-nrql-tutorial.mdx

@@ -7,7 +7,7 @@ tags:
 metaDescription: Use New Relic NerdGraph to make asynchronous NRQL queries that have longer query duration limits.
 ---
 
-You can use our NerdGraph API to run an asynchronous NRQL query. Once initiated, asynchronous queries run in the background, and clients can make follow-up requests to retrieve query results. This avoids issues like browser or HTTP connection timeouts. It’s especially useful for running queries that may take a long time to complete.
+You can [use NerdGraph to run NRQL queries](/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial). In addition, you can also use NerdGraph to run an asynchronous NRQL query. Asynchronous queries run in the background, and you can make follow-up requests to retrieve query results or the query status. This type of query avoids a query being interrupted by issues like browser timeouts or HTTP connection timeouts. It's especially useful for running queries that may take a long time to complete.
 
 ## Requirements [#requirements]
 

src/content/docs/apm/agents/nodejs-agent/api-guides/nodejs-agent-api.mdx

@@ -762,11 +762,13 @@ New Relic's Node.js agent includes additional API calls.
     ```
 
     Use this call if your app is doing its own error handling with domains or try/catch clauses, but you want all of the information about how many errors are coming out of the app to be centrally managed. Unlike other Node.js calls, this can be used outside of route handlers, but it will have additional context if called from within transaction scope.
+    
+    `error` should be an `Error` or one of its subtypes, but the API will handle strings and objects that have an attached `.message` or `.stack` property.
 
     `customAttributes` is an optional object of any custom attributes to be displayed in the New Relic UI.
 
     <Callout variant="caution">
-      Errors recorded using this method do not obey the [ignore_status_codes](/docs/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration#error_ignore) configuration value.
+      Errors recorded using this method do not obey the [`ignore_status_codes`](/docs/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration#error_ignore) configuration value.
     </Callout>
   </Collapser>
 

src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx

@@ -3470,6 +3470,54 @@ For more information about setting up distributed tracing, see [Enable distribut
   </Collapser>
 </CollapserGroup>
 
+## gRPC server instrumentation [#grpc_server]
+
+The `grpc` section controls the behavior of how the gRPC server is instrumented.
+
+
+<CollapserGroup>
+  <Collapser
+    id="record_errors"
+    title="record_errors"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            Boolean
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            `true`
+          </td>
+        </tr>
+        <tr>
+          <th>
+            [Environ variable](#environment)
+          </th>
+
+          <td>
+            `NEW_RELIC_GRPC_RECORD_ERRORS`
+          </td>
+        </tr>
+      </tbody>
+    </table>
+
+    When enabled, the agent will send all error gRPC status codes to New Relic, that is, nonzero status codes. If disabled, the server instrumentation will not send any nonzero status codes to New Relic.
+  </Collapser>
+</CollapserGroup>
+
+
 ## Span events
 
 [Span data](/docs/apm/distributed-tracing/ui-data/span-event) is reported for [distributed tracing](#distributed-tracing). Distributed tracing must be enabled to report spans. Span configuration is set in the `span_events` stanza. Options include:

src/content/docs/data-apis/custom-data/custom-events/apm-report-custom-events-attributes.mdx

@@ -76,9 +76,9 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in Java agent version 3.13.0 or higher. To send custom events, call [`recordCustomEvent`](https://newrelic.github.io/java-agent-api/javadoc/index.html?com/newrelic/api/agent/Insights.html). For example:
 
-    ```
+    ```java
     Map<String, Object> eventAttributes = new HashMap<String, Object>();
-    NewRelic.getAgent().getInsights().recordCustomEvent("<var>MyCustomEvent</var>", <var>eventAttributes</var>);
+    NewRelic.getAgent().getInsights().recordCustomEvent("MyCustomEvent", eventAttributes);
     ```
 
     The first argument defines the name of your event type, and the second argument is a map with the attributes for your custom event. Event attributes must be strings or numbers. Ensure you limit the number of unique event type names that you create, and do not generate these names dynamically. For restrictions on event type names, see our documentation about [limits and restricted characters](/docs/telemetry-data-platform/custom-data/custom-events/data-requirements-limits-custom-event-data) and [NRQL reserved words](/docs/insights/event-data-sources/custom-events/data-requirements-limits-custom-event-data/#reserved-words).
@@ -87,14 +87,14 @@ When creating your own custom events and attributes, follow data requirements fo
 
     Specify the maximum number of events to record per minute as an integer. For example, if you want to send less than the default of 10000 events:
 
-    ```
+    ```yml
     custom_insights_events:
       max_samples_stored: 5000
     ```
 
     To disable custom events entirely, add the following to your `newrelic.yml`:
 
-    ```
+    ```yml
     custom_insights_events:
       enabled: false
     ```
@@ -103,7 +103,7 @@ When creating your own custom events and attributes, follow data requirements fo
 
     For Java agent versions prior to 4.1.0, use the following YAML configuration:
 
-    ```
+    ```yml
     custom_insights_events.enabled: true
     custom_insights_events.max_samples_stored: 5000
     ```
@@ -116,7 +116,7 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in .NET agent version 4.6.29.0 or higher. To send custom events, simply call [`RecordCustomEvent()`](/docs/agents/net-agent/net-agent-api/recordcustomevent-net-agent). For example:
 
-    ```
+    ```cs
     var eventAttributes = new Dictionary<String, Object>();
     NewRelic.Api.Agent.NewRelic.RecordCustomEvent('MyCustomEvent', eventAttributes);
     ```
@@ -135,8 +135,8 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in Node.js agent version 1.15.0 or higher. To send custom events, simply call the relevant API. For example:
 
-    ```
-    recordCustomEvent(<var>eventType</var>, <var>attributes</var>)
+    ```js
+    recordCustomEvent(eventType, attributes)
     ```
 
     Use recordCustomEvent to record an event-based metric, usually associated with a particular duration. The eventType must be an alphanumeric string less than 255 characters. The attributes must be an object of key and value pairs. The keys must be shorter than 255 characters, and the values must be string, number, or boolean. For restrictions on event type names, see our documentation about [limits and restricted characters](/docs/telemetry-data-platform/custom-data/custom-events/data-requirements-limits-custom-event-data) and [NRQL reserved words](/docs/insights/event-data-sources/custom-events/data-requirements-limits-custom-event-data/#reserved-words).
@@ -153,8 +153,8 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in PHP agent version 4.18 or higher. To send custom events, simply call the relevant API function. For example:
 
-    ```
-    newrelic_record_custom_event("<var>WidgetSale</var>", array("<var>color</var>"=>"<var>red</var>", "<var>weight</var>"=><var>12.5</var>));
+    ```php
+    newrelic_record_custom_event("WidgetSale", array("color"=>"red", "weight"=>12.5));
     ```
 
     The first argument defines the name of your event type, and the second argument is an array with the attributes for your custom event. Ensure you limit the number of unique event type names that you create, and do not generate these names dynamically. For restrictions on event type names, see our documentation about [limits and restricted characters](/docs/telemetry-data-platform/custom-data/custom-events/data-requirements-limits-custom-event-data) and [NRQL reserved words](/docs/insights/event-data-sources/custom-events/data-requirements-limits-custom-event-data/#reserved-words).
@@ -173,8 +173,8 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in Python agent version 2.60.0.46 or higher. To send custom events, simply call the relevant API. For example:
 
-    ```
-    newrelic.agent.<mark>record_custom_event</mark>(event_type, params, application=None)
+    ```python
+    newrelic.agent.record_custom_event(event_type, params, application=None)
     ```
 
     The `event_type` defines the name (or type) of the custom event. Attributes of the custom event should be passed in as a dictionary via the `params` keyword argument. Ensure you limit the number of unique event type names that you create, and do not generate these names dynamically. For limits and restrictions on `event_type` and `params`, see our documentation about [limits and restricted characters](/docs/telemetry-data-platform/custom-data/custom-events/apm-report-custom-events-attributes/) and [reserved words](/docs/insights/event-data-sources/custom-events/data-requirements-limits-custom-event-data/#reserved-words)
@@ -193,8 +193,8 @@ When creating your own custom events and attributes, follow data requirements fo
   >
     Custom event collection is enabled by default in Ruby agent version 3.9.8.273 or higher. To send custom events, simply call the relevant API. For example:
 
-    ```
-    ::NewRelic::Agent.record_custom_event('<var>WidgetSale</var>', <var>color</var>: '<var>red</var>', <var>weight</var>: <var>12.5</var>)
+    ```ruby
+    ::NewRelic::Agent.record_custom_event('WidgetSale', color: 'red', weight: 12.5)
     ```
 
     The first argument defines the name of your event type, and the second argument is a hash with the attributes for your custom event. Ensure you limit the number of unique event type names that you create, and do not generate these names dynamically. For restrictions on event type names, see our documentation about [limits and restricted characters](/docs/telemetry-data-platform/custom-data/custom-events/data-requirements-limits-custom-event-data) and [NRQL reserved words](/docs/insights/event-data-sources/custom-events/data-requirements-limits-custom-event-data/#reserved-words).
@@ -204,7 +204,7 @@ When creating your own custom events and attributes, follow data requirements fo
     1. Add [`custom_insights_events.max_samples_stored:`](/docs/agents/ruby-agent/installation-configuration/ruby-agent-configuration#custom_insights_events.max_samples_stored) to your configuration file.
     2. Specify the maximum number of events to record per minute as an integer. For example, if you want to be able to send up to 5000 events per minute, add:
 
-       ```
+       ```yml
        custom_insights_events.max_samples_stored: 5000
        ```
 

src/content/docs/data-apis/manage-data/calculate-data-ingest.mdx

@@ -0,0 +1,14 @@
+---
+subject: Node.js agent
+releaseDate: '2022-07-27'
+version: 8.17.0
+downloadLink: 'https://www.npmjs.com/package/newrelic'
+---
+
+## Notes
+
+* Added [gRPC server instrumentation](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration#grpc_server).
+
+### Support statement:
+
+* New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach [end-of-life](/docs/using-new-relic/cross-product-functions/install-configure/notification-changes-new-relic-saas-features-distributed-software).