daily-release/Jul-25-2023-3_05

scripts/actions/check-job-progress.js

@@ -204,9 +204,14 @@ const updateTranslationRecords = async (project_id, slugStatuses) => {
         { status: StatusEnum.COMPLETED }
       );
 
-      console.log(
-        `Translation ${records[0].id} marked as ${StatusEnum.COMPLETED}`
-      );
+      const id = records[0]?.id;
+
+      if (id == null) {
+        console.log(`Unable to update ${locale} translation for slug ${slug}`);
+        process.exitCode = 1;
+      } else {
+        console.log(`Translation ${id} marked as ${StatusEnum.COMPLETED}`);
+      }
     })
   );
 };

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

@@ -96,7 +96,7 @@ Most New Relic organization have the ability to add core users. This section inc
 Here are some rules for querying your users:
 
 * Use only the `NrMTDConsumption` event.
-* The attributes used to query by user type are: `BasicUsersBillable`, `CoreUsersBillable`, and `FullPlatformUsersBillable`.
+* The attributes used for querying users are `CoreUsersBillable` and `FullPlatformUsersBillable`.
 
 Here are some example NRQL queries for determining user count:
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks.mdx

@@ -83,7 +83,9 @@ Here are some user management tasks you might want to do:
   >
 There are a couple ways to add users: 
 
