From a7cb62ba9035a50241fb53d62fa33c7c6fd24f31 Mon Sep 17 00:00:00 2001 From: nr-opensource-bot Date: Fri, 14 Jul 2023 12:03:47 +0000 Subject: [PATCH] chore: add translations --- .../custom-variables-incident-workflows.mdx | 2 +- .../browser-monitoring-config-nerdgraph.mdx | 2 +- .../kafka/kafka-integration.mdx | 2 +- .../lampy-integration.mdx | 13 +++++----- .../migrating-dashboards.mdx | 2 +- .../autoscale-your-infra.mdx | 24 +++++++++---------- .../custom-variables-incident-workflows.mdx | 2 +- .../browser-monitoring-config-nerdgraph.mdx | 2 +- .../kafka/kafka-integration.mdx | 2 +- .../lampy-integration.mdx | 13 +++++----- .../migrating-dashboards.mdx | 2 +- .../autoscale-your-infra.mdx | 24 +++++++++---------- 12 files changed, 44 insertions(+), 46 deletions(-) diff --git a/src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx b/src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx index 938a8ed4596..7862c8b5cea 100644 --- a/src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx +++ b/src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx @@ -434,7 +434,7 @@ New Relic の応用インテリジェンス [ワークフロー](/docs/alerts-ap - New Relic の応用インテリジェンス機械学習が提案するレスポンダーのリスト。 + (非推奨) New Relic 応用インテリジェンス機械学習が提案するレスポンダーのリスト。 diff --git a/src/i18n/content/jp/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx b/src/i18n/content/jp/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx index b9588d8ebd4..fa85048928a 100644 --- a/src/i18n/content/jp/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx +++ b/src/i18n/content/jp/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx @@ -192,7 +192,7 @@ mutation UpdateBrowserSettingsExample($guid: EntityGuid!, settings: AgentApplica ## アプリケーション構成を取得する [#retrieve-app-config] -[npm パッケージのインストール方法](/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent)で使用するブラウザー アプリケーションの構成を取得できます。必要に応じて、構成を 2 つの異なる形式で返すことができます。Web ページの `head` 要素に挿入する JSON エンコード文字列と、アプリケーション ソース コードでそのまま使用できるオブジェクトです。 +[npm パッケージのインストール方法](https://www.npmjs.com/package/@newrelic/browser-agent)で使用するブラウザ アプリケーション構成を取得できます。ニーズに応じて、構成は 2 つの異なる形式で返すことができます。Web ページの `head` 要素に挿入するための JSON エンコード文字列と、アプリケーションのソース コードでそのまま使用できるオブジェクトです。 クエリ: diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx index 9b15142012c..9cd2090b4cf 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx @@ -268,7 +268,7 @@ Kafkaに関連する特定の設定は、 `kafka-config.yml`構成ファイル これらの設定の値は、いくつかの方法で定義できます。 * 設定ファイルに直接値を追加します。これが最も一般的な方法です。 -* `{{ }}`表記を使用して環境変数の値を置き換えます。 [オンホスト統合での環境変数パススルーの使用](/docs/infrastructure/install-infrastructure-agent/configuration/configure-infrastructure-agent/#passthrough)の詳細を読むか、 [環境変数の置換](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration#envvar-replacement)の例を参照してください。 これには、インフラストラクチャエージェントv1.14.0以降が必要です。 +* `{{ }}` 表記を使用して環境変数の値を置き換えます。 [オンホスト統合での環境変数パススルーの使用](/docs/infrastructure/install-infrastructure-agent/configuration/configure-infrastructure-agent/#passthrough) について詳しく読むか、 [環境変数の置換](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration#envvar-replacement)の例を参照してください。 * シークレット管理の使用。これを使用して、設定ファイルのプレーンテキストで公開されないようにパスワードなどの重要な情報を保護してください。詳細については、[シークレット管理](/docs/integrations/host-integrations/installation/secrets-management)を参照してください。 ### オフセット監視 diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx index 323f1b6c5e8..fbb92207bca 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx @@ -60,15 +60,16 @@ import infrastructureLampyDashboard from 'images/infrastructure_screenshot-full_ 6. 次の行を `wsgi.py` ファイルに追加します。 ```py - import newrelic.agent +import newrelic.agent - from django.conf import settings - from django.core.wsgi import get_wsgi_application +from django.conf import settings +from django.core.wsgi import get_wsgi_application - application = get_wsgi_application() +application = get_wsgi_application() + +newrelic.agent.initialize(settings.NEW_RELIC_CONFIG_FILE) +newrelic.agent.WSGIApplicationWrapper(application) - newrelic.agent.initialize(settings.NEW_RELIC_CONFIG_FILE) - newrelic.agent.WSGIApplicationWrapper(application) ``` ## ステップ 5: Apache サーバーを再起動する diff --git a/src/i18n/content/jp/docs/tutorial-dd-migration/migrating-dashboards.mdx b/src/i18n/content/jp/docs/tutorial-dd-migration/migrating-dashboards.mdx index c752fd6ef5c..c3352c1d14e 100644 --- a/src/i18n/content/jp/docs/tutorial-dd-migration/migrating-dashboards.mdx +++ b/src/i18n/content/jp/docs/tutorial-dd-migration/migrating-dashboards.mdx @@ -28,7 +28,7 @@ New Relic エンティティが多数の観察データを提供できる場合 src={journeyAlertsAndDash} /> -## 最初から視覚化する (#get-go) +## 最初から視覚化する [#get-go] データの取り込みを開始するとすぐに、New Relic は追加のセットアップを行わなくてもデータの監視に役立つ視覚化の提供を自動的に開始します。弊社が生成するダッシュボードとチャートは、監視対象として選択した内容について、すぐに使用できる詳細な情報を提供します。たとえば、APM のセットアップが完了すると、すぐに以下にアクセスできるようになります。 diff --git a/src/i18n/content/jp/docs/tutorial-peak-demand/autoscale-your-infra.mdx b/src/i18n/content/jp/docs/tutorial-peak-demand/autoscale-your-infra.mdx index 59fc70a7444..6201c98e1cf 100644 --- a/src/i18n/content/jp/docs/tutorial-peak-demand/autoscale-your-infra.mdx +++ b/src/i18n/content/jp/docs/tutorial-peak-demand/autoscale-your-infra.mdx @@ -41,9 +41,9 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' Github から次のリポジトリのクローンを作成します。 - ```git - git clone https://github.com/newrelic-experimental/pixie-lab-materials - ​​cd pixie-lab-materials/main + ```bash + git clone https://github.com/newrelic-experimental/pixie-lab-materials + ​​cd pixie-lab-materials/main ./setup.sh ``` @@ -53,7 +53,7 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' 新しいターミナル ウィンドウで、minikube トンネルを開きます。 - ``` + ```bash minikube tunnel -p minikube-pixie-lab ``` @@ -80,13 +80,13 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' New Relic Metrics Adapter をインストールするには、 `newrelic-k8s-metrics-adapter` Helm チャートを使用します。 `nri-bundle-chart` を使用して New Relic Kubernetes コンポーネントをデプロイした場合は、この Helm チャートにアクセスできます。 - ``` + ```bash helm upgrade --install newrelic newrelic/nri-bundle \ - --namespace newrelic --create-namespace --reuse-values \ - --set metrics-adapter.enabled=true \ - --set newrelic-k8s-metrics-adapter.personalAPIKey=YOUR_NEW_RELIC_PERSONAL_API_KEY \ - --set newrelic-k8s-metrics-adapter.config.accountID=YOUR_NEW_RELIC_ACCOUNT_ID \ - --set newrelic-k8s-metrics-adapter.config.externalMetrics.manipulate_average_requests.query='FROM Metric SELECT average(http.server.duration) WHERE instrumentation.provider='pixie'' + --namespace newrelic --create-namespace --reuse-values \ + --set metrics-adapter.enabled=true \ + --set newrelic-k8s-metrics-adapter.personalAPIKey=YOUR_NEW_RELIC_PERSONAL_API_KEY \ + --set newrelic-k8s-metrics-adapter.config.accountID=YOUR_NEW_RELIC_ACCOUNT_ID \ + --set newrelic-k8s-metrics-adapter.config.externalMetrics.manipulate_average_requests.query="FROM Metric SELECT average(http.server.duration) WHERE instrumentation.provider='pixie'" ``` これらのフラグの機能は次のとおりです。 @@ -142,11 +142,9 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' 次のコマンドを実行して、新しい YAML ファイルを適用します。 - ``` - + ```bash cd pixie-lab-materials/main/kube kubectl apply -f hpa.yaml - ``` diff --git a/src/i18n/content/kr/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx b/src/i18n/content/kr/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx index 5409beeef80..3db80d7044e 100644 --- a/src/i18n/content/kr/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx +++ b/src/i18n/content/kr/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/custom-variables-incident-workflows.mdx @@ -434,7 +434,7 @@ New Relic 응용 인텔리전스 [워크플로](/docs/alerts-applied-intelligenc - New Relic 응용 지능 기계 학습 제안 응답자 목록입니다. + (더 이상 사용되지 않음) New Relic 응용 인텔리전스 머신 러닝이 제안한 대응자 목록입니다. diff --git a/src/i18n/content/kr/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx b/src/i18n/content/kr/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx index 0791c832210..3e2b56939c7 100644 --- a/src/i18n/content/kr/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx +++ b/src/i18n/content/kr/docs/apis/nerdgraph/examples/browser-monitoring-config-nerdgraph.mdx @@ -192,7 +192,7 @@ mutation UpdateBrowserSettingsExample($guid: EntityGuid!, settings: AgentApplica ## 애플리케이션 구성 검색 [#retrieve-app-config] -[npm 패키지 설치 방법](/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent)과 함께 사용할 브라우저 애플리케이션 구성을 검색할 수 있습니다. 필요에 따라 구성은 웹페이지의 `head` 요소에 삽입하기 위한 JSON 인코딩 문자열과 애플리케이션 소스 코드에서 그대로 사용할 수 있는 객체의 두 가지 형식으로 반환될 수 있습니다. +[npm 패키지 설치 방법](https://www.npmjs.com/package/@newrelic/browser-agent)과 함께 사용할 브라우저 애플리케이션 구성을 검색할 수 있습니다. 필요에 따라 구성은 웹페이지의 `head` 요소에 삽입하기 위한 JSON 인코딩 문자열과 애플리케이션 소스 코드에서 있는 그대로 사용할 수 있는 객체의 두 가지 형식으로 반환될 수 있습니다. 질문: diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx index 7878362f186..c8fbb814328 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/kafka/kafka-integration.mdx @@ -268,7 +268,7 @@ Kafka와 관련된 특정 설정은 `kafka-config.yml` 구성 파일에 있는 이러한 설정의 값은 여러 가지 방법으로 정의할 수 있습니다. * 구성 파일에 직접 값을 추가합니다. 이것은 가장 일반적인 방법입니다. -* `{{ }}` 표기법을 사용하여 환경 변수의 값 바꾸기. [호스트 내 통합과 함께 환경 변수 패스스루 사용](/docs/infrastructure/install-infrastructure-agent/configuration/configure-infrastructure-agent/#passthrough) 에 대해 자세히 알아보거나 [환경 변수 교체](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration#envvar-replacement) 에 대한 예를 참조하십시오. 이를 위해서는 인프라 에이전트 v1.14.0 이상이 필요합니다. +* `{{ }}` 표기법을 사용하여 환경 변수의 값을 바꿉니다. [온호스트 통합과 함께 환경 변수 패스스루 사용](/docs/infrastructure/install-infrastructure-agent/configuration/configure-infrastructure-agent/#passthrough) 에 대해 자세히 알아보거나 [환경 변수 대체](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration#envvar-replacement)에 대한 예제를 참조하십시오. * 비밀 관리를 사용합니다. 이를 사용하여 구성 파일에서 일반 텍스트로 노출될 암호와 같은 민감한 정보를 보호하십시오. 자세한 내용은 [비밀 관리](/docs/integrations/host-integrations/installation/secrets-management) 를 참조하십시오. ### 오프셋 모니터링 diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx index c63869a4886..5dbda29d34f 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration.mdx @@ -60,15 +60,16 @@ import infrastructureLampyDashboard from 'images/infrastructure_screenshot-full_ 6. `wsgi.py` 파일에 다음 줄을 추가합니다. ```py - import newrelic.agent +import newrelic.agent - from django.conf import settings - from django.core.wsgi import get_wsgi_application +from django.conf import settings +from django.core.wsgi import get_wsgi_application - application = get_wsgi_application() +application = get_wsgi_application() + +newrelic.agent.initialize(settings.NEW_RELIC_CONFIG_FILE) +newrelic.agent.WSGIApplicationWrapper(application) - newrelic.agent.initialize(settings.NEW_RELIC_CONFIG_FILE) - newrelic.agent.WSGIApplicationWrapper(application) ``` ## 5단계: Apache 서버 다시 시작 diff --git a/src/i18n/content/kr/docs/tutorial-dd-migration/migrating-dashboards.mdx b/src/i18n/content/kr/docs/tutorial-dd-migration/migrating-dashboards.mdx index c66a9971bf9..d52c2c2cf25 100644 --- a/src/i18n/content/kr/docs/tutorial-dd-migration/migrating-dashboards.mdx +++ b/src/i18n/content/kr/docs/tutorial-dd-migration/migrating-dashboards.mdx @@ -28,7 +28,7 @@ New Relic 엔터티가 관찰할 수 있는 데이터 점수를 제공할 수 src={journeyAlertsAndDash} /> -## 시작부터 시각화(#get-go) +## 시작부터 시각화 [#get-go] 데이터 수집을 시작하는 즉시 New Relic은 자동으로 시각화를 제공하기 시작하여 추가 설정 없이 데이터를 모니터링할 수 있습니다. 귀하를 위해 생성되는 대시보드와 차트는 귀하가 모니터링하기로 선택한 항목에 대한 기본 세부 정보를 제공합니다. 예를 들어 APM 설정을 완료하면 즉시 다음에 액세스할 수 있습니다. diff --git a/src/i18n/content/kr/docs/tutorial-peak-demand/autoscale-your-infra.mdx b/src/i18n/content/kr/docs/tutorial-peak-demand/autoscale-your-infra.mdx index 4fca1bfa603..f220603267b 100644 --- a/src/i18n/content/kr/docs/tutorial-peak-demand/autoscale-your-infra.mdx +++ b/src/i18n/content/kr/docs/tutorial-peak-demand/autoscale-your-infra.mdx @@ -41,9 +41,9 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' Github에서 다음 리포지토리를 복제합니다. - ```git - git clone https://github.com/newrelic-experimental/pixie-lab-materials - ​​cd pixie-lab-materials/main + ```bash + git clone https://github.com/newrelic-experimental/pixie-lab-materials + ​​cd pixie-lab-materials/main ./setup.sh ``` @@ -53,7 +53,7 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' 새 터미널 창에서 minikube 터널을 엽니다. - ``` + ```bash minikube tunnel -p minikube-pixie-lab ``` @@ -80,13 +80,13 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' New Relic Metrics Adapter를 설치하려면 `newrelic-k8s-metrics-adapter` Helm 차트를 사용하세요. `nri-bundle-chart` 를 사용하여 New Relic Kubernetes 구성요소를 배포한 경우 이 Helm 차트에 액세스할 수 있습니다. - ``` + ```bash helm upgrade --install newrelic newrelic/nri-bundle \ - --namespace newrelic --create-namespace --reuse-values \ - --set metrics-adapter.enabled=true \ - --set newrelic-k8s-metrics-adapter.personalAPIKey=YOUR_NEW_RELIC_PERSONAL_API_KEY \ - --set newrelic-k8s-metrics-adapter.config.accountID=YOUR_NEW_RELIC_ACCOUNT_ID \ - --set newrelic-k8s-metrics-adapter.config.externalMetrics.manipulate_average_requests.query='FROM Metric SELECT average(http.server.duration) WHERE instrumentation.provider='pixie'' + --namespace newrelic --create-namespace --reuse-values \ + --set metrics-adapter.enabled=true \ + --set newrelic-k8s-metrics-adapter.personalAPIKey=YOUR_NEW_RELIC_PERSONAL_API_KEY \ + --set newrelic-k8s-metrics-adapter.config.accountID=YOUR_NEW_RELIC_ACCOUNT_ID \ + --set newrelic-k8s-metrics-adapter.config.externalMetrics.manipulate_average_requests.query="FROM Metric SELECT average(http.server.duration) WHERE instrumentation.provider='pixie'" ``` 이러한 플래그가 수행하는 작업은 다음과 같습니다. @@ -142,11 +142,9 @@ import kubernetesK8sHPA from 'images/kubernetes_diagram_K8s-HPA.webp' 다음을 실행하여 새 YAML 파일을 적용합니다. - ``` - + ```bash cd pixie-lab-materials/main/kube kubectl apply -f hpa.yaml - ```