Merge branch 'develop' into translations-eb9c1df

gatsby-config.js

@@ -361,53 +361,6 @@ module.exports = {
         nodesPerFeedFile: Infinity,
       },
     },
-    {
-      resolve: `gatsby-plugin-generate-json`,
-      options: {
-        query: `
-        {
-          allMdx(filter: {fields: {slug: {regex: "/docs/release-notes/"}}}) {
-            nodes {
-              frontmatter {
-                subject
-                releaseDate(fromNow: false)
-                downloadLink
-                version
-                features
-                bugs
-                security
-              }
-              excerpt(pruneLength: 5000)
-              slug
-            }
-          }
-        }
-        `,
-        path: '/api/agent-release-notes.json',
-        serialize: ({ data }) =>
-          data.allMdx.nodes
-            .map(({ frontmatter, excerpt, slug }) => {
-              const releaseNote = {
-                agent: getAgentName(frontmatter.subject),
-                date: frontmatter.releaseDate,
-                downloadLink: frontmatter.downloadLink,
-                version: frontmatter.version,
-                features: frontmatter.features,
-                bugs: frontmatter.bugs,
-                security: frontmatter.security,
-                description: excerpt,
-                slug: slug,
-              };
-
-              if (releaseNote.date) {
-                releaseNote.eolDate = getEOLDate(releaseNote.date);
-              }
-
-              return releaseNote;
-            })
-            .filter(({ date, agent }) => Boolean(date && agent)),
-      },
-    },
     'gatsby-plugin-release-note-rss',
     'gatsby-plugin-whats-new-rss',
     'gatsby-plugin-security-bulletins-rss',

src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx

@@ -72,12 +72,10 @@ Here are details about the configuration methods shown in the diagram, and their
 
       <td>
         Configuration settings set in these files take highest precedence.
-
-        However, if the agent is disabled in the local or global newrelic.config, the NewRelic.AgentEnabled settings in these files will be ignored.
 
-        If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in an `appsettings.json` these files **will enable the agent**.
-
-        However, if the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in a `web.config` or `app.config` **will be ignored**.
+        If the agent is disabled in the local or global `newrelic.config`: 
+            * The `NewRelic.AgentEnabled` settings in `appsettings.json` **will enable the agent**.
+            * The `NewRelic.AgentEnabled` settings in a `web.config` or `app.config` file **will be ignored**.
 
       </td>
     </tr>
@@ -3419,7 +3417,7 @@ For ASP.NET and .NET Framework console apps you can also configure the following
     ```
 
     <Callout variant="important">
-      If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in these files will enable the agent.
+      If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in these files will **not** enable the agent.
     </Callout>
   </Collapser>
 

src/content/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent.mdx

@@ -152,7 +152,7 @@ To add a new configuration file for the log forwarding feature:
    * Linux: `/etc/newrelic-infra/logging.d/`
    * Windows: `C:\Program Files\New Relic\newrelic-infra\logging.d\`
 
-2. Create a `logging.yml` configuration file, and add the parameters you need. The `logging.d` directory has various `.yml.example` files you can use as a reference or starting point.
+2. Create a `logging.yml` configuration file, and add the parameters you need. The `logging.d` directory has various `.yml.example` files you can use as a reference or starting point. For Windows examples, see [our Github repo](https://github.com/newrelic/infrastructure-agent/tree/master/assets/examples/logging/windows).
 
   ```yml
   # Log forwarder configuration file example

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/view-your-data/opentelemetry-database-page.mdx

@@ -10,7 +10,7 @@ metaDescription: Here are some tips for understanding the OpenTelemetry database
 After you've sent us your OpenTelemetry data and opened your service (entity) in the UI, click **Databases** to learn about the performance of the database queries your service is making. You can see which database calls (e.g., `SELECT` operation on the `ads` table) are taking the most time in total or on average, or have the most throughput. Then you can investigate performance of an individual call and find traces that involve it.
 
 ## Required attributes
-With OpenTelemetry, we rely on [`SpanKind`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind) and the presence of the `db.system` attribute to identify spans representing client usage of a database.
+With OpenTelemetry, we rely on [`SpanKind`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind) and the presence of the [`db.system`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md) attribute to identify spans representing client usage of a database.
 
 For your OpenTelemetry data to appear in the **Databases** page, make sure it has the following attributes, in accordance with the OTel semantic conventions:
 

src/content/docs/new-relic-solutions/new-relic-one/workloads/use-workloads.mdx