-* **Add users**: Go to the [**User management** UI](#where) and select **Add user**. Note that adding users directly to New Relic means users with a billable user type are immediately billable, regardless of whether those users are `Pending` and haven't yet logged into New Relic.  
+* **Add users**: Go to the [**User management** UI](#where) and select **Add user**. Details on adding users: 
+  * Adding users directly means users with a billable user type are immediately billable, even if they've never logged into New Relic and are `Pending`.
+  * Added users receive a verification email, which expires after 15 days. To resend it: in the user management UI, hover over a user's `Pending` icon and click `Resend email`. 
 * **Invite users**: Go to the [user menu](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings) and click **Add user**. Details on inviting users: 
   * If you have [**Authentication domain** permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings), this takes you to the **Add users** UI, where you can add users directly. 
   * If you don't have that permission, you can invite a teammate. This requests review by an admin of that user being added to New Relic. Pending invites that haven't been reviewed are found on the **Invites needing approval** tab of the **User management** page. When an admin reviews an invited user, they complete the **Add user** workflow and that user is then considered provisioned in New Relic.  

src/content/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export.mdx

@@ -30,11 +30,7 @@ If you'd like higher limits, talk to your account representative.
 
 ### Data type restrictions [#data-type-restrictions]
 
-Some [data types](/docs/data-apis/understand-data/new-relic-data-types) are **not** available for export:
-
-* Metric timeslice data
-* Dimensional metrics (the `Metric` data type)
-* Infrastructure events `SystemSample`, `ProcessSample`, `StorageSample`, `NetworkSample`, `ContainerSample`
+[Metric timeslice data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data) is not available for export. 
 
 ### Time range restrictions [#time-range-restrictions]
 

src/content/docs/data-apis/custom-data/explore-public-api-performance-dashboard.mdx

@@ -0,0 +1,74 @@
+---
+title: Explore the Public API Performance dashboard
+tags:
+    - Query your data
+    - Explore and query data
+    - Dashboards
+translate:
+    - jp
+metaDescription: 'How to access the New Relic Public API Performance dashboard.'
+redirects:
+    - /docs/query-your-data/new-relic-one-dashboards/global-performance-dataset/enable-public-api-performance-dashboard
+    - /docs/query-your-data/new-relic-one-dashboards/global-performance-dataset/explore-public-api-performance-dashboard
+---
+
+import publicApiPerformanceDashForGpd from 'images/dashboards_screenshot-full_public-API-perform-gpd.webp'
+
+The Public API Performance dashboard is an out-of-the-box dashboard included as part of your New Relic account. It provides both actionable general insights about the performance of public APIs and an opportunity for new customers to test-drive our dashboarding capabilities before adding their own data.
+
+The dashboard works by showing real latencies experienced by an anonymized sampling of New Relic customers when accessing popular public APIs.
+
+<Callout variant="important">
+  Global Performance data sets are presented as-is. Global Performance data sets represent an aggregate of samples across a range of sources, and New Relic makes no effort to attempt to confirm the correctness, completeness, or veracity of the data. This data should not be relied on as the sole source of information for any purpose you may use it, and New Relic is not responsible for decisions made in reliance on this data. Global Performance data sets should not be viewed as either an endorsement or a recommendation by New Relic of the technologies represented in the data sets.
+</Callout>
+
+## Add the dashboard in New Relic [#Add-dashboard]
+
+To add the Public API Performance dashboard:
+
+1. From the dashboards page, search for the Public API Performance pre-built dashboard. You can click the **View All** link next to the popular pre-built dashboards title to search it.
+2. Select the dashboard.
+3. Select an account from the dropdown.
+4. Click **View dashboard** to add it to your account.
+
+<img
+    title="Public API Performance dashboard"
+    alt="View of the Public API Performance dashboard screen."
+    src={publicApiPerformanceDashForGpd}
+/>
+
+<figcaption>
+    Public API Performance dashboard
+</figcaption>
+
+## Explore the dashboard [#explore-dashboard]
+
+You can customize your new pre-built dashboard. You can change the name and settings, add new content and new widgets, refine the charts, and more! See [Manage your dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) for more info.
+
+Below are some suggestions for how to explore the Public API Performance dashboard.
+
+* Click  the <Icon name="fe-more-horizontal"/> icon on the right corner of any of the charts and select **View query** to view the [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) query used to create the chart.
+* Click  the <Icon name="fe-more-horizontal"/> icon on the right corner of any of the charts and select **Get as image** to view or download any chart as an image.
+* Select specific domains from the bar chart or add a filter by clicking the text field along the at the top of the page.
+* If you've already added your own data, experiment with copying queries and modifying them for your own use.
+
+<Callout variant="important">
+    The Public API Performance dashboard is not currently available to EU customers.
+</Callout>
+
+<Callout variant="important">
+    The Public API Performance dashboard doesn't currently support alerts.
+</Callout>
+
+## Data reported [#data-reported]
+
+We make public API data available to all New Relic organizations via the `Public_APICall` event. This data doesn't count towards your ingest. If you want to see the structure of that data, run this query:
+
+```sql
+FROM Public_APICall select keyset()
+```
+
+## More about dashboards and data [#explore-dashboard]
+
+* For more information about New Relic dashboards, see our [dashboards introduction](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+* Customers can also dive into this data set in greater depth using our [data explorer](/docs/query-your-data/explore-query-data/browse-data/introduction-data-explorer/).

src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx

@@ -56,12 +56,12 @@ The `eventType` field must use `NrAiIncidentExternal`.
 
 Here's an example of how to use curl to send your JSON payload.
 
-```
+```bash
 gzip -c example_incidents.json | curl --data-binary @- -X POST -H "Content-Type: application/json" -H "Api-Key: YOUR_LICENSE_KEY" -H "Content-Encoding: gzip"
 https://insights-collector.newrelic.com/v1/accounts/YOUR_ACCOUNT/events
 ```
 
-```
+```json
 Response
 {"success":true, "uuid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}%
 ```
@@ -74,7 +74,7 @@ You can query your data with [Nerdgraph API](/docs/apis/nerdgraph/get-started/in
 
 Here's an example of a NerdGraph query and its result.
 
-```json
+```graphql
 {
   actor {
     account(id: YOUR_ACCOUNT_ID) {
@@ -175,7 +175,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       <td>
         `state`
 
-        _enum: (trigger, resolve)_
+        _enum: (`trigger`, `resolve`)_
       </td>
 
       <td>
@@ -189,11 +189,11 @@ The incident event API uses the Event API's value types. For descriptions of the
       <td>
         `priority`
 
-        _enum: (low, medium, high, critical)_
+        _enum: (`low`, `medium`, `high`, `critical`)_
       </td>
 
       <td>
-        The incident's priority. Default: _high_.
+        The incident's priority. Default: `high`.
 
         Highest priority will be used when different priorities are sent.
       </td>
@@ -207,7 +207,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       </td>
 
       <td>
-        **REQUIRED, when `state` is _trigger_**
+        **REQUIRED, when `state` is `trigger`**
 
         The triggering event's title.
       </td>
@@ -221,7 +221,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       </td>
 
       <td>
-        **REQUIRED, when `state` is _trigger_**
+        **REQUIRED, when `state` is `trigger`**
 
         The origin of the incident, or the monitoring system that triggered it (not the entity that faulted).
       </td>

src/content/docs/data-apis/ingest-apis/event-api/introduction-event-api.mdx

@@ -232,19 +232,19 @@ The Event API accepts specific formats for attributes included in the payload. O
   >
     Here is an example of a typical JSON data set for sending with the API. This call sends two **Purchase** type events as a JSON array. You can add multiple events in a single HTTP call using a JSON array.
 
-    ```
+    ```json
     [
-      {
-        "eventType":"Purchase",
-        "account":3,
-        "amount":259.54
-      },
-      {
-        "eventType":"Purchase",
-        "account":5,
-        "amount":12309,
-        "product":"Item"
-      }
+        {
+            "eventType": "Purchase",
+            "account": 3,
+            "amount": 259.54
+        },
+        {
+            "eventType": "Purchase",
+            "account": 5,
+            "amount": 12309,
+            "product": "Item"
+        }
     ]
     ```
 
@@ -283,7 +283,7 @@ Data submitted to the Event API uses a compressed JSON format in a simple HTTPS
     id="numberone"
     title="Linux/bash example"
   >
-    ```
+    ```bash
     gzip -c example_events.json | curl -X POST -H "Content-Type: application/json"
     -H "Api-Key: YOUR_LICENSE_KEY" -H "Content-Encoding: gzip"
     https://insights-collector.newrelic.com/v1/accounts/YOUR_ACCOUNT_ID/events --data-binary @-
@@ -294,7 +294,7 @@ Data submitted to the Event API uses a compressed JSON format in a simple HTTPS
     id="numbertwo"
     title="Windows/PowerShell example"
   >
-    ```
+    ```powershell
     $accountId = "YOUR_ACCOUNT_ID"
     $insertkey = "YOUR_LICENSE_KEY"
     # Replace with your custom event for the body
@@ -373,7 +373,7 @@ Other potential issues:
           </td>
 
           <td>
-            ```
+            ```json
             {"success":true,"uuid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}
             ```
           </td>
@@ -592,7 +592,7 @@ Other potential issues:
 
 The [`NrIntegrationError` event](/docs/telemetry-data-platform/manage-data/nrintegrationerror) allows you to query and set alerts on custom data being sent to your New Relic account. **Recommendation:** To get alerts for parsing errors, [create a NRQL alert condition](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) for `NrIntegrationError`. Use this example NRQL query:
 
-```
+```sql
 SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND category = 'EventApiException'
 ```
 
@@ -654,7 +654,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Category`
+        `category`
       </td>
 
       <td>
@@ -664,7 +664,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Message`
+        `message`
       </td>
 
       <td>
@@ -674,7 +674,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Name`
+        `name`
       </td>
 
       <td>
@@ -698,7 +698,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
 To find data sent via the Event API (and from integrations that use this API), you can query it. For example, to query a custom event using [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql), you would run:
 
-```
+```sql
 SELECT * FROM YOUR_CUSTOM_EVENT
 ```
 

src/content/docs/data-apis/ingest-apis/gateway-api-import-data-other-observability-platforms.mdx

@@ -28,7 +28,7 @@ Here's an overview of the steps for enabling the Gateway API for DataDog:
 1. For DataDog: Our account representatives will work with you to map your Datadog API keys to New Relic keys.
 2. For each agent configuration file, point the data to `https://gateway.service.newrelic.com`. An example for DataDog: in the agent’s `datadog.yaml` file, you’d change these settings:
 
-   ```
+   ```yml
    dd_url: https://gateway.service.newrelic.com
    logs_config:
        logs_dd_url:  https://gateway.service.newrelic.com
@@ -48,4 +48,4 @@ Telemetry data brought in from third-party platforms doesn't map perfectly to ou
 
 <Callout variant="tip">
 Interested in unifying your data observability into a single platform? See our [guide on migrating from Datadog](/docs/journey-migration/migrating-from-dd/) to try it out for free.
-</Callout>
+</Callout>