@@ -147,29 +147,9 @@ Below are more details about some aspects of how to define workloads:
     id="add-dashboards"
     title="Add dashboards to workloads"
   >
-    If you have [custom dashboards](/docs/dashboards/new-relic-one-dashboards/get-started/introduction-new-relic-one-dashboards) and you already know which data is relevant to your team for observing and operating their workloads, you can link those <InlinePopover type="dashboards" /> from your workload. You can also set filters on dashboards to scope them to a workload-specific context. When a user selects that dashboard from the workload, it opens with the filter already applied.
+If you have [custom dashboards](/docs/dashboards/new-relic-one-dashboards/get-started/introduction-new-relic-one-dashboards) and you already know which data is relevant to your team for observing and operating their workloads, you can link those <InlinePopover type="dashboards" /> from your workload.
 
-    <img
-      title="new-relic-workloads-add-dashboards.png"
-      alt="New Relic workloads - add dashboards"
-      src={workloadsWorkloadsDashboardEntities}
-    />
-
-    <figcaption>
-      **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Apps > Workloads**: You can add dashboards to a workload.
-    </figcaption>
-
-To add <InlinePopover type="dashboards" /> to a workload:
-
-1. When creating or editing a workload, type `Dashboard` in the workload search bar to filter to dashboard entities.
-2. Add other search terms to filter to specific dashboards.
-3. Click **Add**.
-
-To filter a workload’s dashboard:
-
-1. From a workload’s **Overview** page, select a dashboard.
-2. Add search terms to filter the dashboard to a view that’s relevant for that workload.
-3. Select **Save filter for this workload**.
+To add <InlinePopover type="dashboards" /> to a workload: After you've created a workload, go to the **Activity** page for a workload and click **Add dashboard**.
   </Collapser>
 </CollapserGroup>
 
@@ -185,9 +165,8 @@ You can view a topological map that displays how your workloads relate to and af
 
 To access workloads maps:
 
-1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities)**, then select **All capabilities**.
-2. Click the **Workloads** tile.
-3. In the top pane, click **Maps**. 
+1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Workloads** and select a workload.
+2. Click **Map**.
 
 To learn more about our omnimap-powered maps capabilities, see [Maps in context](/docs/new-relic-solutions/new-relic-one/ui-data/maps-in-context). 
 

src/content/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions.mdx

@@ -1778,11 +1778,11 @@ SELECT histogram(duration, 10, 20) FROM PageView SINCE 1 week ago
 
     It takes three arguments:
 
-    * Attribute name
-    * Maximum value of the sample range. Any outliers will appear in the final bucket.
-    * Total number of buckets
+      * Attribute name
+      * Maximum value of the sample range (any outliers will appear in the final bucket)
+      * Total number of buckets
 
-      For more information and examples, see [Split your data into buckets](/docs/insights/nrql-new-relic-query-language/nrql-query-examples/segment-your-insights-data-buckets).
+    For more information and examples, see [Split your data into buckets](/docs/insights/nrql-new-relic-query-language/nrql-query-examples/segment-your-insights-data-buckets).
   </Collapser>
 
   <Collapser
@@ -1864,7 +1864,7 @@ SELECT histogram(duration, 10, 20) FROM PageView SINCE 1 week ago
       FROM Metric SELECT count(node_filesystem_size) TIMESERIES FACET dimensions()
       ```
 
-      When used with a `FACET` clause, `dimensions()` produces a unique timeseries for all facets available on the event type, similar to how Prometheus behaves with non-aggregated queries.
+    When used with a `FACET` clause, `dimensions()` produces a unique timeseries for all facets available on the event type, similar to how Prometheus behaves with non-aggregated queries.
   </Collapser>
 
   <Collapser
@@ -2082,7 +2082,7 @@ SELECT histogram(duration, 10, 20) FROM PageView SINCE 1 week ago
     * Use [`TIMESERIES`](#sel-timeseries) to generate a line chart with rates mapped over time.
     * Omit [`TIMESERIES`](#sel-timeseries) to generate a billboard showing a single rate value averaged over time.
 
-      Here's a basic query that will generate a line chart showing the rate of throughput for <InlinePopover type="apm" /> transactions per 10 minutes over the past 6 hours:
+    Here's a basic query that will generate a line chart showing the rate of throughput for <InlinePopover type="apm" /> transactions per 10 minutes over the past 6 hours:
 
       ```sql
       SELECT rate(count(*), 10 minute) FROM Transaction SINCE 6 hours ago
@@ -2324,8 +2324,9 @@ Note: `aparse()` is case-insensitive.
     Use `capture()` to extract values from an attribute using a regular expression with [RE2 syntax](https://github.com/google/re2/wiki/Syntax).
 
     It takes two arguments:
-    * Attribute name.
-    * Regular expression with capture syntax. Regex expressions in NRQL use Python-like syntax, `r'...'`.
+
+      * Attribute name
+      * Regular expression with capture syntax (regex expressions in NRQL use Python-like syntax, `r'...'`)
 
     When capturing, use the RE2 named-capture syntax `...(?P<name> pattern )...` to capture the contained pattern, given the specified name.
 

src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/nrql-segment-your-data-buckets.mdx

@@ -17,9 +17,19 @@ import queriesnrqlFacetbyBucketsNRQLQueryBuilder from 'images/queries-nrql_scree
 
 Using [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql), you can split your query results into buckets that cover certain ranges using the [`buckets` function](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-buckets).
 
+## Why use bucketed results? [#overview]
+
+You can use the `FACET buckets()` function to group and categorize data into buckets based on specified ranges, such as for creating histograms or frequency distributions. Use it in combination with aggregating functions like [`count()`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-count) or [`sum()`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-sum) to analyze data distribution across different ranges.
+
+Here are some use cases:
+* Analyzing response times: You can use `FACET buckets()` to group response times into ranges (for example, 0-100ms, 100-200ms, 200-300ms) and calculate the count or average response time within each range. This allows you to understand the distribution of response times and identify performance issues.
+* Examining request sizes: By using `FACET buckets()` on request sizes, you can categorize the size of requests into different buckets (for example, 0-1KB, 1-5KB, 5-10KB) and analyze the frequency of requests falling within each bucket. This can help you identify patterns and optimize resource allocation.
+* Monitoring error rates: You can use `FACET buckets()` on error codes or error rates to group them into specific ranges. For example, you could create buckets for different HTTP error codes (like 400, 500, and others) or error rate ranges (for example, 0-1%, or 1-5%). This allows you to track your error distribution and identify areas requiring attention.
+* Tracking user engagement: If you have a metric related to user engagement, such as session durations or page views, you can use `FACET buckets()` to group them into time intervals. This lets you analyze how users engage with your application or website across different time ranges.
+
 ## Create bucketed NRQL query [#segmentation]
 
-To return bucketed results, use the `FACET buckets()` clause in a NRQL query. A bucketing query has this structure:
+To return bucketed results, use the `FACET buckets()` clause in a NRQL query. A bucketed query has this structure:
 
 ```
 SELECT FUNCTION(ATTRIBUTE) 

src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests-legacy.mdx

@@ -17,7 +17,7 @@ Use synthetic monitoring's [API tests](/docs/synthetics/new-relic-synthetics/get
 Here we present some example functions showing how to use the `$http` object to submit your request. For detailed documentation on the options available for this object, see the [http-request readme](https://github.com/request/request). (Note that Request is deprecated, but these options still apply.)
 
 <Callout variant="tip">
-  To view and share other API test examples, visit the [synthetics scripts](https://discuss.newrelic.com/tags/c/full-stack-observability/synthetic/81/script) section in Support Forum or the [Synthetic Monitoring Quickstarts Library](https://newrelic.github.io/quickstarts-synthetics-library/#/).
+  To view and share other API test examples, visit the [Support Forum synthetics scripts section](https://forum.newrelic.com/s/?c__tags=%5B%7B%22id%22%3A%22a9P8W0000004KS5UAM%22%2C%22sObjectType%22%3A%22Tag__c%22%2C%22subtitle%22%3A%22%22%2C%22title%22%3A%22syntheticsscript%22%2C%22titleFormatted%22%3A%22synthetics%3Cstrong%3Escript%3C%2Fstrong%3E%22%2C%22subtitleFormatted%22%3A%22%22%2C%22icon%22%3A%22standard%3Adefault%22%7D%5D) or the [Synthetic monitoring quickstarts library](https://newrelic.github.io/quickstarts-synthetics-library/#/).
 </Callout>
 
 ## Use API http-request module [#overview]

src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows.mdx

@@ -222,7 +222,7 @@ translationType: machine
 7. 通知する1つまたは複数の送信先を選択し、任意のメッセージを追加します。
 
    <Callout variant="tip">
-     任意のデスティネーションチャンネルで、タイプを開始すると、変数メニューが開きます。変数の名前が表示され、実行時にはその変数の値に置き換えられます。エンリッチメントの結果を使うには、その名前を使います。
+     任意の宛先チャンネルで入力を開始すると、変数メニューが開きます。 [変数](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows)の名前が表示されます。これは実行時に変数の値に置き換えられます。エンリッチャーの結果を使用するには、その名前を使用します。
    </Callout>
 
    <CollapserGroup>
@@ -250,30 +250,36 @@ translationType: machine
   追加できるワークフロー数の初期制限はアカウントあたり 1000 で、フィルター サイズの初期制限はワークフローあたり 4096 文字です。この数を増やしたい場合は、アカウント担当者にお問い合わせください。
 </Callout>
 
-## 問題通知ログ [#issue-notification-log]
+## 発行通知ログ [#issue-notification-log]
 
-問題通知ログは、ワークフローによって生成されたすべての通知を追跡するための詳細な記録をユーザーに提供します。この情報は、問題のトラブルシューティング、ワークフロー パフォーマンスの監視、および通知が正しい宛先に送信されていることを確認します。その結果、ユーザーは、発生する可能性のある問題をすばやく特定し、必要に応じて是正措置を講じることができます。
+問題通知ログは、ワークフローによって生成されたすべての通知を追跡するための詳細な記録をユーザーに提供します。この情報により、問題のトラブルシューティングが行われ、ワークフローのパフォーマンスが監視され、通知が正しい宛先に送信されていることを確認できます。その結果、ユーザーは発生する可能性のある問題を迅速に特定し、必要に応じて修正措置を講じることができます。
 
-問題通知ログにアクセスするには、 **[one.newrelic.com > Alerts & AI > Workflows](https://one.newrelic.com/alerts-ai/workflows)**に移動し、 **Issue Notification Log**をクリックします。
+問題通知ログにアクセスするには、 **[one.newrelic.com > Alerts & AI > Workflows](https://one.newrelic.com/alerts-ai/workflows)**に移動し、 **Issue notification log**をクリックします。
 
-### 問題通知ログのナビゲート [#navigate-notification-log]
+### 問題通知ログの移動 [#navigate-notification-log]
 
 問題通知ログには、次の列が表示されます。
 
 1. **時刻:** この列には、ワークフロー通知が送信された時刻が表示されます。
+
 2. **ステータス:** この列には、通知のステータスが表示されます。
 
-* 送信済み: New Relic から通知が正常に送信されました。
-* 失敗: 通知は New Relic から正常に送信されませんでした。
-* Deferred: 通知は New Relic から正常に送信されましたが、ベンダーによって削除されました。
+   * 送信済み: New Relic から通知が正常に送信されました。
+   * 失敗: 通知は New Relic から正常に送信されませんでした。
+   * Deferred: 通知は New Relic から正常に送信されましたが、ベンダーによって削除されました。
 
 3. **送信先:** この列には、ワークフロー通知を受信する送信先の種類 (Slack や電子メールなど) が表示されます。
+
 4. **問題名:** この列には、ワークフロー通知をトリガーした問題の名前が表示されます。
+
 5. **トリガー イベント:** この列には、ワークフロー通知をトリガーした課題イベントが表示されます。イベントをクリックすると、ワークフローがどのようにトリガーされるかについての詳細が表示されます。
+
 6. **ワークフロー:** この列には、通知をトリガーしたワークフローが表示されます。
+
 7. **エラーの詳細:** この列には、通知が失敗した場合の追加の詳細が表示されます。
+
 8. **通知結果:** 通知が正常に送信された場合、この列にはサード パーティ (Slack スレッドや JIRA チケットなど) の証拠へのリンクが表示されます。
 
 ### 詳細を表示 [#view-details]
 
-問題通知ログの任意の行をクリックすると、追加の詳細を表示できます。これにより、エラーの詳細 (該当する場合) とサードパーティの通知へのリンクが表示されます。
+ユーザーは、問題通知ログの任意の行をクリックすると、追加の詳細を表示できます。これにより、エラーの詳細 (該当する場合) とサードパーティの通知へのリンクが表示されます。

src/i18n/content/jp/docs/apm/agents/java-agent/getting-started/java-agent-eol-policy.mdx

@@ -28,6 +28,20 @@ translationType: machine
   </thead>
 
   <tbody>
+    <tr>
+      <td>
+        v8.3.0
+      </td>
+
+      <td>
+        2023 年 6 月 1 日
+      </td>
+
+      <td>
+        2024 年 6 月 1 日
+      </td>
+    </tr>
+
     <tr>
       <td>
         v8.2.0