From 6a5b7c49a96930d9518ff300b068d90d8a3cb50b Mon Sep 17 00:00:00 2001 From: Amber Sistla Date: Mon, 16 Sep 2024 09:50:38 -0700 Subject: [PATCH 01/49] Create agent-overhead-reduction-tips.mdx INI settings to reduce overhead in PHP agent. --- .../agent-overhead-reduction-tips.mdx | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx diff --git a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx new file mode 100644 index 00000000000..8856ee4979d --- /dev/null +++ b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx @@ -0,0 +1,44 @@ +--- +title: PHP Agent overhead reduction tips +type: troubleshooting +tags: + - Agents + - PHP agent + - Troubleshooting +metaDescription: Agent settings to decrease overhead. +freshnessValidatedDate: never +--- + +## Problem + +Using the New Relic PHP agent results in overhead. + +## Explanation + +Overhead is an expected side effect of monitoring and reporting on software. Our engineers aim to minimize this, but your experience may differ quite a lot, depending on how you're using the agent. If you find that you are experiencing unexpected overhead, there are are various settings in the INI that can help reduce it. + +## INI Settings +Performance settings that can reduce overhead depending on your agent usage. + +1. reduce [newrelic.span_events.max_samples_stored](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored) + +2. disable [code level metrics](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-code-level-metrics-enabled) + +3. disable [logging](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#log-forwarding) + +4. set [newrelic.transaction_tracer.max_segments_web](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegweb) and/or [newrelic.transaction_tracer.max_segments_cli](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegcli) >= 1 + +5. set [newrelic.transaction_tracer.detail](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-detail) = 0 + +6. [newrelic.transaction_tracer.enabled](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-enabled) = false + +7. increase the [transaction tracer threshold](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-threshold) by setting newrelic.transaction_tracer.threshold = higher value + +8. [newrelic.transaction_tracer.explain_enabled](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-explain-enabled) = false + +9. don't trace slow SQL statements by setting [newrelic.transaction_tracer.slow_sql](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-slowsql) = false + + +## Other overhead considerations +A non-performant clocksource can affect the agent which checks the time for every span. Please ensure you are using an appropriate [clocksource](https://forum.newrelic.com/s/hubtopic/aAX8W0000008a7rWAA/relic-solution-php-agent-cpu-overhead-tips). +Fargate is affected by clocksource and is known to cause additional [overhead](https://docs.newrelic.com/docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact/). From cf53c26032445a370fbd5703c24ec0af756797e2 Mon Sep 17 00:00:00 2001 From: Paolo Gallina Date: Mon, 30 Sep 2024 12:57:18 +0200 Subject: [PATCH 02/49] fix(discovery): fix docs related to discovery --- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 +-- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 +-- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 +-- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 +-- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 +-- 15 files changed, 20 insertions(+), 25 deletions(-) diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index cada301ba33..707777505d4 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -284,7 +284,7 @@ Here's a detailed example of doing the above procedure for NGINX: integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -311,7 +311,7 @@ Here's a detailed example of doing the above procedure for NGINX: integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index 3febeb0f071..4b4ea02c42d 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -145,7 +145,7 @@ To troubleshoot and resolve the problem: ``` - nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index 6726acc7259..e71d5f0b81b 100644 --- a/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -44,8 +44,7 @@ These examples (for Docker-only environments and for Kubernetes) show how to con image: /nginx/ label.env: production integrations: - - name: nginx-server-metrics - command: metrics + - name: nri-nginx env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 285923b2c51..a57ee646a34 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ A continuación se muestra un ejemplo detallado de cómo realizar el procedimien integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ A continuación se muestra un ejemplo detallado de cómo realizar el procedimien integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index f3c0bdd61d8..6535540de8d 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ Para solucionar y resolver el problema: ``` - nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index a512e152564..ac5db6ce28f 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,8 +37,7 @@ Estos ejemplos (para entornos solo docker y para Kubernetes) muestran cómo conf image: /nginx/ label.env: production integrations: - - name: nginx-server-metrics - command: metrics + - name: nri-nginx env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 18acd8a2ace..723fef72a1e 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ ECSで動作しているサービスのモニタリングを有効にする方 integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ ECSで動作しているサービスのモニタリングを有効にする方 integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index c9be68ffb2d..578e1dbb328 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -143,7 +143,7 @@ translationType: machine ``` - nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index 8980b88d5fd..bde8e53ed9f 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,8 +37,7 @@ translationType: machine image: /nginx/ label.env: production integrations: - - name: nginx-server-metrics - command: metrics + - name: nri-nginx env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index ac7f783bfe8..87c2f2805cd 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -329,7 +329,7 @@ NGINX에 대해 위의 절차를 수행하는 자세한 예는 다음과 같습 integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -364,7 +364,7 @@ NGINX에 대해 위의 절차를 수행하는 자세한 예는 다음과 같습 integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index 14b0aef4c8c..f1221e13382 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ translationType: machine ``` - nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index afbd8b06fa8..94f7ef8752f 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,8 +37,7 @@ translationType: machine image: /nginx/ label.env: production integrations: - - name: nginx-server-metrics - command: metrics + - name: nri-nginx env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index f8eb7231c82..0d8b633a8a8 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ Aqui está um exemplo detalhado de como executar o procedimento acima para NGINX integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ Aqui está um exemplo detalhado de como executar o procedimento acima para NGINX integrations: - name: nri-nginx env: - STATUS_URL: http://${'${discovery.ip}'}:/status + STATUS_URL: http://${discovery.ip}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index 3748ed316fe..a5957df8bce 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ Para solucionar e resolver o problema: ``` - nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index 27bee6c7fd1..e30f6775853 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,8 +37,7 @@ Estes exemplos (para ambientes Docker-only e para Kubernetes) mostram como confi image: /nginx/ label.env: production integrations: - - name: nginx-server-metrics - command: metrics + - name: nri-nginx env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status From 692195efe672f8a9d8ebdbb3915c53dc029cfd90 Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Tue, 1 Oct 2024 16:41:00 -0700 Subject: [PATCH 03/49] chore: Add usePagination hook --- src/hooks/usePagination.js | 71 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 src/hooks/usePagination.js diff --git a/src/hooks/usePagination.js b/src/hooks/usePagination.js new file mode 100644 index 00000000000..2e1036fddeb --- /dev/null +++ b/src/hooks/usePagination.js @@ -0,0 +1,71 @@ +// pulled from https://github.com/mayankshubham/react-pagination which is used in a freecodecamp tutorial :) +import { useMemo } from 'react'; + +export const DOTS = '...'; + +const range = (start, end) => { + const length = end - start + 1; + return Array.from({ length }, (_, idx) => idx + start); +}; + +export const usePagination = ({ + totalCount, + pageSize, + siblingCount = 1, + currentPage, +}) => { + const paginationRange = useMemo(() => { + const totalPageCount = Math.ceil(totalCount / pageSize); + + // Pages count is determined as siblingCount + firstPage + lastPage + currentPage + 2*DOTS + const totalPageNumbers = siblingCount + 5; + + /* + If the number of pages is less than the page numbers we want to show in our + paginationComponent, we return the range [1..totalPageCount] + */ + if (totalPageNumbers >= totalPageCount) { + return range(1, totalPageCount); + } + + const leftSiblingIndex = Math.max(currentPage - siblingCount, 1); + const rightSiblingIndex = Math.min( + currentPage + siblingCount, + totalPageCount + ); + + /* + We do not want to show dots if there is only one position left + after/before the left/right page count as that would lead to a change if our Pagination + component size which we do not want + */ + const shouldShowLeftDots = leftSiblingIndex > 2; + const shouldShowRightDots = rightSiblingIndex < totalPageCount - 2; + + const firstPageIndex = 1; + const lastPageIndex = totalPageCount; + + if (!shouldShowLeftDots && shouldShowRightDots) { + const leftItemCount = 3 + 2 * siblingCount; + const leftRange = range(1, leftItemCount); + + return [...leftRange, DOTS, totalPageCount]; + } + + if (shouldShowLeftDots && !shouldShowRightDots) { + const rightItemCount = 3 + 2 * siblingCount; + const rightRange = range( + totalPageCount - rightItemCount + 1, + totalPageCount + ); + return [firstPageIndex, DOTS, ...rightRange]; + } + + if (shouldShowLeftDots && shouldShowRightDots) { + const middleRange = range(leftSiblingIndex, rightSiblingIndex); + return [firstPageIndex, DOTS, ...middleRange, DOTS, lastPageIndex]; + } + }, [totalCount, pageSize, siblingCount, currentPage]); + + return paginationRange; +}; From 64f28caaf69139653ddf7fea1669b33f62234453 Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Tue, 1 Oct 2024 16:41:12 -0700 Subject: [PATCH 04/49] chore: Update theme --- package.json | 4 ++-- yarn.lock | 49 ++++++++++++++++++++++++++++++++++++++++++------- 2 files changed, 44 insertions(+), 9 deletions(-) diff --git a/package.json b/package.json index 6f6732e848c..892ffeeebb1 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.8.1", + "@newrelic/gatsby-theme-newrelic": "9.8.3", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", @@ -237,4 +237,4 @@ "bugs": { "url": "https://github.com/newrelic/docs-website/issues" } -} +} \ No newline at end of file diff --git a/yarn.lock b/yarn.lock index b90b3f7acc5..224701fcbd1 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.8.1": - version "9.8.1" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.8.1.tgz#969ff2f9c5f7a9a683279a14372826500c2026f1" - integrity sha512-PPf0yjhO5HkvICLNYp1T37g9+yU7kIE828Buhm/pLqYRrusiQFCqoU1Uia1CjVsxnJUyIE3B6c1hn9h70lSszA== +"@newrelic/gatsby-theme-newrelic@9.8.3": + version "9.8.3" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.8.3.tgz#5c82f6dcce6eb859a631a45eb365f36595beb25f" + integrity sha512-fJivOMouW1kxFjHvH0BXkhL+L2lkaN1myJO5iaDGgqiHXGUQROebzLxOafz4MqMdAWsWSSn1X83grFP33UBJbQ== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" @@ -21232,7 +21232,7 @@ unicode-property-aliases-ecmascript@^2.0.0: resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.0.0.tgz#0a36cb9a585c4f6abd51ad1deddb285c165297c8" integrity sha512-5Zfuy9q/DFr4tfO7ZPeVXb1aPoeQSdeFMLpYuFebehDAhbuevLs5yxSZmIFN1tP5F9Wl4IpJrYojg85/zgyZHQ== -"unified10@npm:unified@^10.1.2", unified@^10.0.0: +"unified10@npm:unified@^10.1.2": version "10.1.2" resolved "https://registry.yarnpkg.com/unified/-/unified-10.1.2.tgz#b1d64e55dafe1f0b98bb6c719881103ecf6c86df" integrity sha512-pUSWAi/RAnVy1Pif2kAoeWNBa3JVrx0MId2LASj8G+7AiHWoKZNTomq6LG326T68U7/e263X6fTdcXIy7XnF7Q== @@ -21245,7 +21245,7 @@ unicode-property-aliases-ecmascript@^2.0.0: trough "^2.0.0" vfile "^5.0.0" -"unified11@npm:unified@^11.0.4", unified@^11.0.0: +"unified11@npm:unified@^11.0.4": version "11.0.4" resolved "https://registry.yarnpkg.com/unified/-/unified-11.0.4.tgz#f4be0ac0fe4c88cb873687c07c64c49ed5969015" integrity sha512-apMPnyLjAX+ty4OrNap7yumyVAMlKx5IWU2wlzzUdYJO9A8f1p9m/gywF/GM2ZDFcjQPrx59Mc90KwmxsoklxQ== @@ -21270,6 +21270,32 @@ unified@9.0.0: trough "^1.0.0" vfile "^4.0.0" +unified@^10.0.0: + version "10.1.2" + resolved "https://registry.yarnpkg.com/unified/-/unified-10.1.2.tgz#b1d64e55dafe1f0b98bb6c719881103ecf6c86df" + integrity sha512-pUSWAi/RAnVy1Pif2kAoeWNBa3JVrx0MId2LASj8G+7AiHWoKZNTomq6LG326T68U7/e263X6fTdcXIy7XnF7Q== + dependencies: + "@types/unist" "^2.0.0" + bail "^2.0.0" + extend "^3.0.0" + is-buffer "^2.0.0" + is-plain-obj "^4.0.0" + trough "^2.0.0" + vfile "^5.0.0" + +unified@^11.0.0: + version "11.0.4" + resolved "https://registry.yarnpkg.com/unified/-/unified-11.0.4.tgz#f4be0ac0fe4c88cb873687c07c64c49ed5969015" + integrity sha512-apMPnyLjAX+ty4OrNap7yumyVAMlKx5IWU2wlzzUdYJO9A8f1p9m/gywF/GM2ZDFcjQPrx59Mc90KwmxsoklxQ== + dependencies: + "@types/unist" "^3.0.0" + bail "^2.0.0" + devlop "^1.0.0" + extend "^3.0.0" + is-plain-obj "^4.0.0" + trough "^2.0.0" + vfile "^6.0.0" + unified@^7.0.0: version "7.1.0" resolved "https://registry.yarnpkg.com/unified/-/unified-7.1.0.tgz#5032f1c1ee3364bd09da12e27fdd4a7553c7be13" @@ -21568,7 +21594,7 @@ unist-util-visit-parents@^6.0.0: "@types/unist" "^3.0.0" unist-util-is "^6.0.0" -"unist-util-visit4@npm:unist-util-visit@^4.1.2", unist-util-visit@^4.0.0: +"unist-util-visit4@npm:unist-util-visit@^4.1.2": version "4.1.2" resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-4.1.2.tgz#125a42d1eb876283715a3cb5cceaa531828c72e2" integrity sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg== @@ -21593,6 +21619,15 @@ unist-util-visit@^1.1.0, unist-util-visit@^1.4.1: dependencies: unist-util-visit-parents "^2.0.0" +unist-util-visit@^4.0.0: + version "4.1.2" + resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-4.1.2.tgz#125a42d1eb876283715a3cb5cceaa531828c72e2" + integrity sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg== + dependencies: + "@types/unist" "^2.0.0" + unist-util-is "^5.0.0" + unist-util-visit-parents "^5.1.1" + unist-util-visit@^5.0.0: version "5.0.0" resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-5.0.0.tgz#a7de1f31f72ffd3519ea71814cccf5fd6a9217d6" From 1e467e06f046f9b91baea5af76f34742f4e57556 Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Tue, 1 Oct 2024 16:41:19 -0700 Subject: [PATCH 05/49] feat: Add search results page --- src/pages/search-results.js | 273 ++++++++++++++++++++++++++++++++++++ 1 file changed, 273 insertions(+) create mode 100644 src/pages/search-results.js diff --git a/src/pages/search-results.js b/src/pages/search-results.js new file mode 100644 index 00000000000..2b54b221b3e --- /dev/null +++ b/src/pages/search-results.js @@ -0,0 +1,273 @@ +import React, { useEffect, useState } from 'react'; +import PropTypes from 'prop-types'; +import { css } from '@emotion/react'; +import styled from '@emotion/styled'; +import { + Icon, + Button, + Link, + search, + Spinner, + Surface, + useLocale, + useQueryParams, +} from '@newrelic/gatsby-theme-newrelic'; + +import { usePagination, DOTS } from '../hooks/usePagination'; + +const SearchResultPageView = ({ pageContext }) => { + const { queryParams } = useQueryParams(); + const query = queryParams.get('query'); + const page = Number(queryParams.get('page')); + const locale = useLocale(); + const [results, setResults] = useState({}); + const { records, pageCount } = results; + const { slug } = pageContext; + + const totalPages = pageCount; + const totalResults = totalPages * 5; + const prevPage = page - 1; + const nextPage = page + 1; + const hasNextPage = nextPage <= totalPages; + const hasPrevPage = prevPage >= 1; + + const paginationRange = usePagination({ + totalCount: totalPages, + pageSize: 5, + siblingCount: 1, + currentPage: page, + }); + + useEffect(() => { + (async () => { + const defaultSources = locale.isDefault + ? ['developer', 'docs', 'opensource', 'quickstarts'] + : [ + `developer-${locale.locale}`, + `docs-${locale.locale}`, + `opensource-${locale.locale}`, + `quickstarts`, + ]; + const results = await search({ + searchTerm: query, + defaultSources, + filters: [ + { type: 'source', defaultFilters: [] }, + { type: 'searchBy', defaultFilters: [] }, + ], + page, + perPage: 5, + }); + setResults({ + pageCount: results.info.page.num_pages, + records: results.records.page, + }); + })(); + }, [locale, page, query]); + + return ( + + {!records && ( + +

Loading results

+ + + )} + {records && ( + <> +

+ {totalResults} results for "{query}" +

+ {records.map((result) => ( + + ))} + + + + + Previous + + + {paginationRange.map((pageNumber) => { + if (pageNumber === DOTS) { + return {DOTS}; + } + return ( + + + {pageNumber} + + + ); + })} + + + Next + + + + + + )} + + ); +}; + +const PageContainer = styled.div` + font-size: 1.125rem; + display: flex; + flex-direction: column; + justify-content: center; + width: 100%; + height: 100%; + h2 { + font-weight: normal; + margin-bottom: 1rem; + } +`; + +const LoadingContainer = styled.div` + height: 100%; + display: flex; + flex-direction: column; + justify-content: center; + align-items: center; +`; + +const PaginationContainer = styled.div` + display: flex; + max-width: 760px; + justify-content: center; + align-items: flex-end; + margin: 3rem auto 0; + a { + margin: 0 0.25rem 0; + display: flex; + button { + &:hover { + color: var(--brand-button-primary-accent-hover); + border-color: var(--brand-button-primary-accent-hover); + } + } + text-decoration: none; + &[disabled] { + pointer-events: none; + button { + border-color: --system-text-muted-light; + color: --system-text-muted-light; + } + } + } +`; + +const PaginationButton = ({ children, ...props }) => ( + +); + +const Result = ({ result }) => { + return ( + +

+ {result.url.replace('https://docs.newrelic.com/docs/', '')} +

+

+

+ + ); +}; + +SearchResultPageView.propTypes = { + location: PropTypes.shape({ + state: PropTypes.shape({ + results: PropTypes.arrayOf( + PropTypes.shape({ + highlight: PropTypes.shape({ + title: PropTypes.string, + body: PropTypes.string, + }), + url: PropTypes.string, + }) + ).isRequired, + }), + }), +}; + +export default SearchResultPageView; From 68880c1be339ba7f48a1699334d48401805a2f4f Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Wed, 2 Oct 2024 14:47:58 -0700 Subject: [PATCH 06/49] fix: Update key prop and page count --- src/hooks/usePagination.js | 7 ++----- src/pages/search-results.js | 7 +++---- 2 files changed, 5 insertions(+), 9 deletions(-) diff --git a/src/hooks/usePagination.js b/src/hooks/usePagination.js index 2e1036fddeb..f4a949f49ce 100644 --- a/src/hooks/usePagination.js +++ b/src/hooks/usePagination.js @@ -9,14 +9,11 @@ const range = (start, end) => { }; export const usePagination = ({ - totalCount, - pageSize, + totalPageCount, siblingCount = 1, currentPage, }) => { const paginationRange = useMemo(() => { - const totalPageCount = Math.ceil(totalCount / pageSize); - // Pages count is determined as siblingCount + firstPage + lastPage + currentPage + 2*DOTS const totalPageNumbers = siblingCount + 5; @@ -65,7 +62,7 @@ export const usePagination = ({ const middleRange = range(leftSiblingIndex, rightSiblingIndex); return [firstPageIndex, DOTS, ...middleRange, DOTS, lastPageIndex]; } - }, [totalCount, pageSize, siblingCount, currentPage]); + }, [totalPageCount, siblingCount, currentPage]); return paginationRange; }; diff --git a/src/pages/search-results.js b/src/pages/search-results.js index 2b54b221b3e..6b34f9d965e 100644 --- a/src/pages/search-results.js +++ b/src/pages/search-results.js @@ -32,8 +32,7 @@ const SearchResultPageView = ({ pageContext }) => { const hasPrevPage = prevPage >= 1; const paginationRange = usePagination({ - totalCount: totalPages, - pageSize: 5, + totalPageCount: totalPages, siblingCount: 1, currentPage: page, }); @@ -84,8 +83,8 @@ const SearchResultPageView = ({ pageContext }) => {

{totalResults} results for "{query}"

- {records.map((result) => ( - + {records.map((result, i) => ( + ))} Date: Fri, 4 Oct 2024 09:57:56 -0700 Subject: [PATCH 07/49] chore: Nullish coalesce page number, add results catch --- src/pages/search-results.js | 45 ++++++++++++++++++++++--------------- 1 file changed, 27 insertions(+), 18 deletions(-) diff --git a/src/pages/search-results.js b/src/pages/search-results.js index 6b34f9d965e..34bf245cf64 100644 --- a/src/pages/search-results.js +++ b/src/pages/search-results.js @@ -18,10 +18,10 @@ import { usePagination, DOTS } from '../hooks/usePagination'; const SearchResultPageView = ({ pageContext }) => { const { queryParams } = useQueryParams(); const query = queryParams.get('query'); - const page = Number(queryParams.get('page')); + const page = Number(queryParams.get('page') ?? 1); const locale = useLocale(); - const [results, setResults] = useState({}); - const { records, pageCount } = results; + const [results, setResults] = useState({ loading: true }); + const { records, pageCount, loading, error } = results; const { slug } = pageContext; const totalPages = pageCount; @@ -47,26 +47,34 @@ const SearchResultPageView = ({ pageContext }) => { `opensource-${locale.locale}`, `quickstarts`, ]; - const results = await search({ - searchTerm: query, - defaultSources, - filters: [ - { type: 'source', defaultFilters: [] }, - { type: 'searchBy', defaultFilters: [] }, - ], - page, - perPage: 5, - }); - setResults({ - pageCount: results.info.page.num_pages, - records: results.records.page, - }); + try { + const results = await search({ + searchTerm: query, + defaultSources, + filters: [ + { type: 'source', defaultFilters: [] }, + { type: 'searchBy', defaultFilters: [] }, + ], + page, + perPage: 5, + }); + setResults({ + pageCount: results.info.page.num_pages, + records: results.records.page, + loading: false, + }); + } catch { + setResults({ + error: 'Unable to get search results, an error has occurred', + loading: false, + }); + } })(); }, [locale, page, query]); return ( - {!records && ( + {loading && (

Loading results

{ )} + {error && !loading && {error}} ); }; From 669d0ee2c772be9ef52f24378951ad70f9c59ec8 Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Fri, 4 Oct 2024 10:19:18 -0700 Subject: [PATCH 08/49] chore: Reroute to homepage if no query --- src/pages/search-results.js | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/search-results.js b/src/pages/search-results.js index 34bf245cf64..fc63d4791db 100644 --- a/src/pages/search-results.js +++ b/src/pages/search-results.js @@ -12,6 +12,7 @@ import { useLocale, useQueryParams, } from '@newrelic/gatsby-theme-newrelic'; +import { navigate } from '@reach/router'; import { usePagination, DOTS } from '../hooks/usePagination'; @@ -38,6 +39,9 @@ const SearchResultPageView = ({ pageContext }) => { }); useEffect(() => { + if (!query) { + navigate('/'); + } (async () => { const defaultSources = locale.isDefault ? ['developer', 'docs', 'opensource', 'quickstarts'] From b055e42cc756399c86a0801e0dee7fe1323743db Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Fri, 4 Oct 2024 11:07:28 -0700 Subject: [PATCH 09/49] chore: Add hover underline to result headers --- src/pages/search-results.js | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/pages/search-results.js b/src/pages/search-results.js index fc63d4791db..90d48d58048 100644 --- a/src/pages/search-results.js +++ b/src/pages/search-results.js @@ -242,6 +242,9 @@ const Result = ({ result }) => { color: var(--primary-font-color); &:hover { color: var(--primary-font-color); + h3 { + text-decoration: underline; + } } `} > From b9cb8eeadffc06f1fc8076bf54b45dcab4588128 Mon Sep 17 00:00:00 2001 From: Liz Baker Date: Fri, 4 Oct 2024 13:46:10 -0700 Subject: [PATCH 10/49] chore: Update proptypes and css --- src/pages/search-results.js | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/src/pages/search-results.js b/src/pages/search-results.js index 90d48d58048..76facc94b63 100644 --- a/src/pages/search-results.js +++ b/src/pages/search-results.js @@ -181,10 +181,15 @@ const PageContainer = styled.div` justify-content: center; width: 100%; height: 100%; + padding-right: 3.5rem; h2 { font-weight: normal; margin-bottom: 1rem; } + + @media (max-width: 1240px) { + padding-right: 0; + } `; const LoadingContainer = styled.div` @@ -270,19 +275,9 @@ const Result = ({ result }) => { }; SearchResultPageView.propTypes = { - location: PropTypes.shape({ - state: PropTypes.shape({ - results: PropTypes.arrayOf( - PropTypes.shape({ - highlight: PropTypes.shape({ - title: PropTypes.string, - body: PropTypes.string, - }), - url: PropTypes.string, - }) - ).isRequired, - }), - }), + pageContext: PropTypes.shape({ + slug: PropTypes.string, + }).isRequired, }; export default SearchResultPageView; From a375e01eec5f3f244d679599c5c5b8f0b7ea7aae Mon Sep 17 00:00:00 2001 From: Gaurab Manandhar Date: Fri, 4 Oct 2024 19:36:57 +0530 Subject: [PATCH 11/49] chore: update homepage search behavior --- src/components/HomepageBanner.js | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/src/components/HomepageBanner.js b/src/components/HomepageBanner.js index b131ac7deee..fea173f485d 100644 --- a/src/components/HomepageBanner.js +++ b/src/components/HomepageBanner.js @@ -78,7 +78,9 @@ const HomepageBanner = () => { searchTerm, searchLocation: 'homepage', }); - navigate(`?q=${searchTerm || ''}`); + if(searchTerm != '') { + navigate(`search-results/?query=${searchTerm}&page=1`); + } }} css={css` max-width: 880px; @@ -116,19 +118,19 @@ const HomepageBanner = () => { `} >

{t('strings.home.search.popularSearches.title')}:

- + {t('strings.home.search.popularSearches.options.0')}, - + {t('strings.home.search.popularSearches.options.1')}, - + {t('strings.home.search.popularSearches.options.2')}, - + {t('strings.home.search.popularSearches.options.3')}, - + {t('strings.home.search.popularSearches.options.4')} From e63747f61dc4dce2a125547bd1d40e26f46e020a Mon Sep 17 00:00:00 2001 From: Gaurab Manandhar Date: Fri, 4 Oct 2024 21:54:05 +0530 Subject: [PATCH 12/49] fix: lint fix --- src/components/HomepageBanner.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/HomepageBanner.js b/src/components/HomepageBanner.js index fea173f485d..a2985ca022b 100644 --- a/src/components/HomepageBanner.js +++ b/src/components/HomepageBanner.js @@ -78,7 +78,7 @@ const HomepageBanner = () => { searchTerm, searchLocation: 'homepage', }); - if(searchTerm != '') { + if(searchTerm !== '') { navigate(`search-results/?query=${searchTerm}&page=1`); } }} From 475ecbeaab4a30ce367c57d321a236087531d9e6 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Mon, 7 Oct 2024 13:14:16 -0400 Subject: [PATCH 13/49] chore: fix lint --- src/components/HomepageBanner.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/HomepageBanner.js b/src/components/HomepageBanner.js index a2985ca022b..a0c67cee1c7 100644 --- a/src/components/HomepageBanner.js +++ b/src/components/HomepageBanner.js @@ -78,7 +78,7 @@ const HomepageBanner = () => { searchTerm, searchLocation: 'homepage', }); - if(searchTerm !== '') { + if (searchTerm !== '') { navigate(`search-results/?query=${searchTerm}&page=1`); } }} From 9915df49f3dc8853fe020a21f217446d61dcf7d2 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Wed, 16 Oct 2024 13:26:43 -0400 Subject: [PATCH 14/49] bump `@newrelic/gatsby-theme-newrelic` to 9.9.0 --- package.json | 4 ++-- yarn.lock | 49 +++++++------------------------------------------ 2 files changed, 9 insertions(+), 44 deletions(-) diff --git a/package.json b/package.json index 6940b3eed65..288d78708cf 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.8.3", + "@newrelic/gatsby-theme-newrelic": "9.9.0", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", @@ -237,4 +237,4 @@ "bugs": { "url": "https://github.com/newrelic/docs-website/issues" } -} \ No newline at end of file +} diff --git a/yarn.lock b/yarn.lock index 224701fcbd1..427cbc61477 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.8.3": - version "9.8.3" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.8.3.tgz#5c82f6dcce6eb859a631a45eb365f36595beb25f" - integrity sha512-fJivOMouW1kxFjHvH0BXkhL+L2lkaN1myJO5iaDGgqiHXGUQROebzLxOafz4MqMdAWsWSSn1X83grFP33UBJbQ== +"@newrelic/gatsby-theme-newrelic@9.9.0": + version "9.9.0" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.9.0.tgz#1940f1bd6f085b402c9fad648ee9c86ac6c3b13c" + integrity sha512-INY4C+xxABUngaFJr7MGo7IApaA413uxR2a08vm/acbsRJSi8ft2Ph+boP1pfUrCqvlnLRDJ8XTHccTCHLhReQ== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" @@ -21232,7 +21232,7 @@ unicode-property-aliases-ecmascript@^2.0.0: resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.0.0.tgz#0a36cb9a585c4f6abd51ad1deddb285c165297c8" integrity sha512-5Zfuy9q/DFr4tfO7ZPeVXb1aPoeQSdeFMLpYuFebehDAhbuevLs5yxSZmIFN1tP5F9Wl4IpJrYojg85/zgyZHQ== -"unified10@npm:unified@^10.1.2": +"unified10@npm:unified@^10.1.2", unified@^10.0.0: version "10.1.2" resolved "https://registry.yarnpkg.com/unified/-/unified-10.1.2.tgz#b1d64e55dafe1f0b98bb6c719881103ecf6c86df" integrity sha512-pUSWAi/RAnVy1Pif2kAoeWNBa3JVrx0MId2LASj8G+7AiHWoKZNTomq6LG326T68U7/e263X6fTdcXIy7XnF7Q== @@ -21245,7 +21245,7 @@ unicode-property-aliases-ecmascript@^2.0.0: trough "^2.0.0" vfile "^5.0.0" -"unified11@npm:unified@^11.0.4": +"unified11@npm:unified@^11.0.4", unified@^11.0.0: version "11.0.4" resolved "https://registry.yarnpkg.com/unified/-/unified-11.0.4.tgz#f4be0ac0fe4c88cb873687c07c64c49ed5969015" integrity sha512-apMPnyLjAX+ty4OrNap7yumyVAMlKx5IWU2wlzzUdYJO9A8f1p9m/gywF/GM2ZDFcjQPrx59Mc90KwmxsoklxQ== @@ -21270,32 +21270,6 @@ unified@9.0.0: trough "^1.0.0" vfile "^4.0.0" -unified@^10.0.0: - version "10.1.2" - resolved "https://registry.yarnpkg.com/unified/-/unified-10.1.2.tgz#b1d64e55dafe1f0b98bb6c719881103ecf6c86df" - integrity sha512-pUSWAi/RAnVy1Pif2kAoeWNBa3JVrx0MId2LASj8G+7AiHWoKZNTomq6LG326T68U7/e263X6fTdcXIy7XnF7Q== - dependencies: - "@types/unist" "^2.0.0" - bail "^2.0.0" - extend "^3.0.0" - is-buffer "^2.0.0" - is-plain-obj "^4.0.0" - trough "^2.0.0" - vfile "^5.0.0" - -unified@^11.0.0: - version "11.0.4" - resolved "https://registry.yarnpkg.com/unified/-/unified-11.0.4.tgz#f4be0ac0fe4c88cb873687c07c64c49ed5969015" - integrity sha512-apMPnyLjAX+ty4OrNap7yumyVAMlKx5IWU2wlzzUdYJO9A8f1p9m/gywF/GM2ZDFcjQPrx59Mc90KwmxsoklxQ== - dependencies: - "@types/unist" "^3.0.0" - bail "^2.0.0" - devlop "^1.0.0" - extend "^3.0.0" - is-plain-obj "^4.0.0" - trough "^2.0.0" - vfile "^6.0.0" - unified@^7.0.0: version "7.1.0" resolved "https://registry.yarnpkg.com/unified/-/unified-7.1.0.tgz#5032f1c1ee3364bd09da12e27fdd4a7553c7be13" @@ -21594,7 +21568,7 @@ unist-util-visit-parents@^6.0.0: "@types/unist" "^3.0.0" unist-util-is "^6.0.0" -"unist-util-visit4@npm:unist-util-visit@^4.1.2": +"unist-util-visit4@npm:unist-util-visit@^4.1.2", unist-util-visit@^4.0.0: version "4.1.2" resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-4.1.2.tgz#125a42d1eb876283715a3cb5cceaa531828c72e2" integrity sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg== @@ -21619,15 +21593,6 @@ unist-util-visit@^1.1.0, unist-util-visit@^1.4.1: dependencies: unist-util-visit-parents "^2.0.0" -unist-util-visit@^4.0.0: - version "4.1.2" - resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-4.1.2.tgz#125a42d1eb876283715a3cb5cceaa531828c72e2" - integrity sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg== - dependencies: - "@types/unist" "^2.0.0" - unist-util-is "^5.0.0" - unist-util-visit-parents "^5.1.1" - unist-util-visit@^5.0.0: version "5.0.0" resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-5.0.0.tgz#a7de1f31f72ffd3519ea71814cccf5fd6a9217d6" From ab0cdb61d2048ee55cf874c5755310db1e762381 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 17 Oct 2024 13:47:15 -0400 Subject: [PATCH 15/49] bump `@newrelic/gatsby-theme-newrelic` to 9.10.0 --- package.json | 2 +- yarn.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index 288d78708cf..72e92d3193a 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.9.0", + "@newrelic/gatsby-theme-newrelic": "9.10.0", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", diff --git a/yarn.lock b/yarn.lock index 427cbc61477..261c1ea1f3d 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.9.0": - version "9.9.0" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.9.0.tgz#1940f1bd6f085b402c9fad648ee9c86ac6c3b13c" - integrity sha512-INY4C+xxABUngaFJr7MGo7IApaA413uxR2a08vm/acbsRJSi8ft2Ph+boP1pfUrCqvlnLRDJ8XTHccTCHLhReQ== +"@newrelic/gatsby-theme-newrelic@9.10.0": + version "9.10.0" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.0.tgz#0f8d08d4446b6261d059f28560f0d592a3511e92" + integrity sha512-nof9Ixk6lIiXIy6Ozf4r295YV2wWuzHMDd4F32h+WFrdiVY0szFNzzbZM920P30Jzm/yCaIJeJxz3Z4VwAkWKg== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" From 8ec0ed24afa840b6752d8de52ced75cd6529a12e Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 17 Oct 2024 14:33:52 -0400 Subject: [PATCH 16/49] remove search from left nav --- src/layouts/MainLayout.js | 31 +------------------------------ 1 file changed, 1 insertion(+), 30 deletions(-) diff --git a/src/layouts/MainLayout.js b/src/layouts/MainLayout.js index 2d131f28989..1308b5ffe4a 100644 --- a/src/layouts/MainLayout.js +++ b/src/layouts/MainLayout.js @@ -8,9 +8,7 @@ import { useLayout, Icon, Button, - SearchInput, addPageAction, - useTranslation, LoggedInProvider, } from '@newrelic/gatsby-theme-newrelic'; import { isNavClosed, setNavClosed } from '../utils/navState'; @@ -20,7 +18,7 @@ import { CSSTransition } from 'react-transition-group'; import Layout from '../components/Layout'; import SEO from '../components/SEO'; import RootNavigation from '../components/RootNavigation'; -import { useLocation, navigate } from '@reach/router'; +import { useLocation } from '@reach/router'; import { MainLayoutContext } from '../components/MainLayoutContext'; const MainLayout = ({ children, pageContext }) => { @@ -28,9 +26,7 @@ const MainLayout = ({ children, pageContext }) => { const { locale, slug } = pageContext; const location = useLocation(); const [isMobileNavOpen, setIsMobileNavOpen] = useState(false); - const [searchTerm, setSearchTerm] = useState(''); const [sidebar, setSidebar] = useState(true); - const { t } = useTranslation(); const navHeaderHeight = '100px'; const isStyleGuide = slug.match(/\/docs\/style-guide/) || slug.match(/\/docs\/agile-handbook/); @@ -195,31 +191,6 @@ const MainLayout = ({ children, pageContext }) => { /> - {sidebar && ( - setSearchTerm(e.target.value)} - onSubmit={() => { - addPageAction({ - eventName: 'swiftypeSearchInput', - category: 'SearchInput', - searchTerm, - searchLocation: 'sidebar', - }); - navigate(`?q=${searchTerm || ''}`); - }} - css={css` - margin: 1.5rem 0 2rem; - svg { - color: var(--primary-text-color); - } - `} - /> - )} <> From 69493846c6137c051e0f02f66e7ae56723885930 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 17 Oct 2024 14:47:40 -0400 Subject: [PATCH 17/49] bump `@newrelic/gatsby-theme-newrelic` to 9.10.1 --- package.json | 2 +- yarn.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index 72e92d3193a..f45cce17967 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.10.0", + "@newrelic/gatsby-theme-newrelic": "9.10.1", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", diff --git a/yarn.lock b/yarn.lock index 261c1ea1f3d..941a49feed0 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.10.0": - version "9.10.0" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.0.tgz#0f8d08d4446b6261d059f28560f0d592a3511e92" - integrity sha512-nof9Ixk6lIiXIy6Ozf4r295YV2wWuzHMDd4F32h+WFrdiVY0szFNzzbZM920P30Jzm/yCaIJeJxz3Z4VwAkWKg== +"@newrelic/gatsby-theme-newrelic@9.10.1": + version "9.10.1" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.1.tgz#98b4e1af21fb2c8e73d5230e57647ef11c09d141" + integrity sha512-edD0WabYLvKi/rkUeabChx2QWdO0lFyF6uQek3xR9S37o8rk2YntRksilRSjsvrXPqDDScmAoiI3uXI5SeYkaw== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" From 382a346a2d5475dfac89d29d25a7dd0e5b05f3b8 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 17 Oct 2024 16:12:53 -0400 Subject: [PATCH 18/49] fix spacing in left nav --- src/components/Navigation.js | 2 +- src/layouts/MainLayout.js | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/components/Navigation.js b/src/components/Navigation.js index 1607490d2b4..b527c816ba6 100644 --- a/src/components/Navigation.js +++ b/src/components/Navigation.js @@ -32,7 +32,7 @@ const Navigation = ({ nav, className }) => { css={css` height: 100%; overflow: auto; - margin: 16px 0; + margin: 0 0 16px; -ms-overflow-style: none; scrollbar-width: none; &::-webkit-scrollbar { diff --git a/src/layouts/MainLayout.js b/src/layouts/MainLayout.js index 1308b5ffe4a..fa638472609 100644 --- a/src/layouts/MainLayout.js +++ b/src/layouts/MainLayout.js @@ -27,7 +27,7 @@ const MainLayout = ({ children, pageContext }) => { const location = useLocation(); const [isMobileNavOpen, setIsMobileNavOpen] = useState(false); const [sidebar, setSidebar] = useState(true); - const navHeaderHeight = '100px'; + const navHeaderHeight = '55px'; const isStyleGuide = slug.match(/\/docs\/style-guide/) || slug.match(/\/docs\/agile-handbook/); const addTrailingSlash = (path) => { From 1e0518f87c17dca528f69285d1494f0b90f9b595 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 17 Oct 2024 17:45:39 -0400 Subject: [PATCH 19/49] bump `@newrelic/gatsby-theme-newrelic` to 9.10.2 --- package.json | 2 +- yarn.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index f45cce17967..be68b0f06cf 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.10.1", + "@newrelic/gatsby-theme-newrelic": "9.10.2", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", diff --git a/yarn.lock b/yarn.lock index 941a49feed0..005fd92dda8 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.10.1": - version "9.10.1" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.1.tgz#98b4e1af21fb2c8e73d5230e57647ef11c09d141" - integrity sha512-edD0WabYLvKi/rkUeabChx2QWdO0lFyF6uQek3xR9S37o8rk2YntRksilRSjsvrXPqDDScmAoiI3uXI5SeYkaw== +"@newrelic/gatsby-theme-newrelic@9.10.2": + version "9.10.2" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.2.tgz#5110aaecdf073db61eed57a6539ec320cb95139e" + integrity sha512-g6u/wGgV2mwp1sC1cLPtFFBj8+/6d+PPvQ/HHRo2pPWHoQfGZ7PCvJwWRkYgtmRnqBEuimgkrdsnu2wkS9N2rg== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" From 3b8d3dc21d2b3a95429118548cc055cf6bc9abaa Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Fri, 18 Oct 2024 13:40:37 -0700 Subject: [PATCH 20/49] docs: remove confusing link to self --- .../synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx index d8b64279a0b..86db37ce546 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx @@ -15,7 +15,7 @@ The synthetics runtime upgrade UI is a central place to view all monitors that u As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use the runtime upgrade UI to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. ## Requirements [#requirements] From 330cb6eb35652a7aa7e53675b2009b1063967d42 Mon Sep 17 00:00:00 2001 From: jcol <116673918+jeff-colucci@users.noreply.github.com> Date: Fri, 18 Oct 2024 17:07:49 -0500 Subject: [PATCH 21/49] Update runtime-upgrade-ui.mdx Fixing styling --- .../using-monitors/runtime-upgrade-ui.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx index 86db37ce546..e86726d7482 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx @@ -13,9 +13,10 @@ Use the synthetics runtime upgrades UI if your monitors use legacy runtimes, inc The synthetics runtime upgrade UI is a central place to view all monitors that use legacy runtimes. It also allows you to update them to the newest runtimes. - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. - - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use the runtime upgrade UI to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. + + * For public locations, use the runtime upgrade UI to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. ## Requirements [#requirements] From b4efe15a21b6178c43c54eb5707156b072b5bf28 Mon Sep 17 00:00:00 2001 From: nbaenam Date: Mon, 21 Oct 2024 12:33:30 +0200 Subject: [PATCH 22/49] style(Synthetics): Added TW edits --- .../nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx | 5 +++-- ...pted-browser-reference-monitor-versions-04x-or-lower.mdx | 5 +++-- ...tics-scripted-browser-reference-monitor-versions-050.mdx | 5 +++-- .../scripting-monitors/write-synthetic-api-tests-legacy.mdx | 5 +++-- .../troubleshooting/runtime-upgrade-troubleshooting.mdx | 5 +++-- .../using-monitors/manage-monitor-runtimes.mdx | 5 +++-- .../synthetic-monitoring/using-monitors/new-runtime.mdx | 5 +++-- .../using-monitors/runtime-upgrade-ui.mdx | 6 +++--- 8 files changed, 24 insertions(+), 17 deletions(-) diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx index cae99212fb1..a474f4db5b3 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx @@ -434,9 +434,10 @@ Below are some sample requests to automate the creation of your synthetic monito - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. diff --git a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-04x-or-lower.mdx b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-04x-or-lower.mdx index b00de4c2c0b..8e5f3e341a3 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-04x-or-lower.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-04x-or-lower.mdx @@ -15,9 +15,10 @@ freshnessValidatedDate: never This document is for synthetic monitor versions 0.4.x or lower. See also the documentation for [Synthetic monitor versions 0.5 or 0.6.0](/docs/synthetics/new-relic-synthetics/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050) and [monitor version Chrome 100 and newer](/docs/synthetics/new-relic-synthetics/scripting-monitors/synthetic-scipted-browser-reference-monitor-versions-chrome100). - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. For some common usage examples, see [Introduction to scripted browser monitors](/docs/synthetics/synthetic-monitoring/scripting-monitors/introduction-scripted-browser-monitors). diff --git a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050.mdx b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050.mdx index 0757c42a116..5da015d4944 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050.mdx @@ -17,9 +17,10 @@ This document describes scripted browser functions available for synthetic monit For more on monitor versions and runtime differences, see [Runtime environments](/docs/synthetics/new-relic-synthetics/scripting-monitors/scripted-monitor-runtime-environment). - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. The Chrome 100+ browser runtime provides backward compatible support for 0.5.0 and 0.6.0 browser runtime syntax. diff --git a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests-legacy.mdx b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests-legacy.mdx index c09d32264e7..7db7510e453 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests-legacy.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests-legacy.mdx @@ -10,9 +10,10 @@ freshnessValidatedDate: never --- - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. Use synthetic monitoring's [API tests](/docs/synthetics/new-relic-synthetics/getting-started/types-synthetics-monitors) to monitor your API endpoint to ensure it is functioning correctly. New Relic uses the [http-request](https://github.com/request/request) module internally to make HTTP calls to your endpoint and validate the results. diff --git a/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting.mdx b/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting.mdx index bd3c2b9947b..2c4276c2d1f 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting.mdx @@ -12,9 +12,10 @@ freshnessValidatedDate: never --- - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. ## Scripted Browser: Attempts to interact with elements fail [#promises] diff --git a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/manage-monitor-runtimes.mdx b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/manage-monitor-runtimes.mdx index a3def22cc15..571e8c619fe 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/manage-monitor-runtimes.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/manage-monitor-runtimes.mdx @@ -14,9 +14,10 @@ freshnessValidatedDate: never --- - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. Simple browser, scripted browser, and API monitors execute in the runtime environment used when the monitors were created. Your monitors won't automatically convert to newer runtimes when those runtimes release. diff --git a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime.mdx b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime.mdx index 7de0fd248bf..ef8199b6d50 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime.mdx @@ -22,9 +22,10 @@ Making the switch gives you these features: * Access to our [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial) to automate the management of your synthetic monitors. - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. + * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. + * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. ## Private location requirements [#private-locations] diff --git a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx index e86726d7482..08af2812420 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui.mdx @@ -13,9 +13,9 @@ Use the synthetics runtime upgrades UI if your monitors use legacy runtimes, inc The synthetics runtime upgrade UI is a central place to view all monitors that use legacy runtimes. It also allows you to update them to the newest runtimes. - As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. + As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. - * For public locations, use the runtime upgrade UI to update your monitors to the newest runtimes. + * For public locations, use the runtime upgrade UI to update your monitors to the newest runtimes. * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation. @@ -72,7 +72,7 @@ You can select and upgrade individual monitors from each tab. You can also use t Monitors may take up to 10 minutes to start using the new runtime after upgrading using the runtime upgrade UI. -## Programmatic runtime upgrades[#programmaticUpgrade] +## Programmatic runtime upgrades [#programmaticUpgrade] Runtime upgrade test results are [available via NerdGraph](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial/#query-runtime-upgrade-status). From a1c1076006fcfaa58f2889fe0f09051644a082b7 Mon Sep 17 00:00:00 2001 From: nbaenam Date: Mon, 21 Oct 2024 15:57:34 +0200 Subject: [PATCH 23/49] style(PHP agent): Added TW edits --- .../agent-overhead-reduction-tips.mdx | 26 +++++----- src/nav/apm.yml | 50 ++++++++++--------- 2 files changed, 39 insertions(+), 37 deletions(-) diff --git a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx index 8856ee4979d..50509e26c58 100644 --- a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx +++ b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx @@ -6,7 +6,7 @@ tags: - PHP agent - Troubleshooting metaDescription: Agent settings to decrease overhead. -freshnessValidatedDate: never +freshnessValidatedDate: 2024-10-21 --- ## Problem @@ -15,30 +15,30 @@ Using the New Relic PHP agent results in overhead. ## Explanation -Overhead is an expected side effect of monitoring and reporting on software. Our engineers aim to minimize this, but your experience may differ quite a lot, depending on how you're using the agent. If you find that you are experiencing unexpected overhead, there are are various settings in the INI that can help reduce it. +Overhead is an expected side effect of monitoring and reporting on software. Our engineers aim to minimize this, but your experience may differ quite a lot, depending on how you're using the agent. If you find that you're experiencing unexpected overhead, there are are various settings in the `INI` that can help reduce it. ## INI Settings Performance settings that can reduce overhead depending on your agent usage. -1. reduce [newrelic.span_events.max_samples_stored](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored) +1. Reduce [`newrelic.span_events.max_samples_stored`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored) -2. disable [code level metrics](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-code-level-metrics-enabled) +2. Disable [code level metrics](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-code-level-metrics). -3. disable [logging](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#log-forwarding) +3. Disable [logging](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#log-forwarding). -4. set [newrelic.transaction_tracer.max_segments_web](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegweb) and/or [newrelic.transaction_tracer.max_segments_cli](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegcli) >= 1 +4. Set [`newrelic.transaction_tracer.max_segments_web`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegweb) and [`newrelic.transaction_tracer.max_segments_cli`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegcli) >= 1. -5. set [newrelic.transaction_tracer.detail](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-detail) = 0 +5. Set [`newrelic.transaction_tracer.detail`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-detail) = 0. -6. [newrelic.transaction_tracer.enabled](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-enabled) = false +6. Set [`newrelic.transaction_tracer.enabled`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-enabled) = false. -7. increase the [transaction tracer threshold](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-threshold) by setting newrelic.transaction_tracer.threshold = higher value +7. Increase the [transaction tracer threshold](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-threshold) by setting `newrelic.transaction_tracer.threshold` = higher value. -8. [newrelic.transaction_tracer.explain_enabled](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-explain-enabled) = false +8. Set [`newrelic.transaction_tracer.explain_enabled`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-explain-enabled) = false. -9. don't trace slow SQL statements by setting [newrelic.transaction_tracer.slow_sql](https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-slowsql) = false +9. Don't trace slow SQL statements by setting [`newrelic.transaction_tracer.slow_sql`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-slowsql) = false. ## Other overhead considerations -A non-performant clocksource can affect the agent which checks the time for every span. Please ensure you are using an appropriate [clocksource](https://forum.newrelic.com/s/hubtopic/aAX8W0000008a7rWAA/relic-solution-php-agent-cpu-overhead-tips). -Fargate is affected by clocksource and is known to cause additional [overhead](https://docs.newrelic.com/docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact/). +A non-performant clocksource can affect the agent which checks the time for every span. Please ensure you're using an appropriate [clocksource](https://forum.newrelic.com/s/hubtopic/aAX8W0000008a7rWAA/relic-solution-php-agent-cpu-overhead-tips). +Fargate is affected by clocksource and is known to cause additional [overhead](/docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact/). diff --git a/src/nav/apm.yml b/src/nav/apm.yml index 0e230ad2f41..8dbbe7bf622 100644 --- a/src/nav/apm.yml +++ b/src/nav/apm.yml @@ -719,54 +719,56 @@ pages: - title: Troubleshooting path: /docs/apm/agents/php-agent/troubleshooting pages: - - title: No data appears - path: /docs/apm/agents/php-agent/troubleshooting/no-data-appears-php - - title: Data stops reporting - path: /docs/apm/agents/php-agent/troubleshooting/data-stops-reporting - - title: First transaction not reported - path: /docs/apm/agents/php-agent/troubleshooting/first-php-transaction-not-reported + - title: Agents stops after updating PHP + path: /docs/apm/agents/php-agent/troubleshooting/agent-stops-working-after-updating-php - title: Agent not reporting errors path: /docs/apm/agents/php-agent/troubleshooting/php-agent-not-reporting-errors + - title: Checking loaded configuration files directory + path: /docs/apm/agents/php-agent/troubleshooting/checking-loaded-configuration-files-directory + - title: Data stops reporting + path: /docs/apm/agents/php-agent/troubleshooting/data-stops-reporting + - title: Data stops reporting while using SELinux + path: /docs/apm/agents/php-agent/troubleshooting/data-stops-reporting-while-using-selinux - title: Determine permissions requirements path: /docs/apm/agents/php-agent/troubleshooting/determine-permissions-requirements-php + - title: First transaction not reported + path: /docs/apm/agents/php-agent/troubleshooting/first-php-transaction-not-reported - title: Generating logs for troubleshooting path: /docs/apm/agents/php-agent/troubleshooting/generating-logs-troubleshooting-php - - title: Data stops reporting while using SELinux - path: /docs/apm/agents/php-agent/troubleshooting/data-stops-reporting-while-using-selinux - - title: Agents stops after updating PHP - path: /docs/apm/agents/php-agent/troubleshooting/agent-stops-working-after-updating-php - - title: Checking loaded configuration files directory - path: /docs/apm/agents/php-agent/troubleshooting/checking-loaded-configuration-files-directory + - title: INI settings not taking effect immediately + path: /docs/apm/agents/php-agent/troubleshooting/ini-settings-not-taking-effect-immediately - title: Missing PHP module path: /docs/apm/agents/php-agent/troubleshooting/missing-php-module + - title: No data appears + path: /docs/apm/agents/php-agent/troubleshooting/no-data-appears-php + - title: Performance issues from long running tasks + path: /docs/apm/agents/php-agent/troubleshooting/performance-issues-long-running-task + - title: Performance issues within AWS Fargate tasks + path: /docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact + - title: PHP Agent overhead reduction tips + path: /docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips - title: Protocol mismatch error path: /docs/apm/agents/php-agent/troubleshooting/protocol-mismatch-error - - title: INI settings not taking effect immediately - path: /docs/apm/agents/php-agent/troubleshooting/ini-settings-not-taking-effect-immediately + - title: Segmentation faults + path: /docs/apm/agents/php-agent/troubleshooting/segmentation-faults - title: Submitting troubleshooting results path: /docs/apm/agents/php-agent/troubleshooting/submitting-troubleshooting-results-php + - title: Symfony 4.4 overhead with opcache.preload + path: /docs/apm/agents/php-agent/troubleshooting/symfony44-performance - title: Threaded Apache worker MPMs path: /docs/apm/agents/php-agent/troubleshooting/threaded-apache-worker-mpms - title: Transactions /index.php or /unknown path: /docs/apm/agents/php-agent/troubleshooting/transactions-named-indexphp-or-unknown - - title: What the PHP instance count means - path: /docs/apm/agents/php-agent/troubleshooting/troubleshoot-php-agent-instance-count - title: Uninstrumented time in traces path: /docs/apm/agents/php-agent/troubleshooting/uninstrumented-time-traces - title: Using phpinfo to verify PHP path: /docs/apm/agents/php-agent/troubleshooting/using-phpinfo-verify-php - title: Verifying the PHP daemon path: /docs/apm/agents/php-agent/troubleshooting/verifying-php-daemon + - title: What the PHP instance count means + path: /docs/apm/agents/php-agent/troubleshooting/troubleshoot-php-agent-instance-count - title: When to restart your web server path: /docs/apm/agents/php-agent/troubleshooting/why-when-restart-your-web-server-php - - title: Performance Issues Within AWS Fargate Tasks - path: /docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact - - title: Performance Issues From Long Running Tasks - path: /docs/apm/agents/php-agent/troubleshooting/performance-issues-long-running-task - - title: Symfony 4.4 overhead with opcache.preload - path: /docs/apm/agents/php-agent/troubleshooting/symfony44-performance - - title: Segmentation faults - path: /docs/apm/agents/php-agent/troubleshooting/segmentation-faults - title: Python monitoring path: /docs/apm/agents/python-agent pages: From a43af5cc9d575611541d94d4245e82c68898f087 Mon Sep 17 00:00:00 2001 From: Zach Neumann Date: Mon, 21 Oct 2024 07:58:51 -0600 Subject: [PATCH 24/49] feat(php): release 11.3 --- .../php-release-notes/php-agent-11-3-0-16.mdx | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx diff --git a/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx new file mode 100644 index 00000000000..68453a26b35 --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx @@ -0,0 +1,37 @@ +--- +subject: PHP agent +releaseDate: '2024-10-21' +version: 11.3.0.16 +downloadLink: 'https://download.newrelic.com/php_agent/archive/11.3.0.16' +features: ['Memcached instance metrics with hostname'] +bugs: ['Fixes possible duplicate INI files on Debian', 'Fixes argument skipping during mysqli::real_connect''] +security: [] +--- + +## New Relic PHP agent v11.3.0.16 + +### New Features + +* Memcached instance metrics with host name + +### Bug Fixes + +* improve magic file recognition performance +* tarball installer checks for existing ini in mods-available directory +* don't skip arguments when calling `mysqli::real_connect` + * Huge thanks to @kovshenin for their community contribution!! + +### Support statement + +* New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our [PHP EOL policy](https://docs.newrelic.com/docs/apm/agents/php-agent/getting-started/php-agent-eol-policy/). +* The [PHP agent compatibility and requirements](https://docs.newrelic.com/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements/) page should be consulted for the latest information on supported PHP versions and platforms. + + + **For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.** This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. + + The PHP agent packages that are affected are: + + * newrelic-php5 + * newrelic-php5-common + * newrelic-daemon + From ed586e7f93a1068f95d52faa8ab3d7dd8a5e522f Mon Sep 17 00:00:00 2001 From: nbaenam Date: Mon, 21 Oct 2024 16:25:35 +0200 Subject: [PATCH 25/49] style(PHP agent): Added TW edits --- .../troubleshooting/agent-overhead-reduction-tips.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx index 50509e26c58..2ec55cb281f 100644 --- a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx +++ b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx @@ -13,12 +13,12 @@ freshnessValidatedDate: 2024-10-21 Using the New Relic PHP agent results in overhead. -## Explanation +## Cause Overhead is an expected side effect of monitoring and reporting on software. Our engineers aim to minimize this, but your experience may differ quite a lot, depending on how you're using the agent. If you find that you're experiencing unexpected overhead, there are are various settings in the `INI` that can help reduce it. -## INI Settings -Performance settings that can reduce overhead depending on your agent usage. +## Solution +Performance INI settings that can reduce overhead depending on your agent usage. 1. Reduce [`newrelic.span_events.max_samples_stored`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored) From a632f8548f4458168d93f9e47fa688ac270014ed Mon Sep 17 00:00:00 2001 From: Zach Neumann Date: Mon, 21 Oct 2024 08:32:06 -0600 Subject: [PATCH 26/49] fixes --- .../php-release-notes/php-agent-11-3-0-16.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx index 68453a26b35..efac407e4f6 100644 --- a/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx +++ b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx @@ -3,7 +3,7 @@ subject: PHP agent releaseDate: '2024-10-21' version: 11.3.0.16 downloadLink: 'https://download.newrelic.com/php_agent/archive/11.3.0.16' -features: ['Memcached instance metrics with hostname'] +features: ['Memcached instance metrics with hostname', 'Dockerized Daemon supports arm64'] bugs: ['Fixes possible duplicate INI files on Debian', 'Fixes argument skipping during mysqli::real_connect''] security: [] --- @@ -13,12 +13,13 @@ security: [] ### New Features * Memcached instance metrics with host name +* [Dockerized Daemon](https://github.com/newrelic/newrelic-php-daemon-docker) now supports arm64 ### Bug Fixes -* improve magic file recognition performance -* tarball installer checks for existing ini in mods-available directory -* don't skip arguments when calling `mysqli::real_connect` +* Improve magic file recognition performance +* Tarball installer checks for existing ini in mods-available directory +* Don't skip arguments when calling `mysqli::real_connect` * Huge thanks to @kovshenin for their community contribution!! ### Support statement From 18ec004ae485fec2a3872d6e33796ab44339f87a Mon Sep 17 00:00:00 2001 From: Zach Neumann Date: Mon, 21 Oct 2024 08:36:04 -0600 Subject: [PATCH 27/49] typo --- .../php-release-notes/php-agent-11-3-0-16.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx index efac407e4f6..5ba4aed620e 100644 --- a/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx +++ b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16.mdx @@ -4,7 +4,7 @@ releaseDate: '2024-10-21' version: 11.3.0.16 downloadLink: 'https://download.newrelic.com/php_agent/archive/11.3.0.16' features: ['Memcached instance metrics with hostname', 'Dockerized Daemon supports arm64'] -bugs: ['Fixes possible duplicate INI files on Debian', 'Fixes argument skipping during mysqli::real_connect''] +bugs: ['Fixes possible duplicate INI files on Debian', 'Fixes argument skipping during mysqli::real_connect'] security: [] --- From 68b429f5caf45ad2e92c6802b0c5ee769eb7e94e Mon Sep 17 00:00:00 2001 From: nbaenam Date: Mon, 21 Oct 2024 17:07:50 +0200 Subject: [PATCH 28/49] style(PHP agent): Added TW edits --- .../php-agent/troubleshooting/agent-overhead-reduction-tips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx index 2ec55cb281f..fd8f05616bb 100644 --- a/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx +++ b/src/content/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx @@ -20,7 +20,7 @@ Overhead is an expected side effect of monitoring and reporting on software. Our ## Solution Performance INI settings that can reduce overhead depending on your agent usage. -1. Reduce [`newrelic.span_events.max_samples_stored`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored) +1. Reduce [`newrelic.span_events.max_samples_stored`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored). 2. Disable [code level metrics](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-code-level-metrics). From 329a66836fd6efae4c17c02d4586fd9b1f4e2cef Mon Sep 17 00:00:00 2001 From: Paolo Gallina Date: Mon, 21 Oct 2024 17:43:21 +0200 Subject: [PATCH 29/49] fix(discovery): fix docs related to discovery --- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../container-auto-discovery-host-integrations.mdx | 5 +++-- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 ++- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 ++- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 ++- .../monitor-services-running-amazon-ecs.mdx | 4 ++-- .../not-seeing-infrastructure-integration-data.mdx | 2 +- .../container-auto-discovery-host-integrations.mdx | 3 ++- 14 files changed, 25 insertions(+), 20 deletions(-) diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 707777505d4..68668a97059 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -284,7 +284,7 @@ Here's a detailed example of doing the above procedure for NGINX: integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${discovery.ip}:${discovery.port}/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -311,7 +311,7 @@ Here's a detailed example of doing the above procedure for NGINX: integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${discovery.ip}:${discovery.port}/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index e71d5f0b81b..2f7c961c0f8 100644 --- a/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/content/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -46,10 +46,10 @@ These examples (for Docker-only environments and for Kubernetes) show how to con integrations: - name: nri-nginx env: - # use discovery.private.ip if container doesn't have attached public ip address + # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status - STATUS_MODULE: discover REMOTE_MONITORING: true + METRICS: 1 labels: env: ${discovery.label.env} role: ${discovery.label.role} @@ -93,6 +93,7 @@ These examples (for Docker-only environments and for Kubernetes) show how to con env: # Use the discovered IP as the host address STATUS_URL: http://${discovery.ip}/server-status?auto + REMOTE_MONITORING: true METRICS: 1 ``` diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index a57ee646a34..285923b2c51 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ A continuación se muestra un ejemplo detallado de cómo realizar el procedimien integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ A continuación se muestra un ejemplo detallado de cómo realizar el procedimien integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index 6535540de8d..f3c0bdd61d8 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ Para solucionar y resolver el problema: ``` - nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index ac5db6ce28f..a512e152564 100644 --- a/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/es/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,7 +37,8 @@ Estos ejemplos (para entornos solo docker y para Kubernetes) muestran cómo conf image: /nginx/ label.env: production integrations: - - name: nri-nginx + - name: nginx-server-metrics + command: metrics env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 723fef72a1e..18acd8a2ace 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ ECSで動作しているサービスのモニタリングを有効にする方 integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ ECSで動作しているサービスのモニタリングを有効にする方 integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index 578e1dbb328..c9be68ffb2d 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -143,7 +143,7 @@ translationType: machine ``` - nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index bde8e53ed9f..8980b88d5fd 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,7 +37,8 @@ translationType: machine image: /nginx/ label.env: production integrations: - - name: nri-nginx + - name: nginx-server-metrics + command: metrics env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 87c2f2805cd..ac7f783bfe8 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -329,7 +329,7 @@ NGINX에 대해 위의 절차를 수행하는 자세한 예는 다음과 같습 integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -364,7 +364,7 @@ NGINX에 대해 위의 절차를 수행하는 자세한 예는 다음과 같습 integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index f1221e13382..14b0aef4c8c 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ translationType: machine ``` - nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index 94f7ef8752f..afbd8b06fa8 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,7 +37,8 @@ translationType: machine image: /nginx/ label.env: production integrations: - - name: nri-nginx + - name: nginx-server-metrics + command: metrics env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx index 0d8b633a8a8..f8eb7231c82 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs.mdx @@ -335,7 +335,7 @@ Aqui está um exemplo detalhado de como executar o procedimento acima para NGINX integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 ``` @@ -370,7 +370,7 @@ Aqui está um exemplo detalhado de como executar o procedimento acima para NGINX integrations: - name: nri-nginx env: - STATUS_URL: http://${discovery.ip}:/status + STATUS_URL: http://${'${discovery.ip}'}:/status REMOTE_MONITORING: true METRICS: 1 path: /etc/newrelic-infra/integrations.d/nginx-config.yml diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx index a5957df8bce..3748ed316fe 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/troubleshooting/not-seeing-infrastructure-integration-data.mdx @@ -142,7 +142,7 @@ Para solucionar e resolver o problema: ``` - nri-nginx: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": + nginx-server-metrics: {\"name\":\"com.newrelic.nginx\",\"protocol_version\":\"1\",\"integration_version\":\"0.5.0\",\"metrics\": [{\"event_type\":\"NginxSample\",\"net.connectionsAcceptedPerSecond\":0.10344827586206896,\"net.connectionsActive\":1, \"net.connectionsDroppedPerSecond\":0,\"net.connectionsReading\":0,\"net.connectionsWaiting\":0,\"net.connectionsWriting\":1, \"net.requestsPerSecond\":0.10344827586206896,\"software.edition\":\"open source\",\"software.version\":\"1.4.6 (Ubuntu)\"}],\"inventory\":{},\"events\":[]} diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx index e30f6775853..27bee6c7fd1 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/installation/container-auto-discovery-host-integrations.mdx @@ -37,7 +37,8 @@ Estes exemplos (para ambientes Docker-only e para Kubernetes) mostram como confi image: /nginx/ label.env: production integrations: - - name: nri-nginx + - name: nginx-server-metrics + command: metrics env: # use discovery.private.ip if container doesn't have attached public ip address STATUS_URL: http://${discovery.ip}:${discovery.port}/status From 1cc89563e99aad4bd6d8ab945f367a4307706a19 Mon Sep 17 00:00:00 2001 From: Saket Chaudhary Date: Mon, 21 Oct 2024 22:27:33 +0530 Subject: [PATCH 30/49] Add example for CDK Lambda instrumentation --- .../instrument-your-own.mdx | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index 42ca4f8c2b3..f078017d3c9 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -26,6 +26,7 @@ New Relic offers several methods to instrument your AWS Lambda functions for com * **Command Line Interface (CLI)**: Use the AWS CLI to quickly add the New Relic layer to your Lambda functions. * **Serverless Framework**: Seamlessly integrate New Relic instrumentation into your serverless deployments. * **CloudFormation/SAM**: Include the New Relic layer in your infrastructure-as-code templates. +* **AWS CDK**: Add New Relic Lambda layer in your CDK code alongside other infrastructure resources. * **Terraform**: Easily manage New Relic instrumentation alongside your other infrastructure resources. * **Manual Instrumentation**: Directly add the New Relic layer through the AWS Lambda console for more granular control. @@ -137,6 +138,46 @@ Depending on your needs, you can choose to either bypass the extension and only ``` + + The AWS Cloud Development Kit (AWS CDK) is a framework for defining cloud resources in code and provisioning it through AWS CloudFormation. + + Below is an example of a basic CDK app that deploys a New Relic instrumented Node.js Lambda function: + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromInline(` + exports.handler = async function(event) { + return { + statusCode: 200, + body: JSON.stringify('Hello World!'), + }; + }; + `), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path to your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + }, + }); + } + } + ``` + + Date: Mon, 21 Oct 2024 23:28:07 +0530 Subject: [PATCH 31/49] modify inline code to code from asset --- .../instrument-your-own.mdx | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index f078017d3c9..156c55a329c 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -159,17 +159,10 @@ Depending on your needs, you can choose to either bypass the extension and only runtime: lambda.Runtime.NODEJS_20_X, // Update functions handler to point to the New Relic Lambda wrapper handler: "newrelic-lambda-wrapper.handler", - code: lambda.Code.fromInline(` - exports.handler = async function(event) { - return { - statusCode: 200, - body: JSON.stringify('Hello World!'), - }; - }; - `), + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], environment: { - // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path to your initial handler. + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. NEW_RELIC_LAMBDA_HANDLER: 'index.handler', }, }); From 1268da4835150751b67fd47b8fda35aa5f686cf6 Mon Sep 17 00:00:00 2001 From: Kayla Reopelle Date: Mon, 21 Oct 2024 16:19:46 -0700 Subject: [PATCH 32/49] chore: Add missing "to" --- .../new-relic-logs/logs-plugin-licenses.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx b/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx index 65ede4c620a..bfef6b0e909 100644 --- a/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx +++ b/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx @@ -216,7 +216,7 @@ The following licenses are for the plugins used to connects your log data with N ## Go plugins for Logs [#go-logs] -The following licenses are for the plugins used link your logs and APM data using New Relic's Go agent. For Go licenses, see [Go agent licenses](/docs/licenses/license-information/agent-licenses/go-agent-licenses). +The following licenses are for the plugins used to link your logs and APM data using New Relic's Go agent. For Go licenses, see [Go agent licenses](/docs/licenses/license-information/agent-licenses/go-agent-licenses). Date: Mon, 21 Oct 2024 17:24:03 -0700 Subject: [PATCH 33/49] Add alternate privatelink endpoint for infra in the EU There are two supported endpoints for infra in the EU, and only one was included in the public docs previously. This commit adds the second endpoint. --- src/content/docs/data-apis/custom-data/aws-privatelink.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/data-apis/custom-data/aws-privatelink.mdx b/src/content/docs/data-apis/custom-data/aws-privatelink.mdx index 0dc8cee00db..167be7f2865 100644 --- a/src/content/docs/data-apis/custom-data/aws-privatelink.mdx +++ b/src/content/docs/data-apis/custom-data/aws-privatelink.mdx @@ -776,11 +776,11 @@ These are the New Relic endpoint services available via AWS PrivateLink: - `infra-api.eu01.nr-data.net` + `infra-api.eu01.nr-data.net` and `infra-api.eu.newrelic.com` - `com.amazonaws.vpce.eu-central-1.vpce-svc-06d5b2d7e79ddd78e` + `com.amazonaws.vpce.eu-central-1.vpce-svc-06d5b2d7e79ddd78e` and `com.amazonaws.vpce.eu-central-1.vpce-svc-02fc7dd8d7be95a32`, respectively From bb48bfb3d403a0fd04fcfaa482298a2b3b8a0eeb Mon Sep 17 00:00:00 2001 From: Qryuu Date: Tue, 22 Oct 2024 18:21:46 +0900 Subject: [PATCH 34/49] Ktranslate log severity The severity of the Ktranslate log has been added. --- .../advanced/ktranslate-container-health.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx b/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx index 3ebc0c982ae..01e869adfe7 100644 --- a/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx +++ b/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx @@ -110,7 +110,11 @@ Below are some common searches that can be used during troubleshooting to gather ```shell KTranslate>cisco-7513 There was an SNMP polling error with the CustomDeviceMetrics walking OID .1.3.6.1.2.1.4.31.1.1.21 after 0 retries: request timeout (after 0 retries). ``` - + + Ktranslate has the following log severity levels: Info, Warn, and Error. + + + Date: Tue, 22 Oct 2024 11:50:53 +0200 Subject: [PATCH 35/49] style(Logs): Added TW edits --- .../new-relic-logs/logs-plugin-licenses.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx b/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx index bfef6b0e909..9982b057692 100644 --- a/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx +++ b/src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx @@ -216,7 +216,7 @@ The following licenses are for the plugins used to connects your log data with N ## Go plugins for Logs [#go-logs] -The following licenses are for the plugins used to link your logs and APM data using New Relic's Go agent. For Go licenses, see [Go agent licenses](/docs/licenses/license-information/agent-licenses/go-agent-licenses). +The following licenses are for the plugins used to link your logs and data using New Relic's Go agent. For Go licenses, see [Go agent licenses](/docs/licenses/license-information/agent-licenses/go-agent-licenses). Date: Tue, 22 Oct 2024 12:19:25 +0200 Subject: [PATCH 36/49] style(Network): Added a minor TW edit --- .../advanced/ktranslate-container-health.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx b/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx index 01e869adfe7..bb8f47bf0b4 100644 --- a/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx +++ b/src/content/docs/network-performance-monitoring/advanced/ktranslate-container-health.mdx @@ -111,7 +111,7 @@ Below are some common searches that can be used during troubleshooting to gather KTranslate>cisco-7513 There was an SNMP polling error with the CustomDeviceMetrics walking OID .1.3.6.1.2.1.4.31.1.1.21 after 0 retries: request timeout (after 0 retries). ``` - Ktranslate has the following log severity levels: Info, Warn, and Error. + Ktranslate has the following log severity levels: `Info`, `Warn`, and `Error`. From c3436f9ab777838e013752b125f68601fa5c6dac Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Tue, 22 Oct 2024 12:05:21 +0000 Subject: [PATCH 37/49] chore: add translations --- .../docs/apis/rest-api-v2/migrate-to-nrql.mdx | 92 +++++++++ .../net-agent-compatibility-requirements.mdx | 39 ++-- .../net-agent/net-agent-api/net-agent-api.mdx | 139 +++++++++++++ .../agent-not-starting-there-are-no-logs.mdx | 4 +- .../incorrect-data-reported.mdx | 52 ++--- ...ce-infrastructure-agents-cpu-footprint.mdx | 32 ++- .../time-gaps-missing-data.mdx | 48 ++--- .../k8s-version2/overview.mdx | 25 +-- .../enable-log-management-new-relic.mdx | 32 ++- .../kubernetes-plugin-log-forwarding.mdx | 10 +- .../docs/logs/get-started/live-archives.mdx | 4 +- .../net-agent-compatibility-requirements.mdx | 35 ++-- .../blazor-webassembly.mdx | 14 +- .../analyze-monitor-data-trends-metrics.mdx | 82 ++------ .../create-metrics-other-data-types.mdx | 35 +--- .../jp/docs/iast/iast-configuration.mdx | 188 +++++++++--------- .../content/jp/docs/iast/troubleshooting.mdx | 151 ++++---------- ...te-logs-troubleshooting-infrastructure.mdx | 13 +- .../infrastructure-agent-logging-behavior.mdx | 24 +-- ...structure-agent-configuration-settings.mdx | 166 ++++++++-------- ...ual-install-infrastructure-agent-linux.mdx | 79 ++------ ...-infrastructure-monitoring-agent-macos.mdx | 22 +- .../uninstall-infrastructure-agent.mdx | 54 ++--- .../uninstall-infrastructure-integrations.mdx | 52 ++--- ...d-install-infrastructure-agent-windows.mdx | 16 +- ...l-install-infrastructure-agent-windows.mdx | 12 +- .../agent-not-starting-there-are-no-logs.mdx | 4 +- .../incorrect-data-reported.mdx | 52 ++--- ...ce-infrastructure-agents-cpu-footprint.mdx | 32 ++- .../time-gaps-missing-data.mdx | 48 ++--- .../k8s-version2/overview.mdx | 25 +-- .../installation/k8s-agent-operator.mdx | 18 +- .../kubernetes-plugin-log-forwarding.mdx | 10 +- .../instrument-your-own.mdx | 59 ++---- .../docs/apis/rest-api-v2/migrate-to-nrql.mdx | 92 +++++++++ .../net-agent-compatibility-requirements.mdx | 35 ++-- .../net-agent/net-agent-api/net-agent-api.mdx | 139 +++++++++++++ .../configuration/php-agent-configuration.mdx | 2 +- .../blazor-webassembly.mdx | 14 +- .../analyze-monitor-data-trends-metrics.mdx | 86 ++------ .../create-metrics-other-data-types.mdx | 35 +--- .../kr/docs/iast/iast-configuration.mdx | 188 +++++++++--------- .../content/kr/docs/iast/troubleshooting.mdx | 153 ++++---------- .../no-data-appears-infrastructure.mdx | 24 +-- ...te-logs-troubleshooting-infrastructure.mdx | 13 +- .../infrastructure-agent-logging-behavior.mdx | 24 +-- ...ual-install-infrastructure-agent-linux.mdx | 79 ++------ ...-infrastructure-monitoring-agent-macos.mdx | 22 +- .../uninstall-infrastructure-agent.mdx | 54 ++--- .../uninstall-infrastructure-integrations.mdx | 52 ++--- .../update-infrastructure-agent.mdx | 2 +- ...d-install-infrastructure-agent-windows.mdx | 16 +- ...l-install-infrastructure-agent-windows.mdx | 12 +- .../agent-not-starting-there-are-no-logs.mdx | 4 +- .../incorrect-data-reported.mdx | 52 ++--- ...ce-infrastructure-agents-cpu-footprint.mdx | 32 ++- .../time-gaps-missing-data.mdx | 48 ++--- .../k8s-version2/overview.mdx | 25 +-- .../installation/k8s-agent-operator.mdx | 18 +- .../kubernetes-plugin-log-forwarding.mdx | 10 +- .../instrument-your-own.mdx | 59 ++---- .../docs/apis/rest-api-v2/migrate-to-nrql.mdx | 92 +++++++++ .../net-agent-compatibility-requirements.mdx | 35 ++-- .../net-agent/net-agent-api/net-agent-api.mdx | 139 +++++++++++++ .../configuration/php-agent-configuration.mdx | 2 +- .../blazor-webassembly.mdx | 14 +- .../analyze-monitor-data-trends-metrics.mdx | 84 ++------ .../create-metrics-other-data-types.mdx | 33 +-- .../pt/docs/iast/iast-configuration.mdx | 188 +++++++++--------- .../content/pt/docs/iast/troubleshooting.mdx | 151 ++++---------- .../no-data-appears-infrastructure.mdx | 24 +-- ...te-logs-troubleshooting-infrastructure.mdx | 13 +- .../infrastructure-agent-logging-behavior.mdx | 24 +-- ...structure-agent-configuration-settings.mdx | 166 ++++++++-------- ...ual-install-infrastructure-agent-linux.mdx | 79 ++------ ...-infrastructure-monitoring-agent-macos.mdx | 22 +- .../uninstall-infrastructure-agent.mdx | 54 ++--- .../uninstall-infrastructure-integrations.mdx | 52 ++--- .../update-infrastructure-agent.mdx | 2 +- ...d-install-infrastructure-agent-windows.mdx | 16 +- ...l-install-infrastructure-agent-windows.mdx | 12 +- .../agent-not-starting-there-are-no-logs.mdx | 4 +- .../incorrect-data-reported.mdx | 52 ++--- ...ce-infrastructure-agents-cpu-footprint.mdx | 32 ++- .../time-gaps-missing-data.mdx | 48 ++--- .../k8s-version2/overview.mdx | 25 +-- .../installation/k8s-agent-operator.mdx | 18 +- .../enable-log-management-new-relic.mdx | 32 ++- .../kubernetes-plugin-log-forwarding.mdx | 10 +- .../docs/logs/get-started/live-archives.mdx | 4 +- .../instrument-your-own.mdx | 57 ++---- 91 files changed, 2059 insertions(+), 2383 deletions(-) create mode 100644 src/i18n/content/es/docs/apis/rest-api-v2/migrate-to-nrql.mdx create mode 100644 src/i18n/content/kr/docs/apis/rest-api-v2/migrate-to-nrql.mdx create mode 100644 src/i18n/content/pt/docs/apis/rest-api-v2/migrate-to-nrql.mdx diff --git a/src/i18n/content/es/docs/apis/rest-api-v2/migrate-to-nrql.mdx b/src/i18n/content/es/docs/apis/rest-api-v2/migrate-to-nrql.mdx new file mode 100644 index 00000000000..fc7e2c8a147 --- /dev/null +++ b/src/i18n/content/es/docs/apis/rest-api-v2/migrate-to-nrql.mdx @@ -0,0 +1,92 @@ +--- +title: Migrar a NRQL +tags: + - APIs + - REST API v2 + - NRQL +metaDescription: How to migrate your REST API v2 queries to NRQL queries. +freshnessValidatedDate: never +translationType: machine +--- + +## Lista de nombres métricos para tu aplicación + +Para ver los nombres métricos disponibles para su aplicación: + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appId = '$APP_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +También puedes filtrar empleando el nombre de la aplicación: + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appName = '$APP_NAME' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +O empleando un agente específico (host): + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE realAgentId = '$AGENT_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +## Obtenga los valores de datos de intervalo de tiempo de métrica de su aplicación + +La REST API v2 acepta una lista de nombres métricos y una lista de valores para recuperar datos de intervalo de tiempo de métrico. + +Los nombres de las métricas son los mismos, puedes filtrarlos con el campo `metricTimesliceName` en tu consulta NRQL . + +Cada valor de API se puede asignar a una función NRQL, puede consultar la siguiente tabla. + +Ejemplo, para la siguiente solicitud API: + +```bash +curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \ + -H "X-Api-Key:${API_KEY}" -i \ + -d 'names[]=HttpDispatcher&values[]=average_call_time&values[]=call_count' +``` + +Emplearías la siguiente consulta: + +```nrql +SELECT COUNT(newrelic.timeslice.value) AS call_count, average(newrelic.timeslice.value) * 1000 AS average_call_time +FROM Metric +WHERE appId = $APP_ID AND metricTimesliceName = 'HttpDispatcher' +``` + +| Value (RPM) | NRQL Function | | -------------------------- | ------------------------------------------------------------------------------------------------- | | average\_response\_time | average(newrelic.timeslice.value) \* 1000 | | calls\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | call\_count | count(newrelic.timeslice.value) | | min\_response\_time | min(newrelic.timeslice.value) \* 1000 | | max\_response\_time | max(newrelic.timeslice.value) \* 1000 | | average\_exclusive\_time | average(newrelic.timeslice.value\['totalExclusive'] / newrelic.timeslice.value\['count']) \* 1000 | | average\_value | average(newrelic.timeslice.value) | | total\_call\_time\_per\_minute | rate(sum(newrelic.timeslice.value), 1 minute) | | requests\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | standard\_deviation | stddev(newrelic.timeslice.value) \* 1000 | | average\_time | average(newrelic.timeslice.value) \* 1000 | | count | count(newrelic.timeslice.value) | | used\_bytes\_by\_host | average(newrelic.timeslice.value) \* 1024 \* 1024 | | used\_mb\_by\_host | average(newrelic.timeslice.value) | | total\_used\_mb | sum(newrelic.timeslice.value) | | average\_call\_time | average(newrelic.timeslice.value) \* 1000 | | total\_value | sum(newrelic.timeslice.value) | | min\_value | min(newrelic.timeslice.value) | | max\_value | max(newrelic.timeslice.value) | | rate | rate(sum(newrelic.timeslice.value), 1 second) | | throughput | rate(count(newrelic.timeslice.value), 1 second) | | as\_percentage | average(newrelic.timeslice.value) \* 100 | | errors\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | error\_count | count(newrelic.timeslice.value) | | total\_time | sum(newrelic.timeslice.value) \* 1000 | | sessions\_active | average(newrelic.timeslice.value) | | total\_visits | sum(newrelic.timeslice.value) | | percent | average(newrelic.timeslice.value) \* 100 | | percent (`CPU/User Time`) | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | time\_percentage | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | utilization | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | visits\_percentage | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | + +Si la función incluye `$TIME_WINDOW_IN_SECONDS`, significa que debes reemplazarla con la ventana de tiempo que deseas consultar. + +Por ejemplo, si consulta un intervalo de tiempo de 30 minutos, reemplazará `$TIME_WINDOW_IN_SECONDS` por `1800`. + +### Apdex métricas + +| Value (RPM) | NRQL Function | | ------------- | ---------------------------------------------------------------------------------- | | score | apdex(newrelic.timeslice.value) | | s | apdex(newrelic.timeslice.value) or count(newrelic.timeslice.value) | | t | apdex(newrelic.timeslice.value) or sum(newrelic.timeslice.value) | | f | apdex(newrelic.timeslice.value) or sum(newrelic.timeslice.value\['totalExclusive']) | | count | apdex(newrelic.timeslice.value) | | value | apdex(newrelic.timeslice.value) | | threshold | max(newrelic.timeslice.value) | | threshold\_min | min(newrelic.timeslice.value) | + +### Métricas para EndUser & Mobile + +Estas métricas devolverán el mismo resultado que obtendría de la REST API v2, pero algunos resultados pueden diferir de lo que ve en la New Relic UI. Esto se debe a que la UI emplea evento en lugar de datos de intervalo de tiempo. Si desea obtener los mismos resultados que la UI, debe consultar el evento directamente. + +| Value (RPM) | NRQL Function | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | average\_response\_time | sum(newrelic.timeslice.value) / count(newrelic.timeslice.value) \* 1000 | | error\_percentage | (filter(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'EndUser/errors') / filter(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Browser')) | | average\_fe\_response\_time | sum(newrelic.timeslice.value\['totalExclusive']) / count(newrelic.timeslice.value) \* 1000 | | average\_be\_response\_time | 1000 \* (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive'])) / count(newrelic.timeslice.value) | | average\_network\_time | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) / count(newrelic.timeslice.value) | | total\_network\_time | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) | | network\_time\_percentage | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) / `$TIME_WINDOW_IN_SECONDS` | | total\_fe\_time | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) | | fe\_time\_percentage | 100 \* sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) / `$TIME_WINDOW_IN_SECONDS` | | average\_dom\_content\_load\_time | average(newrelic.timeslice.value) \* 1000 | | average\_queue\_time | average(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | total\_queue\_time | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | total\_dom\_content\_time | sum(newrelic.timeslice.value) \* 1000 | | total\_app\_time | sum(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) | | average\_app\_time | sum(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) / count(newrelic.timeslice.value) | | average\_sent\_bytes | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | average\_received\_bytes | 1000 \* sum(newrelic.timeslice.value) / count(newrelic.timeslice.value) | | launch\_count | count(newrelic.timeslice.value) | + +### Seriales temporales y resúmenes + +De forma predeterminada, la API REST devuelve un serial de valores de datos métricos basados. Para obtener el promedio de estos valores, deberá incluir `&summarize=true` en su llamada API. + +En NRQL, ocurre lo opuesto. Obtendrás un resumen de forma predeterminada y puedes obtener el serial temporal agregando `TIMESERIES` a tu consulta. + +Otra diferencia es que la ventana de tiempo predeterminada de la API REST es de 30 minutos, mientras que en NRQL es de 1 hora. + +## Consulta multiple metricas + +Aún puedes consultar múltiples métricas a la vez con NRQL, aquí hay un ejemplo: + +```nrql +SELECT + FILTER(1000 * AVERAGE(newrelic.timeslice.value), WHERE metricTimesliceName = 'HttpDispatcher') as average_response_time, + FILTER(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Errors/all') as error_count, + FILTER(average(newrelic.timeslice.value), WHERE metricTimesliceName = 'Memory/Heap/Max') as used_mb_by_host +FROM Metric +WHERE appName = '$APP_NAME' +SINCE 1 day ago +``` \ No newline at end of file diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 7fc0453cc63..c771e5f3981 100644 --- a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -331,7 +331,8 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum El agente .NET `v9.2.0` o superior instrumentó automáticamente la biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versión mínima admitida: 3.17.0 - * Última versión compatible verificada: 3.23.0 + * Última versión compatible verificada: 3.44.0 + * Las versiones 3.35.0 y superiores son compatibles a partir del agente .NET v10.32.0 @@ -372,7 +373,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Emplee [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/) * Versión mínima compatible: 23.4.0 - * Última versión compatible verificada: 23.5.1 + * Última versión compatible verificada: 23.6.0 Es posible que se instrumentaron versiones anteriores de `Oracle.ManagedDataAccess.Core` , pero no se probaron y no reciben soporte. @@ -409,7 +410,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 2.3.0 - Última versión compatible verificada: 2.26.0 + Última versión compatible verificada: 2.29.0 A partir de la versión 10.12.0 del agente, se instrumentan los siguientes métodos agregados en la versión 2.7 del controlador o después: @@ -478,7 +479,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum **Elastic.Clients.Elasticsearch** * Versión mínima admitida: 8.0.0 - * Última versión compatible verificada: 8.14.6 + * Última versión compatible verificada: 8.15.8 * Se admiten las versiones 8.10.0 y superiores a partir del agente .NET v10.20.1 * Las versiones 8.12.1 y superiores son compatibles a partir del agente .NET v10.23.0 @@ -596,7 +597,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 3.7.403.4 + 3.7.404.5 @@ -660,7 +661,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 3.1.1 + 4.0.1 @@ -678,7 +679,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 5.3.2 + 5.3.14 @@ -696,7 +697,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 8.0.0 + 8.0.1 @@ -790,7 +791,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 7.1.0 - * Última versión compatible verificada: 8.1.1 + * Última versión compatible verificada: 8.2.5 @@ -804,7 +805,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Última versión compatible verificada: 3.7.400.19 + * Última versión compatible verificada: 3.7.400.33 @@ -840,7 +841,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - [monitoreo del navegador](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser) + [Monitoreo del navegador](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser) @@ -1249,7 +1250,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 2.3.0 - Última versión compatible verificada: 2.26.0 + Última versión compatible verificada: 2.29.0 A partir de la versión 10.12.0 del agente, se instrumentan los siguientes métodos agregados en la versión 2.7 del controlador o después: @@ -1465,7 +1466,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 105.2.3 - Última versión compatible verificada: 111.4.0 + Última versión compatible verificada: 112.1.0 Versiones incompatibles conocidas: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -1541,7 +1542,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 3.7.403.4 + 3.7.404.5 @@ -1605,7 +1606,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 3.1.1 + 4.0.1 @@ -1623,7 +1624,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - 5.3.2 + 5.3.14 @@ -1741,7 +1742,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 7.1.0 - * Última versión compatible verificada: 8.1.1 + * Última versión compatible verificada: 8.2.5 @@ -1755,7 +1756,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Última versión compatible verificada: 3.7.400.19 + * Última versión compatible verificada: 3.7.400.33 @@ -1863,7 +1864,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - [monitoreo del navegador](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/) + [Monitoreo del navegador](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/) diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx index 34c0cb43095..e62ddd1e2e5 100644 --- a/src/i18n/content/es/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx +++ b/src/i18n/content/es/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx @@ -472,6 +472,16 @@ La siguiente lista contiene las diferentes llamadas que puede realizar con la AP Asocia un ID de usuario a la transacción actual (ver a continuación para más detalles). + + + + `RecordDatastoreSegment` + + + + Permite instrumentar un almacenamiento de datos no compatible (consulte a continuación para obtener más detalles). + + @@ -975,6 +985,135 @@ La siguiente lista contiene las diferentes llamadas que puede realizar con la AP transaction.SetUserId("BobSmith123"); ``` + + + ### Sintaxis + + ```cs + SegmentWrapper? RecordDatastoreSegment(string vendor, string model, string operation, string? commandText = null, string? host = null, string? portPathOrID = null, string? databaseName = null) + ``` + + Permite instrumentar un almacenamiento de datos no compatible de la misma manera que el agente .NET instrumenta automáticamente sus almacenes de datos compatibles. + + Este método requiere el agente .NET y la API del agente .NET [versión 10.22.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-22-0/) o superior. + + ### Parámetros + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parámetro + + Descripción +
+ `vendor` + + *cadena* + + Nombre del proveedor de almacenamiento de datos, como MySQL, MSSQL o MongoDB. +
+ `model` + + *cadena* + + Nombre de la tabla, o identificador similar en un almacenamiento de datos no relacional. +
+ `operation` + + *cadena* + + Operación que se está realizando, como “SELECT” o “UPDATE” para base de datos SQL. +
+ `commandText` + + *¿cadena?* + + Opcional. Consulta, o descriptor similar en un almacenamiento de datos no relacional. +
+ `host` + + *¿cadena?* + + Opcional. Servidor que aloja el almacenamiento de datos. +
+ `portPathOrID` + + *¿cadena?* + + Opcional. Puerto, ruta u otro identificador, emparejado con el host para ayudar a identificar el almacenamiento de datos. +
+ `databaseName` + + *¿cadena?* + + Opcional. Nombre del almacenamiento de datos o identificador similar. +
+ + ### Devoluciones + + Contenedor de segmento desechable que crea y finaliza el segmento automáticamente. + + ### Ejemplo + + ```cs + var transaction = NewRelic.Api.Agent.NewRelic.GetAgent().CurrentTransaction; + using (transaction.RecordDatastoreSegment(vendor, model, operation, + commandText, host, portPathOrID, databaseName)) + { + DatastoreWorker(); + } + ``` + diff --git a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx index ec1fc86c28d..b8dd5d5f11a 100644 --- a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx +++ b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx @@ -44,6 +44,6 @@ Para resolver esto, pruebe una de estas opciones: * Cambie la entrada `log_file` en el archivo de configuración `/etc/newrelic-infra.yml` . Nuestro script de instalación crea la carpeta `/var/log/newrelic-infra/` para ese propósito, por lo que recomendamos el siguiente valor: - ``` + ```yml log_file: /var/log/newrelic-infra/newrelic-infra.log - ``` + ``` \ No newline at end of file diff --git a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx index 29f87367a88..c4c27f5edc0 100644 --- a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx +++ b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx @@ -19,63 +19,51 @@ El agente de infraestructura incluye un registro de nivel de traza que se puede 1. Edite el archivo de configuración [newrelic-infra.yml](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#logging-variables) y agregue los indicadores necesarios para habilitar el registro. Por ejemplo, para habilitar todos los registros de traza en la ruta predeterminada del archivo de registro: - ``` - log: - level: trace + ```yml + log: + level: trace ``` La versión 1.26.0 o anterior del agente de infraestructura requiere una configuración de registro diferente: -``` - verbose: 1 - trace: - # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. - - v3.submission - # dm.submission enables detailed logging for integrations using Dimensional Metric format. - - dm.submission +```yml +verbose: 1 +trace: + # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. + - v3.submission + # dm.submission enables detailed logging for integrations using Dimensional Metric format. + - dm.submission ``` 2. Utilice [su sistema de inicio](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) para reiniciar el servicio del agente: - + Utilice comandos SystemD con CentOS 7, Debian 8, RHEL 7 y Ubuntu 15.04 o superior: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Utilice comandos de System V con Debian 7: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Utilice comandos Upstart con Amazon Linux, CentOS 6, RHEL 6 y Ubuntu 14.10 o anterior: - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -86,9 +74,9 @@ La versión 1.26.0 o anterior del agente de infraestructura requiere una configu Ejemplo log cuando v3.submission está habilitado: -``` +```log time="2021-12-28T09:27:28Z" level=debug msg="Sending events to metrics-ingest." component=MetricsIngestSender key=... numEvents=3 postCount=1 timestamps="[2021-01-01 09:27:28 +0000 UTC]" time="2021-12-28T09:27:28Z" level=debug msg="Preparing metrics post." component=MetricsIngestSender postCount=1 time="2021-12-28T09:27:28Z" level=trace msg="[{\"EntityID\":111,\"IsAgent\":true,\"Events\":[{\"eventType\":\"SystemSample\",\"timestamp\":1640683648,\"entityKey\":\"...\",\"cpuPercent\":0.2004008016032026, ...}]" feature=v3.submission time="2021-12-28T09:27:29Z" level=debug msg="Metrics post succeeded." component=MetricsIngestSender postCount=1 -``` +``` \ No newline at end of file diff --git a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx index 8e521ffa611..003b6c803d6 100644 --- a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx +++ b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx @@ -110,22 +110,19 @@ La siguiente tabla enumera algunos muestreadores para configurar: -### Reducir los informes del complemento del agente [#reduce_plugins] +### Reducir los informes del complemento del agente [#reduce\_plugins][#reduce_plugins] El agente de infraestructura tiene un complemento incorporado que recopila datos de inventario (configuración específica del sistema e información de estado). Para algunos sistemas, el consumo de CPU puede ser relativamente alto si el complemento recopila muchos datos. Para reducir el espacio, puede deshabilitar o disminuir la frecuencia de muestreo para complementos específicos que informan datos que no desea. - + * **Disable a single plugin:** Para deshabilitar un complemento, establezca el valor de propiedad correspondiente en `-1`. * **Disable all plugins:** `disable_all_plugins: true` * **Enable selected plugins:** Para habilitar determinado complemento, inserte una excepción en `disable_all_plugins`. Por ejemplo, la siguiente configuración desactiva todos los complementos y vuelve a habilitar las interfaces de red y el complemento SELinus para informar cada 120 segundos: - ``` + ```yml disable_all_plugins: true network_interface_interval_sec: 120 selinux_interval_sec: 120 @@ -134,7 +131,10 @@ El agente de infraestructura tiene un complemento incorporado que recopila datos Deshabilitar SELinux semodule -l (solo Linux)} + title={<>Deshabilitar SELinux + semodule -l + (solo Linux) + } > El complemento SELinux invoca periódicamente el comando del sistema `semodule -l` para obtener información sobre los módulos SELinux existentes. En la mayoría de las distribuciones CentOS/RedHat, este comando generará picos de consumo de CPU. @@ -143,33 +143,27 @@ El agente de infraestructura tiene un complemento incorporado que recopila datos `selinux_enable_semodule: false` - + El complemento Sysctl recorre toda la estructura del directorio `/sys` y lee los valores de todos los archivos allí. Deshabilitarlo o reducir el intervalo puede disminuir parte del tiempo del sistema de CPU en el agente de infraestructura. Puede deshabilitar la frecuencia del inventario configurándola en un número negativo o reducir la frecuencia estableciendo el valor de configuración `sysctl_interval_sec` en la cantidad de segundos entre ejecuciones consecutivas del complemento. Por ejemplo, para ejecutar el complemento una vez cada 10 minutos: - ``` + ```yml sysctl_interval_sec: 600 ``` Para desactivar el complemento Sysctl: - ``` + ```yml sysctl_interval_sec: -1 ``` El valor predeterminado actual para la propiedad `sysctl_interval_sec` es `60`. - + Los siguientes complementos de inventario no consumen especialmente CPU, pero aún puedes reducir su frecuencia o deshabilitarlos configurando las opciones de configuración correspondientes. @@ -222,11 +216,11 @@ El agente de infraestructura tiene un complemento incorporado que recopila datos -### Revisar integración en el host [#on_host_integrations] +### Revisar integración en el host [#on\_host\_integrations][#on_host_integrations] Si utiliza infraestructura integración en el host, esto puede tener impactos adicionales en el uso de la CPU. La naturaleza del impacto y los métodos para ajustarlo dependen de la integración que esté utilizando. A continuación se muestran algunas formas de ajustar el uso de CPU de integración en el host: * Vea si su [integración](/docs/integrations/host-integrations/host-integrations-list) tiene opciones de configuración que pueda ajustar. -* Si es posible, distribuya la carga de monitoreo agregando un agente de infraestructura adicional. Por ejemplo, la integración de Kafka permite un [despliegue multiagente](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents). +* Si es posible, distribuya la carga de monitoreo agregando un agente de infraestructura adicional. Por ejemplo, la integración de Kafka permite un [despliegue multiagente](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents). \ No newline at end of file diff --git a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx index 944032f86e9..cc0616f2639 100644 --- a/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx +++ b/src/i18n/content/es/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx @@ -23,28 +23,22 @@ Los siguientes pasos mitigan el problema de las lagunas de datos: 1. Elimine el límite de un subproceso para el agente, permitiendo un subproceso por núcleo. - - 1. Abra el siguiente archivo en su editor de texto plano favorito: C:\\Program Files\\New Relic\\newrelic-infra\\newrelic-infra.yml + + 1. Abra el siguiente archivo en su editor de texto plano favorito: `C:\Program Files\New Relic\newrelic-infra\newrelic-infra.yml` 2. Agregue la siguiente opción de configuración: - ``` + ```yml max_procs: -1 ``` - - 1. Abra el siguiente archivo en su editor de texto plano favorito: /etc/newrelic-infra.yml + + 1. Abra el siguiente archivo en su editor de texto plano favorito: `/etc/newrelic-infra.yml` 2. Agregue la siguiente opción de configuración: - ``` + ```yml max_procs: -1 ``` @@ -53,44 +47,32 @@ Los siguientes pasos mitigan el problema de las lagunas de datos: 2. Utilice [su sistema de inicio](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) para reiniciar el servicio del agente: - + Utilice comandos SystemD con CentOS 7, Debian 8, RHEL 7 y Ubuntu 15.04 o superior: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Utilice comandos de System V con Debian 7: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Utilice comandos Upstart con Amazon Linux, CentOS 6, RHEL 6 y Ubuntu 14.10 o anterior: - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -101,4 +83,4 @@ Los siguientes pasos mitigan el problema de las lagunas de datos: El agente New Relic Infrastructure , de forma predeterminada, se ejecuta en un único subproceso del sistema operativo. Esto puede significar que, especialmente en entornos Windows, el programador de procesos le da pocas posibilidades de obtener tiempo de CPU cuando el sistema está sobrecargado. -La opción de configuración `max_procs: -1` elimina esta limitación y permite que el agente utilice un subproceso por núcleo de CPU (como máximo). +La opción de configuración `max_procs: -1` elimina esta limitación y permite que el agente utilice un subproceso por núcleo de CPU (como máximo). \ No newline at end of file diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx index c4ed2cce77f..a02982a06c8 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx @@ -12,7 +12,7 @@ translationType: machine La versión 2 de integración de Kubernetes tiene algunas configuraciones y requisitos diferentes a los de la versión 3. Este documento repasa las configuraciones que son diferentes de la versión 3 y que necesitará para la versión 2. Si no especificamos nada diferente, puede usar la configuración de la versión 3. - Tenga en cuenta que reemplazamos la versión 2 y no debe usarla. Mantenemos esta documentación para los usuarios que todavía usan la versión 2. + New Relic dejó obsoleta la versión 2 y recomienda no emplearla. Mantenemos esta documentación para los usuarios que todavía usan la versión 2 aunque ya no la soportemos. Consulte [Introducción a la integración de Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/) para comenzar con la versión actual de Kubernetes. @@ -289,10 +289,7 @@ Para configurar el monitoreo del plano de control en OpenShift, descomente las s Si desea generar un registro detallado y obtener información de versión y configuración, simplemente consulte la información a continuación. - + Para la integración Kubernetes , el agente de infraestructura solo agrega una entrada log en caso de error. Los errores más comunes se muestran en el registro estándar (no detallado). Si está realizando una investigación más profunda por su cuenta o con el soporte de New Relic, puede habilitar el modo detallado. @@ -336,11 +333,7 @@ Si desea generar un registro detallado y obtener información de versión y conf 9. [Recuperar la configuración del servicio `kube-state-metrics` ](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + Para la integración Kubernetes , el agente de infraestructura solo agrega una entrada log en caso de error. Los errores más comunes se muestran en el registro estándar (no detallado). Si está realizando una investigación más profunda por su cuenta o con el soporte de New Relic, puede habilitar el modo detallado. @@ -386,10 +379,7 @@ Si desea generar un registro detallado y obtener información de versión y conf 8. [Recuperar la configuración del servicio `kube-state-metrics` ](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + Para obtener el registro del pod que se conecta a `kube-state-metrics`: 1. Ejecute este comando: @@ -425,10 +415,7 @@ Si desea generar un registro detallado y obtener información de versión y conf ``` - + Para obtener el registro de un pod que se ejecuta en un nodo maestro: 1. Obtenga los nodos etiquetados como maestros: @@ -500,4 +487,4 @@ Consulte el documento [Habilitar el monitoreo de servicios usando el Helm Chart] ### Agregue un servicio YAML a la configuración de integración de Kubernetes [#add-service-yaml] -Si está empleando la versión 2 de integración de Kubernetes, debe agregar una entrada para este ConfigMap en las secciones `volumes` y `volumeMounts` del `spec` de DaemonSet, para garantizar que todos los archivos en ConfigMap estén montados en `/etc/newrelic-infra/integrations.d/`. +Si está empleando la versión 2 de integración de Kubernetes, debe agregar una entrada para este ConfigMap en las secciones `volumes` y `volumeMounts` del `spec` de DaemonSet, para garantizar que todos los archivos en ConfigMap estén montados en `/etc/newrelic-infra/integrations.d/`. \ No newline at end of file diff --git a/src/i18n/content/es/docs/logs/forward-logs/enable-log-management-new-relic.mdx b/src/i18n/content/es/docs/logs/forward-logs/enable-log-management-new-relic.mdx index 8cd66da1183..eff417c3dfc 100644 --- a/src/i18n/content/es/docs/logs/forward-logs/enable-log-management-new-relic.mdx +++ b/src/i18n/content/es/docs/logs/forward-logs/enable-log-management-new-relic.mdx @@ -9,13 +9,9 @@ freshnessValidatedDate: never translationType: machine --- -Nuestras capacidades le ayudan a recopilar, procesar, explorar, consultar y alertar sobre sus datos log . Para iniciar sesión en New Relic, puede utilizar cualquiera de estas opciones: +Nuestras capacidades le ayudan a recopilar, procesar, explorar, consultar y alertar sobre sus datos log . Para iniciar sesión en New Relic, puede utilizar cualquiera de estas opciones: -Diagram of options to get your logs into New Relic +Diagram of options to get your logs into New Relic Para obtener una descripción general de nuestras diversas soluciones de logging, consulte [Introducción a los logs](/docs/logs/get-started/get-started-log-management#integrate-logs). @@ -73,8 +69,8 @@ A continuación se muestran algunos detalles sobre cómo lograr casos de uso esp * Utilice nuestro agente de infraestructura para recopilar logs a nivel de host. En el archivo de configuración `logging.yml` , asegúrese de seguir el directorio `/var/log/containers/*.log` . Por ejemplo: ```yml logs: - - name: Docker-logs - file: /var/log/containers/*.log # Path to Docker log files + - name: Docker-logs + file: /var/log/containers/*.log # Path to Docker log files ``` * Utilice nuestra [imagen de Docker independiente](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) @@ -86,7 +82,7 @@ A continuación se muestran algunos detalles sobre cómo lograr casos de uso esp - Emplee nuestro agente y agente de infraestructura. Deje que el agente APM de su aplicación reenvíe los datos log directamente a New Relic con [los logs en el contexto de APM](/docs/apm/new-relic-apm/getting-started/get-started-logs-context). ¡No es necesario instalar ni mantener software adicional de terceros! + Emplee nuestro agente y agente de infraestructura. Deje que el agente APM de su aplicación reenvíe los datos log directamente a New Relic con [los logs en el contexto de APM](/docs/apm/new-relic-apm/getting-started/get-started-logs-context). ¡No es necesario instalar ni mantener software adicional de terceros! @@ -110,11 +106,11 @@ A continuación se muestran algunos detalles sobre cómo lograr casos de uso esp Puede reenviar el log a través de nuestro agente de infraestructura o uno de nuestros servicios log de terceros compatibles. Así es cómo: -1. Tenga su New Relic listo para la cuenta a la que desea informar el inicio de sesión. +1. Tenga su New Relic listo para la cuenta a la que desea informar el inicio de sesión. 2. Instale un [reenviador de logs compatible](#log-forwarding). 3. Asegúrese de que la conectividad saliente en el puerto TCP 443 esté permitida en el [rango CIDR](/docs/using-new-relic/cross-product-functions/install-configure/networks/#infrastructure) que coincida con su [región](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers). 4. Dependiendo de dónde se almacenen los datos de su cuenta en New Relic, use el nombre DNS `log-api.newrelic.com` o `log-api.eu.newrelic.com` para la configuración. -5. Si corresponde, configure el agente de su aplicación siguiendo los procedimientos [de logs en el contexto](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/) . +5. Si corresponde, configure el agente de su aplicación siguiendo los procedimientos [de logs en el contexto](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/) . ## Opciones de reenvío de logs [#log-forwarding] @@ -149,7 +145,7 @@ Admitimos el siguiente reenviador de logs de Microsoft: ### Otro reenviador de logs compatible [#forward-other] -Admitimos el siguiente reenviador de logs. Algunas de estas opciones vienen con inicios rápidos, que le brindan alertas y listos para usar. Puede instalar inicios rápidos después de configurar su reenvío de logs. +Admitimos el siguiente reenviador de logs. Algunas de estas opciones vienen con inicios rápidos, que le brindan alertas y listos para usar. Puede instalar inicios rápidos después de configurar su reenvío de logs. * Flujo de datos de Akamai 2: @@ -171,7 +167,7 @@ Admitimos el siguiente reenviador de logs. Algunas de estas opciones vienen con * [Complemento vectorial](/docs/logs/forward-logs/vector-output-sink-log-forwarding) - + ## Extremo TCP [#enable-endpoint] @@ -183,13 +179,9 @@ Si prefiere conectarse a New Relic sin instalar un complemento, ofrecemos una in ## Cómo funciona el reenvío de logs [#enable] -El siguiente diagrama muestra el ciclo de vida de un mensaje de log para una aplicación, desde el enriquecimiento con metadatos del agente (logging contextual) hasta el formateo y el reenvío de los datos log a New Relic. +El siguiente diagrama muestra el ciclo de vida de un mensaje de log para una aplicación, desde el enriquecimiento con metadatos del agente (logging contextual) hasta el formateo y el reenvío de los datos log a New Relic. -Diagram of how your logs flow into New Relic +Diagram of how your logs flow into New Relic
Este diagrama ilustra el flujo de mensaje de log a través de New Relic. @@ -209,4 +201,4 @@ Después de habilitar su reenviador de logs, aproveche al máximo sus datos en N * Vea su logs en el contexto del rendimiento de su aplicación en la [UI de APM](/docs/logs/ui-data/use-logs-ui/#links). Solucionar [errores](/docs/apm/apm-ui-pages/error-analytics/errors-page-find-fix-verify-problems/) con [rastreo distribuido](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data), rastreo del stack, log de aplicación y más. * Obtenga una visibilidad más profunda de los datos de rendimiento de su aplicación y de su plataforma si envía su log a nuestro [agente de infraestructura](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/). Revise su [log de infraestructura](/docs/logs/ui-data/use-logs-ui/#links) en la UI. * Configurar [alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/). -* [Consulta tus datos](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) y [crea un panel](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/). Por ejemplo, consulte nuestros tutoriales de NerdGraph para consultar y administrar sus [reglas de partición de datos](/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial) y sus [reglas de análisis de logs](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). +* [Consulta tus datos](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) y [crea un panel](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/). Por ejemplo, consulte nuestros tutoriales de NerdGraph para consultar y administrar sus [reglas de partición de datos](/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial) y sus [reglas de análisis de logs](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). \ No newline at end of file diff --git a/src/i18n/content/es/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx b/src/i18n/content/es/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx index 524bbd96719..2dd20fc7ded 100644 --- a/src/i18n/content/es/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx +++ b/src/i18n/content/es/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx @@ -29,9 +29,9 @@ Para reenviar su log de Kubernetes a New Relic con nuestro complemento: Si está [empleando un secreto Kubernetes ](https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging/values.yaml#L8-L25)para almacenar New Relic , el gráfico `newrelic-logging` tiene como valor predeterminado enviar el registro a los extremos de API de EE. UU. Si la clave de licencia pertenece a una cuenta de la UE o FedRAMP, y se emplea un secreto para el almacenamiento de la clave, debe actualizar la configuración de extremo con el valor apropiado de los [documentos de referenciaAPI ](/docs/logs/log-api/introduction-log-api/#endpoint). A continuación se muestra un ejemplo de cómo configurar esto para cuentas de la UE: ```yml - newrelic-logging: - enabled: true - endpoint: https://log-api.eu.newrelic.com/log/v1 + newrelic-logging: + enabled: true + endpoint: https://log-api.eu.newrelic.com/log/v1 ``` @@ -67,8 +67,8 @@ Para configurar su clúster de Kubernetes para enviar los loginternos al reenvia ```yml newrelic-logging: - fluentBit: - sendMetrics: true + fluentBit: + sendMetrics: true ``` Solo necesita habilitar la configuración `newrelic-logging.fluentBit.sendMetrics` cuando resuelva problemas en un clúster de Kubernetes. Recomendamos habilitarlo para un único clúster de Kubernetes a la vez para facilitar la resolución de problemas. diff --git a/src/i18n/content/es/docs/logs/get-started/live-archives.mdx b/src/i18n/content/es/docs/logs/get-started/live-archives.mdx index 1e7f4fdb6ae..6edf2da0ed5 100644 --- a/src/i18n/content/es/docs/logs/get-started/live-archives.mdx +++ b/src/i18n/content/es/docs/logs/get-started/live-archives.mdx @@ -118,13 +118,13 @@ La característica Live Archives ofrece almacenamiento de datos log a largo plaz A continuación se muestra una consulta de ejemplo: - ``` + ```graphql query { actor { account(id: 1234567) { nrql( query: "SELECT count(*) FROM Log SINCE '2024-02-01 12:00:00' UNTIL '2024-02-01 13:00:00'" - options: {eventNamespaces: "Logging:Archive"} + options: { eventNamespaces: "Logging:Archive" } async: true ) { results diff --git a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index c10aefd7051..ca337b9bd0b 100644 --- a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -331,7 +331,8 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor .NETエージェント`v9.2.0`以降では、[Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos)ライブラリを自動的にインストゥルメントします。 * サポートされている最小バージョン：3.17.0 - * 最新の検証済み互換バージョン：3.23.0 + * 最新の検証済み互換バージョン: 3.44.0 + * バージョン 3.35.0 以降は、.NET エージェント v10.32.0 以降でサポートされます。 @@ -372,7 +373,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/)を使用する * サポートされる最小バージョン: 23.4.0 - * 最新の検証済み互換バージョン: 23.5.1 + * 最新の検証済み互換バージョン: 23.6.0 `Oracle.ManagedDataAccess.Core`の古いバージョンはインストゥルメントされた可能性がありますが、テストされておらず、サポートされていません。 @@ -409,7 +410,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：2.3.0 - 最新の検証済み互換バージョン：2.26.0 + 最新の検証済み互換バージョン: 2.29.0 エージェントバージョン10.12.0以降では、ドライババージョン2.7以降に追加された以下のメソッドがインストゥルメントされます。 @@ -478,7 +479,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor **Elastic.Clients.Elasticsearch** * サポートされている最小バージョン：8.0.0 - * 最新の検証済み互換バージョン：8.14.6 + * 最新の検証済み互換バージョン: 8.15.8 * バージョン8.10.0以降は、.NETエージェントv10.20.1以降でサポートされます。 * バージョン8.12.1以降は、.NETエージェントv10.23.0以降でサポートされます。 @@ -596,7 +597,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 3.7.403.4 + 3.7.404.5 @@ -660,7 +661,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 3.1.1 + 4.0.1 @@ -678,7 +679,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 5.3.2 + 5.3.14 @@ -696,7 +697,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 8.0.0 + 8.0.1 @@ -790,7 +791,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：7.1.0 - * 最新の検証済み互換バージョン：8.1.1 + * 最新の検証済み互換バージョン: 8.2.5 @@ -804,7 +805,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * 最新の検証済み互換バージョン: 3.7.400.19 + * 最新の検証済み互換バージョン: 3.7.400.33 @@ -1249,7 +1250,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：2.3.0 - 最新の検証済み互換バージョン：2.26.0 + 最新の検証済み互換バージョン: 2.29.0 エージェントバージョン10.12.0以降では、ドライババージョン2.7以降に追加された以下のメソッドがインストゥルメントされます。 @@ -1465,7 +1466,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：105.2.3 - 最新の検証済み互換バージョン：111.4.0 + 最新の検証済み互換バージョン: 112.1.0 互換性のない既知のバージョン：106.8.0、106.9.0、106.10.0、106.10.1 @@ -1541,7 +1542,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 3.7.403.4 + 3.7.404.5 @@ -1605,7 +1606,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 3.1.1 + 4.0.1 @@ -1623,7 +1624,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - 5.3.2 + 5.3.14 @@ -1741,7 +1742,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：7.1.0 - * 最新の検証済み互換バージョン：8.1.1 + * 最新の検証済み互換バージョン: 8.2.5 @@ -1755,7 +1756,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * 最新の検証済み互換バージョン: 3.7.400.19 + * 最新の検証済み互換バージョン: 3.7.400.33 diff --git a/src/i18n/content/jp/docs/browser/browser-integrations/blazor-webassembly.mdx b/src/i18n/content/jp/docs/browser/browser-integrations/blazor-webassembly.mdx index af0894f2d94..2c4096e0cf7 100644 --- a/src/i18n/content/jp/docs/browser/browser-integrations/blazor-webassembly.mdx +++ b/src/i18n/content/jp/docs/browser/browser-integrations/blazor-webassembly.mdx @@ -10,13 +10,9 @@ translationType: machine Blazor WebAssembly ダッシュボードを使用すると、ゴールデン メトリックを簡単に監視し、エンド ユーザー エクスペリエンスを追跡し、経時的な合計ページ ビューを確認できます。 -ブラウザ監視エージェントで構築された Blazor WebAssembly 統合により、最も重要な書き込みデータであるオールインワン プレイスを表示できる一連の既定のが提供されます。 +ブラウザ監視エージェントで構築された Blazor WebAssembly 統合により、最も重要な書き込みデータであるオールインワン プレイスを表示できる一連の既定のが提供されます。 -Blazor WebAssembly dashboard page +Blazor WebAssembly dashboard page
Blazor WebAssembly と New Relic の統合を設定すると、すぐにデータがこのようなダッシュボードに表示されます。 @@ -34,7 +30,7 @@ Blazor WebAssembly を New Relic と統合するためにインフラストラ Blazor WebAssembly からデータを収集するには、次の手順に従います。 -1. [one.newrelic.com](https://one.newrelic.com)から、 [**Integrations & Agents**ページ](https://one.newrelic.com/marketplace)に移動します。 +1. [one.newrelic.com](https://one.newrelic.com)から、 [**Integrations & Agents**ページ](https://one.newrelic.com/marketplace)に移動します。 2. **Browser and mobile**をクリックし、次に**Browser monitoring**をクリックします。 @@ -50,7 +46,7 @@ Blazor WebAssembly からデータを収集するには、次の手順に従い 8. アプリケーションを再起動します。 -9. **[one.newrelic.com](https://one.newrelic.com/all-capabilities)**に移動し、 **Metrics & events**をクリックします。 サンプル NRQL クエリを実行して、New Relic がデータを収集していることを確認します。 +9. **[one.newrelic.com](https://one.newrelic.com/all-capabilities)**に移動し、 **Metrics & events**をクリックします。 サンプル NRQL クエリを実行して、New Relic がデータを収集していることを確認します。 ```sql SELECT average(windowLoad) FROM PageViewTiming WHERE (deviceType = 'Desktop') FACET `userAgentName` SINCE 604800 seconds AGO TIMESERIES @@ -66,4 +62,4 @@ NRQL クエリの作成とダッシュボードの生成の詳細については * 基本的なクエリと高度なクエリを作成する[ためのクエリ ビルダーの概要](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder)。 * [ダッシュボードをカスタマイズしてさまざまなアクションを実行するためのダッシュボードの概要](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards)。 -* ダッシュボードを[管理して、ダッシュ](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard)ボードの表示モードを調整したり、ダッシュボードにコンテンツを追加したりします。 +* ダッシュボードを[管理して、ダッシュ](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard)ボードの表示モードを調整したり、ダッシュボードにコンテンツを追加したりします。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx b/src/i18n/content/jp/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx index 1dc3dc96d2a..ea45cfa1f2b 100644 --- a/src/i18n/content/jp/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx +++ b/src/i18n/content/jp/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx @@ -20,17 +20,8 @@ translationType: machine メトリクスを使用することで、より効率的にデータを保存することができます。これにより、データの照会やチャートの作成がより簡単にできるようになります。New Relic におけるメトリクスと他の種類のデータの違いは、時間に基づいています。詳しくは、 [Understand data types](/docs/using-new-relic/data/understand-data/new-relic-data-types) をご覧ください。 -* - **Events, logs, spans:** - - - これらのタイプのデータは、特定の瞬間における単一のレコードを表します。 たとえば、システムへのリクエストごとにイベントが発生する場合があります。 このデータは、詳細なトラブルシューティングと分析に最適です。 - -* - **Metrics:** - - - これらは、イベント、ログ、またはスパンの集約ビューを提供します。 メトリックスは、より長い時間範囲にわたる傾向を示すのに適しています。 たとえば、サービスごとのリクエストの合計数を 1 つのメトリックに集計し、この情報を月ごとに調べることができます。 +* **Events, logs, spans:** これらのタイプのデータは、特定の瞬間における単一のレコードを表します。 たとえば、システムへのリクエストごとにイベントが発生する場合があります。 このデータは、詳細なトラブルシューティングと分析に最適です。 +* **Metrics:** これらは、イベント、ログ、またはスパンの集約ビューを提供します。 メトリックスは、より長い時間範囲にわたる傾向を示すのに適しています。 たとえば、サービスごとのリクエストの合計数を 1 つのメトリックに集計し、この情報を月ごとに調べることができます。 @@ -83,10 +74,7 @@ translationType: machine イベント データからメトリクス データを生成する方法を示すビデオは次のとおりです (7 分 47 分)。 -
- + 返されたレスポンスの例を示します。 ```json @@ -273,10 +267,7 @@ APIリクエストの準備ができたら、 [NerdGraph API](/docs/introduction 利用可能な [NRQL アグリゲータ関数](/docs/insights/nrql-new-relic-query-language/nrql-reference/nrql-syntax-components-functions#functions) は、作成した [メトリックタイプ](#summary-and-uniquecount) によって異なります。以下に例を示します。 - + サマリー指標タイプを作成した場合は、次のクエリに示すように、 `count` 、 `sum` 、 `max` 、 `min` 、および`average`アグリゲーター関数を使用できます。 ``` @@ -284,10 +275,7 @@ APIリクエストの準備ができたら、 [NerdGraph API](/docs/introduction ``` - + `uniqueCount`指標タイプを作成した場合、次のクエリに示すように、 `uniqueCount`関数のみを使用できます。 ```sql @@ -295,10 +283,7 @@ APIリクエストの準備ができたら、 [NerdGraph API](/docs/introduction ``` - + `distribution`指標タイプを作成した場合は、次のクエリに示すように、 `percentile`または`histogram`関数を使用します。 ```sql @@ -321,4 +306,4 @@ NerdGraphの呼び出しが正しく構築されていない場合、以下の Cannot parse the unexpected character "\u201C” ``` -NerdGraphコール内の引用符がスマートクォート（カーリークォート）でないことを確認してください。NerdGraph APIはストレートな引用符しか受け付けません。 +NerdGraphコール内の引用符がスマートクォート（カーリークォート）でないことを確認してください。NerdGraph APIはストレートな引用符しか受け付けません。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/iast/iast-configuration.mdx b/src/i18n/content/jp/docs/iast/iast-configuration.mdx index 4d7df8f991e..aee6e3ce080 100644 --- a/src/i18n/content/jp/docs/iast/iast-configuration.mdx +++ b/src/i18n/content/jp/docs/iast/iast-configuration.mdx @@ -22,10 +22,10 @@ translationType: machine ```yml security: scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default is forever - schedule: "" #Cron Expression to define start time - always_sample_traces: false #regardless of scan schedule + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default is forever + schedule: "" # Cron Expression to define start time + always_sample_traces: false # regardless of scan schedule ``` @@ -90,10 +90,10 @@ security: IAST をアプリケーションの起動後 30 分後に開始し、300 分間実行するようにスケジュールするには、遅延を 30 に設定し、期間を 300 に設定する必要があります。 ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - duration: 300 #In minutes, default is forever + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + duration: 300 # In minutes, default is forever ``` @@ -101,9 +101,9 @@ security: IAST を特定の時間に実行するようにスケジュールするには、希望する時間を表す cron 式にスケジュールを設定します。 たとえば、IAST を毎日深夜に実行するようにスケジュールするには、スケジュールを`"0 0 0 * * ?"`に設定します。 ```yml - security: - scan_schedule: - schedule: "0 0 0 * * ?" #By default, schedule is inactive + security: + scan_schedule: + schedule: "0 0 0 * * ?" # By default, schedule is inactive ``` @@ -115,10 +115,10 @@ security: IAST で常にトレースをサンプリングする場合は、 `always_sample_traces` `true`に設定します。 デフォルトでは、これは`false`に設定されており、IAST はアクティブなスキャン ウィンドウ内のトレースのみをサンプリングすることを意味します。 ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - always_sample_traces: true #regardless of scan schedule + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + always_sample_traces: true # regardless of scan schedule ``` @@ -157,10 +157,10 @@ security: API を指定するための形式は次のとおりです。 ```yml - exclude_from_iast_scan: - api: - - .*account.* - - .*/\api\/v1\/.*?\/login +exclude_from_iast_scan: + api: + - .*account.* + - .*/\api\/v1\/.*?\/login ``` 例えば： @@ -178,16 +178,18 @@ API を指定するための形式は次のとおりです。 これは HTTP ヘッダー キーのリストです。 リクエストにこれらのキーを含むヘッダーが含まれている場合、対応する IAST スキャンはスキップされます。 たとえば、ヘッダー付きの curl リクエストがあり、`X-Forwarded-For` ヘッダーのIASTスキャンをスキップしたい場合は、次の設定を渡すことができます。 ```bash - curl -X POST -H "X-Forwarded-For: 123.456.789.012" -H "Content-Type: application/x-www-form-urlencoded" -d "param1=value1¶m2=value2" http://example.com + curl -X POST -H "X-Forwarded-For: 123.456.789.012" \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "param1=value1¶m2=value2" http://example.com ``` 次の設定を使用できます: ```yml - exclude_from_iast_scan: - http_request_parameters: - header: - - X-Forwarded-For + exclude_from_iast_scan: + http_request_parameters: + header: + - X-Forwarded-For ``` @@ -195,17 +197,17 @@ API を指定するための形式は次のとおりです。 これは、問題キーのリストです。 リクエストの最初の文字列にこれらの問題が存在すると、 IASTスキャンがスキップされます。 たとえば、問題のあるカール リクエストがあり、`customerID` と `username` のIASTスキャンをスキップしたい場合は、次の設定を渡すことができます。 ```bash - curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' + curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' ``` 次の設定を使用できます: ```yml - exclude_from_iast_scan: - http_request_parameters: - query: - - username - - customerID + exclude_from_iast_scan: + http_request_parameters: + query: + - username + - customerID ``` @@ -217,29 +219,29 @@ API を指定するための形式は次のとおりです。 これは、JSON 本文を含む curl リクエストがあり、 `customerID`および`firstName`で IAST スキャンをスキップする場合の JSON コンテンツ タイプの curl の例です。 ```bash - curl --location --request POST 'localhost:8080/application/json/post' \ + curl --location --request POST 'localhost:8080/application/json/post' \ --header 'Content-Type: application/json' \ --data '{ - "path": "sample.txt", - "script":"testscript", - "customerID":"GREAL", - "name": { - "firstName": "john", - "lastName": "wick" - }, - "url":"http://example.com", - "cmd":"ls" + "path": "sample.txt", + "script":"testscript", + "customerID":"GREAL", + "name": { + "firstName": "john", + "lastName": "wick" + }, + "url":"http://example.com", + "cmd":"ls" }' ``` 次の設定を使用できます: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - customerID - - name.firstName + exclude_from_iast_scan: + http_request_parameters: + body: + - customerID + - name.firstName ``` #### XMLコンテンツタイプの例 @@ -247,7 +249,7 @@ API を指定するための形式は次のとおりです。 これは XML 本文を含む curl リクエストであり、 `customerID`と`username`での IAST スキャンをスキップします。 ```bash - curl --location 'localhost:8080/application/xml/post' \ + curl --location 'localhost:8080/application/xml/post' \ --header 'Content-Type: application/xml' \ --data ' @@ -265,11 +267,11 @@ API を指定するための形式は次のとおりです。 次の設定を使用できます: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - AppData.customerID - - AppData.username + exclude_from_iast_scan: + http_request_parameters: + body: + - AppData.customerID + - AppData.username ``` #### フォーム URL エンコードされたコンテンツ タイプの例 @@ -277,7 +279,7 @@ API を指定するための形式は次のとおりです。 これは、Form-URL-Encoded 本文を含む curl リクエストであり、 `customerID`および`username`での IAST スキャンをスキップします。 ```bash - curl --location 'localhost:8080/application/urlencode/post' \ + curl --location 'localhost:8080/application/urlencode/post' \ --header 'Content-Type: application/x-www-form-urlencoded' \ -d 'name=madhav&path=sample.txt&customerID=GREAL&script=K2&url=http://example.com&username=bob&firstName=Aliko&cmd=ls' ``` @@ -285,10 +287,10 @@ API を指定するための形式は次のとおりです。 次の設定を使用できます: ```yml - http_request_parameters: - body: - - customerID - - username + http_request_parameters: + body: + - customerID + - username ``` @@ -304,18 +306,18 @@ API を指定するための形式は次のとおりです。 SQL インジェクションと SSRF のスキャンをスキップするには、この例を参照してください。 `sql_injection`と`ssrf`問題は`true`に設定されます。 ```yml - exclude_from_iast_scan: - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: true - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: true - rxss: false +exclude_from_iast_scan: + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: true + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: true + rxss: false ``` @@ -325,32 +327,32 @@ SQL インジェクションと SSRF のスキャンをスキップするには 以下の組み合わせ設定を使用できます: ```yml - security: +security: + enabled: true + scan_schedule: + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default will be forever + #schedule: "" # Cron Expression to define start time + always_sample_traces: false # continuously collect samples + exclude_from_iast_scan: + api: [] + http_request_parameters: + header: [] + query: [] + body: [] + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: false + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: false + rxss: false + agent: enabled: true - scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default will be forever - #schedule: "" #Cron Expression to define start time - always_sample_traces: false #continuously collect samples - exclude_from_iast_scan: - api: [] - http_request_parameters: - header: [] - query: [] - body: [] - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: false - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: false - rxss: false - agent: - enabled: true ``` ## IASTスキャンコントローラ [#iast-scan-controllers] diff --git a/src/i18n/content/jp/docs/iast/troubleshooting.mdx b/src/i18n/content/jp/docs/iast/troubleshooting.mdx index bd006d6de7e..865f93f85f5 100644 --- a/src/i18n/content/jp/docs/iast/troubleshooting.mdx +++ b/src/i18n/content/jp/docs/iast/troubleshooting.mdx @@ -14,84 +14,43 @@ translationType: machine 問題がここにリストされていない場合は、いつでも[New Relic サポート](https://support.newrelic.com)にお問い合わせください。 - - **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**に移動します。 アプリケーションをクリックすると、アプリケーションのテスト効率、脆弱性、カバーされている API、メソッド呼び出しなどのデータを確認できます。 + + **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**に移動します。 アプリケーションをクリックすると、アプリケーションのテスト効率、脆弱性、カバーされている API、メソッド呼び出しなどのデータを確認できます。 - + IAST を有効にした後、アプリケーションを再起動する必要があります。 - + これが新しいアプリの場合、ファイアウォールにより NR プラットフォームとの通信が妨げられている可能性があります。 `nr-security-home/logs/snapshots`の最新のタイムスタンプを含むファイル内のサービス統計セクションを確認してください。 そのリスト内の 6 つの項目すべてに「OK」と表示されるはずです。 そうでない場合は、ログで追加情報を確認するか、 [New Relic サポート](https://support.newrelic.com)にお問い合わせください。 [標準のファイアウォールのドキュメント](/docs/new-relic-solutions/get-started/networks/)も参照できます。 New Relic UI にアプリケーションが表示され、セキュリティ エージェントが IAST を正常に開始したにもかかわらず、UI に脆弱性が表示されない場合は、次の点を確認してください。 - * アプリケーションの効率レベル: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**に移動します。 アプリケーションを検索し、概要セクションを確認してください。 アプリケーションの IAST カバレッジが低い場合は、アプリケーションにテスト ケースを追加して、テスト効率を高めます。 + * アプリケーションの効率レベル: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**に移動します。 アプリケーションを検索し、概要セクションを確認してください。 アプリケーションの IAST カバレッジが低い場合は、アプリケーションにテスト ケースを追加して、テスト効率を高めます。 - * IAST カバレッジ: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**に移動します。 アプリケーションを検索してクリックします。 概要セクションで、IAST 分析の範囲が広く、脆弱性が検出されていないかどうかを確認します。これは、アプリケーションが安全であることを意味します。 + * IAST カバレッジ: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**に移動します。 アプリケーションを検索してクリックします。 概要セクションで、IAST 分析の範囲が広く、脆弱性が検出されていないかどうかを確認します。これは、アプリケーションが安全であることを意味します。 * アプリケーションのフレームワークまたは脆弱性カテゴリはサポートされていません。 これらを確認しても IAST に脆弱性が見つからない場合は、 [New Relic サポート](https://support.newrelic.com/s/)にお問い合わせください。 - - **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**にアプリケーションが表示されない場合は、次の点を確認してください。 + + **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**にアプリケーションが表示されない場合は、次の点を確認してください。 * アプリケーションは稼働中です。アプリケーション プロセスまたは[\[APM とサービス\] ページ](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/view-events-their-products#products)を確認してください。 - * アプリケーションのログを調べて、問題があるかどうかを確認します。 - * APMエージェントのバージョンを確認し、必要に応じて更新します。 - * `newrelic.yml`構成ファイルには、[インストール ページ](/docs/iast/install)に示されているように、問題の変更が含まれています。 - * `nr-security-home/logs`ディレクトリに移動し、 `LANGUAGE-security-collector-init.log`ファイル内の`[SETP-8]`行を見つけます。 予期しないエラーがあるかどうかを確認し、何が失敗したかを確認します。 - * アプリケーションにトラフィックが発生しています。 IAST がアプリケーションをテストできるように、トラフィックを生成します。 - - * プロキシまたはファイアウォールがアクセスをブロックしています。 ドメイン - - - **csec.nr-data.net** - - - の次の IP `3.134.136.130, 18.219.177.104, 18.117.21.106` 、ドメイン - - - **csec-gov.nr-data.net** - - - の次の IP `3.130.22.102, 3.138.243.136, 3.139.218.150` 、ドメイン - - - **csec.eu01.nr-data.net** - - - の次の IP `18.185.235.118, 3.125.193.113, 3.75.166.122`をホワイトリストに追加します。 ただし、IP はいつでも変更される可能性があるため、IP ではなくドメインをホワイトリストに追加することをお勧めします。 - - * TLS 証明書は正しいです。 Let's Encrypt CA 証明書 ( [Let's Encrypt 証明書](https://letsencrypt.org/certificates/#root-certificates)からダウンロード) をローカル信頼ストアに追加します。 完全な信頼チェーンを確立するには、ルート証明書と中間証明書 (ISRG Root X1 と Let's Encrypt R3) の両方を含めます。 - + * プロキシまたはファイアウォールがアクセスをブロックしています。 ドメイン**csec.nr-data.net**の次の IP `3.134.136.130, 18.219.177.104, 18.117.21.106` 、ドメイン**csec-gov.nr-data.net**の次の IP `3.130.22.102, 3.138.243.136, 3.139.218.150` 、ドメイン**csec.eu01.nr-data.net**の次の IP `18.185.235.118, 3.125.193.113, 3.75.166.122`をホワイトリストに追加します。 ただし、IP はいつでも変更される可能性があるため、IP ではなくドメインをホワイトリストに追加することをお勧めします。 + * TLS 証明書は正しいです。 Let's Encrypt CA 証明書 ( [Let's Encrypt 証明書](https://letsencrypt.org/certificates/#root-certificates)からダウンロード) をローカル信頼ストアに追加します。 完全な信頼チェーンを確立するには、ルート証明書と中間証明書 (ISRG Root X1 と Let&apos;s Encrypt R3) の両方を含めます。 * アプリケーションのフレームワークまたは脆弱性カテゴリがサポートされています。 - + [APM の高セキュリティ モード](/docs/apm/agents/manage-apm-agents/configuration/high-security-mode/)を使用している場合、エージェントは機能しません。 @@ -100,7 +59,7 @@ translationType: machine セキュリティ エージェントが正常に動作している場合: - * **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**にアプリケーションが表示されます。 アプリケーションが起動され、トラフィックが生成されます。 + * **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**にアプリケーションが表示されます。 アプリケーションが起動され、トラフィックが生成されます。 * `nr-security-home/logs`ディレクトリで、 `LANGUAGE-security-collector-init.log`ファイルを検索します。 ファイル名の`LANGUAGE` 、使用しているものに置き換えます。 次の手順を検索して、問題の場所を確認します。 @@ -124,13 +83,10 @@ translationType: machine ``` - + IAST UI にアプリケーションが表示され、セキュリティ エージェントが正常に開始された場合でも、IAST が動作しているかどうかを確認できます。 確認するには次の手順に従います。 - 1. **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**に移動します。 + 1. **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**に移動します。 2. **Application tests**タブでアプリケーションを検索し、クリックします。 @@ -139,68 +95,49 @@ translationType: machine また、ログレベルを**debug/finest**に設定すると、 `nr-security-home/logs/java-security-collector.log`ファイルで**Fuzz request received**を検索できます。 これは、IAST 分析が進行中であることを示しています。 - + IAST はトラフィックの存在を検出するとテストを開始するため、アプリケーションが動作するかどうか、またはアプリケーションに向けられたトラフィックがあるかどうかを確認してください。 アプリのUIまたはAPIエンドポイントを実行します。 - + IAST が既知の脆弱性を検出しない場合は、次のような理由が考えられます。 * IAST はアプリケーション フレームワークをサポートしていません。 + * このモジュールにはインストレーションはありません。 - + アプリケーションは、IAST の一部として、しばらくの間、高トラフィックとレイテンシを表示する可能性があります。 この問題は、IAST テストが終了すると数分で解決するはずです。 `nr-security-home/logs/snapshots` フォルダー内のスナップショット ログ ファイルを確認することもできます。ログ ファイルには、セキュリティ エージェントのステータス、リソースの使用状況、および最後の 5 つのエラーが表示されます。 - + アプリケーションに HTTP リクエストの処理の一環としてファイルやディレクトリを作成する機能がある場合、IAST はコード パスをテストし、そのようなファイルやディレクトリを作成しようとします。 アプリケーション コードは、受信 HTTP リクエストの影響を受けて、これらのファイルを作成します。 エージェントはそれらを削除できません。 どの API もファイルやディレクトリを作成できないことが確実な場合は、アプリケーションの設定とログを[New Relic Support](https://support.newrelic.com)と共有してください。 - + IAST の一部として、セキュリティ エージェントは負荷を増加させる新しいリクエストをアプリケーションに送信し、その結果リソース使用率が増加します。この IAST 分析では、アプリケーション内の捕捉されなかったエラーや例外を明らかにすることもできます。 リソース不足によりアプリケーションがクラッシュした場合は、リソースを増やし、アプリケーションを再起動し、再度 IAST を実行します。 - + 以下のクエリの`appId`を更新し、それを書き込みビルダーで実行すると、アプリケーションに関して報告されたすべての脆弱性を見つけることができます。 ```sql - SELECT * FROM Vulnerability WHERE issueType = 'Application Vulnerability' AND appId = '{your application's appId}' + SELECT * FROM Vulnerability + WHERE issueType = 'Application Vulnerability' AND appId = YOU_APPLICATION_ID ``` - + IAST が誤検知を報告したと思われる場合は、脆弱性のステータスを更新してください。 次の手順を実行します： - * アプリケーションを検索: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**に移動します。 + * アプリケーションを検索: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**に移動します。 * \[すべてのアプリケーション] タブをクリックし、実際の脆弱性ではない脆弱性を選択します。 @@ -213,15 +150,12 @@ translationType: machine * ステータスを更新した脆弱性を一覧表示する場合は、検出された悪用可能な脆弱性リストでフィルターを適用できます。 - + * Golang の場合は、アプリケーションが使用するライブラリとフレームワークに必要なインストルメンテーション パッケージをインポートしていることを確認してください。 たとえば、アプリケーションが[Mongo DB](http://go.mongodb.org/mongo-driver/mongo)のライブラリを使用していると仮定します。 この特定のライブラリの場合、この[インストゥルメンテーション パッケージを](https://github.com/newrelic/csec-go-agent/tree/main/instrumentation/csec_mongodb_mongo)newrelic からインポートする必要があります。 - ``` + ```go import ( "github.com/newrelic/go-agent/v3/integrations/nrsecurityagent" "github.com/newrelic/go-agent/v3/newrelic" @@ -232,12 +166,12 @@ translationType: machine アプリケーションの要件によっては、他のパッケージをインポートする必要がある場合があります。 サポートされているパッケージのリストは[ここで](https://github.com/newrelic/csec-go-agent#instrumentation-packages)確認してください。 - 各モジュールに対応する[パッケージ](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks)がインポートされていることを確認してください。 + 各モジュールに対応する[パッケージ](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks)がインポートされていることを確認してください。 * HTTP プロトコル エンドポイントを開いている場合は、エンドポイント名の前後に`newrelic.WrapListen`関数を配置して、そのエンドポイントに対する脆弱性スキャンを有効にします。 - ``` - http.ListenAndServe(newrelic.WrapListen(":"), nil) + ```go + http.ListenAndServe(newrelic.WrapListen(":YOUR_PORT_NUMBER"), nil) ``` @@ -247,38 +181,29 @@ translationType: machine * **Outbound HTTP Request**の特定のケースまたは外部サービスへの呼び出しの場合は、[アプリケーション メソッドを更新する](/docs/apm/agents/go-agent/instrumentation/instrument-go-segments/#go-external-segments)必要があります。 - + IAST は Windows 環境でサポートされています。 ただし、一部の Java アプリケーションでは、 `classCirculatoryError`が発生する可能性があり、次のようにエージェント設定で優先度の低いインストゥルメンテーションを無効にする必要があります。 * セキュリティ設定から低優先度のインストゥルメンテーションを無効にします。 - ``` + ```yml low-priority-instrumentation: - enabled: false + enabled: false ``` * 優先度の低いインストゥルメンテーション クラスをクラス トランスフォーマーから除外します。 これを行うには、構成ファイルの`class_transformer`セクションに指定された行を追加します。 - ``` + ```yml com.newrelic.instrumentation.security.low-priority-instrumentation: - enabled: false + enabled: false ``` - + いいえ、IAST の調査結果をダウンロードするための API はありません。 - + IAST は、テスト中に観察した内容に基づいて、新しいリクエストをアプリケーションに送信します。 目的は、エクスプロイト ペイロードを使用した追加の API およびメソッド呼び出しの呼び出しを含む悪意のある動作が可能かどうかを判断することです。 これにより、顧客データの望ましくない操作やランタイム保護サービスのトリガーが発生する可能性があります。 - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx b/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx index b07a9a4aaed..f0bb3a539a8 100644 --- a/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx +++ b/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx @@ -46,7 +46,7 @@ translationType: machine ロギング設定を使用して`newrelic-infra.yml`ファイルを編集します。 - ``` + ```yml log: level: debug file: /path/to/logfile.log @@ -123,17 +123,14 @@ infrastructure agent v1.9.0以降では、ログにsmart verboseモードを使 [一般的なロギング手順](#verbose) を補完するために使用される、特定のシステムに対する追加の注意事項と要件です。 - + コンテナ化されたインフラストラクチャエージェントを使用している場合： 1. 次のいずれかのオプションを選択して、ログレベルを verbose に変更します。 * 推奨: 環境変数`NRIA_LOG_LEVEL`を`debug`に設定します。 これをコマンドラインで実行すると次のようになります。 - ``` + ```sh -e NRIA_LOG_LEVEL=debug ``` @@ -143,10 +140,10 @@ infrastructure agent v1.9.0以降では、ログにsmart verboseモードを使 2. `journalctl`を使用してログを収集します。 - ``` + ```sh journalctl -u newrelic-infra > newrelic-infra.log ``` 3. 数分間ログを収集した後、ログレベルを`info`または`warn`に戻します。 - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx b/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx index a44f7487498..fc6529c4879 100644 --- a/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx +++ b/src/i18n/content/jp/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx @@ -15,7 +15,7 @@ New Relicのインフラストラクチャエージェントは、独自のデ 次の例は、Linuxシステムでのエージェントログの一般的な構成を示しています（Windowsまたは他のプラットフォームを実行している場合はファイルパスを変更します）。 -``` +```yml log: level: info file: '/var/log/newrelic-infra/newrelic-infra.log' @@ -60,7 +60,7 @@ containerized agent found in container また、ログをJSONファイルとしてフォーマットすることもできます。 -``` +```json {"context":{},"level":"info","msg":"upstart_interval_sec: 0","timestamp":"2019-07-11T18:24:03+02:00"} {"context":{},"level":"info","msg":"plugin_dir: ","timestamp":"2019-07-11T18:24:03+02:00"} ``` @@ -81,18 +81,18 @@ Smart verboseモードでは、エラーメッセージが検出されるまで ## 統合ログ管理 -インテグレーションは、JSONペイロードをSTDOUTに、プレーンテキスト（将来的にはJSON構造化）のログをSTDERRに書き込みます。 +統合では、JSON ペイロードを`STDOUT`に書き込み、プレーンテキスト (将来構造化される JSON) ログを`STDERR`に書き込みます。 -インフラストラクチャエージェントは統合STDERR行を処理し、この出力をエージェントログに転送します。 +インフラストラクチャエージェントは統合`STDERR`行を処理し、この出力をエージェントログに転送します。 -エージェントは各STDERR行を以下のように処理します。 +エージェントは各`STDERR`行を次のように処理します。 -* **when agent runs in verbose mode**: 完全な STDERR 行を DEBUG エージェント ログ エントリとして転送し、インテグレーション行のコンテキストを \`msg\` フィールド内に配置します。 -* **otherwise**: 予想される形式 (下記参照) に照らして行を解析し、インテグレーションによって生成された重大度レベルが \`fatal\` または \`error\` のエントリのみを ERROR レベルとしてログに記録します。 この場合、フィールドは構造化された方法で抽出され、転送されます (したがって、エージェントに対して JSON 出力が有効になっている場合、フィールドはクエリ可能になります)。 +* **When agent runs in verbose mode**: `STDERR`行全体を DEBUG エージェント ログ エントリとして転送し、統合行コンテキストを`msg`フィールド内に配置します。 +* **Otherwise**: 予期される形式 (下記を参照) に対して行を解析し、統合によって生成された重大度レベルが`fatal`または`error`のエントリを、エージェント ERROR レベルとしてのみログに記録します。 この場合、フィールドは構造化された方法で抽出され、転送されます (したがって、エージェントに対して JSON 出力が有効になっている場合は、フィールドがクエリ可能になります)。 デフォルトでは、インフラストラクチャエージェントは、統合の実行を妨げない統合からのエラーをフィルタリングして除外します。 ログレベルが DEBUG に設定されている場合、または統合がログ構成に具体的にリストされている場合にのみ、統合からのすべてのエラーが表示されます。 たとえば、この設定では、ログレベルが INFO であっても、 `nri-mssql`からのすべてのエラーが表示されます。 -```YAML +```yml log: include_filters: integration_name: @@ -103,13 +103,13 @@ log: 行は、等号で区切られたキーと値のペアのリストであることが期待されます。キーには任意の文字を含めることができますが、値には3つの異なる形式があります。 -1. string:<quote>任意の文字（エスケープされた引用符を含む） ▽"< quote> -2. 地図：&{任意の文字}。 +1. string:<quote>任意の文字（エスケープされた引用符を含む） ▽"< quote> +2. 地図：&\{任意の文字}。 3. word: スペースを除く任意の文字 エージェントの内部では、この正規表現を使ってフィールドを抽出しています。 -``` +```regex ([^\s]*?)=(".*?[^\\]"|&{.*?}|[^\s]*) ``` @@ -126,4 +126,4 @@ time="2015-03-26T01:27:38-04:00" level=error msg="Foo bar baz" foo=bar - "level": "error" - "msg": "Foo bar baz" - "foo": "bar" -``` +``` \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx index 73d261e282e..423a72500c4 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx @@ -3269,26 +3269,26 @@ translationType: machine この例では、実行可能ファイルと名前を使用してプロセス メトリクスを除外します。 - ``` - exclude_matching_metrics: # You can combine attributes from different metrics - process.name: - - regex "^java" # Exclude all processes starting with "java" - process.executable: - - "/usr/bin/python2" # Exclude the Python 2.x executable - - regex "\\System32\\svchost" # Exclude all svchost executables + ```yml + exclude_matching_metrics: # You can combine attributes from different metrics + process.name: + - regex "^java" # Exclude all processes starting with "java" + process.executable: + - "/usr/bin/python2" # Exclude the Python 2.x executable + - regex "\\System32\\svchost" # Exclude all svchost executables ``` `exclude_matching_metrics` [をKubernetesインテグレーション](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/)の環境変数として構成するには、それを `env:` オブジェクト内のマニフェストに追加します。 ```yml env: - - name: NRIA_EXCLUDE_MATCHING_METRICS - value: | - process.name: - - regex "^java" - process.executable: - - "/usr/bin/python2" - - regex "\\System32\\svchost" + - name: NRIA_EXCLUDE_MATCHING_METRICS + value: | + process.name: + - regex "^java" + process.executable: + - "/usr/bin/python2" + - regex "\\System32\\svchost" ``` デフォルト @@ -5550,83 +5550,83 @@ translationType: machine ```bash curl http://localhost:8003/v1/status - { - "checks": { - "endpoints": [ - { - "url": "https://infrastructure-command-api.newrelic.com/agent_commands/v1/commands", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/infra/v2/metrics", - "reachable": true - }, - { - "url": "https://identity-api.newrelic.com/identity/v1", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/inventory", - "reachable": true - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://infrastructure-command-api.newrelic.com/agent_commands/v1/commands", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://identity-api.newrelic.com/identity/v1", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/inventory", + [output] "reachable": true + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` メイン ステータス エンドポイント (エラーあり): ```bash curl http://localhost:8003/v1/status - { - "checks": { - "endpoints": [ - { - "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", - "reachable": false, - "error": "endpoint check timeout exceeded" - }, - { - "url": "https://infra-api.newrelic.com/infra/v2/metrics", - "reachable": true - }, - { - "url": "https://identity-api.newrelic.com/identity/v1", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/inventory", - "reachable": true - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": false, + [output] "error": "endpoint check timeout exceeded" + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://identity-api.newrelic.com/identity/v1", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/inventory", + [output] "reachable": true + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` エラーエンドポイントの例: ```bash curl http://localhost:18003/v1/status/errors - { - "checks": { - "endpoints": [ - { - "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", - "reachable": false, - "error": "endpoint check timeout exceeded" - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": false, + [output] "error": "endpoint check timeout exceeded" + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` これはメイン ステータス エンドポイントに似ていますが、エラーのあるエンドポイントのみをフィルターします。 @@ -5635,10 +5635,10 @@ translationType: machine ```bash curl http://localhost:8003/v1/status/entity - { - "guid":"MMMMNjI0NjR8SU5GUkF8TkF8ODIwMDg3MDc0ODE0MTUwNTMy", - "key":"your-host-name" - } + [output] { + [output] "guid":"MMMMNjI0NjR8SU5GUkF8TkF8ODIwMDg3MDc0ODE0MTUwNTMy", + [output] "key":"your-host-name" + [output] } ``` エージェント/ホスト エンティティに関する情報を返します。エージェントがエージェント/ホスト エンティティに関する情報をまだ持っていない場合、応答ステータス コード*204* (「コンテンツなし」) が返されます。したがって、エージェントがエンティティ データを提供するまでに、いくつかのリクエストが必要になる場合があります。 diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx index 85dfefcc265..ef33ce5f264 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx @@ -117,7 +117,7 @@ translationType: machine * [ログファイルの設定](#log-file). * [エージェントのバイナリの場所を変更する](#agent-binary). - + ## サービススクリプトのインストール [#install-service-script] @@ -131,10 +131,7 @@ translationType: machine - + ホストで使用されているサービスマネージャーをプログラムで知る良い方法はありませんが、いくつかのヒューリスティックな方法をご紹介します。 サービスマネージャーを決定するには、以下のコマンドを使用します。 @@ -168,10 +165,7 @@ translationType: machine サポートされているサービスマネージャーのいずれかを使用している場合は、ホスト用のサービススクリプトをインストールします。 - + 1. サービスファイル`./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`をにコピーします `/etc/systemd/system/newrelic-infra.service` 2. サービススクリプトを有効にします。 @@ -181,10 +175,7 @@ translationType: machine ``` - + 1. サービスファイル`./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`をにコピーします `/etc/init.d/system/newrelic-infra` 2. 以下のコマンドを実行してください。 @@ -195,10 +186,7 @@ translationType: machine ``` - + 1. サービスファイル`./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`をにコピーします `/etc/init/newrelic-infra.conf` 2. 次のコマンドを実行してください。 @@ -230,20 +218,14 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml この変更を恒久的なものにするには、サービススクリプトを編集します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`を開きます。 2. 行`ExecStart=/usr/bin/newrelic-infra`を検索します。 3. 構成フラグと構成ファイルのパスを追加します。この例では、構成ファイルは`/opt`ディレクトリ`ExecStart=/usr/bin/newrelic-infra -config /opt/config.yaml`にあります。 4. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`を開きます。 2. 行`DAEMON=/usr/bin/$NAME”`を検索します。 @@ -257,10 +239,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml 5. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`を開きます。 2. 行`exec /usr/bin/newrelic-infra`を検索します。 3. `config flag`と`config file path`を追加します。ここで、 `config file`は`/opt`ディレクトリ`exec /usr/bin/newrelic-infra -config /opt/config.yaml`にあります。 @@ -279,10 +258,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml `pid-file`の場所を変更するには： - + 起動時に、エージェントはプロセス`pid`を`pid-file`に書き込みます。ファイルが存在しない場合は、ファイルが作成されます。 デフォルトでは、エージェントはパス`/var/run/newrelic-infra/newrelic-infra.pid`を使用して`pid-file`を作成します。変更するには、次のいずれかのオプションを使用します。 @@ -304,10 +280,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml ``` - + `pid-file`を管理するために`PIDFILE`環境変数を使用することはお勧めしません。 @@ -333,30 +306,21 @@ Linuxエージェントはデフォルトで`root`として実行されますが 1. サービススクリプトを編集します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`を開きます。 2. 行`[Service]`を検索します。 3. 行`User=user_name`を追加し、 `user_name`をエージェントを実行するユーザー（ `PRIVILEGED`または`UNPRIVILEGED` ）に置き換えます。 4. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`を開きます。 2. 行`USER=root`を検索します。 3. `root`を、エージェントを実行するユーザー（ `PRIVILEGED`または`UNPRIVILEGED` ）に置き換えます。 4. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`を開きます。 2. 行`exec /usr/bin/newrelic-infra`を検索します。 3. `exec su -s /bin/sh -c ‘exec “$0” “$@“’ user_name-- /usr/bin/newrelic-infra`に置き換えます。 @@ -427,30 +391,21 @@ Linuxエージェントはデフォルトで`root`として実行されますが 実行ファイルの場所を変更するには、サービススクリプトを編集します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`を開きます。 2. 行`[ExecStart=/usr/bin/newrelic-infra]`を検索します。 3. パスの交換 4. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`を開きます。 2. 行`DAEMON=/usr/bin/$NAME`を検索します。 3. パスの交換 4. ファイルを保存します。 - + 1. サービススクリプト`./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`を開きます。 2. 行`exec /usr/bin/newrelic-infra`を検索します。 3. パスの交換 @@ -467,4 +422,4 @@ Linuxエージェントはデフォルトで`root`として実行されますが * [ログ転送](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent#tarball-install)を有効にします。 * [Flex 実行可能ファイルを手動で追加して、](https://github.com/newrelic/nri-flex/releases) Flex 統合を有効にします。 * 他の [インフラストラクチャの統合を追加](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) 外部サービスからデータを収集します。 -* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure-start-stop-restart-check-agent-status#linux). +* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure-start-stop-restart-check-agent-status#linux). \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx index 37db1280501..53422166cb2 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx @@ -34,46 +34,46 @@ macOSでは、Infrastructureエージェントの以下の機能はまだ利用 2. システムに[Homebrew](https://brew.sh/)がインストールされていることを確認します。Homebrewが以下とともにインストールされているかどうかを確認できます。 ```bash - which brew + which brew ``` インストールされていない場合は、このコマンドでインストールできます（または[Homebrew](https://brew.sh/)の最新の手順を確認してください）。 ```bash - /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" + /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ``` 3. 次に、ターミナルを開いて次のコマンドを実行します。 ```bash - brew install newrelic-infra-agent -q + brew install newrelic-infra-agent -q ``` 4. Infrastructureエージェントサービスを開始します。 ```bash - brew services start newrelic-infra-agent + brew services start newrelic-infra-agent ``` -5. 設定ファイルを作成し、を追加します。 +5. 設定ファイルを作成し、を追加します。 Intel x86： ```bash - sudo mkdir -p /usr/local/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /usr/local/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml ``` Appleシリコン： ```bash - sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml ``` 数分待ってから、[Infrastructure UIでサーバーを確認します](/docs/infrastructure/infrastructure-ui-pages/infra-ui-overview)。数分待ってもデータが表示されない場合は、[トラブルシューティングの手順](/docs/infrastructure/new-relic-infrastructure/troubleshooting/no-data-appears-infrastructure)に従ってください。 - + ## 次は何ですか？ [#configure] @@ -85,4 +85,4 @@ macOSでは、Infrastructureエージェントの以下の機能はまだ利用 ## エージェントの更新 [#update] -最新バージョンにアップグレードするには、標準の手順に従って[インフラストラクチャエージェントを更新します](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent)。 +最新バージョンにアップグレードするには、標準の手順に従って[インフラストラクチャエージェントを更新します](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent)。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx index 45a5a905a63..d4d678766dc 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx @@ -24,33 +24,36 @@ Linux環境用のインフラストラクチャエージェントをデフォル apt でアンインストール (Debian.webpデビアン、ubuntu iconUbuntu）} + title={<>aptでアンインストールする（Debian.webpデビアン、ubuntu icon + } > root権限として、以下のコマンドを実行します。 - ``` + ```sh sudo apt-get remove newrelic-infra ``` yum (amazon linux.webpアマゾン・リナックス、centos iconCentOS、redhat iconRHEL）} + title={<>yumでアンインストールする（amazon linux.webpAmazon Linux、centos iconセントOS、redhat icon + } > root権限として、以下のコマンドを実行します。 - ``` + ```sh sudo yum remove newrelic-infra ``` Zypper でアンインストール (suse iconSLES）} + title={<>Zypperでアンインストール（suse icon + } > root権限として、以下のコマンドを実行します。 - ``` + ```sh sudo zypper -n remove newrelic-infra ``` @@ -62,52 +65,31 @@ Linux環境用のインフラストラクチャエージェントをデフォル また、Azure や Google Cloud Platform 統合などのモニタリング クラウド統合もアンインストールする必要があります。 そうしないと、UI にデータのないホストが表示され続けます。 -## アンインストールするWindows Server iconインフラストラクチャエージェント [#uninstall-windows] +## アンインストールWindows Server icon [#uninstall-windows] Windows環境用のインフラストラクチャエージェントのデフォルトのインストール手順を使用した場合は、アンインストールするために 1. Windows 管理者グループに[アドミニストレータ権限が](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure#permissions)あることを確認してください。 - 2. [インフラストラクチャエージェントの停止](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#windows). - -3. Windows - - - **Control Panel** - - - から、 - - - **Add/Remove Programs and Features** - - - ツールを使用してインフラストラクチャエージェントをアンインストールします。 - -4. Windows - - - **Program Files** - - - から、 New Relicフォルダーを手動で削除して、Windows のインフラストラクチャエージェントに関連付けられているすべてのファイルを削除します。 +3. Windows **Control Panel**から、 **Add/Remove Programs and Features**ツールを使用してインフラストラクチャエージェントをアンインストールします。 +4. Windows **Program Files** から、 New Relicフォルダーを手動で削除して、Windows のインフラストラクチャエージェントに関連付けられているすべてのファイルを削除します。 [assisted](/docs/infrastructure/install-configure-infrastructure/windows-installation/assisted-install-infrastructure-windows) または [manual](/docs/infrastructure/install-configure-infrastructure/windows-installation/manual-install-infrastructure-windows) のインストールプロセスに従った場合は、エージェントファイルを解凍したときに作成されたすべてのファイルを手動で削除する必要があります。 -## アンインストールmacOS iconmacOSインフラストラクチャエージェント [#uninstall-macos] +## アンインストールmacOS icon [#uninstall-macos] macOS環境用のインフラストラクチャエージェントのデフォルトのインストール手順を使用した場合、アンインストールするには 1. [インフラストラクチャエージェントの停止](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#macOS): - ``` - brew services stop newrelic-infra-agent + ```sh + brew services stop newrelic-infra-agent ``` 2. ターミナルからアンインストールコマンドを実行します。 - ``` - brew uninstall newrelic-infra-agent + ```sh + brew uninstall newrelic-infra-agent ``` ## コンフィグ管理ツールによるアンインストール [#uninstall-other] @@ -146,4 +128,4 @@ macOS環境用のインフラストラクチャエージェントのデフォル ## オプション残りのファイルを消去する [#leftover-files] -選択したプラットフォームの標準パッケージ管理ツールを使用している場合、アンインストールプロセスでは通常、設定ファイルやその他の雑多なファイルが残ります。New Relic インフラストラクチャ エージェントをアンインストールした後、残ったファイルを完全に消去する必要がある場合は、お使いのオペレーティング システムの標準的な手順に従ってください。 +選択したプラットフォームの標準パッケージ管理ツールを使用している場合、アンインストールプロセスでは通常、設定ファイルやその他の雑多なファイルが残ります。New Relic インフラストラクチャ エージェントをアンインストールした後、残ったファイルを完全に消去する必要がある場合は、お使いのオペレーティング システムの標準的な手順に従ってください。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx index 60bf0d290f9..43d5f14f01f 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx @@ -20,10 +20,7 @@ translationType: machine 以下にいくつか例を示します。 - + @@ -75,10 +72,7 @@ translationType: machine
- + @@ -130,41 +124,35 @@ translationType: machine
- + Helmと`kubectl`を実行するマシンで適切なコンテキストを使用していることを確認してください。 で利用可能なコンテキストを確認することができます。 - ``` + ```sh kubectl config get-contexts ``` で、目的のコンテキストに切り替えます。 - ``` + ```sh kubectl config use-context CONTEXT_NAME ``` Helmを使ってKubernetesの統合機能をインストールした場合は、Helmを使ってアンインストールすればよい。 - ``` + ```sh helm uninstall --namespace NAMESPACE_USED_DURING_INSTALLATION RELEASE_NAME ``` マニフェストを使用してKubernetesインテグレーションをインストールした場合は、同じマニフェストを使用してアンインストールします。 - ``` + ```sh kubectl delete -f newrelic-infrastructure.yaml ``` - + @@ -216,10 +204,7 @@ translationType: machine
- + @@ -271,10 +256,7 @@ translationType: machine
- + @@ -326,10 +308,7 @@ translationType: machine
- + 1. `cd /path/to/statsd` 2. `npm uninstall @newrelic/statsd-infra-backend` 3. StatsD config.js から、バックエンドのリストから`"@newrelic/statsd-infra-backend"`エントリを削除してください。 @@ -354,10 +333,7 @@ translationType: machine 1. 以下の手順で、integrationsパッケージを削除します。古い統合機能の設定ファイルは削除されませんので、再度設定する必要はありません。 - + @@ -404,7 +380,7 @@ translationType: machine @@ -414,4 +390,4 @@ translationType: machine -2. [以下の説明にしたがって、統合機能を一つずつインストールしてください](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic) 。インテグレーションパッケージを複製するには、利用可能なすべてのインテグレーションを再度インストールする必要があります。 +2. [以下の説明にしたがって、統合機能を一つずつインストールしてください](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic) 。インテグレーションパッケージを複製するには、利用可能なすべてのインテグレーションを再度インストールする必要があります。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx index cc3bf4bed13..157ed121750 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx @@ -17,7 +17,7 @@ Windows用インフラストラクチャエージェントのアシストイン 1. [パッケージ化されたエージェントファイル](https://download.newrelic.com/infrastructure_agent/binaries/windows/)をダウンロードするか、次のコマンドを使用して、エージェントの特定のバージョンとそのチェックサムを自動的にフェッチし、ダウンロード後に検証します。`$arch=amd64`を目的のアーキテクチャ（amd64、386）に置き換え、 `$v=1.27.4`を[最新または特定のバージョン](https://github.com/newrelic/infrastructure-agent/releases/latest)に置き換えます。 - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -25,21 +25,17 @@ Windows用インフラストラクチャエージェントのアシストイン 3. ファイルが以下のような構造で解凍されることを確認してください。 - Infra-windows-files.png + Infra-windows-files.png 4. 解凍したら、インストールPowerShellスクリプト`installer.ps1`にアクセスして編集します。 -5. 更新する . +5. 更新します。 6. オプション。その他の [パラメータを更新する](#parameters). 7. 管理者権限で`installer.ps1`を実行します。 - + ## インストールの設定 [#parameters] @@ -123,7 +119,7 @@ Windowsのアシストインストールでは、以下のパラメータを設 @@ -198,4 +194,4 @@ Windowsのアシストインストールでは、以下のパラメータを設 * [カスタムアトリビュートを追加](/docs/Infrastructure-configure-your-agent#conf-custom_attributes)して、Infrastructureデータに注釈を付けます。 * [AWSアカウントを接続します](/docs/infrastructure-amazon-aws-ec2-integration#connect)（お使いのサーバーがAmazon EC2上で稼働している場合）。 * 他の[New Relic Infrastructureインテグレーション](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations)を追加して、外部サービスからデータを収集します。 -* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure-start-stop-restart-check-agent-status#linux). +* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure-start-stop-restart-check-agent-status#linux). \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx index ec94fe2e99c..ea47df19246 100644 --- a/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/jp/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx @@ -21,7 +21,7 @@ Windows用インフラストラクチャ・エージェントのカスタム・ 1. [パッケージ化されたエージェントファイル](https://download.newrelic.com/infrastructure_agent/binaries/windows/)をダウンロードするか、次のコマンドを使用して、エージェントの特定のバージョンとそのチェックサムを自動的にフェッチし、ダウンロード後に検証します。`$arch=amd64`を目的のアーキテクチャ（amd64、386）に置き換え、 `$v=1.27.4`を[最新または特定のバージョン](https://github.com/newrelic/infrastructure-agent/releases/latest)に置き換えます。 - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -29,11 +29,7 @@ Windows用インフラストラクチャ・エージェントのカスタム・ 3. ファイルが以下のような構造で解凍されることを確認してください。 - Infra-windows-files.png + Infra-windows-files.png 4. [サービススクリプトのインストール](#install-service-script). @@ -116,7 +112,7 @@ C:\Program Files\New Relic\newrelic-infra\installer.ps1 * `log_file`フィールドを使用して`newrelic-infra.yml`構成ファイルにカスタムパスを設定します。 * `newrelic-infra`バイナリを実行するときに、 `-log_file`を使用してコマンドライン引数として渡します。 - + ## 次は何ですか？ [#what-next] @@ -125,4 +121,4 @@ C:\Program Files\New Relic\newrelic-infra\installer.ps1 * [カスタムアトリビュート](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes) を追加して、インフラストラクチャデータに注釈を付けます。 * [](/docs/integrations/amazon-integrations/get-started/connect-aws-new-relic-infrastructure-monitoring/)サーバーがAmazon EC2でホストされている場合は、AWSアカウントを接続します。 * その他 [New Relic のインフラ統合](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations/) を追加して、外部サービスからデータを収集する。 -* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows). +* 手動で [起動、停止、再起動、またはエージェントの状態を確認](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows). \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx index 1e170f0868c..00d1ed4cf61 100644 --- a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx +++ b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx @@ -44,6 +44,6 @@ translationType: machine * `/etc/newrelic-infra.yml`構成ファイルの`log_file`エントリを変更します。インストール スクリプトはその目的のために`/var/log/newrelic-infra/`フォルダーを作成するため、次の値をお勧めします。 - ``` + ```yml log_file: /var/log/newrelic-infra/newrelic-infra.log - ``` + ``` \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx index 244fa509cbe..8d3c36b1fe7 100644 --- a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx +++ b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx @@ -19,63 +19,51 @@ translationType: machine 1. [newrelic-infra.yml](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#logging-variables)構成ファイルを編集し、ログを有効にするために必要なフラグを追加します。たとえば、デフォルトのログファイルパスですべてのトレースログを有効にするには、次のようにします。 - ``` - log: - level: trace + ```yml + log: + level: trace ``` インフラストラクチャエージェントバージョン1.26.0以前では、異なるログ設定が必要です。 -``` - verbose: 1 - trace: - # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. - - v3.submission - # dm.submission enables detailed logging for integrations using Dimensional Metric format. - - dm.submission +```yml +verbose: 1 +trace: + # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. + - v3.submission + # dm.submission enables detailed logging for integrations using Dimensional Metric format. + - dm.submission ``` 2. [あなたのinitシステム](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) を使って、エージェントサービスを再起動してください。 - + CentOS 7、Debian 8、RHEL 7、Ubuntu 15.04以降ではSystemDコマンドを使用します。 - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Debian 7ではSystem Vコマンドを使用します。 - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Amazon Linux、CentOS 6、RHEL 6、Ubuntu 14.10以下でUpstartコマンドを使用します。 - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -86,9 +74,9 @@ translationType: machine v3.submissionが有効な場合のログ例。 -``` +```log time="2021-12-28T09:27:28Z" level=debug msg="Sending events to metrics-ingest." component=MetricsIngestSender key=... numEvents=3 postCount=1 timestamps="[2021-01-01 09:27:28 +0000 UTC]" time="2021-12-28T09:27:28Z" level=debug msg="Preparing metrics post." component=MetricsIngestSender postCount=1 time="2021-12-28T09:27:28Z" level=trace msg="[{\"EntityID\":111,\"IsAgent\":true,\"Events\":[{\"eventType\":\"SystemSample\",\"timestamp\":1640683648,\"entityKey\":\"...\",\"cpuPercent\":0.2004008016032026, ...}]" feature=v3.submission time="2021-12-28T09:27:29Z" level=debug msg="Metrics post succeeded." component=MetricsIngestSender postCount=1 -``` +``` \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx index 2542716f06b..199ab7a7e2c 100644 --- a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx +++ b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx @@ -110,22 +110,19 @@ New Relic のインフラストラクチャ エージェントは、CPU やメ
- ``` + ```sh sudo zypper -n remove newrelic-infra-integrations --clean-deps ``` - ニューレリック . + New Relic 。
-### エージェントプラグインレポートの削減 [#reduce_plugins] +### エージェントプラグインレポートの削減 [#reduce\_plugins][#reduce_plugins] インフラストラクチャエージェントには、インベントリデータ（特定のシステム構成や状態の情報）を収集するプラグインが組み込まれています。システムによっては、プラグインが多くのデータを収集している場合、CPU の消費量が比較的大きくなることがあります。フットプリントを減らすために、不要なデータを報告する特定のプラグインを無効にしたり、サンプリングの頻度を減らしたりすることができます。 - + * **Disable a single plugin:** プラグインを無効にするには、対応するプロパティ値を`-1`に設定します。 * **Disable all plugins:** `disable_all_plugins: true` * **Enable selected plugins:** 特定のプラグインを有効にするには、 `disable_all_plugins`に例外を挿入します。 たとえば、次の設定では、すべてのプラグインが無効になり、ネットワーク インターフェイスと SELinus プラグインが 120 秒ごとにレポートするように再度有効になります。 - ``` + ```yml disable_all_plugins: true network_interface_interval_sec: 120 selinux_interval_sec: 120 @@ -134,7 +131,10 @@ New Relic のインフラストラクチャ エージェントは、CPU やメ SELinux semodule -lを無効にする（Linuxのみ）} + title={<>SELinux + semodule -l + を無効にする（Linuxのみ） + } > SELinuxプラグインは、 `semodule -l`システムコマンドを定期的に呼び出して、既存のSELinuxモジュールに関する情報を取得します。ほとんどのCentOS/RedHatディストリビューションでは、このコマンドはCPU消費のピークを生成します。 @@ -143,33 +143,27 @@ New Relic のインフラストラクチャ エージェントは、CPU やメ `selinux_enable_semodule: false` - + Sysctl プラグインは、 `/sys` ディレクトリ構造全体を調べ、そこにあるすべてのファイルから値を読み取ります。これを無効にするか間隔を短縮すると、インフラストラクチャ エージェントの CPU システム時間がいくらか減少する可能性があります。 インベントリの頻度を負の数に設定して無効にするか、 `sysctl_interval_sec`構成値をプラグインの連続実行間の秒数に設定して頻度を減らすことができます。 例えば、10分に1回プラグインを実行するように。 - ``` + ```yml sysctl_interval_sec: 600 ``` Sysctlプラグインを無効にするには、次のようにします。 - ``` + ```yml sysctl_interval_sec: -1 ``` `sysctl_interval_sec`プロパティの現在のデフォルト値は`60`です。 - + 以下のインベントリプラグインは、特にCPUを消費するものではありませんが、対応する設定オプションを設定することで、頻度を下げたり、無効にしたりすることができます。 @@ -222,11 +216,11 @@ New Relic のインフラストラクチャ エージェントは、CPU やメ -### ホスト上の統合の見直し [#on_host_integrations] +### ホスト上の統合の見直し [#on\_host\_integrations][#on_host_integrations] インフラストラクチャのオンホスト統合機能を使用している場合は、CPU使用率に追加の影響が出ることがあります。影響の内容や調整方法は、使用している統合機能によって異なります。 ここでは、オン・ホスト・インテグレーションのCPU使用率を調整する方法をご紹介します。 * [統合](/docs/integrations/host-integrations/host-integrations-list) に調整可能な構成オプションがあるかどうかを確認してください。 -* 可能であれば、インフラストラクチャエージェントを追加することで、監視の負荷を分散します。例えば、Kafkaの統合では、 [マルチエージェントの展開が可能です](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents) 。 +* 可能であれば、インフラストラクチャエージェントを追加することで、監視の負荷を分散します。例えば、Kafkaの統合では、 [マルチエージェントの展開が可能です](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents) 。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx index 3d36b3674ef..004c1a3e3e2 100644 --- a/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx +++ b/src/i18n/content/jp/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx @@ -23,28 +23,22 @@ New Relicのインフラストラクチャエージェントは稼働してい 1. エージェントに対する1スレッドの制限を解除し、コアごとに1スレッドを許可します。 - - 1. 以下のファイルをプレーンテキストエディターで開いてください。C:Program Files\\New Relic--newrelic-infra--newrelic-infra.yml + + 1. お気に入りのプレーンテキストエディタで次のファイルを開きます。 `C:\Program Files\New Relic\newrelic-infra\newrelic-infra.yml` 2. 以下の設定オプションを追加します。 - ``` + ```yml max_procs: -1 ``` - - 1. お好きなプレーンテキストエディターで以下のファイルを開いてください。/etc/newrelic-infra.yml + + 1. お気に入りのプレーンテキストエディタで次のファイルを開きます。 `/etc/newrelic-infra.yml` 2. 以下の設定オプションを追加します。 - ``` + ```yml max_procs: -1 ``` @@ -53,44 +47,32 @@ New Relicのインフラストラクチャエージェントは稼働してい 2. [あなたのinitシステム](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) を使って、エージェントサービスを再起動してください。 - + CentOS 7、Debian 8、RHEL 7、Ubuntu 15.04以降ではSystemDコマンドを使用します。 - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Debian 7ではSystem Vコマンドを使用します。 - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Amazon Linux、CentOS 6、RHEL 6、Ubuntu 14.10以前ではUpstartコマンドを使用します。 - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -101,4 +83,4 @@ New Relicのインフラストラクチャエージェントは稼働してい New Relic インフラストラクチャ エージェントは、デフォルトでは単一のオペレーティング システム スレッドで実行されます。これは、特に Windows 環境では、システムが過負荷になったときにプロセス スケジューラが CPU 時間を取得する機会をほとんど与えないことを意味している可能性があります。 -`max_procs: -1` 構成オプションを使用すると、この制限がなくなり、エージェントは CPU コアごとに 1 つのスレッドを (最大で) 使用できるようになります。 +`max_procs: -1` 構成オプションを使用すると、この制限がなくなり、エージェントは CPU コアごとに 1 つのスレッドを (最大で) 使用できるようになります。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx index f6b62552e9d..70dbfc316d9 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx @@ -12,7 +12,7 @@ translationType: machine Kubernetesインテグレーション バージョン 2 には、バージョン 3 とは異なる設定と要件がいくつかあります。 このドキュメントでは、バージョン 3 とは異なる設定と、バージョン 2 に必要な設定について説明します。特に指定がない場合は、バージョン 3 の設定を使用できます。 - バージョン 2 は置き換えられたため、使用しないでください。 このドキュメントは、バージョン 2 をまだ使用しているユーザーのために維持されています。 + New Relic ではバージョン 2 が非推奨となっており、使用は推奨されていません。 バージョン 2 のサポートは終了していますが、引き続きバージョン 2 を使用しているユーザーのためにこのドキュメントを維持しています。 現在のバージョンの [の使用を開始するには 、 インテグレーションの概要」Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/)Kubernetes を参照してください。 @@ -289,10 +289,7 @@ OpenShift でコントロール プレーンの監視を構成するには、[ 詳細なログを生成し、バージョンと設定情報を取得したい場合は、以下の情報を確認してください。 - + Kubernetesの場合、インフラストラクチャエージェントはエラーのイベントにログ エントリを追加するだけです。 最も一般的なエラーは、標準の (詳細ではない) ログに表示されます。 独自に、または New Relic サポートと協力してより詳細な調査を行う場合は、詳細モードを有効にすることができます。 @@ -336,11 +333,7 @@ OpenShift でコントロール プレーンの監視を構成するには、[ 9. [`kube-state-metrics`サービスの設定を取得します](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version)。 - + Kubernetes 統合の場合、インフラストラクチャ エージェントはエラーが発生した場合にのみログ エントリを追加します。最も一般的なエラーは、標準 (詳細ではない) ログに表示されます。独自で、または New Relic サポートと協力してより詳細な調査を行っている場合は、冗長モードを有効にすることができます。 @@ -386,10 +379,7 @@ OpenShift でコントロール プレーンの監視を構成するには、[ 8. [`kube-state-metrics`サービスの設定を取得します](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version)。 - + `kube-state-metrics`に接続しているポッドからログを取得するには: 1. 以下のコマンドを実行します。 @@ -425,10 +415,7 @@ OpenShift でコントロール プレーンの監視を構成するには、[ ``` - + マスターノードで動作しているポッドのログを取得するには 1. マスターと表示されているノードを取得します。 @@ -500,4 +487,4 @@ Kubernetes のモニタリング サービスは [、インフラストラクチ ### サービスYAMLをKubernetes統合構成に追加します [#add-service-yaml] -Kubernetesインテグレーション バージョン 2 を使用している場合は、ConfigMap 内のすべてのファイルが `/etc/newrelic-infra/integrations.d/` にマウントされるように、DaemonSet の `spec` の `volumes` および `volumeMounts` セクションにこの ConfigMap のエントリを追加する必要があります。 +Kubernetesインテグレーション バージョン 2 を使用している場合は、ConfigMap 内のすべてのファイルが `/etc/newrelic-infra/integrations.d/` にマウントされるように、DaemonSet の `spec` の `volumes` および `volumeMounts` セクションにこの ConfigMap のエントリを追加する必要があります。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx index 24db4a60427..312ebd28a6a 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx @@ -82,7 +82,7 @@ Kubernetesシークレットは、オペレーターのネームスペースか * [.NET](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-init/general) * [Ruby](https://hub.docker.com/repository/docker/newrelic/newrelic-ruby-init/general) -.NETの場合 +.NET の場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -96,7 +96,7 @@ spec: # env: ... ``` -Javaの場合 +Javaの場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -111,7 +111,7 @@ spec: # env: ... ``` -NodeJSの場合 +Node.jsの場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -126,7 +126,7 @@ spec: # env: ... ``` -Pythonの場合 +Pythonの場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -141,7 +141,7 @@ spec: # env: ... ``` -Rubyの場合 +Rubyの場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -156,7 +156,7 @@ spec: # env: ... ``` -環境固有の設定用 +環境固有の設定の場合: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -180,7 +180,7 @@ spec: value: "$(NEW_RELIC_LABELS)-$(NEW_RELIC_POD_NAME)" ``` -特定のネームスペース内のすべてをラベルでターゲットにする +ラベルを使用して特定のネームスペース内のすべてをターゲットにする: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -197,7 +197,7 @@ spec: values: ["java"] ``` -特定のラベルを持つポッドをターゲットにする +特定のラベルを持つポッドをターゲットにする: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -214,7 +214,7 @@ spec: values: ["dotnet"] ``` -デフォルト以外の名前のシークレットを使用する +デフォルト以外の名前を持つシークレットを使用する: ```yaml apiVersion: newrelic.com/v1alpha2 diff --git a/src/i18n/content/jp/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx b/src/i18n/content/jp/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx index 8408b27070f..c5e1d3930c6 100644 --- a/src/i18n/content/jp/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx +++ b/src/i18n/content/jp/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx @@ -29,9 +29,9 @@ New Relicのログ転送用Kubernetesプラグインを使用すると、クラ [Kubernetesシークレットを使用し](https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging/values.yaml#L8-L25)てNew Relic を保存している場合、`newrelic-logging` チャートはデフォルトでログを US APIエンドポイントに送信します。 ライセンスキーが EU または FedRAMP アカウントに属しており、キーの保管にシークレットが使用されている場合は、 [APIリファレンス ドキュメント](/docs/logs/log-api/introduction-log-api/#endpoint)の適切な値でエンドポイント設定を更新する必要があります。 EU アカウントでこれを設定する方法の例を次に示します。 ```yml - newrelic-logging: - enabled: true - endpoint: https://log-api.eu.newrelic.com/log/v1 + newrelic-logging: + enabled: true + endpoint: https://log-api.eu.newrelic.com/log/v1 ``` @@ -67,8 +67,8 @@ Fluent Bit の内部メトリクスをキャプチャするには、その[`prom ```yml newrelic-logging: - fluentBit: - sendMetrics: true + fluentBit: + sendMetrics: true ``` Kubernetes クラスタを tr する場合にのみ、 `newrelic-logging.fluentBit.sendMetrics`設定を有効にする必要があります。 トラブルシューティングを容易にするために、一度に 1 つの Kubernetes クラスタに対して有効にすることをお勧めします。 diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index 31d6ca08649..331c0cc9ae5 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -7,11 +7,7 @@ translationType: machine New RelicAWSAWSとNew Relic アカウントを正常にリンクしたら、 Lambda レイヤーを追加して、コンテナ化されていない Lambda 関数を実装できます。これにより、New Relic エージェントが統合され、関数が呼び出されるたびに自動監視が可能になります。 -a diagram depicting non-containerized lambda function instrumentation +a diagram depicting non-containerized lambda function instrumentation ## あなたが始める前に [#begin] @@ -33,10 +29,7 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす ニーズに応じて、拡張機能をバイパスして CloudWatch でテレメトリーのみを表示するか、CloudWatch をバイパスするか、CloudWatch をフォールバックとして使用するかを選択できます。 このドキュメントの最後にある[CloudWatch](#CloudWatch-only)セクションで、各オプションについて説明します。 - + `newrelic-lambda` CLI クイックスタートを使用して Lambda 関数を計算できます。 New Relicインストゥルメンテーション レイヤーをインストールまたはアップグレードするには、次のコマンドを実行します。 @@ -52,10 +45,7 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす CLIはバッチで多くの関数を操作できることに注意してください。 `--function all` 、 `--function installed` 、または`--function not-installed`を使用して、リージョン内のすべての関数を操作するか、既存のNewRelicインストルメンテーションの有無にかかわらず関数のみを操作します。 - + AWSのサーバーレスアプリケーションモデル（SAM）は、CloudFormationテンプレートの一種であり、機能を依存するリソースに関連づけたり、アプリケーション全体のライフサイクルを管理したりすることを容易にします。私たちはLambdaのサンプル関数のほとんどにSAMとCloudFormationを使用しており、他の多くのツールはCloudFormationテンプレートの上に構築され、抽象化の追加レイヤーを提供しています。 CloudFormation は、 AWSリソースのプロビジョニングと管理を簡素化するAWSサービスです。 YAML または JSON テンプレートでリソースの望ましい状態を定義することにより、CloudFormation は基盤となるAPIコールを自動的に処理し、必要に応じてリソースを作成、更新、または削除します。 この宣言型アプローチにより、インフラストラクチャ管理が自動化され、一貫性と再現性が確保されます。 @@ -99,10 +89,7 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす 通常、関数とそのリソースを記述する`template.yaml`という名前のファイルがあります。 - + Serverless フレームワークは、サーバーレス アプリケーション向けの人気のある開発およびデプロイメント ツールです。 これは AWS 向けに Node.js で記述されており、主に CloudFormation テンプレート上の高レベルの抽象化として機能します。 Node、Python、Ruby、Java、.NET 関数に適しています。 New Relic では、Serverless Framework アプリケーションのインスツルメンテーションを簡素化するために、 [Serverless Framework Plugin](https://github.com/newrelic/serverless-newrelic-lambda-layers) を提供しています。 @@ -134,19 +121,13 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす ``` - + Terraform は、コード ツールとしての一般的なインフラストラクチャとして人気の高いツールです。 AWS リソースの管理に使用できます。 Terraform スクリプトを使用して インストゥルメントされた Lambda 関数のデプロイの [例をいくつか](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) 紹介します。New Relic [New Relic Terraform プロバイダーを](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations)使用して、 AWSインテグレーションをセットアップできます。 - + 上記の方法よりもエラーが発生しやすく、手間がかかりますが、AWS LambdaコンソールからNew Relicを使用するようにLambda関数の設定を手動で変更することができます。Node.jsの場合、 Python、Ruby、Java。 New Relicランタイムに LambdaRuby を実装する方法の例を次に示します。 @@ -182,15 +163,17 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす * `NEW_RELIC_LAMBDA_HANDLER`: 先ほどコピーした関数の元のハンドラ値に設定します。 * `NEW_RELIC_LICENSE_KEY`: New Relicライセンスキーに設定します。 - * `NEW_RELIC_LOG_ENDPOINT`: [https://log-api.newrelic.com/log/v1](https://log-api.newrelic.com/log/v1) に設定します。 - * `NEW_RELIC_TELEMETRY_ENDPOINT`: [https://cloud-collector.newrelic.com/aws/lambda/v1](https://cloud-collector.newrelic.com/aws/lambda/v1) に設定します。 + * `NEW_RELIC_LOG_ENDPOINT`: [https://log-api.newrelic.com/log/v1](https://log-api.newrelic.com/log/v1)に設定します。 + * `NEW_RELIC_TELEMETRY_ENDPOINT`: [https://cloud-collector.newrelic.com/aws/lambda/v1](https://cloud-collector.newrelic.com/aws/lambda/v1)に設定します。 14. Lambda 関数のログ (関数が STDOUT に書き込むすべての内容を含む) をNew Relicに送信する場合は、必ず `NEW_RELIC_EXTENSION_SEND_FUNCTION_LOGS` 環境変数を `true` に設定してください。 15. 実行ロールを変更して、 New Relicシークレットにアクセスできるようにします。 * `NEW_RELIC_LICENSE_KEY`という名前のシークレットの ARN を見つけます。 + * 関数の実行ロールに、以下のコードのような新しいインライン ポリシーを追加します。 `SECRET_ARN`を上記で見つけた値に置き換えます。 + ```json "Statement": [ { @@ -203,11 +186,11 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす ] ``` - - New Relicレイヤーは、 New Relic Rubyエージェントを自動的に配信し、Lambda 関数の呼び出し前にRuby `require` を介してロードされます。 競合を避けるため、Ruby エージェントのコピーを他の場所に含めないでください。 エージェントの存在を活用するために、関数内で必要なNew Relic RubyエージェントAPI呼び出しを自由に実行してください。 - + + New Relicレイヤーは、 New Relic Rubyエージェントを自動的に配信し、Lambda 関数の呼び出し前にRuby `require` を介してロードされます。 競合を避けるため、Ruby エージェントのコピーを他の場所に含めないでください。 エージェントの存在を活用するために、関数内で必要なNew Relic RubyエージェントAPI呼び出しを自由に実行してください。 + - Java、Python、Node.js、および .Net ランタイムは、 Rubyと同じインストゥルメンテーション フローに従いますが、ハンドラーがいくつか異なります。 関数のコンソールで新しくアタッチされたレイヤーを指すように関数のハンドラーを更新する方法は次のとおりです。 + Java、Python、Node.js、および .Net ランタイムは、 Rubyと同じインストゥルメンテーション フローに従いますが、ハンドラーがいくつか異なります。 関数のコンソールで新しくアタッチされたレイヤーを指すように関数のハンドラーを更新する方法は次のとおりです。 * Javaです。 @@ -220,17 +203,14 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす * .Net の場合、ハンドラーを設定する必要はありません。 - Go の場合、Lambda関数を計装するにはソースコードを変更する必要があることに注意してください。 設定変更だけでは十分ではありません。 + Go の場合、Lambda関数を計装するにはソースコードを変更する必要があることに注意してください。 設定変更だけでは十分ではありません。 ## 輸送方法 - + 各エージェント レイヤーには、CloudWatch をバイパスしてログとペイロードを New Relic に送信するための拡張機能も含まれています。 これにより、レイテンシとコストを削減できます。 ただし、関数のパフォーマンスと信頼性に影響を及ぼすリスクがあります。 New Relic Lambda レイヤーを追加すると、拡張機能が有効になり、ログ配布はデフォルトで無効になります。 @@ -240,10 +220,7 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす 関数ログは、関数の呼び出し中に関数によって記録されたログにすぎないことに注意することが重要です。 拡張機能は、 `START` 、 `END` 、 `REPORT`行などの Lambda ランタイム ログを送信しません。 - + データを CloudWatch のみに送信するか、フォールバックとして送信するかを選択できます。詳細については、 [CloudWatch フォールバックのドキュメント](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloudwatch-fallback)をご覧ください。 @@ -251,4 +228,4 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす ## 次は何ですか？ [#find-data] * これらの手順を完了すると、 [Lambda 監視UI](/docs/lambda-monitoring-ui)にデータレポートが表示されます。 -* データが見つからない場合は、 [「Lambda 有効化のトラブルシューティング」](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot)を参照してください。 +* データが見つからない場合は、 [「Lambda 有効化のトラブルシューティング」](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot)を参照してください。 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apis/rest-api-v2/migrate-to-nrql.mdx b/src/i18n/content/kr/docs/apis/rest-api-v2/migrate-to-nrql.mdx new file mode 100644 index 00000000000..543b74ebd86 --- /dev/null +++ b/src/i18n/content/kr/docs/apis/rest-api-v2/migrate-to-nrql.mdx @@ -0,0 +1,92 @@ +--- +title: NRQL로 마이그레이션 +tags: + - APIs + - REST API v2 + - NRQL +metaDescription: How to migrate your REST API v2 queries to NRQL queries. +freshnessValidatedDate: never +translationType: machine +--- + +## 앱의 측정항목 이름 나열 + +애플리케이션에 사용할 수 있는 메트릭 이름을 보려면 다음을 수행하십시오. + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appId = '$APP_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +애플리케이션 이름을 사용해서 필터링할 수도 있습니다. + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appName = '$APP_NAME' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +또는 특정 에이전트(호스트)를 사용하는 경우: + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE realAgentId = '$AGENT_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +## 앱의 메트릭 타임슬라이스 데이터 값 가져오기 + +REST API v2는 지표 이름 목록과 지표 타임슬라이스 데이터를 가져오는 값 목록을 허용합니다. + +메트릭 이름은 동일하므로 NRQL 쿼리의 `metricTimesliceName` 필드로 필터링할 수 있습니다. + +각 API 값은 NRQL 함수에 매핑될 수 있습니다. 아래 표를 참조하세요. + +예를 들어 다음 API 요청에 대해: + +```bash +curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \ + -H "X-Api-Key:${API_KEY}" -i \ + -d 'names[]=HttpDispatcher&values[]=average_call_time&values[]=call_count' +``` + +다음 쿼리를 사용하면 됩니다. + +```nrql +SELECT COUNT(newrelic.timeslice.value) AS call_count, average(newrelic.timeslice.value) * 1000 AS average_call_time +FROM Metric +WHERE appId = $APP_ID AND metricTimesliceName = 'HttpDispatcher' +``` + +| 값(RPM) | NRQL 함수 | | -------------------------- | ----------------------------------------------------------------------------------------------------------- | | 평균\_응답\_시간 | 평균(newrelic.timeslice.value) \* 1000 | | 분당 통화 | 비율(newrelic.timeslice.value의 개수), 1분) | | 통화 횟수 | newrelic.timeslice.value의 개수 | | 최소\_응답\_시간 | 최소(newrelic.timeslice.value) \* 1000 | | 최대\_응답\_시간 | 최대(newrelic.timeslice.value) \* 1000 | | 평균\_독점\_시간 | 평균(newrelic.timeslice.value\['totalExclusive'] / newrelic.timeslice.value\['개수']) \* 1000 | | 평균값 | 평균(newrelic.timeslice.value) | | 분당 총 통화 시간 | 비율(newrelic.timeslice.value 합계), 1분) | | 분당 요청 수 | 비율(newrelic.timeslice.value 개수), 1분) | | 표준 편차 | stddev(newrelic.timeslice.value) \* 1000 | | 평균\_시간 | 평균(newrelic.timeslice.value) \* 1000 | | 개수 | 개수(newrelic.timeslice.value) | | 호스트별 사용 바이트 | 평균(newrelic.timeslice.value) \* 1024 \* 1024 | | 호스트별\_사용된\_mb | 평균(newrelic.timeslice.value) | | 총\_사용\_MB | 합계(newrelic.timeslice.value) | | 평균\_통화\_시간 | 평균(newrelic.timeslice.value) \* 1000 | | 총\_값 | 합계(newrelic.timeslice.value) | | 최소값 | 최소값(newrelic.timeslice.value) | | 최대값 | 최대(newrelic.timeslice.value) | | 비율 | 비율(newrelic.timeslice.value 합계), 1초) | | 처리량 | 비율(newrelic.timeslice.value 개수), 1초) | | as\_percentage | 평균(newrelic.timeslice.value) \* 100 | | 오류율(count(newrelic.timeslice.value), 1분) | | 오류\_카운트 | count(newrelic.timeslice.value) | | 총 시간 | 합계(newrelic.timeslice.value) \* 1000 | | 활성 세션 | 평균(newrelic.timeslice.value) | | 총 방문수 | 합계(newrelic.timeslice.value) | | 퍼센트 | 평균(newrelic.timeslice.value) \* 100 | | 퍼센트(`CPU/User Time`) | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | 시간 백분율 | 100 \* 합계(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | 활용도 | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | 방문\_백분율 | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | + +함수에 `$TIME_WINDOW_IN_SECONDS` 포함되어 있는 경우 이를 쿼리하려는 시간 창으로 바꿔야 함을 의미합니다. + +예를 들어, 30분 시간 창을 쿼리하는 경우 `$TIME_WINDOW_IN_SECONDS` `1800` 로 바꿔야 합니다. + +### Apdex 메트릭 + +| 값(RPM) | NRQL 함수 | | ------------- | -------------------------------------------------------------------------------------------- | | 점수 | apdex(newrelic.timeslice.value) | | s | apdex(newrelic.timeslice.value) 또는 count(newrelic.timeslice.value) | | t | apdex(newrelic.timeslice.value) 또는 sum(newrelic.timeslice.value) | | f | apdex(newrelic.timeslice.value) 또는 sum(newrelic.timeslice.value\['totalExclusive']) | | 카운트 | apdex(newrelic.timeslice.value) | | 값 | apdex(newrelic.timeslice.value) | | 해리값, 경계 | 최대(newrelic.timeslice.value) | | 레버값, | 최소(newrelic.timeslice.value) | + +### 최종 사용자 및 모바일 사용자 + +이러한 지표는 REST API v2에서 얻을 수 있는 것과 동일한 결과를 반환하지만, 일부 결과는 뉴렐릭 UI 에서 보는 것과 다를 수 있습니다. 이는 UI가 타임슬라이스 데이터 대신 이벤트를 사용하기 때문입니다. UI와 동일한 결과를 얻으려면 이벤트를 직접 쿼리해야 합니다. + +| 값(RPM) | NRQL 함수 | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 평균\_응답\_시간 | 합계(newrelic.timeslice.value) / count(newrelic.timeslice.value) \* 1000 | | 오류 비율 | (필터(count(newrelic.timeslice.value), WHERE metricTimesliceName = '최종 사용자/오류') / 필터(count(newrelic.timeslice.value), WHERE metricTimesliceName = '브라우저')) | | 평균\_fe\_응답\_시간 | 합계(newrelic.timeslice.value\['totalExclusive']) / count(newrelic.timeslice.value) \* 1000 | | 평균\_응답\_시간 | 1000 \* (합계(newrelic.타임슬라이스.값) - 합계(newrelic.타임슬라이스.값\['총\_배타적'])) / count(newrelic.timeslice.value) | | 평균\_네트워크\_시간 | (합계(newrelic.타임슬라이스.값) - 합계(newrelic.타임슬라이스.값\['총제외']) - 합계(newrelic.타임슬라이스.값\['제곱합계'])) / count(newrelic.timeslice.value) | | 총 네트워크 시간 | (newrelic.타임슬라이스.값의 합계 - newrelic.타임슬라이스.값\['총배타적']의 합계) - newrelic.타임슬라이스.값\['제곱합계']의 합계)) | | 네트워크\_시간\_백분율 | (newrelic.타임슬라이스.값의 합계 - newrelic.타임슬라이스.값\['총제외']의 합계) - newrelic.타임슬라이스.값\['제곱합계']의 합계)) / `$TIME_WINDOW_IN_SECONDS` | | 총\_독점\_시간 | 합계(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) | | fe\_time\_percentage | 100 \* 합계(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) / `$TIME_WINDOW_IN_SECONDS` | | 평균\_dom\_콘텐츠\_로드\_시간 | 평균(newrelic.timeslice.value) \* 1000 | | 평균\_대기열\_시간 | 평균(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | 총 대기열 시간 | 합계(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | 총\_도메인\_콘텐츠\_시간 | 합계(newrelic.timeslice.value) \* 1000 | | 총 앱 시간 | 합계(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) | | 평균 앱 시간 | 합계(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) / count(newrelic.timeslice.value) | | 평균\_전송\_바이트 | 합계(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | 평균 수신 바이트 | 1000 \* sum(newrelic.timeslice.value) / count(newrelic.timeslice.value) | | 출시 횟수 | 횟수(newrelic.timeslice.value) | + +### 시계열 및 요약 + +기본적으로 REST API는 일련의 메트릭 데이터 값을 반환합니다. 이러한 값의 평균을 구하려면 API 호출에 `&summarize=true` 포함시킵니다. + +NRQL에서는 그 반대입니다. 기본적으로 요약을 얻을 수 있으며, 쿼리에 `TIMESERIES` 추가하여 시계열을 얻을 수 있습니다. + +또 다른 차이점은 REST API의 기본 시간 창이 30분인 반면 NRQL에서는 1시간이라는 것입니다. + +## 여러 메트릭 쿼리 + +NRQL을 사용하면 여러 메트릭을 동시에 쿼리할 수 있습니다. 다음은 그 예입니다. + +```nrql +SELECT + FILTER(1000 * AVERAGE(newrelic.timeslice.value), WHERE metricTimesliceName = 'HttpDispatcher') as average_response_time, + FILTER(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Errors/all') as error_count, + FILTER(average(newrelic.timeslice.value), WHERE metricTimesliceName = 'Memory/Heap/Max') as used_mb_by_host +FROM Metric +WHERE appName = '$APP_NAME' +SINCE 1 day ago +``` \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index c96451998fb..d83e5c3a054 100644 --- a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -331,7 +331,8 @@ translationType: machine .NET 에이전트 `v9.2.0` 이상은 [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) 라이브러리를 자동으로 계측합니다. * 지원되는 최소 버전: 3.17.0 - * 최근 검증된 호환 버전: 3.23.0 + * 최신 검증된 호환 버전: 3.44.0 + * .NET 에이전트 v10.32.0부터 버전 3.35.0 이상이 지원됩니다. @@ -372,7 +373,7 @@ translationType: machine [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/)를 사용하세요 * 최소 지원 버전: 23.4.0 - * 최신 검증된 호환 버전: 23.5.1 + * 최신 검증된 호환 버전: 23.6.0 `Oracle.ManagedDataAccess.Core` 의 이전 버전은 통계적으로 분석될 수 있지만 테스트되지 않았으며 지원되지 않습니다. @@ -409,7 +410,7 @@ translationType: machine 지원되는 최소 버전: 2.3.0 - 최근 검증된 호환 버전: 2.26.0 + 최신 검증된 호환 버전: 2.29.0 에이전트 버전 10.12.0부터 드라이버 버전 2.7 이후에 추가된 다음 메서드가 계측됩니다. @@ -478,7 +479,7 @@ translationType: machine **Elastic.Clients.Elasticsearch** * 최소 지원 버전: 8.0.0 - * 최근 검증된 호환 버전: 8.14.6 + * 최신 검증된 호환 버전: 8.15.8 * .NET 에이전트 v10.20.1부터 버전 8.10.0 이상이 지원됩니다. * 버전 8.12.1 이상은 .NET 에이전트 v10.23.0부터 지원됩니다. @@ -596,7 +597,7 @@ translationType: machine - 3.7.403.4 + 3.7.404.5 @@ -660,7 +661,7 @@ translationType: machine - 3.1.1 + 4.0.1 @@ -678,7 +679,7 @@ translationType: machine - 5.3.2 + 5.3.14 @@ -696,7 +697,7 @@ translationType: machine - 8.0.0 + 8.0.1 @@ -790,7 +791,7 @@ translationType: machine * 최소 지원 버전: 7.1.0 - * 최근 검증된 호환 버전: 8.1.1 + * 최신 검증된 호환 버전: 8.2.5 @@ -804,7 +805,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * 최신 검증된 호환 버전: 3.7.400.19 + * 최신 검증된 호환 버전: 3.7.400.33 @@ -1249,7 +1250,7 @@ translationType: machine 지원되는 최소 버전: 2.3.0 - 최근 검증된 호환 버전: 2.26.0 + 최신 검증된 호환 버전: 2.29.0 에이전트 버전 10.12.0부터 드라이버 버전 2.7 이후에 추가된 다음 메서드가 계측됩니다. @@ -1465,7 +1466,7 @@ translationType: machine 지원되는 최소 버전: 105.2.3 - 최근 검증된 호환 버전: 111.4.0 + 최신 검증된 호환 버전: 112.1.0 알려진 비호환 버전: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -1541,7 +1542,7 @@ translationType: machine - 3.7.403.4 + 3.7.404.5 @@ -1605,7 +1606,7 @@ translationType: machine - 3.1.1 + 4.0.1 @@ -1623,7 +1624,7 @@ translationType: machine - 5.3.2 + 5.3.14 @@ -1741,7 +1742,7 @@ translationType: machine * 최소 지원 버전: 7.1.0 - * 최근 검증된 호환 버전: 8.1.1 + * 최신 검증된 호환 버전: 8.2.5 @@ -1755,7 +1756,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * 최신 검증된 호환 버전: 3.7.400.19 + * 최신 검증된 호환 버전: 3.7.400.33 diff --git a/src/i18n/content/kr/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx b/src/i18n/content/kr/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx index 19578338e73..f06f1fd5ba4 100644 --- a/src/i18n/content/kr/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx +++ b/src/i18n/content/kr/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx @@ -472,6 +472,16 @@ translationType: machine 사용자 ID를 현재 소니에 연결합니다(자세한 내용은 아래 참조). + + + + `RecordDatastoreSegment` + + + + 지원되지 않는 데이터스토어를 사이트화할 수 있도록 허용합니다(자세한 내용은 아래 참조). + + @@ -975,6 +985,135 @@ translationType: machine transaction.SetUserId("BobSmith123"); ``` + + + ### 통사론 + + ```cs + SegmentWrapper? RecordDatastoreSegment(string vendor, string model, string operation, string? commandText = null, string? host = null, string? portPathOrID = null, string? databaseName = null) + ``` + + .NET 에이전트가 지원되는 데이터 저장소와 동일한 방식으로 지원되지 않는 데이터 스토어를 자동으로 업로드할 수 있습니다. + + 이 방법을 사용하려면 .NET 에이전트와 .NET 에이전트 API [버전 10.22.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-22-0/) 이상이 필요합니다. + + ### 매개변수 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 매개변수 + + 설명 +
+ `vendor` + + *끈* + + MySQL, MSSQL, MongoDB와 같은 데이터스토어 공급업체 이름입니다. +
+ `model` + + *끈* + + 비관계형에서 테이블 이름 또는 이와 유사한 데이터스토어. +
+ `operation` + + *끈* + + SQL 데이터베이스의 "SELECT" 또는 "UPDATE"와 같은 수행되는 작업입니다. +
+ `commandText` + + *끈?* + + 선택 과목. 쿼리 또는 비관계형 데이터스토어의 유사한 설명자입니다. +
+ `host` + + *끈?* + + 선택 과목. 데이터스토어를 호스팅하는 서버입니다. +
+ `portPathOrID` + + *끈?* + + 선택 과목. 데이터스토어를 식별하는 데 도움이 되도록 호스트와 쌍을 이루는 포트, 경로 또는 기타 제외. +
+ `databaseName` + + *끈?* + + 선택 과목. 데이터스토어 이름 또는 이와 유사한 제외. +
+ + ### 보고 + + 세그먼트를 자동으로 생성하고 종료하는 IDisposable 세그먼트 래퍼입니다. + + ### 예시 + + ```cs + var transaction = NewRelic.Api.Agent.NewRelic.GetAgent().CurrentTransaction; + using (transaction.RecordDatastoreSegment(vendor, model, operation, + commandText, host, portPathOrID, databaseName)) + { + DatastoreWorker(); + } + ``` + diff --git a/src/i18n/content/kr/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx b/src/i18n/content/kr/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx index 686435f4618..000489bb0b4 100644 --- a/src/i18n/content/kr/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx +++ b/src/i18n/content/kr/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx @@ -1498,7 +1498,7 @@ PHP 에이전트 버전 10.1.0 [컨텍스트에서 APM 로그](/docs/apm/new-rel [지원되는 로깅 프레임워크를](/docs/logs/logs-context/configure-logs-context-php) 사용하는 경우 에이전트에 앱 로그를 New Relic으로 전달하도록 지시할 수 있습니다. -* `newrelic.application_logging.forward.enabled` 로그 전달을 활성화하거나 비활성화합니다. +* `newrelic.application_logging.forwarding.enabled` 로그 전달을 활성화하거나 비활성화합니다. * `newrelic.application_logging.forwarding.max_samples_stored` 앱이 New Relic에 전달하는 로그 수를 제한합니다. * `newrelic.application_logging.forwarding.log_level` 앱이 New Relic에 전달할 로그 종류를 선택할 수 있습니다. diff --git a/src/i18n/content/kr/docs/browser/browser-integrations/blazor-webassembly.mdx b/src/i18n/content/kr/docs/browser/browser-integrations/blazor-webassembly.mdx index 5f032d2dfbc..68e54ec1727 100644 --- a/src/i18n/content/kr/docs/browser/browser-integrations/blazor-webassembly.mdx +++ b/src/i18n/content/kr/docs/browser/browser-integrations/blazor-webassembly.mdx @@ -10,13 +10,9 @@ translationType: machine Blazor WebAssembly 대시보드를 사용하면 골든 메트릭을 쉽게 모니터링하고, 최종 사용자 경험을 추적하고, 시간 경과에 따른 총 페이지 보기를 확인할 수 있습니다. -우리의 브라우저 이온 에이전트로 구축된 Blazor WebAssembly 통합은 가장 중요한 쿼리 데이터인 올인원 위치를 볼 수 있는 기본 세트를 제공합니다. +우리의 브라우저 이온 에이전트로 구축된 Blazor WebAssembly 통합은 가장 중요한 쿼리 데이터인 올인원 위치를 볼 수 있는 기본 세트를 제공합니다. -Blazor WebAssembly dashboard page +Blazor WebAssembly dashboard page
New Relic과 Blazor WebAssembly 통합을 설정하면 데이터가 바로 이러한 대시보드에 표시됩니다. @@ -34,7 +30,7 @@ Blazor WebAssembly를 New Relic과 통합하는 데 인프라 에이전트가 Blazor WebAssembly에서 데이터를 수집하려면 다음 절차를 따르세요. -1. [one.newrelic.com](https://one.newrelic.com) 에서, [**Integrations & Agents** 페이지](https://one.newrelic.com/marketplace) 로 이동하세요. +1. [one.newrelic.com](https://one.newrelic.com) 에서, [**Integrations & Agents** 페이지](https://one.newrelic.com/marketplace) 로 이동하세요. 2. **Browser and mobile** 클릭한 다음 **Browser monitoring** 클릭합니다. @@ -50,7 +46,7 @@ Blazor WebAssembly에서 데이터를 수집하려면 다음 절차를 따르세 8. 응용 프로그램을 다시 시작하십시오. -9. **[one.newrelic.com](https://one.newrelic.com/all-capabilities)** 으로 이동한 다음 **Metrics & events** 클릭하세요. 샘플 NRQL 쿼리를 실행하여 뉴렐릭이 데이터를 수집하고 있는지 확인하세요. +9. **[one.newrelic.com](https://one.newrelic.com/all-capabilities)** 으로 이동한 다음 **Metrics & events** 클릭하세요. 샘플 NRQL 쿼리를 실행하여 뉴렐릭이 데이터를 수집하고 있는지 확인하세요. ```sql SELECT average(windowLoad) FROM PageViewTiming WHERE (deviceType = 'Desktop') FACET `userAgentName` SINCE 604800 seconds AGO TIMESERIES @@ -66,4 +62,4 @@ NRQL 쿼리 작성 및 대시보드 생성에 대해 자세히 알아보려면 * 기본 및 고급 쿼리를 생성 [하기 위한 쿼리 빌더 소개](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder) * [대시보드를 사용자 지정하고 다양한 작업을 수행하기 위한 대시보드 소개](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) -* 대시보드를 [관리하여 대시](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard) 보드 표시 모드를 조정하거나 대시보드에 더 많은 콘텐츠를 추가합니다. +* 대시보드를 [관리하여 대시](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard) 보드 표시 모드를 조정하거나 대시보드에 더 많은 콘텐츠를 추가합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx b/src/i18n/content/kr/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx index 307d0cf0ea5..5e26ff8c538 100644 --- a/src/i18n/content/kr/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx +++ b/src/i18n/content/kr/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx @@ -20,17 +20,8 @@ translationType: machine 메트릭을 사용하면 보다 효율적인 데이터 저장이 가능합니다. 이를 통해 데이터를 쿼리하고 차트를 보다 쉽게 작성할 수 있습니다. New Relic에서 측정항목과 다른 유형의 데이터 간의 차이는 시간을 기반으로 합니다. 자세한 내용은 [데이터 유형 이해](/docs/using-new-relic/data/understand-data/new-relic-data-types) 를 참조하십시오. -* - **Events, logs, spans:** - - - 이러한 유형의 데이터는 특정 시점의 단일 레코드를 나타냅니다. 예를 들어 시스템에 대한 모든 요청에 대해 이벤트가 있을 수 있습니다. 이 데이터는 심층적인 문제 해결 및 분석에 이상적입니다. - -* - **Metrics:** - - - 이는 이벤트, 로그 또는 범위에 대한 집계된 보기를 제공합니다. 지표는 더 긴 시간 범위에 대한 추세를 표시하는 데 더 좋습니다. 예를 들어 서비스당 총 요청 수를 하나의 지표로 집계한 다음 이 정보를 월 단위로 조사할 수 있습니다. +* **Events, logs, spans:** 이러한 유형의 데이터는 특정 시점의 단일 레코드를 나타냅니다. 예를 들어 시스템에 대한 모든 요청에 대해 이벤트가 있을 수 있습니다. 이 데이터는 심층적인 문제 해결 및 분석에 이상적입니다. +* **Metrics:** 이는 이벤트, 로그 또는 범위에 대한 집계된 보기를 제공합니다. 지표는 더 긴 시간 범위에 대한 추세를 표시하는 데 더 좋습니다. 예를 들어 서비스당 총 요청 수를 하나의 지표로 집계한 다음 이 정보를 월 단위로 조사할 수 있습니다. @@ -83,10 +74,7 @@ translationType: machine 다음은 이벤트 데이터에서 측정항목 데이터를 생성하는 방법을 보여주는 동영상입니다(7분 47초). -
여기에서 성공 또는 실패로 반환되는 데이터를 정의합니다. 다음 블록에 사용 가능한 매개변수: - * `id` (또는 { `submitted` }의 경우 `ruleId` }) + * `id` (또는 \{ `submitted` }의 경우 `ruleId` }) * `name` * `description` * `nrql` @@ -248,10 +221,7 @@ translationType: machine ``` - + 이 작업은 프로덕션 설정을 수정하므로 작업을 실행하기 전에 변경 사항을 철저히 검토하는 것이 좋습니다. @@ -344,7 +314,7 @@ translationType: machine 여기에서 성공 또는 실패로 반환되는 데이터를 정의합니다. 다음 블록에 사용 가능한 매개변수: - * `id` (또는 { `submitted` }의 경우 `ruleId` }) + * `id` (또는 \{ `submitted` }의 경우 `ruleId` }) * `name` * `description` * `nrql` @@ -362,10 +332,7 @@ translationType: machine 쿼리 작업에는 다음이 포함됩니다. - + New Relic 계정의 모든 규칙을 나열하거나 [특정 규칙을 반환할](#list-rule-by-rule-id) 수 있습니다. @@ -513,10 +480,7 @@ translationType: machine ``` - + 규칙의 정확한 ID를 알고 있는 경우 특정 규칙을 쿼리할 수 있습니다. 예를 들어, 방금 규칙을 만들었고 이제 검토할 수 있도록 해당 내용을 나열하려고 할 수 있습니다. @@ -582,27 +546,7 @@ translationType: machine GraphiQL 도구인 NerdGraph API 탐색기를 사용하여 데이터 구조를 탐색할 수 있습니다. 또한 이를 사용하여 이벤트, 로그 및 스팬을 메트릭으로 변환하는 [작업을](#operations) 빌드하고 실행할 수 있습니다. 이 도구를 사용하려면: 1. 필수 매개변수를 사용하여 측정항목 작업의 요청을 생성합니다. - -2. - **[one.newrelic.com](https://one.newrelic.com) > All capabilities > Apps > NerdGraph API explorer** - - - 으로 이동하여 쿼리를 상자에 붙여넣습니다. - -3. 작업을 실행하려면 빨간색 - - - **Execute query** - - - 버튼을 클릭하세요. 또는 컬 형식을 얻으려면 - - - **Tools > Copy as CURL** - - - 선택하십시오. - +2. **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; Apps &gt; NerdGraph API explorer** 으로 이동하여 쿼리를 상자에 붙여넣습니다. +3. 작업을 실행하려면 빨간색 **Execute query** 버튼을 클릭하세요. 또는 컬 형식을 얻으려면 **Tools > Copy as CURL** 선택하십시오. 4. 응답 상자에서 응답을 확인합니다. - -5. 선택 사항: 규칙 생성 작업이 성공적으로 수행되었는지 확인하려면 [해당 규칙 ID에 대한 목록 쿼리를 실행합니다](#list-rule-by-rule-id) . +5. 선택 사항: 규칙 생성 작업이 성공적으로 수행되었는지 확인하려면 [해당 규칙 ID에 대한 목록 쿼리를 실행합니다](#list-rule-by-rule-id) . \ No newline at end of file diff --git a/src/i18n/content/kr/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx b/src/i18n/content/kr/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx index b654ba7a0e3..71855051381 100644 --- a/src/i18n/content/kr/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx +++ b/src/i18n/content/kr/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx @@ -31,9 +31,9 @@ translationType: machine WHERE nr.entityType = 'HOST' ``` - - [측정항목 규칙에 대한 이벤트는](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) [NRQL 쿼리](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language/) 에서 `WITH ... AS` 절을 지원하지 않습니다. - + + [측정항목 규칙에 대한 이벤트는](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) [NRQL 쿼리](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language/) 에서 `WITH ... AS` 절을 지원하지 않습니다. + 2. 사용 가능한 세 가지 측정항목 유형 중 하나를 사용하도록 쿼리를 편집합니다. @@ -102,10 +102,7 @@ NRQL 규칙이 완료되면 이를 [사용하여 API 요청을 생성합니다]( 규칙이 올바르게 생성되었는지 확인하기 [위해 쿼리를 실행하여 ID를 사용하여 해당 규칙을 반환](/docs/introduction-events-metrics-api#list-rule-by-rule-id) 할 수 있습니다. 생성한 메트릭 쿼리에 대한 팁은 메트릭 [쿼리 및 차트](#find-your-data) 작성을 참조하십시오. - + 다음 예제 NerdGraph API 요청은 1단계의 동일한 NRQL 규칙을 사용합니다. `IO Total Read Bytes Rule` 은 `io.totalread.bytes` 이라는 측정항목을 생성합니다. (규칙 이름에는 [메트릭 명명 규칙](#naming) 과 다른 공백이 있을 수 있습니다.) ```graphql @@ -198,7 +195,7 @@ NRQL 규칙이 완료되면 이를 [사용하여 API 요청을 생성합니다]( 여기에서 성공 또는 실패 응답에 의해 반환되는 데이터를 정의합니다. 이러한 블록에 사용 가능한 매개변수는 다음과 같습니다. - * `id` ( { `submitted` }에 대한 `ruleId` }) + * `id` ( \{ `submitted` }에 대한 `ruleId` }) * `name` * `description` * `nrql` @@ -220,10 +217,7 @@ NRQL 규칙이 완료되면 이를 [사용하여 API 요청을 생성합니다](
- + 다음은 반환된 응답의 예입니다. ```json @@ -273,10 +267,7 @@ API 요청이 준비되면 [NerdGraph API](/docs/introduction-events-metrics-api 사용 가능한 [NRQL 집계 기능](/docs/insights/nrql-new-relic-query-language/nrql-reference/nrql-syntax-components-functions#functions) 은 생성한 [메트릭 유형](#summary-and-uniquecount) 에 따라 다릅니다. 여기 몇 가지 예가 있어요. - + 요약 측정항목 유형을 만든 경우 다음 쿼리와 같이 `count` , `sum` , `max` , `min` 및 `average` 집계 함수를 사용할 수 있습니다. ``` @@ -284,10 +275,7 @@ API 요청이 준비되면 [NerdGraph API](/docs/introduction-events-metrics-api ``` - + `uniqueCount` 측정항목 유형을 만든 경우 다음 쿼리와 같이 `uniqueCount` 함수만 사용할 수 있습니다. ```sql @@ -295,10 +283,7 @@ API 요청이 준비되면 [NerdGraph API](/docs/introduction-events-metrics-api ``` - + `distribution` 측정항목 유형을 만든 경우 다음 쿼리와 같이 `percentile` 또는 `histogram` 함수를 사용합니다. ```sql @@ -321,4 +306,4 @@ NerdGraph 호출이 올바르게 구성되지 않은 경우 다음과 같은 메 Cannot parse the unexpected character "\u201C” ``` -NerdGraph 호출의 따옴표가 스마트 따옴표(중괄호)가 아닌지 확인합니다. NerdGraph API는 직선 따옴표만 허용합니다. +NerdGraph 호출의 따옴표가 스마트 따옴표(중괄호)가 아닌지 확인합니다. NerdGraph API는 직선 따옴표만 허용합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/iast/iast-configuration.mdx b/src/i18n/content/kr/docs/iast/iast-configuration.mdx index ea132f0404c..20548702917 100644 --- a/src/i18n/content/kr/docs/iast/iast-configuration.mdx +++ b/src/i18n/content/kr/docs/iast/iast-configuration.mdx @@ -22,10 +22,10 @@ IAST를 구성하여 스캔 일정을 처리할 수 있습니다. 이러한 설 ```yml security: scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default is forever - schedule: "" #Cron Expression to define start time - always_sample_traces: false #regardless of scan schedule + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default is forever + schedule: "" # Cron Expression to define start time + always_sample_traces: false # regardless of scan schedule ``` @@ -90,10 +90,10 @@ security: 애플리케이션이 시작된 후 30분 후에 IAST를 시작해서 300분 동안 실행되도록 예약하려면 지연 시간을 30으로, 기간을 300으로 설정해야 합니다. ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - duration: 300 #In minutes, default is forever + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + duration: 300 # In minutes, default is forever ``` @@ -101,9 +101,9 @@ security: 특정 시간에 IAST가 실행되도록 예약하려면 원하는 시간을 나타내는 Cron 표현식으로 일정을 설정합니다. 예를 들어, IAST를 매일 자정에 실행하도록 예약하려면 일정을 `"0 0 0 * * ?"` 으로 설정합니다. ```yml - security: - scan_schedule: - schedule: "0 0 0 * * ?" #By default, schedule is inactive + security: + scan_schedule: + schedule: "0 0 0 * * ?" # By default, schedule is inactive ``` @@ -115,10 +115,10 @@ security: IAST 항상 트레이스를 샘플링하도록 하려면 `always_sample_traces` 을 `true`로 설정합니다. 기본적으로 이 값은 `false`로 설정되며 이는 IAST 활성 스캔 창 내에서만 트레이스를 샘플링한다는 것을 의미합니다. ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - always_sample_traces: true #regardless of scan schedule + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + always_sample_traces: true # regardless of scan schedule ``` @@ -157,10 +157,10 @@ security: API를 지정하는 형식은 다음과 같습니다. ```yml - exclude_from_iast_scan: - api: - - .*account.* - - .*/\api\/v1\/.*?\/login +exclude_from_iast_scan: + api: + - .*account.* + - .*/\api\/v1\/.*?\/login ``` 예를 들어: @@ -178,16 +178,18 @@ API를 지정하는 형식은 다음과 같습니다. 이는 HTTP 헤더 키 목록입니다. 요청에 이러한 키가 포함된 헤더가 포함되어 있으면 해당 IAST 스캔은 건너뜁니다. 예를 들어 헤더가 포함된 curl 요청이 있고 `X-Forwarded-For` 헤더에서 IAST 스캐닝을 건너뛰고 싶은 경우 다음 설정을 전달할 수 있습니다. ```bash - curl -X POST -H "X-Forwarded-For: 123.456.789.012" -H "Content-Type: application/x-www-form-urlencoded" -d "param1=value1¶m2=value2" http://example.com + curl -X POST -H "X-Forwarded-For: 123.456.789.012" \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "param1=value1¶m2=value2" http://example.com ``` 이 설정을 사용할 수 있습니다: ```yml - exclude_from_iast_scan: - http_request_parameters: - header: - - X-Forwarded-For + exclude_from_iast_scan: + http_request_parameters: + header: + - X-Forwarded-For ``` @@ -195,17 +197,17 @@ API를 지정하는 형식은 다음과 같습니다. 이는 시위에 대응하는 키 목록입니다. 요청의 쿼리 문자열에 이러한 파라미터, 변수가 있으면 IAST 스캔을 건너뛰게 됩니다. 예를 들어, 쿼리 검증을 사용하여 컬 요청이 있고 `customerID` 및 `username` 검증 검증에서 IAST 검사를 건너뛰려는 경우 다음 설정을 전달할 수 있습니다. ```bash - curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' + curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' ``` 이 설정을 사용할 수 있습니다: ```yml - exclude_from_iast_scan: - http_request_parameters: - query: - - username - - customerID + exclude_from_iast_scan: + http_request_parameters: + query: + - username + - customerID ``` @@ -217,29 +219,29 @@ API를 지정하는 형식은 다음과 같습니다. JSON 본문이 포함된 curl 요청이 있고 `customerID` 및 `firstName` 에서 IAST 스캐닝을 건너뛰고 싶을 때 JSON 콘텐츠 유형에 대한 curl 예입니다. ```bash - curl --location --request POST 'localhost:8080/application/json/post' \ + curl --location --request POST 'localhost:8080/application/json/post' \ --header 'Content-Type: application/json' \ --data '{ - "path": "sample.txt", - "script":"testscript", - "customerID":"GREAL", - "name": { - "firstName": "john", - "lastName": "wick" - }, - "url":"http://example.com", - "cmd":"ls" + "path": "sample.txt", + "script":"testscript", + "customerID":"GREAL", + "name": { + "firstName": "john", + "lastName": "wick" + }, + "url":"http://example.com", + "cmd":"ls" }' ``` 이 설정을 사용할 수 있습니다: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - customerID - - name.firstName + exclude_from_iast_scan: + http_request_parameters: + body: + - customerID + - name.firstName ``` #### XML 콘텐츠 유형의 예 @@ -247,7 +249,7 @@ API를 지정하는 형식은 다음과 같습니다. 이는 XML 본문이 포함된 curl 요청이며 `customerID` 및 `username` 에서 IAST 스캐닝을 건너뛰려고 합니다. ```bash - curl --location 'localhost:8080/application/xml/post' \ + curl --location 'localhost:8080/application/xml/post' \ --header 'Content-Type: application/xml' \ --data ' @@ -265,11 +267,11 @@ API를 지정하는 형식은 다음과 같습니다. 이 설정을 사용할 수 있습니다: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - AppData.customerID - - AppData.username + exclude_from_iast_scan: + http_request_parameters: + body: + - AppData.customerID + - AppData.username ``` #### 예제 Form-URL-Encoded Content-Type @@ -277,7 +279,7 @@ API를 지정하는 형식은 다음과 같습니다. 이는 Form-URL-Encoded 본문이 포함된 curl 요청이며 `customerID` 및 `username` 에서 IAST 스캐닝을 건너뛰려고 합니다. ```bash - curl --location 'localhost:8080/application/urlencode/post' \ + curl --location 'localhost:8080/application/urlencode/post' \ --header 'Content-Type: application/x-www-form-urlencoded' \ -d 'name=madhav&path=sample.txt&customerID=GREAL&script=K2&url=http://example.com&username=bob&firstName=Aliko&cmd=ls' ``` @@ -285,10 +287,10 @@ API를 지정하는 형식은 다음과 같습니다. 이 설정을 사용할 수 있습니다: ```yml - http_request_parameters: - body: - - customerID - - username + http_request_parameters: + body: + - customerID + - username ``` @@ -304,18 +306,18 @@ API를 지정하는 형식은 다음과 같습니다. SQL 주입 및 SSRF 검사를 건너뛰려면 이 예를 참조하세요. `sql_injection` 및 `ssrf` 보고서가 `true` 로 설정되었습니다. ```yml - exclude_from_iast_scan: - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: true - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: true - rxss: false +exclude_from_iast_scan: + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: true + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: true + rxss: false ``` @@ -325,32 +327,32 @@ SQL 주입 및 SSRF 검사를 건너뛰려면 이 예를 참조하세요. `sql_i 다음과 같은 결합된 설정을 사용할 수 있습니다. ```yml - security: +security: + enabled: true + scan_schedule: + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default will be forever + #schedule: "" # Cron Expression to define start time + always_sample_traces: false # continuously collect samples + exclude_from_iast_scan: + api: [] + http_request_parameters: + header: [] + query: [] + body: [] + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: false + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: false + rxss: false + agent: enabled: true - scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default will be forever - #schedule: "" #Cron Expression to define start time - always_sample_traces: false #continuously collect samples - exclude_from_iast_scan: - api: [] - http_request_parameters: - header: [] - query: [] - body: [] - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: false - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: false - rxss: false - agent: - enabled: true ``` ## IAST 스캔 컨트롤러 [#iast-scan-controllers] diff --git a/src/i18n/content/kr/docs/iast/troubleshooting.mdx b/src/i18n/content/kr/docs/iast/troubleshooting.mdx index c425804758c..352886f70f4 100644 --- a/src/i18n/content/kr/docs/iast/troubleshooting.mdx +++ b/src/i18n/content/kr/docs/iast/troubleshooting.mdx @@ -14,84 +14,43 @@ translationType: machine 여기에 나열된 문제를 찾을 수 없다면 언제든지 [New Relic 지원팀](https://support.newrelic.com) 에 문의하실 수 있습니다. - - **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 로 이동합니다. 애플리케이션을 클릭하면 애플리케이션 테스트 효율성, 취약점, 적용되는 API, 메소드 호출 등을 확인할 수 있습니다. + + **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 로 이동합니다. 애플리케이션을 클릭하면 애플리케이션 테스트 효율성, 취약점, 적용되는 API, 메소드 호출 등을 확인할 수 있습니다. - + IAST를 사용하려면 애플리케이션을 활성화한 후 다시 시작해야 합니다. - + 새로운 앱인 경우 방화벽으로 인해 NR 플랫폼과의 통신이 차단될 수 있습니다. `nr-security-home/logs/snapshots` 의 최신 타임스탬프가 있는 파일의 서비스 통계 섹션을 확인하세요. 해당 목록의 6개 항목 모두 OK라고 표시되어야 합니다. 그렇지 않은 경우 로그를 검토하여 추가 정보를 확인하거나 [New Relic 지원팀](https://support.newrelic.com) 에 문의하세요. [표준 방화벽 설명서를](/docs/new-relic-solutions/get-started/networks/) 볼 수도 있습니다. New Relic UI에 애플리케이션이 표시되고 보안 에이전트가 IAST를 성공적으로 시작했지만 UI에 취약점이 표시되지 않는 경우 다음을 확인하세요. - * 애플리케이션의 효율성 수준: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 으로 이동하세요. 귀하의 기능을 검색하고 요약 섹션을 확인하세요. 애플리케이션의 IAST 적용 범위가 낮은 경우 애플리케이션에 추가 테스트 사례를 추가하여 더 높은 수준의 테스트 효율성을 얻으세요. + * 애플리케이션의 효율성 수준: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 으로 이동하세요. 귀하의 기능을 검색하고 요약 섹션을 확인하세요. 애플리케이션의 IAST 적용 범위가 낮은 경우 애플리케이션에 추가 테스트 사례를 추가하여 더 높은 수준의 테스트 효율성을 얻으세요. - * IAST 적용 범위: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 로 이동하세요. 해당 애플리케이션을 검색하고 클릭하세요. 요약 섹션에서 IAST 분석 적용 범위가 높고 취약점이 발견되지 않았는지 확인하세요. 이는 애플리케이션이 안전하다는 의미입니다. + * IAST 적용 범위: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 로 이동하세요. 해당 애플리케이션을 검색하고 클릭하세요. 요약 섹션에서 IAST 분석 적용 범위가 높고 취약점이 발견되지 않았는지 확인하세요. 이는 애플리케이션이 안전하다는 의미입니다. * 귀하의 애플리케이션의 프레임워크 또는 취약점 카테고리는 지원되지 않습니다. 이를 확인한 후에도 여전히 IAST의 취약점이 발견되지 않으면 [New Relic 지원팀](https://support.newrelic.com/s/) 에 문의하세요. - - **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 에 애플리케이션이 표시되지 않으면 다음을 확인하세요. - - * 귀하의 애플리케이션이 실행 중입니다. 애플리케이션 프로세스 또는 [APM & 서비스 페이지를](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/view-events-their-products#products) 확인하세요. + + **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 에 애플리케이션이 표시되지 않으면 다음을 확인하세요. + * 귀하의 애플리케이션이 실행 중입니다. 애플리케이션 프로세스 또는 [APM & 서비스 페이지를](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/view-events-their-products#products) 확인하세요. * 문제가 있는지 확인하기 위한 애플리케이션 로그입니다. - * APM 에이전트 버전 및 필요한 경우 업데이트합니다. - * `newrelic.yml` 구성 파일에는 [설치 페이지](/docs/iast/install) 에 표시된 대로 실험의 수정 사항이 포함되어 있습니다. - * `nr-security-home/logs` 디렉터리로 이동하여 `LANGUAGE-security-collector-init.log` 파일에서 `[SETP-8]` 줄을 찾습니다. 예상치 못한 오류가 있는지 확인하고 무엇이 실패했는지 알아보세요. - * 애플리케이션에 트래픽이 있습니다. IAST가 애플리케이션을 테스트할 수 있도록 일부 트래픽을 생성합니다. - - * 프록시 또는 방화벽이 액세스를 차단합니다. 화이트리스트/수정 - - - **csec.nr-data.net** - - - 에 대한 다음 IP `3.134.136.130, 18.219.177.104, 18.117.21.106` , 덮어쓰기 - - - **csec-gov.nr-data.net** - - - 에 대한 다음 IP `3.130.22.102, 3.138.243.136, 3.139.218.150` , 다루기 - - - **csec.eu01.nr-data.net** - - - 에 대한 다음 IP `18.185.235.118, 3.125.193.113, 3.75.166.122` 포함합니다. 하지만 IP는 언제든지 변경될 수 있으므로 해당 IP 대신 화이트리스트/포함에 추가하는 것이 좋습니다. - - * TLS 인증서가 정확합니다. 로컬 신뢰 저장소에 Let's Encrypt CA 인증서( [Let's Encrypt Certificates](https://letsencrypt.org/certificates/#root-certificates) 에서 다운로드)를 추가합니다. 루트 인증서와 중간 인증서(ISRG Root X1 & Let's Encrypt R3)를 모두 포함하여 완전한 신뢰 체인을 설정합니다. - + * 프록시 또는 방화벽이 액세스를 차단합니다. 화이트리스트/수정 **csec.nr-data.net** 에 대한 다음 IP `3.134.136.130, 18.219.177.104, 18.117.21.106` , 덮어쓰기 **csec-gov.nr-data.net** 에 대한 다음 IP `3.130.22.102, 3.138.243.136, 3.139.218.150` , 다루기 **csec.eu01.nr-data.net** 에 대한 다음 IP `18.185.235.118, 3.125.193.113, 3.75.166.122` 포함합니다. 하지만 IP는 언제든지 변경될 수 있으므로 해당 IP 대신 화이트리스트/포함에 추가하는 것이 좋습니다. + * TLS 인증서가 정확합니다. 로컬 신뢰 저장소에 Let's Encrypt CA 인증서( [Let's Encrypt Certificates](https://letsencrypt.org/certificates/#root-certificates) 에서 다운로드)를 추가합니다. 루트 인증서와 중간 인증서(ISRG Root X1 &amp; Let&apos;s Encrypt R3)를 모두 포함하여 완전한 신뢰 체인을 설정합니다. * 애플리케이션의 프레임워크 또는 취약점 카테고리가 지원됩니다. - + [APM의 높은 보안 모드를](/docs/apm/agents/manage-apm-agents/configuration/high-security-mode/)사용 중인 경우 에이전트가 작동하지 않습니다. @@ -100,7 +59,7 @@ translationType: machine 보안 에이전트가 올바르게 작동하는 경우: - * **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 에서 애플리케이션을 볼 수 있습니다. 애플리케이션이 시작되고 트래픽이 생성됩니다. + * **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 에서 애플리케이션을 볼 수 있습니다. 애플리케이션이 시작되고 트래픽이 생성됩니다. * `nr-security-home/logs` 디렉터리에서 `LANGUAGE-security-collector-init.log` 파일을 검색합니다. 파일 이름의 `LANGUAGE` 사용 중인 이름으로 바꾸세요. 문제가 있는 위치를 확인하려면 다음 단계를 검색하세요. @@ -124,13 +83,10 @@ translationType: machine ``` - + IAST UI에 애플리케이션이 표시되고 보안 에이전트가 성공적으로 시작된 경우에도 IAST가 작동하는지 확인할 수 있습니다. 확인하려면 다음 단계를 따르세요. - 1. **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 으)로 이동합니다. + 1. **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 으)로 이동합니다. 2. **Application tests** 탭에서 애플리케이션을 검색하고 클릭하세요. @@ -139,68 +95,49 @@ translationType: machine 또한, 로그인 레벨을 **debug/finest** 으로 설정하면 `nr-security-home/logs/java-security-collector.log` 파일에서 **Fuzz request received** (를) 검색할 수 있습니다. 이는 IAST 분석이 진행 중임을 나타냅니다. - + IAST는 트래픽이 감지되면 테스트를 시작하므로 애플리케이션이 제대로 작동하는지 또는 해당 애플리케이션으로 향하는 트래픽이 있는지 확인하세요. 앱의 UI 또는 API 엔드포인트를 수행합니다. - + IAST가 알려진 취약점을 감지하지 못하는 이유는 다음과 같습니다. * IAST는 애플리케이션 프레임워크를 지원하지 않습니다. + * 모듈에 대한 측정, 로그가 없습니다. - + 귀하의 애플리케이션은 IAST의 일부로 한동안 높은 트래픽과 지연 시간을 표시할 수 있습니다. IAST 테스트가 완료되면 이 문제는 몇 분 안에 해결됩니다. `nr-security-home/logs/snapshots` 폴더에서 스냅샷 로그 파일도 확인할 수 있습니다. 로그 파일에는 보안 에이전트의 상태, 리소스 사용량 및 최근 5개의 오류가 표시됩니다. - + 애플리케이션에 HTTP 요청 제공의 일부로 파일과 디렉터리를 생성하는 기능이 있는 경우 IAST는 코드 경로를 테스트하여 해당 파일과 디렉터리를 생성하려고 시도합니다. 애플리케이션 코드는 들어오는 HTTP 요청의 영향을 받아 이러한 파일을 생성합니다. 에이전트는 해당 항목을 삭제할 수 없습니다. 귀하의 API 중 어느 것도 파일과 디렉터리를 생성할 수 없다고 확신한다면 애플리케이션의 설정과 로그를 [New Relic 지원팀](https://support.newrelic.com) 과 공유하세요. - + IAST의 일부로 보안 에이전트는 부하를 증가시키는 애플리케이션에 새로운 요청을 보내 리소스 활용도를 높입니다. 이 IAST 분석은 애플리케이션에서 포착되지 않은 오류 또는 예외를 노출할 수도 있습니다. 리소스 부족으로 인해 애플리케이션이 충돌한 경우 리소스를 늘리고 애플리케이션을 다시 시작하고 IAST를 다시 수행하십시오. - + 아래 쿼리에서 `appId` 를 업데이트하고 쿼리 빌더에서 실행하여 애플리케이션에 대해 보고된 모든 취약점을 찾을 수 있습니다. ```sql - SELECT * FROM Vulnerability WHERE issueType = 'Application Vulnerability' AND appId = '{your application's appId}' + SELECT * FROM Vulnerability + WHERE issueType = 'Application Vulnerability' AND appId = YOU_APPLICATION_ID ``` - + IAST가 오탐지를 보고했다고 생각되면 취약점 상태를 업데이트하세요. 다음과 같이하세요: - * 애플리케이션 검색: **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests** 으)로 이동하세요. + * 애플리케이션 검색: **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests** 으)로 이동하세요. * 모든 애플리케이션 탭을 클릭하고 실제 취약점이 아닌 취약점을 선택합니다. @@ -213,15 +150,12 @@ translationType: machine * 상태를 업데이트한 취약점을 나열하려면 검색된 악용 가능한 취약점 목록에 필터를 적용하면 됩니다. - + * Golang의 경우 애플리케이션에서 사용하는 라이브러리 및 프레임워크에 필요한 계측 패키지를 가져왔는지 확인하세요. 따라서, 귀하의 애플리케이션이 [Mongo DB](http://go.mongodb.org/mongo-driver/mongo) 용 라이브러리를 사용하고 있다고 가정해 보겠습니다. 이 특정 라이브러리의 경우 newrelic에서 이 [측정, 로그 패키지를](https://github.com/newrelic/csec-go-agent/tree/main/instrumentation/csec_mongodb_mongo) 가져와야 합니다. - ``` + ```go import ( "github.com/newrelic/go-agent/v3/integrations/nrsecurityagent" "github.com/newrelic/go-agent/v3/newrelic" @@ -232,12 +166,12 @@ translationType: machine 애플리케이션 요구 사항에 따라 가져와야 할 수 있는 다른 패키지가 있습니다. 지원되는 패키지 목록은 [여기에서](https://github.com/newrelic/csec-go-agent#instrumentation-packages) 확인하세요. - 각 모듈에 해당하는 [패키지를](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks) 가져왔는지 확인하세요. + 각 모듈에 해당하는 [패키지를](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks) 가져왔는지 확인하세요. * HTTP 프로토콜 엔드포인트를 여는 경우 엔드포인트 이름 주위에 `newrelic.WrapListen` 함수를 배치하여 해당 엔드포인트에 대해 연구소 스캐닝을 활성화합니다. - ``` - http.ListenAndServe(newrelic.WrapListen(":"), nil) + ```go + http.ListenAndServe(newrelic.WrapListen(":YOUR_PORT_NUMBER"), nil) ``` @@ -247,38 +181,29 @@ translationType: machine * **Outbound HTTP Request** 의 특정 사례 또는 외부 서비스 호출의 경우 [애플리케이션 방법을 업데이트](/docs/apm/agents/go-agent/instrumentation/instrument-go-segments/#go-external-segments) 해야 합니다. - + IAST는 Windows 환경에서 지원됩니다. 그러나 일부 Java 애플리케이션의 경우 `classCirculatoryError` 발생할 수 있으며 다음과 같이 에이전트 설정에서 낮은 우선순위 측정값을 비활성화해야 합니다. * 보안 구성에서 낮은 우선순위 측정, 측정 비활성화: - ``` + ```yml low-priority-instrumentation: - enabled: false + enabled: false ``` * 클래스 변환기에서 우선순위가 낮은 측정, 측정 클래스를 제외합니다. 이렇게 하려면 구성 파일의 `class_transformer` 섹션에 지정된 줄을 추가하세요. - ``` + ```yml com.newrelic.instrumentation.security.low-priority-instrumentation: - enabled: false + enabled: false ``` - + 아니요, IAST 조사 결과를 다운로드할 수 있는 API가 없습니다. - + IAST는 테스트 중에 관찰한 내용을 기반으로 애플리케이션에 새 요청을 보냅니다. 목표는 익스플로잇 페이로드를 사용하여 추가 API 및 메서드 호출을 호출하는 것과 관련된 악의적인 동작이 가능한지 확인하는 것입니다. 이로 인해 고객 데이터가 바람직하지 않게 조작되고 런타임 보호 서비스가 트리거될 수 있습니다. - + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx index d965b8b1648..7ddf6b82be8 100644 --- a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx +++ b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx @@ -36,7 +36,7 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. `dpkg` 을 사용하여 에이전트가 설치되었는지 확인합니다. - ``` + ```sh dpkg -l | grep newrelic-infra ``` @@ -46,7 +46,7 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. `rpm` 을 사용하여 에이전트가 설치되었는지 확인합니다. - ``` + ```sh rpm -qa | grep newrelic-infra ``` @@ -56,7 +56,7 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. Windows 명령 프롬프트 또는 Powershell을 사용하여 [에이전트 디렉터리](/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#infra-agent) 가 있는지 확인합니다. - ``` + ```sh dir "C:\Program Files\New Relic\newrelic-infra" ``` @@ -72,13 +72,13 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. 에이전트가 실행 중인지 확인합니다. - ``` + ```sh sudo systemctl status newrelic-infra ``` 2. 에이전트가 실행되고 있지 않으면 에이전트를 수동으로 시작합니다. - ``` + ```sh sudo systemctl start newrelic-infra ``` @@ -88,13 +88,13 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. 에이전트가 실행 중인지 확인합니다. - ``` + ```sh sudo /etc/init.d/newrelic-infra status ``` 2. 에이전트가 실행되고 있지 않으면 에이전트를 수동으로 시작합니다. - ``` + ```sh sudo /etc/init.d/newrelic-infra start ``` @@ -104,13 +104,13 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. 에이전트가 실행 중인지 확인합니다. - ``` + ```sh sudo initctl status newrelic-infra ``` 2. 에이전트가 실행되고 있지 않으면 에이전트를 수동으로 시작합니다. - ``` + ```sh sudo initctl start newrelic-infra ``` @@ -120,13 +120,13 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 1. 에이전트가 실행 중인지 확인합니다. - ``` + ```sh sc query "newrelic-infra" | find "RUNNING" ``` 2. 에이전트가 실행되고 있지 않으면 Windows 명령 프롬프트를 사용하여 수동으로 에이전트를 시작합니다. - ``` + ```sh net start newrelic-infra ``` @@ -150,7 +150,7 @@ UI에 데이터가 표시되지 않으면 다음 단계를 시도하여 문제 7. 다음과 같이 쿼리 빌더에서 기본 쿼리를 생성하여 호스트가 인프라 모니터링 UI에 표시되지 않더라도 호스트가 올바르게 보고하는지 확인합니다. - ``` + ```sql SELECT * FROM SystemSample SINCE 60 minutes ago LIMIT 100 ``` diff --git a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx index 0a9ede7a467..a384b17ba14 100644 --- a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx +++ b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx @@ -46,7 +46,7 @@ translationType: machine 로깅 설정으로 `newrelic-infra.yml` 파일을 수정합니다. - ``` + ```yml log: level: debug file: /path/to/logfile.log @@ -123,17 +123,14 @@ Infrastructure Agent v1.9.0 이상부터 스마트 상세 정보 표시 모드 다음은 [일반 로깅 지침](#verbose) 을 보완하는 데 사용되는 특정 시스템에 대한 몇 가지 추가 참고 사항 및 요구 사항입니다. - + 컨테이너화된 인프라 에이전트를 사용하는 경우: 1. 로그 수준을 자세한 정보로 변경하려면 다음 옵션 중 하나를 선택합니다. * 권장 사항: 환경 변수 `NRIA_LOG_LEVEL` `debug` 로 설정합니다. 명령줄에서 이를 실행하면 다음과 같습니다. - ``` + ```sh -e NRIA_LOG_LEVEL=debug ``` @@ -143,10 +140,10 @@ Infrastructure Agent v1.9.0 이상부터 스마트 상세 정보 표시 모드 2. `journalctl` 을 사용하여 로그를 수집합니다. - ``` + ```sh journalctl -u newrelic-infra > newrelic-infra.log ``` 3. 몇 분 동안 로그를 수집한 후 로깅 수준을 다시 `info` 또는 `warn` 로 설정합니다. - + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx index 7742971c66e..2158166e574 100644 --- a/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx +++ b/src/i18n/content/kr/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx @@ -15,7 +15,7 @@ New Relic의 인프라 에이전트는 자체 데이터와 통합 로그를 수 다음 예는 Linux 시스템의 에이전트 로그에 대한 일반적인 구성을 보여줍니다(Windows 또는 기타 플랫폼을 실행할 때 파일 경로 변경). -``` +```yml log: level: info file: '/var/log/newrelic-infra/newrelic-infra.log' @@ -60,7 +60,7 @@ containerized agent found in container 또는 로그를 JSON 파일로 형식화할 수 있습니다. -``` +```json {"context":{},"level":"info","msg":"upstart_interval_sec: 0","timestamp":"2019-07-11T18:24:03+02:00"} {"context":{},"level":"info","msg":"plugin_dir: ","timestamp":"2019-07-11T18:24:03+02:00"} ``` @@ -81,18 +81,18 @@ containerized agent found in container ## 통합 로그 관리 -통합은 JSON 페이로드를 STDOUT에 기록하고 일반 텍스트(향후에는 JSON 구조화)를 STDERR에 기록합니다. +통합은 JSON 페이로드를 `STDOUT` 에 쓰고 일반 텍스트(향후 JSON 구조) 로그를 `STDERR` 에 씁니다. -인프라 에이전트는 통합 STDERR 라인을 처리하고 이 출력을 에이전트 로그로 전달합니다. +인프라 에이전트는 통합 `STDERR` 줄을 처리하고 이 출력을 에이전트 로그로 전달합니다. -에이전트는 다음과 같이 각 STDERR 라인을 처리합니다. +에이전트는 각 `STDERR` 줄을 다음과 같이 처리합니다. -* **when agent runs in verbose mode**: 전체 STDERR 라인을 &apos;msg&apos; 필드 내에 통합 라인 컨텍스트를 배치하는 DEBUG 에이전트 로그 항목으로 전달합니다. -* **otherwise**: 예상되는 형식(아래 참조)에 대해 행을 구문 분석하고 에이전트 ERROR 수준, &apos;치명적&apos; 또는 &apos;오류&apos; 심각도 수준으로 통합하여 생성된 항목으로만 로그인합니다. 이 경우 필드는 구조화된 방식으로 추출되고 전달됩니다. 따라서 에이전트 필드에 대해 JSON 출력이 활성화되면 쿼리가 가능해집니다. +* **When agent runs in verbose mode**: `STDERR` 줄 전체를 DEBUG 에이전트 로그 항목으로 전달하고 `msg` 필드에 통합 줄 컨텍스트를 배치합니다. +* **Otherwise**: 예상 형식에 따라 줄을 구문 분석하고 `fatal` 또는 `error` 심각도 수준을 가진 통합으로 생성된 항목만 대리점 ERROR 수준으로 로그합니다. 이 경우 필드는 구조화된 방식으로 추출되어 전달됩니다. 따라서 에이전트 필드에 JSON 출력이 활성화되면 해당 필드를 쿼리할 수 있게 됩니다. 기본적으로 인프라 에이전트는 통합 실행을 방해하지 않는 통합 오류를 필터링합니다. 로그인 레벨이 DEBUG로 설정되어 있거나 통합이 로그 구성에 구체적으로 나열되어 있는 경우에만 통합의 모든 오류가 표시됩니다. 예를 들어 이 설정에서는 로그 레벨이 INFO인 경우에도 `nri-mssql` 에서 발생하는 모든 오류가 표시됩니다. -```YAML +```yml log: include_filters: integration_name: @@ -103,13 +103,13 @@ log: 줄은 동일한 문자로 구분된 키-값 쌍의 목록이어야 합니다. 키는 모든 문자를 포함할 수 있지만 값은 세 가지 형식을 가질 수 있습니다. -1. string: <quote>이스케이프된 따옴표를 포함한 모든 문자 \\"<quote> -2. 지도: &{모든 문자} +1. string: <quote>이스케이프된 따옴표를 포함한 모든 문자 \\"<quote> +2. 지도: &\{모든 문자} 3. 단어: 공백을 제외한 모든 문자 내부적으로 에이전트는 이 정규식을 사용하여 필드를 추출했습니다. -``` +```regex ([^\s]*?)=(".*?[^\\]"|&{.*?}|[^\s]*) ``` @@ -126,4 +126,4 @@ time="2015-03-26T01:27:38-04:00" level=error msg="Foo bar baz" foo=bar - "level": "error" - "msg": "Foo bar baz" - "foo": "bar" -``` +``` \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx index 790d3f26ec0..87ad46d71d9 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx @@ -117,7 +117,7 @@ translationType: machine * [로그 파일을 구성합니다](#log-file) . * [에이전트 바이너리의 위치를 변경합니다](#agent-binary) . - + ## 서비스 스크립트 설치 [#install-service-script] @@ -131,10 +131,7 @@ translationType: machine - + 호스트에서 사용 중인 서비스 관리자를 프로그래밍 방식으로 알 수 있는 좋은 방법은 없지만 몇 가지 경험적 방법을 제공할 수 있습니다. 서비스 관리자를 확인하려면 다음 명령을 사용하십시오. @@ -168,10 +165,7 @@ translationType: machine 지원되는 서비스 관리자 중 하나를 사용하는 경우 호스트에 대한 서비스 스크립트를 설치합니다. - + 1. 서비스 파일 `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service` 복사 `/etc/systemd/system/newrelic-infra.service` 2. 서비스 스크립트를 활성화합니다. @@ -181,10 +175,7 @@ translationType: machine ``` - + 1. 서비스 파일 `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra` 복사 `/etc/init.d/system/newrelic-infra` 2. 다음 명령을 실행합니다. @@ -195,10 +186,7 @@ translationType: machine ``` - + 1. 서비스 파일 `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra` 복사 `/etc/init/newrelic-infra.conf` 2. 다음 명령을 실행합니다. @@ -230,20 +218,14 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml 이 변경 사항을 영구적으로 적용하려면 서비스 스크립트를 편집하십시오. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service` 을(를) 엽니다. 2. `ExecStart=/usr/bin/newrelic-infra` 행을 검색합니다. 3. 구성 플래그와 구성 파일 경로를 추가합니다. 이 예에서 구성 파일은 `/opt` 디렉토리 `ExecStart=/usr/bin/newrelic-infra -config /opt/config.yaml` 에 있습니다. 4. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra` 을(를) 엽니다. 2. `DAEMON=/usr/bin/$NAME”` 행을 검색합니다. @@ -257,10 +239,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml 5. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra` 을(를) 엽니다. 2. `exec /usr/bin/newrelic-infra` 행을 검색합니다. 3. `config flag` 및 `config file path` 을(를) 추가합니다. 여기에서 `config file` 는 `/opt` 디렉토리 `exec /usr/bin/newrelic-infra -config /opt/config.yaml` 에 있습니다. @@ -279,10 +258,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml `pid-file` 의 위치를 변경하려면: - + 시작 시 에이전트는 프로세스 `pid` 를 `pid-file` 에 씁니다. 파일이 존재하지 않으면 생성됩니다. 기본적으로 에이전트는 `/var/run/newrelic-infra/newrelic-infra.pid` 경로를 사용하여 `pid-file` 을 생성합니다. 수정하려면 다음 옵션 중 하나를 사용하십시오. @@ -304,10 +280,7 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml ``` - + `PIDFILE` 환경 변수를 사용하여 `pid-file` 을 관리하지 않는 것이 좋습니다. @@ -333,30 +306,21 @@ Linux 에이전트는 기본적으로 `root` 으로 실행되지만 더 적은 1. 서비스 스크립트를 편집합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service` 을(를) 엽니다. 2. `[Service]` 행을 검색합니다. 3. `User=user_name` 줄을 추가하고 `user_name` 을 에이전트를 실행할 사용자( `PRIVILEGED` 또는 `UNPRIVILEGED` )로 바꿉니다. 4. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra` 을(를) 엽니다. 2. `USER=root` 행을 검색합니다. 3. `root` 을 에이전트를 실행할 사용자( `PRIVILEGED` 또는 `UNPRIVILEGED` )로 바꿉니다. 4. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra` 을(를) 엽니다. 2. `exec /usr/bin/newrelic-infra` 행을 검색합니다. 3. `exec su -s /bin/sh -c ‘exec “$0” “$@“’ user_name-- /usr/bin/newrelic-infra` 으로 바꿉니다. @@ -427,30 +391,21 @@ Linux 에이전트는 기본적으로 `root` 으로 실행되지만 더 적은 실행 파일의 위치를 변경하려면 서비스 스크립트를 편집하십시오. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service` 을(를) 엽니다. 2. `[ExecStart=/usr/bin/newrelic-infra]` 행을 검색합니다. 3. 경로를 바꿉니다. 4. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra` 을(를) 엽니다. 2. `DAEMON=/usr/bin/$NAME` 행을 검색합니다. 3. 경로를 바꿉니다. 4. 파일을 저장합니다. - + 1. 서비스 스크립트 `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra` 을(를) 엽니다. 2. `exec /usr/bin/newrelic-infra` 행을 검색합니다. 3. 경로를 바꿉니다. @@ -467,4 +422,4 @@ Linux 에이전트는 기본적으로 `root` 으로 실행되지만 더 적은 * [로그 전달](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent#tarball-install) 을 활성화합니다. * [Flex 실행 파일을 수동으로 추가하여](https://github.com/newrelic/nri-flex/releases) Flex 통합을 활성화합니다. * 다른 [인프라 통합](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) 을 추가하여 외부 서비스에서 데이터를 수집합니다. -* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure-start-stop-restart-check-agent-status#linux) . +* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure-start-stop-restart-check-agent-status#linux) . \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx index f1744d35635..221071e8a5c 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx @@ -34,46 +34,46 @@ translationType: machine 2. [Homebrew가](https://brew.sh/) 시스템에 설치되어 있는지 확인하십시오. 다음을 사용하여 Homebrew 설치를 확인할 수 있습니다. ```bash - which brew + which brew ``` 설치되어 있지 않은 경우 다음 명령으로 설치할 수 있습니다(또는 [Homebrew](https://brew.sh/) 최신 지침 확인). ```bash - /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" + /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ``` 3. 그런 다음 터미널을 열고 다음 명령을 실행하십시오. ```bash - brew install newrelic-infra-agent -q + brew install newrelic-infra-agent -q ``` 4. 인프라 에이전트 서비스를 시작합니다. ```bash - brew services start newrelic-infra-agent + brew services start newrelic-infra-agent ``` -5. 구성 파일을 생성하고 를 추가합니다. +5. 구성 파일을 생성하고 를 추가합니다. 인텔 x86: ```bash - sudo mkdir -p /usr/local/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /usr/local/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml ``` 애플 실리콘: ```bash - sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml ``` 몇 분 정도 기다린 후 [인프라 UI에서 서버를 확인합니다](/docs/infrastructure/infrastructure-ui-pages/infra-ui-overview). 몇 분을 기다린 후에도 데이터가 나타나지 않으면 [문제 해결 단계를](/docs/infrastructure/new-relic-infrastructure/troubleshooting/no-data-appears-infrastructure) 따르십시오. - + ## 다음은 뭐지? [#configure] @@ -85,4 +85,4 @@ translationType: machine ## 에이전트 업데이트 [#update] -최신 버전으로 업그레이드하려면 표준 절차에 따라 [인프라 에이전트를 업데이트하세요](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent). +최신 버전으로 업그레이드하려면 표준 절차에 따라 [인프라 에이전트를 업데이트하세요](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent). \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx index 3e146b159b2..453a90c027d 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx @@ -24,33 +24,36 @@ Linux 환경용 인프라 에이전트에 기본 설치 절차를 사용한 경 apt로 제거(Debian.webp데비안,ubuntu icon우분투)} + title={<>apt로 제거 (Debian.webp데비안,ubuntu icon + } > 루트로 다음 명령을 실행합니다. - ``` + ```sh sudo apt-get remove newrelic-infra ``` yum으로 제거(amazon linux.webp아마존 리눅스,centos icon센트OS,redhat iconRHEL)} + title={<>yum으로 제거 (amazon linux.webp아마존 리눅스,centos icon센트OS,redhat icon + } > 루트로 다음 명령을 실행합니다. - ``` + ```sh sudo yum remove newrelic-infra ``` 지퍼로 제거(suse iconSLES)} + title={<>Zypper로 제거 (suse icon + } > 루트로 다음 명령을 실행합니다. - ``` + ```sh sudo zypper -n remove newrelic-infra ``` @@ -62,52 +65,31 @@ Linux 환경용 인프라 에이전트에 기본 설치 절차를 사용한 경 또한 Azure 또는 Google Cloud Platform 통합과 같은 클라우드 모니터링 통합도 제거해야 합니다. 그렇지 않으면 데이터 없이 UI에 호스트가 계속 표시됩니다. -## 제거Windows Server iconWindows 인프라 에이전트 [#uninstall-windows] +## 제거Windows Server icon [#uninstall-windows] Windows 환경용 인프라 에이전트에 대한 기본 설치 절차를 사용한 경우 제거하려면: 1. Windows 관리 그룹에 [관리자 권한이](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure#permissions) 있는지 확인하십시오. - 2. [인프라 에이전트를 중지합니다](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#windows) . - -3. Windows - - - **Control Panel** - - - 에서 - - - **Add/Remove Programs and Features** - - - 도구를 사용하여 인프라 에이전트를 제거합니다. - -4. Windows - - - **Program Files** - - - 에서 뉴렐릭 폴더를 수동으로 삭제하여 Windows용 에이전트와 관련된 모든 파일을 삭제합니다. +3. Windows **Control Panel** 에서 **Add/Remove Programs and Features** 도구를 사용하여 인프라 에이전트를 제거합니다. +4. Windows **Program Files** 에서 뉴렐릭 폴더를 수동으로 삭제하여 Windows용 에이전트와 관련된 모든 파일을 삭제합니다. [지원](/docs/infrastructure/install-configure-infrastructure/windows-installation/assisted-install-infrastructure-windows) 또는 [수동](/docs/infrastructure/install-configure-infrastructure/windows-installation/manual-install-infrastructure-windows) 설치 프로세스를 따랐다면 에이전트 파일의 압축을 풀 때 생성된 모든 파일을 수동으로 삭제해야 합니다. -## 제거macOS iconmacOS 인프라 에이전트 [#uninstall-macos] +## 제거macOS icon [#uninstall-macos] macOS 환경용 인프라 에이전트에 기본 설치 절차를 사용한 경우 제거하려면: 1. [인프라 에이전트 중지](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#macOS) : - ``` - brew services stop newrelic-infra-agent + ```sh + brew services stop newrelic-infra-agent ``` 2. 터미널에서 제거 명령을 실행합니다. - ``` - brew uninstall newrelic-infra-agent + ```sh + brew uninstall newrelic-infra-agent ``` ## 구성 관리 도구를 사용하여 제거 [#uninstall-other] @@ -146,4 +128,4 @@ macOS 환경용 인프라 에이전트에 기본 설치 절차를 사용한 경 ## 선택 사항: 나머지 파일 제거 [#leftover-files] -선택한 플랫폼에 대해 표준 패키지 관리 도구를 사용하는 경우 일반적으로 제거 프로세스에서 구성 및 기타 기타 파일이 남습니다. New Relic 인프라 에이전트를 제거한 후 나머지 파일을 완전히 제거해야 하는 경우 운영 체제에 대한 표준 절차를 따르십시오. +선택한 플랫폼에 대해 표준 패키지 관리 도구를 사용하는 경우 일반적으로 제거 프로세스에서 구성 및 기타 기타 파일이 남습니다. New Relic 인프라 에이전트를 제거한 후 나머지 파일을 완전히 제거해야 하는 경우 운영 체제에 대한 표준 절차를 따르십시오. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx index a2ab906c879..b7e768e0889 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx @@ -20,10 +20,7 @@ translationType: machine 여기 몇 가지 예가 있어요. - + @@ -75,10 +72,7 @@ translationType: machine
- + @@ -130,41 +124,35 @@ translationType: machine
- + Helm 및 `kubectl` 를 실행할 머신에서 적절한 컨텍스트를 사용하고 있는지 확인합니다. 다음을 사용하여 사용 가능한 컨텍스트를 확인할 수 있습니다. - ``` + ```sh kubectl config get-contexts ``` 다음을 사용하여 원하는 컨텍스트로 전환합니다. - ``` + ```sh kubectl config use-context CONTEXT_NAME ``` Helm을 사용하여 Kubernetes 통합을 설치한 경우 Helm을 사용하여 제거하기만 하면 됩니다. - ``` + ```sh helm uninstall --namespace NAMESPACE_USED_DURING_INSTALLATION RELEASE_NAME ``` 매니페스트를 사용하여 Kubernetes 통합을 설치한 경우 동일한 매니페스트를 사용하여 제거합니다. - ``` + ```sh kubectl delete -f newrelic-infrastructure.yaml ``` - + @@ -216,10 +204,7 @@ translationType: machine
- + @@ -271,10 +256,7 @@ translationType: machine
- + @@ -326,10 +308,7 @@ translationType: machine
- + 1. `cd /path/to/statsd` 2. `npm uninstall @newrelic/statsd-infra-backend` 3. StatsD config.js의 백엔드 목록에서 `"@newrelic/statsd-infra-backend"` 항목을 제거합니다. @@ -354,10 +333,7 @@ translationType: machine 1. 다음 지침에 따라 통합 패키지를 제거합니다. 이전 통합의 구성 파일은 삭제되지 않으므로 다시 구성할 필요가 없습니다. - + @@ -404,7 +380,7 @@ translationType: machine @@ -414,4 +390,4 @@ translationType: machine -2. 다음 [지침](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic) 에 따라 통합을 하나씩 설치합니다. 통합 패키지를 복제하려면 사용 가능한 모든 통합을 다시 설치해야 합니다. +2. 다음 [지침](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic) 에 따라 통합을 하나씩 설치합니다. 통합 패키지를 복제하려면 사용 가능한 모든 통합을 다시 설치해야 합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx index 93f63f2a2a3..870950566c5 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx @@ -22,7 +22,7 @@ New Relic UI에서 호스트의 현재 인프라 에이전트 버전을 보려 * 단일 호스트: [호스트 엔터티](/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#find) 에서 `agentVersion` 태그를 확인하거나 **Infrastructure** UI에서 해당 `Agent version` 찾습니다. * 여러 호스트: 버전별 활성 호스트 목록을 보려면 **Infrastructure > Navigator** 으로 이동하여 보고 엔터티를 `agentVersion` 로 그룹화하세요. * 쿼리: 보고서를 생성하려면 표준 상담원 측정항목에서 `agentVersion` 속성을 사용하세요. 예를 들어 다음 NRQL 쿼리는 에이전트 버전별로 고유한 활성 호스트 그룹의 수를 보여줍니다. - ``` + ```sql FROM SystemSample SELECT uniqueCount(hostname) FACET agentVersion LIMIT MAX diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx index 74b1e0a6596..3cceaa6f90a 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx @@ -17,7 +17,7 @@ Windows용 인프라 에이전트의 지원 설치를 통해 사용자 환경에 1. [패키지된 에이전트 파일](https://download.newrelic.com/infrastructure_agent/binaries/windows/) 을 다운로드하거나 특정 버전의 에이전트, 해당 체크섬을 자동으로 가져와 다운로드 후 확인하는 다음 명령을 사용합니다.`$arch=amd64` 을 원하는 아키텍처(amd64, 386)로 바꾸고 `$v=1.27.4` 을 [최신 또는 특정 버전](https://github.com/newrelic/infrastructure-agent/releases/latest) 으로 바꿉니다. - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -25,21 +25,17 @@ Windows용 인프라 에이전트의 지원 설치를 통해 사용자 환경에 3. 파일이 다음 구조로 압축 해제되었는지 확인하십시오. - Infra-windows-files.png + Infra-windows-files.png 4. 압축을 풀면 설치 PowerShell 스크립트 `installer.ps1` 에 액세스하여 편집합니다. -5. 업데이트 . +5. 을 업데이트하세요. 6. 선택 사항: 다른 [매개변수](#parameters) 를 업데이트합니다. 7. 관리자 권한으로 `installer.ps1` 을 실행합니다. - + ## 설치 구성 [#parameters] @@ -123,7 +119,7 @@ Windows용 지원 설치 중에 다음 매개변수를 구성할 수 있습니 @@ -198,4 +194,4 @@ Windows용 지원 설치 중에 다음 매개변수를 구성할 수 있습니 * 인프라 데이터에 주석을 달기 위해 [사용자 정의 속성](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) 을 추가하십시오. * 서버가 Amazon EC2에서 호스팅되는 경우 [AWS 계정을 연결하십시오](/docs/infrastructure-amazon-aws-ec2-integration#connect) . * 다른 [New Relic 인프라 통합](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) 을 추가하여 외부 서비스에서 데이터를 수집합니다. -* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure-start-stop-restart-check-agent-status#linux) . +* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure-start-stop-restart-check-agent-status#linux) . \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx index 37ce195878f..286f376dad5 100644 --- a/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/kr/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx @@ -21,7 +21,7 @@ Windows용 인프라 에이전트에 대한 사용자 지정 설치 프로세스 1. [패키지된 에이전트 파일](https://download.newrelic.com/infrastructure_agent/binaries/windows/) 을 다운로드하거나 특정 버전의 에이전트, 해당 체크섬을 자동으로 가져와 다운로드 후 확인하는 다음 명령을 사용합니다.`$arch=amd64` 을 원하는 아키텍처(amd64, 386)로 바꾸고 `$v=1.27.4` 을 [최신 또는 특정 버전](https://github.com/newrelic/infrastructure-agent/releases/latest) 으로 바꿉니다. - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -29,11 +29,7 @@ Windows용 인프라 에이전트에 대한 사용자 지정 설치 프로세스 3. 파일이 다음 구조로 압축 해제되었는지 확인하십시오. - Infra-windows-files.png + Infra-windows-files.png 4. [서비스 스크립트를 설치합니다](#install-service-script) . @@ -116,7 +112,7 @@ C:\Program Files\New Relic\newrelic-infra\installer.ps1 * `log_file` 필드를 사용하여 `newrelic-infra.yml` 구성 파일에서 사용자 정의 경로를 설정합니다. * `newrelic-infra` 바이너리를 실행할 때 `-log_file` 을 사용하여 명령줄 인수로 전달합니다. - + ## 다음은 뭐지? [#what-next] @@ -125,4 +121,4 @@ C:\Program Files\New Relic\newrelic-infra\installer.ps1 * 인프라 데이터에 주석을 달기 위해 [사용자 정의 속성](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes) 을 추가하십시오. * 서버가 Amazon EC2에서 호스팅되는 경우 [AWS 계정을 연결하십시오](/docs/integrations/amazon-integrations/get-started/connect-aws-new-relic-infrastructure-monitoring/) . * 다른 [New Relic 인프라 통합](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations/) 을 추가하여 외부 서비스에서 데이터를 수집합니다. -* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows) . +* 수동 [으로 시작, 중지, 다시 시작하거나 에이전트 상태를 확인합니다](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows) . \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx index 112ed38b52c..950b4ee8a72 100644 --- a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx +++ b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx @@ -44,6 +44,6 @@ translationType: machine * `/etc/newrelic-infra.yml` 구성 파일에서 `log_file` 항목을 변경합니다. 설치 스크립트는 이를 위해 `/var/log/newrelic-infra/` 폴더를 생성하므로 다음 값을 권장합니다. - ``` + ```yml log_file: /var/log/newrelic-infra/newrelic-infra.log - ``` + ``` \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx index ed29b17a22c..ff85d906f01 100644 --- a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx +++ b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx @@ -19,63 +19,51 @@ translationType: machine 1. [newrelic-infra.yml](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#logging-variables) 구성 파일을 편집하고 필요한 플래그를 추가하여 로그를 활성화합니다. 예를 들어 기본 로그 파일 경로에서 모든 추적 로그를 활성화하려면 다음을 수행합니다. - ``` - log: - level: trace + ```yml + log: + level: trace ``` Infrastructure Agent 버전 1.26.0 이상에는 다른 로깅 구성이 필요합니다. -``` - verbose: 1 - trace: - # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. - - v3.submission - # dm.submission enables detailed logging for integrations using Dimensional Metric format. - - dm.submission +```yml +verbose: 1 +trace: + # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. + - v3.submission + # dm.submission enables detailed logging for integrations using Dimensional Metric format. + - dm.submission ``` 2. [초기화 시스템을 사용하여](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) 에이전트 서비스를 다시 시작합니다. - + CentOS 7, Debian 8, RHEL 7 및 Ubuntu 15.04 이상에서 SystemD 명령 사용: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Debian 7에서 System V 명령 사용: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Amazon Linux, CentOS 6, RHEL 6 및 Ubuntu 14.10 이하에서 Upstart 명령을 사용합니다. - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -86,9 +74,9 @@ Infrastructure Agent 버전 1.26.0 이상에는 다른 로깅 구성이 필요 v3.submission이 활성화된 경우의 로그 예: -``` +```log time="2021-12-28T09:27:28Z" level=debug msg="Sending events to metrics-ingest." component=MetricsIngestSender key=... numEvents=3 postCount=1 timestamps="[2021-01-01 09:27:28 +0000 UTC]" time="2021-12-28T09:27:28Z" level=debug msg="Preparing metrics post." component=MetricsIngestSender postCount=1 time="2021-12-28T09:27:28Z" level=trace msg="[{\"EntityID\":111,\"IsAgent\":true,\"Events\":[{\"eventType\":\"SystemSample\",\"timestamp\":1640683648,\"entityKey\":\"...\",\"cpuPercent\":0.2004008016032026, ...}]" feature=v3.submission time="2021-12-28T09:27:29Z" level=debug msg="Metrics post succeeded." component=MetricsIngestSender postCount=1 -``` +``` \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx index 27dc9dd8a59..609d25d2486 100644 --- a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx +++ b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx @@ -110,22 +110,19 @@ New Relic 인프라 에이전트는 최소한의 CPU 및 메모리 소비로 광
- ``` + ```sh sudo zypper -n remove newrelic-infra-integrations --clean-deps ``` - New Relic . + 뉴엘릭 .
-### 에이전트 플러그인 보고 줄이기 [#reduce_plugins] +### 에이전트 플러그인 보고 줄이기 [#reduce\_plugins][#reduce_plugins] 인프라 에이전트에는 인벤토리 데이터(특정 시스템 구성 및 상태 정보)를 수집하는 플러그인이 내장되어 있습니다. 일부 시스템의 경우 플러그인이 많은 데이터를 수집하는 경우 CPU 소비가 상대적으로 높을 수 있습니다. 공간을 줄이려면 원하지 않는 데이터를 보고하는 특정 플러그인의 샘플링 빈도를 비활성화하거나 줄일 수 있습니다. - + * **Disable a single plugin:** 플러그인을 비활성화하려면 해당 속성 값을 `-1` 으로 설정하세요. * **Disable all plugins:** `disable_all_plugins: true` * **Enable selected plugins:** 특정 플러그인을 활성화하려면 `disable_all_plugins` 에 예외를 삽입하세요. 예를 들어, 다음 설정은 모든 키워드를 비활성화하고 네트워크 인터페이스 및 SELinus 플러그인을 다시 활성화하여 120초마다 보고합니다. - ``` + ```yml disable_all_plugins: true network_interface_interval_sec: 120 selinux_interval_sec: 120 @@ -134,7 +131,10 @@ New Relic 인프라 에이전트는 최소한의 CPU 및 메모리 소비로 광 SELinux 비활성화 semodule -l (Linux만 해당)} + title={<>SELinux 비활성화 + semodule -l + (Linux만 해당) + } > SELinux 플러그인은 주기적으로 `semodule -l` 시스템 명령을 호출하여 기존 SELinux 모듈에 대한 정보를 가져옵니다. 대부분의 CentOS/RedHat 배포판에서 이 명령은 CPU 소비 피크를 생성합니다. @@ -143,33 +143,27 @@ New Relic 인프라 에이전트는 최소한의 CPU 및 메모리 소비로 광 `selinux_enable_semodule: false` - + Sysctl 플러그인은 전체 `/sys` 디렉토리 구조를 탐색하고 거기에 있는 모든 파일에서 값을 읽습니다. 이를 비활성화하거나 간격을 줄이면 인프라 에이전트에서 일부 CPU 시스템 시간이 줄어들 수 있습니다. 인벤토리 빈도를 음수로 설정하여 비활성화하거나 `sysctl_interval_sec` 구성 값을 플러그인의 연속 실행 사이의 시간(초)으로 설정하여 빈도를 줄일 수 있습니다. 예를 들어, 플러그인을 10분마다 한 번씩 실행하려면: - ``` + ```yml sysctl_interval_sec: 600 ``` Sysctl 플러그인을 비활성화하려면: - ``` + ```yml sysctl_interval_sec: -1 ``` `sysctl_interval_sec` 속성의 현재 기본값은 `60` 입니다. - + 다음 인벤토리 플러그인은 특히 CPU를 많이 사용하지 않지만 해당 구성 옵션을 설정하여 빈도를 줄이거나 비활성화할 수 있습니다. @@ -222,11 +216,11 @@ New Relic 인프라 에이전트는 최소한의 CPU 및 메모리 소비로 광 -### 호스트 내 통합 검토 [#on_host_integrations] +### 호스트 내 통합 검토 [#on\_host\_integrations][#on_host_integrations] 인프라 온-호스트 통합을 사용하는 경우 CPU 사용량에 추가적인 영향을 미칠 수 있습니다. 영향의 특성과 영향을 조정하는 방법은 사용 중인 통합에 따라 다릅니다. 다음은 호스트 통합 CPU 사용량을 조정하는 몇 가지 방법입니다. * [통합](/docs/integrations/host-integrations/host-integrations-list) 에 조정할 수 있는 구성 옵션이 있는지 확인하십시오. -* 가능하면 인프라 에이전트를 추가하여 모니터링 부하를 분산합니다. 예를 들어 Kafka 통합은 [다중 에이전트 배포를](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents) 허용합니다. +* 가능하면 인프라 에이전트를 추가하여 모니터링 부하를 분산합니다. 예를 들어 Kafka 통합은 [다중 에이전트 배포를](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents) 허용합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx index ac39956530f..b2dee46477a 100644 --- a/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx +++ b/src/i18n/content/kr/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx @@ -23,28 +23,22 @@ New Relic 인프라 에이전트가 실행 중이지만 CPU 사용량이 높은 1. 에이전트에 대한 하나의 스레드 제한을 제거하여 코어당 하나의 스레드를 허용합니다. - - 1. 즐겨 사용하는 일반 텍스트 편집기에서 다음 파일을 엽니다. C:\\Program Files\\New Relic\\newrelic-infra\\newrelic-infra.yml + + 1. 좋아하는 일반 텍스트 편집기에서 다음 파일을 여세요. `C:\Program Files\New Relic\newrelic-infra\newrelic-infra.yml` 2. 다음 구성 옵션을 추가합니다. - ``` + ```yml max_procs: -1 ``` - - 1. 즐겨 사용하는 일반 텍스트 편집기에서 다음 파일을 엽니다. /etc/newrelic-infra.yml + + 1. 좋아하는 일반 텍스트 편집기에서 다음 파일을 여세요. `/etc/newrelic-infra.yml` 2. 다음 구성 옵션을 추가합니다. - ``` + ```yml max_procs: -1 ``` @@ -53,44 +47,32 @@ New Relic 인프라 에이전트가 실행 중이지만 CPU 사용량이 높은 2. [초기화 시스템을 사용하여](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) 에이전트 서비스를 다시 시작합니다. - + CentOS 7, Debian 8, RHEL 7 및 Ubuntu 15.04 이상에서 SystemD 명령 사용: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Debian 7에서 System V 명령 사용: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Amazon Linux, CentOS 6, RHEL 6 및 Ubuntu 14.10 이하에서 Upstart 명령을 사용합니다. - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -101,4 +83,4 @@ New Relic 인프라 에이전트가 실행 중이지만 CPU 사용량이 높은 New Relic 인프라 에이전트는 기본적으로 단일 운영 체제 스레드에서 실행됩니다. 이는 특히 Windows 환경에서 시스템이 과부하 상태일 때 프로세스 스케줄러가 CPU 시간을 얻을 기회를 거의 주지 않는다는 것을 의미할 수 있습니다. -`max_procs: -1` 구성 옵션은 이 제한을 제거하고 에이전트가 CPU 코어당 하나의 스레드(최대값)를 사용할 수 있도록 합니다. +`max_procs: -1` 구성 옵션은 이 제한을 제거하고 에이전트가 CPU 코어당 하나의 스레드(최대값)를 사용할 수 있도록 합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx index 8ade2488c94..f0685d437dd 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx @@ -12,7 +12,7 @@ translationType: machine Kubernetes 통합 버전 2에는 버전 3과 몇 가지 다른 설정 및 요구 사항이 있습니다. 이 문서에서는 버전 3과 다른 설정과 버전 2에 필요한 설정에 대해 설명합니다. 다르게 지정하지 않으면 버전 3의 설정을 사용할 수 있습니다. - 우리는 버전 2를 대체했으며 이를 사용해서는 안 된다는 점을 명심하세요. 우리는 여전히 버전 2를 사용하고 있는 사용자를 위해 이 문서를 유지 관리합니다. + 뉴렐릭 버전 2는 더 이상 사용되지 않으며 사용을 권장하지 않습니다. 더 이상 지원하지 않더라도 버전 2를 사용하는 사용자를 위해 이 문서를 보관합니다. 현재 버전의 Kubernetes를 시작하려면 [Kubernetes 통합 소개를](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/) 참조하세요. @@ -289,10 +289,7 @@ OpenShift에서 제어 플레인 모니터링을 구성하려면 [사용자 정 자세한 로그를 생성하고 버전 및 설정 정보를 얻으려면 아래 정보를 확인하세요. - + Kubernetes 통합의 경우, 서비스 에이전트는 오류 발생 시에만 로그인 항목을 추가합니다. 가장 일반적인 오류는 표준(상세하지 않은) 로그에 표시됩니다. 직접적으로 또는 블루렐릭 지원팀을 통해 보다 심층적인 조사를 수행하는 경우 자세한 정보 표시 모드를 활성화할 수 있습니다. @@ -336,11 +333,7 @@ OpenShift에서 제어 플레인 모니터링을 구성하려면 [사용자 정 9. [`kube-state-metrics` 서비스 설정을 검색합니다](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + Kubernetes 통합의 경우 인프라 에이전트는 오류가 발생한 경우에만 로그 항목을 추가합니다. 가장 일반적인 오류는 표준(상세하지 않은) 로그에 표시됩니다. 직접적으로 또는 New Relic 지원을 통해 보다 심층적인 조사를 수행하는 경우 자세한 정보 표시 모드를 활성화할 수 있습니다. @@ -386,10 +379,7 @@ OpenShift에서 제어 플레인 모니터링을 구성하려면 [사용자 정 8. [`kube-state-metrics` 서비스 설정을 검색합니다](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + `kube-state-metrics` 에 연결하는 Pod에서 로그를 가져오려면 다음 안내를 따르세요. 1. 다음 명령을 실행합니다. @@ -425,10 +415,7 @@ OpenShift에서 제어 플레인 모니터링을 구성하려면 [사용자 정 ``` - + 마스터 노드에서 실행 중인 포드에서 로그를 가져오려면: 1. 마스터로 레이블이 지정된 노드를 가져옵니다. @@ -500,4 +487,4 @@ Kubernetes의 모니터링 서비스는 [인프라 에이전트와 호스트 내 ### Kubernetes 통합 구성에 서비스 YAML 추가 [#add-service-yaml] -Kubernetes 통합 버전 2를 사용하는 경우 DaemonSet의 `spec` 의 `volumes` 및 `volumeMounts` 섹션에 이 ConfigMap에 대한 항목을 추가하여 ConfigMap의 모든 파일이 `/etc/newrelic-infra/integrations.d/` 에 마운트되도록 해야 합니다. . +Kubernetes 통합 버전 2를 사용하는 경우 DaemonSet의 `spec` 의 `volumes` 및 `volumeMounts` 섹션에 이 ConfigMap에 대한 항목을 추가하여 ConfigMap의 모든 파일이 `/etc/newrelic-infra/integrations.d/` 에 마운트되도록 해야 합니다. . \ No newline at end of file diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx index 1a7c761956d..66ee6db198b 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx @@ -82,7 +82,7 @@ Kubernetes 비밀은 운영자의 삭제스페이스에서 패드를 모니터 * [.그물](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-init/general) * [루비](https://hub.docker.com/repository/docker/newrelic/newrelic-ruby-init/general) -.NET의 경우 +.NET의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -96,7 +96,7 @@ spec: # env: ... ``` -자바의 경우 +자바의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -111,7 +111,7 @@ spec: # env: ... ``` -NodeJS의 경우 +Node.js의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -126,7 +126,7 @@ spec: # env: ... ``` -파이썬의 경우 +파이썬의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -141,7 +141,7 @@ spec: # env: ... ``` -루비의 경우 +루비의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -156,7 +156,7 @@ spec: # env: ... ``` -환경별 설정의 경우 +환경별 설정의 경우: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -180,7 +180,7 @@ spec: value: "$(NEW_RELIC_LABELS)-$(NEW_RELIC_POD_NAME)" ``` -레이블을 사용하여 특정 네임스페이스의 모든 항목을 타겟팅 +특정 네임스페이스의 모든 항목을 레이블로 타겟팅: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -197,7 +197,7 @@ spec: values: ["java"] ``` -특정 라벨로 파드를 타겟팅 +특정 라벨이 있는 파드를 타겟팅: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -214,7 +214,7 @@ spec: values: ["dotnet"] ``` -기본 이름이 아닌 비밀 사용 +기본 이름이 아닌 비밀을 사용하는 경우: ```yaml apiVersion: newrelic.com/v1alpha2 diff --git a/src/i18n/content/kr/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx b/src/i18n/content/kr/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx index 3d366000543..ae54a709909 100644 --- a/src/i18n/content/kr/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx +++ b/src/i18n/content/kr/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx @@ -29,9 +29,9 @@ translationType: machine [Kubernetes 비밀을 사용하여](https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging/values.yaml#L8-L25) 뉴렐릭 을 저장하는 경우 `newrelic-logging` 차트는 기본적으로 US API 엔드포인트에 로그를 보내는 것으로 설정됩니다. 라이선스 키가 EU 또는 FedRAMP 계정에 속하고 키 저장에 비밀이 사용되는 경우 [API 참조 문서](/docs/logs/log-api/introduction-log-api/#endpoint) 에서 적절한 값으로 엔드포인트 설정을 업데이트해야 합니다. 다음은 EU 계정에 이를 설정하는 방법의 예입니다. ```yml - newrelic-logging: - enabled: true - endpoint: https://log-api.eu.newrelic.com/log/v1 + newrelic-logging: + enabled: true + endpoint: https://log-api.eu.newrelic.com/log/v1 ``` @@ -67,8 +67,8 @@ Fluent Bit의 내부 메트릭은 [`prometheus_scrape` 입력 플러그인](http ```yml newrelic-logging: - fluentBit: - sendMetrics: true + fluentBit: + sendMetrics: true ``` 쿠버네티스 클러스터를 해결할 때 문제 해결 시 `newrelic-logging.fluentBit.sendMetrics` 설정만 활성화하면 됩니다. 문제 해결을 쉽게 하려면 한 번에 하나의 쿠버네티스 클러스터에 대해 활성화하는 것이 좋습니다. diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index d2c270c90f8..aa0fa736e1d 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -7,11 +7,7 @@ translationType: machine 뉴렐릭과 AWS 계정을 성공적으로 연결한 후에는 뉴렐릭 Lambda 계층을 추가하여 컨테이너화되지 않은 AWS Lambda 함수를 렌더링할 수 있습니다. 이는 뉴렐릭 에이전트를 통합하여 함수가 호출될 때마다 자동 모니터링을 가능하게 합니다. -a diagram depicting non-containerized lambda function instrumentation +a diagram depicting non-containerized lambda function instrumentation ## 시작하기 전에 [#begin] @@ -33,10 +29,7 @@ translationType: machine 필요에 따라 확장 프로그램을 우회하고 CloudWatch에서 텔넷리만 보거나, CloudWatch를 우회하거나, CloudWatch를 대체 수단으로 사용하도록 선택할 수 있습니다. 이 문서 끝에 있는 [CloudWatch](#CloudWatch-only) 섹션에서는 각 옵션을 안내합니다. - + `newrelic-lambda` CLI 퀵스타트를 사용하여 Lambda 함수를 충전할 수 있습니다. 뉴렐릭 레이어를 설치하거나 업그레이드하려면 다음 명령을 실행하세요. @@ -52,10 +45,7 @@ translationType: machine CLI는 일괄 처리로 많은 기능에서 작동할 수 있습니다. `--function all` , `--function installed` 또는 `--function not-installed` 를 사용하여 지역의 모든 기능에서 작동하거나 기존 New Relic 계측이 있거나 없는 기능에서만 작동합니다. - + AWS의 서버리스 애플리케이션 모델(SAM)은 의존하는 리소스와 기능을 단순화하고 전체 애플리케이션의 수명 주기를 관리하는 CloudFormation 템플릿의 변형입니다. 우리는 대부분의 Lambda 예제 함수에 SAM 및 CloudFormation을 사용하고, 다른 많은 도구는 CloudFormation 템플릿 위에 구축되어 추가 추상화 계층을 제공합니다. CloudFormation은 AWS 리소스의 프로비저닝 및 관리를 단순화하는 AWS 서비스입니다. YAML 또는 JSON 템플릿에서 원하는 리소스 상태를 정의함으로써 CloudFormation은 기본 API 호출을 자동으로 처리하여 필요에 따라 리소스를 생성, 업데이트 또는 삭제합니다. 이 선언적 접근 방식은 인프라 관리를 자동화하여 일관성과 재현성을 보장합니다. @@ -99,10 +89,7 @@ translationType: machine 일반적으로 함수와 해당 리소스를 설명하는 `template.yaml` 이라는 파일이 있습니다. - + 서버리스 프레임워크는 서버리스 애플리케이션을 위한 널리 사용되는 개발 및 배포 도구입니다. Node.js에서 AWS용으로 작성되었으며 대부분 CloudFormation 템플릿 위에서 높은 수준의 추상화 역할을 합니다. Node, Python, Ruby, Java 및 .NET 함수에 적합합니다. New Relic은 Serverless Framework 애플리케이션의 계측을 단순화하기 위해 [Serverless Framework 플러그인](https://github.com/newrelic/serverless-newrelic-lambda-layers) 을 제공합니다. @@ -134,19 +121,13 @@ translationType: machine ``` - + Terraform은 코드 도구로서 널리 사용되는 범용 인프라입니다. AWS 리소스를 관리하는 데 사용할 수 있습니다. 우리는 Terraform 펼쳐보기를 사용하여 뉴렐릭 권한이 있는 Lambda 함수 구현, 배포의 [몇 가지 예를](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) 제공합니다. [뉴렐릭 Terraform 공급자를](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) 사용하여 AWS 통합을 설정할 수 있습니다. - + 위의 접근 방식보다 오류가 발생하기 쉽고 노동 집약적이지만 Node.js의 경우 AWS Lambda 콘솔에서 뉴렐릭을 사용하도록 Lambda 함수의 설정을 수동으로 변경할 수 있습니다. 파이썬, 루비, 자바. 다음은 루비 런타임에 대한 리소스를 사용하는 방법에 대한 예입니다. @@ -182,15 +163,17 @@ translationType: machine * `NEW_RELIC_LAMBDA_HANDLER`: 이전에 복사한 함수의 원래 Handler 값으로 설정합니다. * `NEW_RELIC_LICENSE_KEY`: 귀하의 뉴렐릭 키로 설정하세요. - * `NEW_RELIC_LOG_ENDPOINT`: [https://log-api.newrelic.com/log/v1로](https://log-api.newrelic.com/log/v1로) 설정하세요. - * `NEW_RELIC_TELEMETRY_ENDPOINT`: [https://cloud-collector.newrelic.com/aws/lambda/v1로](https://cloud-collector.newrelic.com/aws/lambda/v1로) 설정합니다. + * `NEW_RELIC_LOG_ENDPOINT`: [https://log-api.newrelic.com/log/v1](https://log-api.newrelic.com/log/v1) 로 설정합니다. + * `NEW_RELIC_TELEMETRY_ENDPOINT`: [https://cloud-collector.newrelic.com/aws/lambda/v1](https://cloud-collector.newrelic.com/aws/lambda/v1) 로 설정합니다. 14. 함수가 STDOUT에 쓰는 모든 내용을 포함하는 Lambda 호출의 로그를 뉴렐릭으로 보내려면 `NEW_RELIC_EXTENSION_SEND_FUNCTION_LOGS` 환경 변수를 `true` 로 설정해야 합니다. 15. 뉴렐릭 클러스터 키 비밀에 대한 액세스를 허용하도록 실행 역할을 수정합니다. * `NEW_RELIC_LICENSE_KEY` 라는 비밀의 ARN을 찾습니다. + * 아래 코드와 같이 함수의 실행 역할에 새 인라인 정책을 추가합니다. `SECRET_ARN` 위에서 찾은 값으로 바꿉니다. + ```json "Statement": [ { @@ -203,11 +186,11 @@ translationType: machine ] ``` - - 뉴렐릭 레이어는 뉴렐릭 루비 에이전트를 자동으로 전달하고 Lambda 함수 호출 전에 루비 `require` 를 통해 로드됩니다. 충돌을 피하려면 다른 곳에 루비 에이전트 사본을 포함하지 마세요. 에이전트의 존재를 활용하려면 함수 내에서 원하는 뉴렐릭 루비 에이전트 API 호출을 자유롭게 수행하세요. - + + 뉴렐릭 레이어는 뉴렐릭 루비 에이전트를 자동으로 전달하고 Lambda 함수 호출 전에 루비 `require` 를 통해 로드됩니다. 충돌을 피하려면 다른 곳에 루비 에이전트 사본을 포함하지 마세요. 에이전트의 존재를 활용하려면 함수 내에서 원하는 뉴렐릭 루비 에이전트 API 호출을 자유롭게 수행하세요. + - Java, Python, Node.js 및 .Net 런타임은 루비와 동일한 소비 흐름을 따르지만 일부 다른 핸들러를 사용합니다. 함수 콘솔에서 새로 연결된 레이어를 가리키도록 함수 핸들러를 업데이트하는 방법은 다음과 같습니다. + Java, Python, Node.js 및 .Net 런타임은 루비와 동일한 소비 흐름을 따르지만 일부 다른 핸들러를 사용합니다. 함수 콘솔에서 새로 연결된 레이어를 가리키도록 함수 핸들러를 업데이트하는 방법은 다음과 같습니다. * 자바: @@ -220,17 +203,14 @@ translationType: machine * .Net의 경우 핸들러를 설정할 필요가 없습니다. - Go의 경우 Lambda 함수의 소스 코드를 변경하여 이를 소비해야 합니다. 설정 변경만으로는 충분하지 않습니다. + Go의 경우 Lambda 함수의 소스 코드를 변경하여 이를 소비해야 합니다. 설정 변경만으로는 충분하지 않습니다. ## 배송 방법 - + 모든 에이전트 레이어에는 CloudWatch를 우회하여 로그인 및 페이로드를 뉴렐릭으로 보내기 위한 확장 기능도 포함되어 있습니다. 이는 지연 시간과 비용을 줄이는 데 도움이 될 수 있습니다. 그러나 기능의 성능과 안정성에 영향을 미칠 위험이 있습니다. 뉴렐릭 Lambda 레이어를 추가하면 확장 기능이 활성화되고 기본적으로 로그 전달이 비활성화됩니다. @@ -240,10 +220,7 @@ translationType: machine 함수 로그는 함수가 호출되는 동안 기록된 로그일 뿐이라는 점을 기억하는 것이 중요합니다. 확장 프로그램은 `START`, `END` 및 `REPORT` 줄과 같은 Lambda 런타임 로그를 보내지 않습니다. - + CloudWatch로만 데이터를 보내거나 대체로 데이터를 보내도록 선택할 수 있습니다. 자세한 내용은 [CloudWatch 대체 문서를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloudwatch-fallback) 참조하십시오. @@ -251,4 +228,4 @@ translationType: machine ## 다음은 뭐지? [#find-data] * 이러한 단계를 완료하면 [Lambda 모니터링 UI](/docs/lambda-monitoring-ui) 에서 데이터 보고를 볼 수 있습니다. -* 데이터를 찾는 데 문제가 있는 경우 [Lambda 활성화 문제 해결을](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot) 참조하십시오. +* 데이터를 찾는 데 문제가 있는 경우 [Lambda 활성화 문제 해결을](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot) 참조하십시오. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apis/rest-api-v2/migrate-to-nrql.mdx b/src/i18n/content/pt/docs/apis/rest-api-v2/migrate-to-nrql.mdx new file mode 100644 index 00000000000..23f9f064e41 --- /dev/null +++ b/src/i18n/content/pt/docs/apis/rest-api-v2/migrate-to-nrql.mdx @@ -0,0 +1,92 @@ +--- +title: Migrar para NRQL +tags: + - APIs + - REST API v2 + - NRQL +metaDescription: How to migrate your REST API v2 queries to NRQL queries. +freshnessValidatedDate: never +translationType: machine +--- + +## Liste nomes de métricas para seu aplicativo + +Para visualizar os nomes de métricas disponíveis para sua aplicação: + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appId = '$APP_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +Você também pode filtrar usando o nome do aplicativo: + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE appName = '$APP_NAME' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +Ou usando um agente específico (host): + +```nrql +SELECT uniques(metricTimesliceName) FROM Metric WHERE realAgentId = '$AGENT_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX +``` + +## Obtenha os valores de dados da métrica de fração de tempo do seu aplicativo + +A API REST v2 aceita uma lista de nomes de métricas e uma lista de valores para buscar dados de métricas de frações de tempo. + +Os nomes das métricas são os mesmos, você pode filtrá-los com o campo `metricTimesliceName` na sua consulta NRQL . + +Cada valor de API pode ser mapeado para uma função NRQL. Você pode consultar a tabela abaixo. + +Exemplo, para a seguinte solicitação de API: + +```bash +curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \ + -H "X-Api-Key:${API_KEY}" -i \ + -d 'names[]=HttpDispatcher&values[]=average_call_time&values[]=call_count' +``` + +Você usaria a seguinte consulta: + +```nrql +SELECT COUNT(newrelic.timeslice.value) AS call_count, average(newrelic.timeslice.value) * 1000 AS average_call_time +FROM Metric +WHERE appId = $APP_ID AND metricTimesliceName = 'HttpDispatcher' +``` + +| Value (RPM) | NRQL Function | | -------------------------- | ------------------------------------------------------------------------------------------------- | | average\_response\_time | average(newrelic.timeslice.value) \* 1000 | | calls\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | call\_count | count(newrelic.timeslice.value) | | min\_response\_time | min(newrelic.timeslice.value) \* 1000 | | max\_response\_time | max(newrelic.timeslice.value) \* 1000 | | average\_exclusive\_time | average(newrelic.timeslice.value\['totalExclusive'] / newrelic.timeslice.value\['count']) \* 1000 | | average\_value | average(newrelic.timeslice.value) | | total\_call\_time\_per\_minute | rate(sum(newrelic.timeslice.value), 1 minute) | | requests\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | standard\_deviation | stddev(newrelic.timeslice.value) \* 1000 | | average\_time | average(newrelic.timeslice.value) \* 1000 | | count | count(newrelic.timeslice.value) | | used\_bytes\_by\_host | average(newrelic.timeslice.value) \* 1024 \* 1024 | | used\_mb\_by\_host | average(newrelic.timeslice.value) | | total\_used\_mb | sum(newrelic.timeslice.value) | | average\_call\_time | average(newrelic.timeslice.value) \* 1000 | | total\_value | sum(newrelic.timeslice.value) | | min\_value | min(newrelic.timeslice.value) | | max\_value | max(newrelic.timeslice.value) | | rate | rate(sum(newrelic.timeslice.value), 1 second) | | throughput | rate(count(newrelic.timeslice.value), 1 second) | | as\_percentage | average(newrelic.timeslice.value) \* 100 | | errors\_per\_minute | rate(count(newrelic.timeslice.value), 1 minute) | | error\_count | count(newrelic.timeslice.value) | | total\_time | sum(newrelic.timeslice.value) \* 1000 | | sessions\_active | average(newrelic.timeslice.value) | | total\_visits | sum(newrelic.timeslice.value) | | percent | average(newrelic.timeslice.value) \* 100 | | percent (`CPU/User Time`) | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | time\_percentage | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | utilization | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | | visits\_percentage | 100 \* sum(newrelic.timeslice.value) / `$TIME_WINDOW_IN_SECONDS` | + +Se a função incluir `$TIME_WINDOW_IN_SECONDS`, significa que você precisa substituí-la pela janela de tempo que deseja consultar. + +Por exemplo, se você consultar uma janela de tempo de 30 minutos, você substituiria `$TIME_WINDOW_IN_SECONDS` por `1800`. + +### Apdex métricas + +| Value (RPM) | NRQL Function | | ------------- | ---------------------------------------------------------------------------------- | | score | apdex(newrelic.timeslice.value) | | s | apdex(newrelic.timeslice.value) or count(newrelic.timeslice.value) | | t | apdex(newrelic.timeslice.value) or sum(newrelic.timeslice.value) | | f | apdex(newrelic.timeslice.value) or sum(newrelic.timeslice.value\['totalExclusive']) | | count | apdex(newrelic.timeslice.value) | | value | apdex(newrelic.timeslice.value) | | threshold | max(newrelic.timeslice.value) | | threshold\_min | min(newrelic.timeslice.value) | + +### Métrica do EndUser & Mobile + +Essas métricas retornarão o mesmo resultado que você obteria da REST API v2, mas alguns resultados podem ser diferentes do que você vê na interface New Relic . Isso ocorre porque a interface utiliza evento em vez de dados da fração de tempo. Se você quiser obter os mesmos resultados da interface, consulte o evento diretamente. + +| Value (RPM) | NRQL Function | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | average\_response\_time | sum(newrelic.timeslice.value) / count(newrelic.timeslice.value) \* 1000 | | error\_percentage | (filter(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'EndUser/errors') / filter(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Browser')) | | average\_fe\_response\_time | sum(newrelic.timeslice.value\['totalExclusive']) / count(newrelic.timeslice.value) \* 1000 | | average\_be\_response\_time | 1000 \* (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive'])) / count(newrelic.timeslice.value) | | average\_network\_time | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) / count(newrelic.timeslice.value) | | total\_network\_time | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) | | network\_time\_percentage | (sum(newrelic.timeslice.value) - sum(newrelic.timeslice.value\['totalExclusive']) - sum(newrelic.timeslice.value\['sumOfSquares'])) / `$TIME_WINDOW_IN_SECONDS` | | total\_fe\_time | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) | | fe\_time\_percentage | 100 \* sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) / `$TIME_WINDOW_IN_SECONDS` | | average\_dom\_content\_load\_time | average(newrelic.timeslice.value) \* 1000 | | average\_queue\_time | average(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | total\_queue\_time | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | total\_dom\_content\_time | sum(newrelic.timeslice.value) \* 1000 | | total\_app\_time | sum(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) | | average\_app\_time | sum(newrelic.timeslice.value\[&apos;sumOfSquares&apos;]) / count(newrelic.timeslice.value) | | average\_sent\_bytes | sum(newrelic.timeslice.value\[&apos;totalExclusive&apos;]) \* 1000 | | average\_received\_bytes | 1000 \* sum(newrelic.timeslice.value) / count(newrelic.timeslice.value) | | launch\_count | count(newrelic.timeslice.value) | + +### Séries temporais e resumos + +Por padrão, a API REST retorna uma série de valores de dados métricos baseados. Para obter a média desses valores, você incluiria `&summarize=true` na sua chamada de API. + +Em NRQL, é o oposto. Você obtém um resumo por padrão e pode obter as séries temporais adicionando `TIMESERIES` à sua consulta. + +Outra diferença é que a janela de tempo padrão da API REST é de 30 minutos, enquanto na NRQL é de 1 hora. + +## Consulta múltipla métricas + +Você ainda pode consultar várias métricas de uma vez com NRQL, aqui está um exemplo: + +```nrql +SELECT + FILTER(1000 * AVERAGE(newrelic.timeslice.value), WHERE metricTimesliceName = 'HttpDispatcher') as average_response_time, + FILTER(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Errors/all') as error_count, + FILTER(average(newrelic.timeslice.value), WHERE metricTimesliceName = 'Memory/Heap/Max') as used_mb_by_host +FROM Metric +WHERE appName = '$APP_NAME' +SINCE 1 day ago +``` \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 208ec92dd1b..5e1b20299d9 100644 --- a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -331,7 +331,8 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic O agente .NET `v9.2.0` ou superior utiliza automaticamente a biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versão mínima suportada: 3.17.0 - * Última versão compatível verificada: 3.23.0 + * Última versão compatível verificada: 3.44.0 + * As versões 3.35.0 e superiores são suportadas a partir do agente .NET v10.32.0 @@ -372,7 +373,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Use [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/) * Versão mínima suportada: 23.4.0 - * Última versão compatível verificada: 23.5.1 + * Última versão compatível verificada: 23.6.0 Versões mais antigas de `Oracle.ManagedDataAccess.Core` podem ser instrumentadas, mas não foram testadas e não são suportadas. @@ -409,7 +410,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 2.3.0 - Última versão compatível verificada: 2.26.0 + Última versão compatível verificada: 2.29.0 A partir da versão 10.12.0 do agente, os seguintes métodos adicionados ou após a versão 2.7 do driver são instrumentados: @@ -478,7 +479,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic **Elastic.Clients.Elasticsearch** * Versão mínima suportada: 8.0.0 - * Versão compatível verificada mais recente: 8.14.6 + * Última versão compatível verificada: 8.15.8 * As versões 8.10.0 e superiores são suportadas a partir do agente .NET v10.20.1 * As versões 8.12.1 e superiores são suportadas a partir do agente .NET v10.23.0 @@ -596,7 +597,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 3.7.403.4 + 3.7.404.5 @@ -660,7 +661,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 3.1.1 + 4.0.1 @@ -678,7 +679,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 5.3.2 + 5.3.14 @@ -696,7 +697,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 8.0.0 + 8.0.1 @@ -790,7 +791,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 7.1.0 - * Última versão compatível verificada: 8.1.1 + * Última versão compatível verificada: 8.2.5 @@ -804,7 +805,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Última versão compatível verificada: 3.7.400.19 + * Última versão compatível verificada: 3.7.400.33 @@ -1249,7 +1250,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 2.3.0 - Última versão compatível verificada: 2.26.0 + Última versão compatível verificada: 2.29.0 A partir da versão 10.12.0 do agente, os seguintes métodos adicionados ou após a versão 2.7 do driver são instrumentados: @@ -1465,7 +1466,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 105.2.3 - Última versão compatível verificada: 111.4.0 + Última versão compatível verificada: 112.1.0 Versões incompatíveis conhecidas: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -1541,7 +1542,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 3.7.403.4 + 3.7.404.5 @@ -1605,7 +1606,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 3.1.1 + 4.0.1 @@ -1623,7 +1624,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - 5.3.2 + 5.3.14 @@ -1741,7 +1742,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 7.1.0 - * Última versão compatível verificada: 8.1.1 + * Última versão compatível verificada: 8.2.5 @@ -1755,7 +1756,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Última versão compatível verificada: 3.7.400.19 + * Última versão compatível verificada: 3.7.400.33 diff --git a/src/i18n/content/pt/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx b/src/i18n/content/pt/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx index d8b714c9985..30a1d247f2b 100644 --- a/src/i18n/content/pt/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx +++ b/src/i18n/content/pt/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx @@ -472,6 +472,16 @@ A lista a seguir contém as diferentes chamadas que você pode fazer com a API, Associa um ID de usuário à transação atual (veja abaixo para mais detalhes). + + + + `RecordDatastoreSegment` + + + + Permite que um armazenamento de dados não suportado seja instrumentado (veja abaixo para mais detalhes). + + @@ -975,6 +985,135 @@ A lista a seguir contém as diferentes chamadas que você pode fazer com a API, transaction.SetUserId("BobSmith123"); ``` + + + ### Sintaxe + + ```cs + SegmentWrapper? RecordDatastoreSegment(string vendor, string model, string operation, string? commandText = null, string? host = null, string? portPathOrID = null, string? databaseName = null) + ``` + + Permite que um armazenamento de dados não suportado seja instrumentado da mesma forma que o agente .NET instrumenta automaticamente seus datastores suportados. + + Este método requer o agente .NET e a API do agente .NET [versão 10.22.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-22-0/) ou superior. + + ### Parâmetro + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parâmetro + + Descrição +
+ `vendor` + + *corda* + + Nome do fornecedor do armazenamento de dados, como MySQL, MSSQL ou MongoDB. +
+ `model` + + *corda* + + Nome da tabela ou identificador semelhante em um armazenamento de dados não relacional. +
+ `operation` + + *corda* + + Operação sendo executada, como "SELECT" ou "UPDATE" para SQL banco de dados. +
+ `commandText` + + *corda?* + + Opcional. Consulta, ou descritor semelhante em um armazenamento de dados não relacional. +
+ `host` + + *corda?* + + Opcional. Servidor que hospeda o armazenamento de dados. +
+ `portPathOrID` + + *corda?* + + Opcional. Porta, caminho ou outro identificador, pareado com o host para auxiliar na identificação do armazenamento de dados. +
+ `databaseName` + + *corda?* + + Opcional. Nome do armazenamento de dados ou identificador semelhante. +
+ + ### Devoluções + + Wrapper de segmento descartável que cria e finaliza o segmento automaticamente. + + ### Exemplo + + ```cs + var transaction = NewRelic.Api.Agent.NewRelic.GetAgent().CurrentTransaction; + using (transaction.RecordDatastoreSegment(vendor, model, operation, + commandText, host, portPathOrID, databaseName)) + { + DatastoreWorker(); + } + ``` + diff --git a/src/i18n/content/pt/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx b/src/i18n/content/pt/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx index a5359600fd5..cd6c33f891e 100644 --- a/src/i18n/content/pt/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx +++ b/src/i18n/content/pt/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx @@ -1498,7 +1498,7 @@ Lembre-se de que a alteração das configurações no arquivo de configuração Se você estiver usando uma [framework de registro em log compatível](/docs/logs/logs-context/configure-logs-context-php), poderá instruir o agente a encaminhar os logs do seu aplicativo para o New Relic. -* `newrelic.application_logging.forward.enabled` ativa ou desativa o encaminhamento de logs +* `newrelic.application_logging.forwarding.enabled` ativa ou desativa o encaminhamento de logs * `newrelic.application_logging.forwarding.max_samples_stored` limita quantos registros seu aplicativo encaminha para o New Relic * `newrelic.application_logging.forwarding.log_level` permite escolher quais tipos de log seu aplicativo encaminha para o New Relic diff --git a/src/i18n/content/pt/docs/browser/browser-integrations/blazor-webassembly.mdx b/src/i18n/content/pt/docs/browser/browser-integrations/blazor-webassembly.mdx index 6d3a0595094..5337bd85213 100644 --- a/src/i18n/content/pt/docs/browser/browser-integrations/blazor-webassembly.mdx +++ b/src/i18n/content/pt/docs/browser/browser-integrations/blazor-webassembly.mdx @@ -10,13 +10,9 @@ translationType: machine Com nosso dashboard Blazor WebAssembly, você pode monitor facilmente suas métricas clássicas, rastrear a experiência do usuário final e ver o total de visualizações de página ao longo do tempo. -Construída com nosso agente de monitoramento de browser, a integração do Blazor WebAssembly oferece um conjunto de padrão que permite visualizar seus dados de consulta mais críticos, em local completo. +Construída com nosso agente de monitoramento de browser, a integração do Blazor WebAssembly oferece um conjunto de padrão que permite visualizar seus dados de consulta mais críticos, em local completo. -Blazor WebAssembly dashboard page +Blazor WebAssembly dashboard page
Depois de configurar a integração do Blazor WebAssembly com o New Relic, seus dados serão exibidos em um painel como este, pronto para uso. @@ -34,7 +30,7 @@ Existem dois métodos para instalar o agente de infraestrutura: Para coletar dados do Blazor WebAssembly, siga os procedimentos abaixo: -1. De [one.newrelic.com](https://one.newrelic.com), vá para a [página**Integrations & Agents** ](https://one.newrelic.com/marketplace). +1. De [one.newrelic.com](https://one.newrelic.com), vá para a [página**Integrations & Agents** ](https://one.newrelic.com/marketplace). 2. Clique em **Browser and mobile** e em **Browser monitoring**. @@ -50,7 +46,7 @@ Para coletar dados do Blazor WebAssembly, siga os procedimentos abaixo: 8. Reinicie seu aplicativo. -9. Vá para **[one.newrelic.com](https://one.newrelic.com/all-capabilities)** e clique em **Metrics & events**. Execute um exemplo de consulta NRQL para confirmar se o New Relic está coletando dados: +9. Vá para **[one.newrelic.com](https://one.newrelic.com/all-capabilities)** e clique em **Metrics & events**. Execute um exemplo de consulta NRQL para confirmar se o New Relic está coletando dados: ```sql SELECT average(windowLoad) FROM PageViewTiming WHERE (deviceType = 'Desktop') FACET `userAgentName` SINCE 604800 seconds AGO TIMESERIES @@ -66,4 +62,4 @@ Para saber mais sobre como construir uma consulta NRQL e gerar um painel, confir * [Introdução ao criador de consulta](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder) para criação de consultas básicas e avançadas. * [Introdução aos dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) para personalizar seu dashboard e realizar diversas ações. -* [Gerencie seu dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard) para ajustar o modo de exibição dos painéis ou para adicionar mais conteúdo ao seu dashboard. +* [Gerencie seu dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard) para ajustar o modo de exibição dos painéis ou para adicionar mais conteúdo ao seu dashboard. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx b/src/i18n/content/pt/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx index cd47600832e..1d77c9cc9c8 100644 --- a/src/i18n/content/pt/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx +++ b/src/i18n/content/pt/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx @@ -20,17 +20,8 @@ Este documento explica: O uso da métrica permite um armazenamento de dados mais eficiente. Isso, por sua vez, permite consultar seus dados e construir gráficos com mais facilidade. A diferença entre métricas e outros tipos de dados no New Relic é baseada no tempo. Para obter mais informações, consulte [Compreender os tipos de dados](/docs/using-new-relic/data/understand-data/new-relic-data-types). -* - **Events, logs, spans:** - - - Esses tipos de dados representam um único registro em um momento específico. Por exemplo, você pode ter um evento para cada solicitação ao sistema. Esses dados são ideais para resolução de problemas e análises aprofundadas. - -* - **Metrics:** - - - Eles fornecem uma visão agregada do seu evento, log ou períodos. métricas são melhores para mostrar tendências em intervalos de tempo mais longos. Por exemplo, você pode agregar o número total de solicitações por serviço a uma métrica e depois examinar essas informações mês após mês. +* **Events, logs, spans:** Esses tipos de dados representam um único registro em um momento específico. Por exemplo, você pode ter um evento para cada solicitação ao sistema. Esses dados são ideais para resolução de problemas e análises aprofundadas. +* **Metrics:** Eles fornecem uma visão agregada do seu evento, log ou períodos. métricas são melhores para mostrar tendências em intervalos de tempo mais longos. Por exemplo, você pode agregar o número total de solicitações por serviço a uma métrica e depois examinar essas informações mês após mês. @@ -83,10 +74,7 @@ O uso da métrica permite um armazenamento de dados mais eficiente. Isso, por su Aqui está um vídeo mostrando como gerar dados métricos a partir de dados de eventos (7:47 minutos): -
- + Aqui está um exemplo de uma resposta retornada: ```json @@ -273,10 +267,7 @@ Depois de criar uma regra métrica para converter dados para seu evento, log ou As [funções do agregador NRQL](/docs/insights/nrql-new-relic-query-language/nrql-reference/nrql-syntax-components-functions#functions) disponíveis dependem do [tipo de métrica](#summary-and-uniquecount) que você criou. Aqui estão alguns exemplos. - + Se você criou um tipo de métrica de resumo, poderá usar as funções agregadoras `count`, `sum`, `max`, `min` e `average` , conforme mostrado na consulta a seguir: ``` @@ -284,10 +275,7 @@ As [funções do agregador NRQL](/docs/insights/nrql-new-relic-query-language/nr ``` - + Se você criou um tipo de métrica `uniqueCount` , só poderá usar a função `uniqueCount` , conforme mostrado na consulta a seguir: ```sql @@ -295,10 +283,7 @@ As [funções do agregador NRQL](/docs/insights/nrql-new-relic-query-language/nr ``` - + Se você criou um tipo de métrica `distribution` , use as funções `percentile` ou `histogram` , conforme mostrado na consulta a seguir: ```sql @@ -321,4 +306,4 @@ Se sua chamada do NerdGraph não for construída corretamente, você poderá rec Cannot parse the unexpected character "\u201C” ``` -Verifique se as aspas na chamada do NerdGraph não são aspas inteligentes (aspas curvas). Nossa API NerdGraph aceita apenas cotações diretas. +Verifique se as aspas na chamada do NerdGraph não são aspas inteligentes (aspas curvas). Nossa API NerdGraph aceita apenas cotações diretas. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/iast/iast-configuration.mdx b/src/i18n/content/pt/docs/iast/iast-configuration.mdx index c418f44cf8f..1fc926437c9 100644 --- a/src/i18n/content/pt/docs/iast/iast-configuration.mdx +++ b/src/i18n/content/pt/docs/iast/iast-configuration.mdx @@ -22,10 +22,10 @@ Abra o arquivo de configuração `newrelic.yml` para definir o parâmetro `scan_ ```yml security: scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default is forever - schedule: "" #Cron Expression to define start time - always_sample_traces: false #regardless of scan schedule + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default is forever + schedule: "" # Cron Expression to define start time + always_sample_traces: false # regardless of scan schedule ``` @@ -90,10 +90,10 @@ security: Para programar o IAST para iniciar 30 minutos após o início do aplicativo e ser executado por 300 minutos, você deve definir o atraso como 30 e a duração como 300. ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - duration: 300 #In minutes, default is forever + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + duration: 300 # In minutes, default is forever ``` @@ -101,9 +101,9 @@ security: Para agendar a execução do IAST em um horário específico, defina a programação para uma expressão cron que represente o horário desejado. Por exemplo, para programar o IAST para ser executado todos os dias à meia-noite, você definiria a programação como `"0 0 0 * * ?"`. ```yml - security: - scan_schedule: - schedule: "0 0 0 * * ?" #By default, schedule is inactive + security: + scan_schedule: + schedule: "0 0 0 * * ?" # By default, schedule is inactive ``` @@ -115,10 +115,10 @@ security: Se você quiser que IAST sempre faça a amostragem do rastreamento, defina `always_sample_traces` como `true`. Por padrão, isso é definido como `false`, o que significa que IAST coleta amostras apenas do rastreamento dentro da janela de verificação ativa. ```yml - security: - scan_schedule: - delay: 30 #In minutes, default is 0 min - always_sample_traces: true #regardless of scan schedule + security: + scan_schedule: + delay: 30 # In minutes, default is 0 min + always_sample_traces: true # regardless of scan schedule ``` @@ -157,10 +157,10 @@ Você pode ignorar API específicas da análise IAST adicionando-as à seção A Este é o formato para especificar API: ```yml - exclude_from_iast_scan: - api: - - .*account.* - - .*/\api\/v1\/.*?\/login +exclude_from_iast_scan: + api: + - .*account.* + - .*/\api\/v1\/.*?\/login ``` Por exemplo: @@ -178,16 +178,18 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Esta é uma lista de chaves de cabeçalho HTTP. Se uma solicitação incluir cabeçalhos com essas chaves, a verificação IAST correspondente será ignorada. Por exemplo, se você tiver uma solicitação curl com cabeçalhos e quiser pular a varredura IAST no cabeçalho `X-Forwarded-For` , poderá passar esta configuração: ```bash - curl -X POST -H "X-Forwarded-For: 123.456.789.012" -H "Content-Type: application/x-www-form-urlencoded" -d "param1=value1¶m2=value2" http://example.com + curl -X POST -H "X-Forwarded-For: 123.456.789.012" \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "param1=value1¶m2=value2" http://example.com ``` Você pode usar esta configuração: ```yml - exclude_from_iast_scan: - http_request_parameters: - header: - - X-Forwarded-For + exclude_from_iast_scan: + http_request_parameters: + header: + - X-Forwarded-For ``` @@ -195,17 +197,17 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Esta é uma lista de chaves de parâmetros de consulta. A presença desses parâmetros na string de consulta da solicitação fará com que a varredura IAST seja ignorada. Por exemplo, se você tiver uma requisição curl com parâmetro de consulta e quiser pular a varredura IAST no parâmetro de consulta `customerID` e `username`, você pode passar esta configuração: ```bash - curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' + curl --location --request GET 'localhost:8080/sql/save?firstName=test&lastName=user&customerID=testuser&username=test123' ``` Você pode usar esta configuração: ```yml - exclude_from_iast_scan: - http_request_parameters: - query: - - username - - customerID + exclude_from_iast_scan: + http_request_parameters: + query: + - username + - customerID ``` @@ -217,29 +219,29 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Este é um exemplo de curl para o tipo de conteúdo JSON quando você tem uma solicitação curl com corpo JSON e deseja pular a varredura IAST em `customerID` e `firstName`. ```bash - curl --location --request POST 'localhost:8080/application/json/post' \ + curl --location --request POST 'localhost:8080/application/json/post' \ --header 'Content-Type: application/json' \ --data '{ - "path": "sample.txt", - "script":"testscript", - "customerID":"GREAL", - "name": { - "firstName": "john", - "lastName": "wick" - }, - "url":"http://example.com", - "cmd":"ls" + "path": "sample.txt", + "script":"testscript", + "customerID":"GREAL", + "name": { + "firstName": "john", + "lastName": "wick" + }, + "url":"http://example.com", + "cmd":"ls" }' ``` Você pode usar esta configuração: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - customerID - - name.firstName + exclude_from_iast_scan: + http_request_parameters: + body: + - customerID + - name.firstName ``` #### Exemplo para XML Content-Type @@ -247,7 +249,7 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Esta é uma solicitação curl com corpo XML e você deseja pular a varredura IAST em `customerID` e `username`. ```bash - curl --location 'localhost:8080/application/xml/post' \ + curl --location 'localhost:8080/application/xml/post' \ --header 'Content-Type: application/xml' \ --data ' @@ -265,11 +267,11 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Você pode usar esta configuração: ```yml - exclude_from_iast_scan: - http_request_parameters: - body: - - AppData.customerID - - AppData.username + exclude_from_iast_scan: + http_request_parameters: + body: + - AppData.customerID + - AppData.username ``` #### Exemplo de tipo de conteúdo codificado em URL de formulário @@ -277,7 +279,7 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Esta é uma solicitação curl com corpo Form-URL-Encoded, e você deseja pular a varredura IAST em `customerID` e `username`. ```bash - curl --location 'localhost:8080/application/urlencode/post' \ + curl --location 'localhost:8080/application/urlencode/post' \ --header 'Content-Type: application/x-www-form-urlencoded' \ -d 'name=madhav&path=sample.txt&customerID=GREAL&script=K2&url=http://example.com&username=bob&firstName=Aliko&cmd=ls' ``` @@ -285,10 +287,10 @@ Você pode ignorar parâmetros de solicitação HTTP específicos da análise IA Você pode usar esta configuração: ```yml - http_request_parameters: - body: - - customerID - - username + http_request_parameters: + body: + - customerID + - username ``` @@ -304,18 +306,18 @@ A configuração `iast_detection_category` permite que o usuário especifique ca Veja este exemplo para pular a verificação de injeção de SQL e SSRF. Os parâmetros `sql_injection` e `ssrf` são definidos como `true`: ```yml - exclude_from_iast_scan: - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: true - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: true - rxss: false +exclude_from_iast_scan: + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: true + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: true + rxss: false ``` @@ -325,32 +327,32 @@ Veja este exemplo para pular a verificação de injeção de SQL e SSRF. Os par Você pode usar esta configuração combinada: ```yml - security: +security: + enabled: true + scan_schedule: + delay: 0 # In minutes, default is 0 min + duration: 0 # In minutes, default will be forever + #schedule: "" # Cron Expression to define start time + always_sample_traces: false # continuously collect samples + exclude_from_iast_scan: + api: [] + http_request_parameters: + header: [] + query: [] + body: [] + iast_detection_category: + insecure_settings: false + invalid_file_access: false + sql_injection: false + nosql_injection: false + ldap_injection: false + javascript_injection: false + command_injection: false + xpath_injection: false + ssrf: false + rxss: false + agent: enabled: true - scan_schedule: - delay: 0 #In minutes, default is 0 min - duration: 0 #In minutes, default will be forever - #schedule: "" #Cron Expression to define start time - always_sample_traces: false #continuously collect samples - exclude_from_iast_scan: - api: [] - http_request_parameters: - header: [] - query: [] - body: [] - iast_detection_category: - insecure_settings: false - invalid_file_access: false - sql_injection: false - nosql_injection: false - ldap_injection: false - javascript_injection: false - command_injection: false - xpath_injection: false - ssrf: false - rxss: false - agent: - enabled: true ``` ## Controladores de varredura IAST [#iast-scan-controllers] diff --git a/src/i18n/content/pt/docs/iast/troubleshooting.mdx b/src/i18n/content/pt/docs/iast/troubleshooting.mdx index d9531f7bb11..04b6e0419b4 100644 --- a/src/i18n/content/pt/docs/iast/troubleshooting.mdx +++ b/src/i18n/content/pt/docs/iast/troubleshooting.mdx @@ -14,84 +14,43 @@ Esta é a primeira etapa para diagnosticar você mesmo o problema do New Relic I Se você não encontrar seu problema listado aqui, você pode entrar em contato com [o suporte da New Relic](https://support.newrelic.com). - - Vá para **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. Clique em um aplicativo para verificar a eficiência dos testes do aplicativo, vulnerabilidades, API coberta e chamadas de métodos, entre outros dados. + + Vá para **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. Clique em um aplicativo para verificar a eficiência dos testes do aplicativo, vulnerabilidades, API coberta e chamadas de métodos, entre outros dados. - + O IAST exige a reinicialização do aplicativo depois de habilitado. - + Se este for um aplicativo novo, o firewall pode estar impedindo a comunicação com a plataforma NR. Verifique a seção de estatísticas de serviço no arquivo com o timestamp mais recente em `nr-security-home/logs/snapshots`. Todos os 6 itens dessa lista devem dizer OK. Caso contrário, revise o registro para obter informações adicionais ou entre em contato com [o suporte da New Relic](https://support.newrelic.com). Você também pode ver a [documentação padrão do firewall](/docs/new-relic-solutions/get-started/networks/). Se você puder ver seu aplicativo na interface do usuário do New Relic e o agente de segurança tiver iniciado o IAST com êxito, mas não encontrar vulnerabilidades na interface do usuário, verifique o seguinte: - * O nível de eficiência do seu aplicativo: Vá para **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. Procure seu aplicativo e verifique a seção de resumo. Se a cobertura do IAST for baixa para seu aplicativo, adicione casos de teste adicionais ao seu aplicativo para obter um nível mais alto de eficiência de teste. + * O nível de eficiência do seu aplicativo: Vá para **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. Procure seu aplicativo e verifique a seção de resumo. Se a cobertura do IAST for baixa para seu aplicativo, adicione casos de teste adicionais ao seu aplicativo para obter um nível mais alto de eficiência de teste. - * A cobertura do IAST: vá para **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. Procure seu aplicativo e clique nele. Na seção de resumo, verifique se a cobertura da análise IAST é alta e nenhuma vulnerabilidade foi detectada, o que significa que seu aplicativo está seguro. + * A cobertura do IAST: vá para **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. Procure seu aplicativo e clique nele. Na seção de resumo, verifique se a cobertura da análise IAST é alta e nenhuma vulnerabilidade foi detectada, o que significa que seu aplicativo está seguro. * Framework ou categoria de vulnerabilidades do seu aplicativo não é suportada. Se depois de verificar isso você ainda não estiver vendo vulnerabilidades no IAST, entre em contato com [o suporte da New Relic](https://support.newrelic.com/s/). - - Se você não vir seu aplicativo em **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**, verifique o seguinte: + + Se você não vir seu aplicativo em **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**, verifique o seguinte: * Seu aplicativo está instalado e funcionando: verifique o processo do aplicativo ou a [página APM e serviços](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/view-events-their-products#products). - * O log do aplicativo para descobrir se há algum problema. - * A versão do seu agente APM e atualize-a, se necessário. - * O arquivo de configuração `newrelic.yml` inclui a modificação do parâmetro conforme indicado na [página de instalação](/docs/iast/install). - * Vá para o diretório `nr-security-home/logs` e localize a linha `[SETP-8]` no arquivo `LANGUAGE-security-collector-init.log` . Verifique se há um erro inesperado e saiba o que falhou. - * O aplicativo tem tráfego. Gere algum tráfego para permitir que o IAST teste seu aplicativo. - - * Proxy ou firewall bloqueando o acesso. Coloque na lista de permissões os seguintes IPs `3.134.136.130, 18.219.177.104, 18.117.21.106` para o domínio - - - **csec.nr-data.net** - - - , os seguintes IPs `3.130.22.102, 3.138.243.136, 3.139.218.150` para o domínio - - - **csec-gov.nr-data.net** - - - e os seguintes IPs `18.185.235.118, 3.125.193.113, 3.75.166.122` para o domínio - - - **csec.eu01.nr-data.net** - - - . Mas nossa recomendação é adicionar domínios na lista de permissões em vez dos IPs, pois esses IPs podem mudar a qualquer momento. - - * O certificado TLS está correto. Adicione o certificado Let's Encrypt CA (baixe em [Let's Encrypt Certificates](https://letsencrypt.org/certificates/#root-certificates)) ao seu armazenamento confiável local. Inclua os certificados raiz e intermediários (ISRG Root X1 e Let's Encrypt R3) para estabelecer a cadeia de confiança completa. - + * Proxy ou firewall bloqueando o acesso. Coloque na lista de permissões os seguintes IPs `3.134.136.130, 18.219.177.104, 18.117.21.106` para o domínio **csec.nr-data.net**, os seguintes IPs `3.130.22.102, 3.138.243.136, 3.139.218.150` para o domínio **csec-gov.nr-data.net** e os seguintes IPs `18.185.235.118, 3.125.193.113, 3.75.166.122` para o domínio **csec.eu01.nr-data.net**. Mas nossa recomendação é adicionar domínios na lista de permissões em vez dos IPs, pois esses IPs podem mudar a qualquer momento. + * O certificado TLS está correto. Adicione o certificado Let's Encrypt CA (baixe em [Let's Encrypt Certificates](https://letsencrypt.org/certificates/#root-certificates)) ao seu armazenamento confiável local. Inclua os certificados raiz e intermediários (ISRG Root X1 e Let&apos;s Encrypt R3) para estabelecer a cadeia de confiança completa. * Framework ou categoria de vulnerabilidades do seu aplicativo é suportada. - + Se você estiver usando [o modo de alta segurança do APM](/docs/apm/agents/manage-apm-agents/configuration/high-security-mode/), o agente não funcionará. @@ -100,7 +59,7 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato Quando o agente de segurança está funcionando corretamente: - * Você vê seu aplicativo em **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. O aplicativo é iniciado e há tráfego gerado. + * Você vê seu aplicativo em **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. O aplicativo é iniciado e há tráfego gerado. * No diretório `nr-security-home/logs` , procure o arquivo `LANGUAGE-security-collector-init.log` . Substitua `LANGUAGE` no nome do arquivo pelo que você está usando. Pesquise estas etapas para ver onde está o problema: @@ -124,13 +83,10 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato ``` - + Você pode verificar se o IAST está funcionando, mesmo se estiver vendo seu aplicativo na interface do IAST e o agente de segurança tiver sido iniciado com êxito. Siga estas etapas para verificar: - 1. Vá para **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. + 1. Vá para **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. 2. Procure seu aplicativo na aba **Application tests** e clique nele. @@ -139,68 +95,49 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato Além disso, se você definir o nível de log como **debug/finest**, poderá procurar por **Fuzz request received** no arquivo `nr-security-home/logs/java-security-collector.log` . Isto mostra que a análise do IAST está em andamento. - + O IAST inicia os testes quando detecta que há tráfego, então verifique se o seu aplicativo funciona ou tem algum tráfego direcionado a ele. Execute a interface do aplicativo ou endpoints de API. - + Estas podem ser as razões pelas quais o IAST não detecta vulnerabilidades conhecidas: * IAST não oferece suporte framework de aplicativo. + * Não há instrumentação para o módulo. - + Seu aplicativo pode apresentar alto tráfego e latência por algum tempo como parte do IAST. Isso deve ser resolvido em alguns minutos quando o teste IAST for concluído. Você também pode verificar o arquivo de log do snapshot na pasta `nr-security-home/logs/snapshots` . O arquivo de log mostra o status do agente de segurança, o uso de recursos e os últimos cinco erros. - + Se o seu aplicativo tiver a funcionalidade de criar arquivos e diretórios como parte do atendimento a uma solicitação HTTP, o IAST tentará testar o caminho do código e, portanto, criar esses arquivos e diretórios. O código do aplicativo, sob a influência das solicitações HTTP recebidas, cria esses arquivos. O agente não pode excluí-los. Se você tiver certeza de que nenhuma API pode criar arquivos e diretórios, compartilhe a configuração e o log do seu aplicativo com [o suporte da New Relic](https://support.newrelic.com). - + Como parte do IAST, o agente de segurança envia novas solicitações ao aplicativo que aumenta a carga, resultando em um aumento na utilização de recursos. Essa análise IAST também pode expor erros ou exceções não detectados em seu aplicativo. Se o aplicativo travou devido à falta de recursos, aumente os recursos, reinicie o aplicativo e execute o IAST novamente. - + Você pode atualizar o `appId` na consulta abaixo e executá-lo no criador de consulta para encontrar todas as vulnerabilidades relatadas para sua aplicação. ```sql - SELECT * FROM Vulnerability WHERE issueType = 'Application Vulnerability' AND appId = '{your application's appId}' + SELECT * FROM Vulnerability + WHERE issueType = 'Application Vulnerability' AND appId = YOU_APPLICATION_ID ``` - + Atualize o status de suas vulnerabilidades se achar que o IAST relatou um falso positivo. Siga esses passos: - * Pesquise seu aplicativo: Vá para **[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**. + * Pesquise seu aplicativo: Vá para **[one.newrelic.com](https://one.newrelic.com) &gt; All capabilities &gt; IAST &gt; Tests**. * Clique na guia Todos os aplicativos e selecione as vulnerabilidades que não são vulnerabilidades reais. @@ -213,15 +150,12 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato * Se quiser listar as vulnerabilidades para as quais você atualizou o status, você pode aplicar o filtro na lista de vulnerabilidades exploráveis detectadas. - + * Para Golang, certifique-se de importar os pacotes de instrumentação necessários para a biblioteca e estrutura que seu aplicativo usa. Por exemplo, vamos supor que sua aplicação esteja usando biblioteca para [Mongo DB](http://go.mongodb.org/mongo-driver/mongo). Para esta biblioteca específica, você precisa importar este [pacote de instrumentação](https://github.com/newrelic/csec-go-agent/tree/main/instrumentation/csec_mongodb_mongo) do newrelic: - ``` + ```go import ( "github.com/newrelic/go-agent/v3/integrations/nrsecurityagent" "github.com/newrelic/go-agent/v3/newrelic" @@ -232,12 +166,12 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato Dependendo dos requisitos do seu aplicativo, existem outros pacotes que você pode precisar importar. Confira [aqui](https://github.com/newrelic/csec-go-agent#instrumentation-packages) a lista de pacotes suportados. - Certifique-se de importar o [pacote](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks) correspondente para cada módulo. + Certifique-se de importar o [pacote](https://github.com/newrelic/go-agent?tab=readme-ov-file#service-frameworks) correspondente para cada módulo. * Se você estiver abrindo um endpoint de protocolo HTTP, coloque a função `newrelic.WrapListen` ao redor do nome do endpoint para ativar a varredura de vulnerabilidades nesse endpoint: - ``` - http.ListenAndServe(newrelic.WrapListen(":"), nil) + ```go + http.ListenAndServe(newrelic.WrapListen(":YOUR_PORT_NUMBER"), nil) ``` @@ -247,38 +181,29 @@ Se você não encontrar seu problema listado aqui, você pode entrar em contato * Para um caso específico de **Outbound HTTP Request** ou chamadas para serviços externos, é necessário [atualizar o método do seu aplicativo](/docs/apm/agents/go-agent/instrumentation/instrument-go-segments/#go-external-segments). - + O IAST é compatível com o ambiente Windows. No entanto, para alguns aplicativos Java, você pode enfrentar `classCirculatoryError` e precisar desabilitar a instrumentação de baixa prioridade na configuração do agente da seguinte forma: * Desative a instrumentação de baixa prioridade na configuração de segurança: - ``` + ```yml low-priority-instrumentation: - enabled: false + enabled: false ``` * Exclua a classe de instrumentação de baixa prioridade do transformador de classe. Para fazer isso, adicione as linhas fornecidas na seção `class_transformer` do arquivo de configuração: - ``` + ```yml com.newrelic.instrumentation.security.low-priority-instrumentation: - enabled: false + enabled: false ``` - + Não, não temos nenhuma API para baixar as descobertas do IAST. - + O IAST envia novas solicitações ao aplicativo com base no que observa durante o teste. O objetivo é determinar se comportamentos maliciosos são possíveis, o que envolve a invocação API adicionais e chamadas de métodos usando uma carga útil de exploração. Isso pode resultar na manipulação indesejável dos dados dos clientes e no acionamento de serviços de proteção de tempo de execução. - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx index dd3e8eda436..8bd8dedbb52 100644 --- a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx +++ b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx @@ -36,7 +36,7 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Use `dpkg` para verificar se o agente está instalado: - ``` + ```sh dpkg -l | grep newrelic-infra ``` @@ -46,7 +46,7 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Use `rpm` para verificar se o agente está instalado: - ``` + ```sh rpm -qa | grep newrelic-infra ``` @@ -56,7 +56,7 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Use o prompt de comando do Windows ou o Powershell para verificar se o [diretório do agente](/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#infra-agent) existe: - ``` + ```sh dir "C:\Program Files\New Relic\newrelic-infra" ``` @@ -72,13 +72,13 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Verifique se o agente está em execução: - ``` + ```sh sudo systemctl status newrelic-infra ``` 2. Se o agente não estiver em execução, inicie-o manualmente: - ``` + ```sh sudo systemctl start newrelic-infra ``` @@ -88,13 +88,13 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Verifique se o agente está em execução: - ``` + ```sh sudo /etc/init.d/newrelic-infra status ``` 2. Se o agente não estiver em execução, inicie-o manualmente: - ``` + ```sh sudo /etc/init.d/newrelic-infra start ``` @@ -104,13 +104,13 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Verifique se o agente está em execução: - ``` + ```sh sudo initctl status newrelic-infra ``` 2. Se o agente não estiver em execução, inicie-o manualmente: - ``` + ```sh sudo initctl start newrelic-infra ``` @@ -120,13 +120,13 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 1. Verifique se o agente está em execução: - ``` + ```sh sc query "newrelic-infra" | find "RUNNING" ``` 2. Se o agente não estiver em execução, inicie-o manualmente com o prompt de comando do Windows: - ``` + ```sh net start newrelic-infra ``` @@ -150,7 +150,7 @@ Se nenhum dado aparecer na interface, tente as seguintes etapas para diagnostica 7. Confirme se o host está reportando corretamente mesmo que não esteja aparecendo na interface de monitoramento de infraestrutura criando uma consulta básica no criador de consulta, como: - ``` + ```sql SELECT * FROM SystemSample SINCE 60 minutes ago LIMIT 100 ``` diff --git a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx index d7e5eddea0f..b58a3e7c91b 100644 --- a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx +++ b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/generate-logs-troubleshooting-infrastructure.mdx @@ -46,7 +46,7 @@ A geração do arquivo de log `debug` requer a edição do arquivo de configura Edite seu arquivo `newrelic-infra.yml` com configurações de registro: - ``` + ```yml log: level: debug file: /path/to/logfile.log @@ -123,17 +123,14 @@ Para obter detalhes sobre como habilitar o encaminhamento de logs para o agente Estas são algumas notas e requisitos adicionais para sistemas específicos, usados para complementar as [instruções gerais de registro](#verbose): - + Se você estiver usando um agente de infraestrutura em contêiner: 1. Escolha uma destas opções para alterar o nível de log para detalhado: * Recomendado: defina a variável de ambiente `NRIA_LOG_LEVEL` como `debug`. Executar isso na linha de comando seria semelhante a: - ``` + ```sh -e NRIA_LOG_LEVEL=debug ``` @@ -143,10 +140,10 @@ Estas são algumas notas e requisitos adicionais para sistemas específicos, usa 2. Use `journalctl` para coletar o registro: - ``` + ```sh journalctl -u newrelic-infra > newrelic-infra.log ``` 3. Defina o nível de registro novamente para `info` ou `warn` após coletar o registro por alguns minutos. - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx index 514e1e6ebf1..05102f332db 100644 --- a/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx +++ b/src/i18n/content/pt/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-logs/infrastructure-agent-logging-behavior.mdx @@ -15,7 +15,7 @@ O agente de infraestrutura da New Relic reúne seus próprios dados, bem como o O exemplo a seguir mostra uma configuração típica para o log do agente em sistemas Linux (alterar o caminho do arquivo ao executar o Windows ou outra plataforma): -``` +```yml log: level: info file: '/var/log/newrelic-infra/newrelic-infra.log' @@ -60,7 +60,7 @@ Por padrão, os logs de infraestrutura são formatados como texto: Alternativamente, o log pode ser formatado como um arquivo JSON: -``` +```json {"context":{},"level":"info","msg":"upstart_interval_sec: 0","timestamp":"2019-07-11T18:24:03+02:00"} {"context":{},"level":"info","msg":"plugin_dir: ","timestamp":"2019-07-11T18:24:03+02:00"} ``` @@ -81,18 +81,18 @@ Para obter mais informações sobre como ativar o modo detalhado inteligente e o ## Integração gerenciamento de logs -Integração grava a carga JSON em STDOUT e o texto simples (JSON estruturado no futuro) faz login em STDERR. +Integração escreve JSON carga em `STDOUT` e texto simples (JSON estruturado no futuro) log em `STDERR`. -O agente de infraestrutura manipula linhas STDERR de integração e encaminha essa saída para o log do agente. +O agente de infraestrutura manipula as linhas de integração `STDERR` e encaminha essa saída para o log do agente. -O agente trata cada linha STDERR da seguinte maneira: +O agente manipula cada linha `STDERR` da seguinte maneira: -* **when agent runs in verbose mode**: apenas encaminha a linha STDERR completa como uma entrada de log do agente DEBUG, colocando contextos de linha de integração dentro do campo \`msg\`. -* **otherwise**: analisa a linha em relação ao formato esperado (veja abaixo) e registra apenas como nível de agente ERROR, entradas produzidas pela integração com níveis de severidade \`fatal\` ou \`error\`. Nesse caso, os campos são extraídos e encaminhados de maneira estruturada (portanto, se a saída JSON estiver habilitada para o agente, os campos se tornarão consultáveis. +* **When agent runs in verbose mode**: ele apenas encaminha a linha `STDERR` completa como uma entrada de log do agente DEBUG, colocando contextos de linha de integração dentro do campo `msg` . +* **Otherwise**: ele analisa a linha em relação ao formato esperado (veja abaixo) e registra apenas como nível de ERRO do agente, entradas produzidas pela integração com níveis de severidade `fatal` ou `error` . Nesse caso, os campos são extraídos e encaminhados de maneira estruturada (portanto, se a saída JSON estiver habilitada para o agente, os campos se tornarão consultáveis). Por padrão, o agente de infraestrutura filtra quaisquer erros de integração que não impeçam a execução da integração. Você só verá todos os erros de uma integração se o nível de log estiver definido como DEBUG ou se a integração estiver listada especificamente na configuração do log. Por exemplo, nesta configuração, todos os erros provenientes de `nri-mssql` serão mostrados, mesmo que o nível de log seja INFO: -```YAML +```yml log: include_filters: integration_name: @@ -103,13 +103,13 @@ log: Espera-se que uma linha seja uma lista de pares de valores principais separados por um caractere igual. As chaves podem conter qualquer caractere, enquanto os valores podem ter três formatos diferentes: -1. string: <quote>qualquer caractere incluindo aspas de escape \\"<quote> -2. mapa: &{qualquer caractere} +1. string: <quote>qualquer caractere incluindo aspas de escape \\"<quote> +2. mapa: &\{qualquer caractere} 3. palavra: qualquer caractere, exceto espaços Internamente o agente usou este regex para extrair os campos: -``` +```regex ([^\s]*?)=(".*?[^\\]"|&{.*?}|[^\s]*) ``` @@ -126,4 +126,4 @@ Irá gerar uma linha log do agente estruturada com estes campos: - "level": "error" - "msg": "Foo bar baz" - "foo": "bar" -``` +``` \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx index 47935c48f31..24c5a73070c 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx @@ -3269,26 +3269,26 @@ Se o agente estiver sendo executado em uma instância de nuvem, o agente tentar Neste exemplo, excluímos o processo métrica usando arquivos executáveis e nomes: - ``` - exclude_matching_metrics: # You can combine attributes from different metrics - process.name: - - regex "^java" # Exclude all processes starting with "java" - process.executable: - - "/usr/bin/python2" # Exclude the Python 2.x executable - - regex "\\System32\\svchost" # Exclude all svchost executables + ```yml + exclude_matching_metrics: # You can combine attributes from different metrics + process.name: + - regex "^java" # Exclude all processes starting with "java" + process.executable: + - "/usr/bin/python2" # Exclude the Python 2.x executable + - regex "\\System32\\svchost" # Exclude all svchost executables ``` Para configurar `exclude_matching_metrics` como uma variável de ambiente para a [integração do Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/), adicione-a no manifesto dentro do objeto `env:` : ```yml env: - - name: NRIA_EXCLUDE_MATCHING_METRICS - value: | - process.name: - - regex "^java" - process.executable: - - "/usr/bin/python2" - - regex "\\System32\\svchost" + - name: NRIA_EXCLUDE_MATCHING_METRICS + value: | + process.name: + - regex "^java" + process.executable: + - "/usr/bin/python2" + - regex "\\System32\\svchost" ``` Padrão @@ -5550,83 +5550,83 @@ Se você estiver tendo problemas com a configuração do proxy, consulte [Resolu ```bash curl http://localhost:8003/v1/status - { - "checks": { - "endpoints": [ - { - "url": "https://infrastructure-command-api.newrelic.com/agent_commands/v1/commands", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/infra/v2/metrics", - "reachable": true - }, - { - "url": "https://identity-api.newrelic.com/identity/v1", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/inventory", - "reachable": true - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://infrastructure-command-api.newrelic.com/agent_commands/v1/commands", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://identity-api.newrelic.com/identity/v1", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/inventory", + [output] "reachable": true + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` Endpoint de status principal (com erros): ```bash curl http://localhost:8003/v1/status - { - "checks": { - "endpoints": [ - { - "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", - "reachable": false, - "error": "endpoint check timeout exceeded" - }, - { - "url": "https://infra-api.newrelic.com/infra/v2/metrics", - "reachable": true - }, - { - "url": "https://identity-api.newrelic.com/identity/v1", - "reachable": true - }, - { - "url": "https://infra-api.newrelic.com/inventory", - "reachable": true - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": false, + [output] "error": "endpoint check timeout exceeded" + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://identity-api.newrelic.com/identity/v1", + [output] "reachable": true + [output] }, + [output] { + [output] "url": "https://infra-api.newrelic.com/inventory", + [output] "reachable": true + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` Exemplo de endpoint de erros: ```bash curl http://localhost:18003/v1/status/errors - { - "checks": { - "endpoints": [ - { - "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", - "reachable": false, - "error": "endpoint check timeout exceeded" - } - ] - }, - "config": { - "reachability_timeout": "10s" - } - } + [output] { + [output] "checks": { + [output] "endpoints": [ + [output] { + [output] "url": "https://staging-infra-api.newrelic.com/infra/v2/metrics", + [output] "reachable": false, + [output] "error": "endpoint check timeout exceeded" + [output] } + [output] ] + [output] }, + [output] "config": { + [output] "reachability_timeout": "10s" + [output] } + [output] } ``` Isso é semelhante ao endpoint de status principal, mas filtra apenas aqueles com erros. @@ -5635,10 +5635,10 @@ Se você estiver tendo problemas com a configuração do proxy, consulte [Resolu ```bash curl http://localhost:8003/v1/status/entity - { - "guid":"MMMMNjI0NjR8SU5GUkF8TkF8ODIwMDg3MDc0ODE0MTUwNTMy", - "key":"your-host-name" - } + [output] { + [output] "guid":"MMMMNjI0NjR8SU5GUkF8TkF8ODIwMDg3MDc0ODE0MTUwNTMy", + [output] "key":"your-host-name" + [output] } ``` Retorna informações sobre a entidade agente/host. Um código de status de resposta *204* (&quot;Sem Conteúdo&quot;) será retornado quando o agente ainda não tiver informações sobre a entidade agente/host. Portanto, podem ser necessárias várias solicitações até que o agente forneça os dados da entidade. diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx index eaa59d18c77..230f8ebc66d 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx @@ -117,7 +117,7 @@ Você também pode realizar estas etapas adicionais: * [Configure o arquivo de log](#log-file). * [Altere o local do binário do agente](#agent-binary). - + ## Instale o script de serviço [#install-service-script] @@ -131,10 +131,7 @@ Antes de prosseguir com a instalação do script de serviço, você precisa dete - + Não há uma boa maneira de saber programaticamente qual gerenciador de serviços está sendo usado em seu host, mas podemos fornecer algumas heurísticas. Para determinar o gerenciador de serviços, use os seguintes comandos: @@ -168,10 +165,7 @@ Antes de prosseguir com a instalação do script de serviço, você precisa dete Se você usar um dos gerenciadores de serviços suportados, instale o script de serviço para seu host: - + 1. Copie o arquivo de serviço `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service` para `/etc/systemd/system/newrelic-infra.service` 2. Habilite o script de serviço: @@ -181,10 +175,7 @@ Se você usar um dos gerenciadores de serviços suportados, instale o script de ``` - + 1. Copie o arquivo de serviço `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra` para `/etc/init.d/system/newrelic-infra` 2. Execute os seguintes comandos: @@ -195,10 +186,7 @@ Se você usar um dos gerenciadores de serviços suportados, instale o script de ``` - + 1. Copie o arquivo de serviço `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra` para `/etc/init/newrelic-infra.conf` 2. Execute o seguinte comando: @@ -230,20 +218,14 @@ usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml Para tornar essa alteração permanente, edite o script de serviço: - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`. 2. Procure a linha `ExecStart=/usr/bin/newrelic-infra`. 3. Adicione o sinalizador de configuração e o caminho do arquivo de configuração. Neste exemplo, o arquivo de configuração está localizado no diretório `/opt` `ExecStart=/usr/bin/newrelic-infra -config /opt/config.yaml`. 4. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`. 2. Procure a linha `DAEMON=/usr/bin/$NAME”`. @@ -257,10 +239,7 @@ Para tornar essa alteração permanente, edite o script de serviço: 5. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`. 2. Procure a linha `exec /usr/bin/newrelic-infra`. 3. Adicione o `config flag` e o `config file path`. Aqui o `config file` está localizado no diretório `/opt` `exec /usr/bin/newrelic-infra -config /opt/config.yaml`. @@ -279,10 +258,7 @@ O agente de infraestrutura usa um `pid-file` para manter o número de identifica Para alterar a localização do `pid-file`: - + Na inicialização, o agente grava seu processo `pid` no `pid-file`. Se o arquivo não existir, ele será criado. Por padrão, o agente cria o `pid-file` usando o caminho `/var/run/newrelic-infra/newrelic-infra.pid`. Para modificá-lo, use uma destas opções: @@ -304,10 +280,7 @@ Para alterar a localização do `pid-file`: ``` - + Não recomendamos usar a variável de ambiente `PIDFILE` para gerenciar o `pid-file`. @@ -333,30 +306,21 @@ Para alterar o modo de execução: 1. Edite o script de serviço: - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`. 2. Procure a linha `[Service]`. 3. Adicione a linha `User=user_name` e substitua `user_name` pelo usuário que você deseja executar o agente (`PRIVILEGED` ou `UNPRIVILEGED`). 4. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`. 2. Procure a linha `USER=root`. 3. Substitua `root` pelo usuário que você deseja executar o agente (`PRIVILEGED` ou `UNPRIVILEGED`). 4. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`. 2. Procure a linha `exec /usr/bin/newrelic-infra`. 3. Substitua-o por `exec su -s /bin/sh -c ‘exec “$0” “$@“’ user_name-- /usr/bin/newrelic-infra`. @@ -427,30 +391,21 @@ Para substituir o local predefinido do arquivo de log, use um dos seguintes mét Para alterar a localização do executável, edite o script de serviço: - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service`. 2. Procure a linha `[ExecStart=/usr/bin/newrelic-infra]`. 3. Substitua o caminho. 4. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/sysv/newrelic-infra`. 2. Procure a linha `DAEMON=/usr/bin/$NAME`. 3. Substitua o caminho. 4. Salve o arquivo. - + 1. Abra o script de serviço `./newrelic-infra/etc/init_scripts/upstart/newrelic-infra`. 2. Procure a linha `exec /usr/bin/newrelic-infra`. 3. Substitua o caminho. @@ -467,4 +422,4 @@ Você também pode querer: * Habilite [o encaminhamento de logs](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent#tarball-install). * Habilite nossa integração Flex [adicionando manualmente o executável Flex](https://github.com/newrelic/nri-flex/releases). * Adicione outra [integração de infraestrutura](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) para coletar dados de serviços externos. -* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure-start-stop-restart-check-agent-status#linux). +* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure-start-stop-restart-check-agent-status#linux). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx index bf28a671247..c59064f5712 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx @@ -34,46 +34,46 @@ Para instalar o agente de infraestrutura, siga as instruções passo a passo: 2. Certifique-se de que [o Homebrew](https://brew.sh/) esteja instalado no sistema. Você pode verificar a instalação do Homebrew com: ```bash - which brew + which brew ``` Se não estiver instalado, você pode instalá-lo com este comando (ou verificar as instruções atualizadas [do Homebrew](https://brew.sh/) ): ```bash - /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" + /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ``` 3. Em seguida, abra o terminal e execute o seguinte comand:: ```bash - brew install newrelic-infra-agent -q + brew install newrelic-infra-agent -q ``` 4. Inicie o serviço do agente de infraestrutura: ```bash - brew services start newrelic-infra-agent + brew services start newrelic-infra-agent ``` -5. Crie o arquivo de configuração e adicione seu : +5. Crie o arquivo de configuração e adicione seu : Intel x86: ```bash - sudo mkdir -p /usr/local/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /usr/local/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml ``` Silício da Apple: ```bash - sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ - echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml + sudo mkdir -p /opt/homebrew/etc/newrelic-infra/ + echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /opt/homebrew/etc/newrelic-infra/newrelic-infra.yml ``` Aguarde alguns minutos e [visualize seu servidor na interface de infraestrutura](/docs/infrastructure/infrastructure-ui-pages/infra-ui-overview). Se nenhum dado aparecer após esperar alguns minutos, siga as [etapas de resolução de problemas](/docs/infrastructure/new-relic-infrastructure/troubleshooting/no-data-appears-infrastructure). - + ## Qual é o próximo? [#configure] @@ -85,4 +85,4 @@ A única [opção de configuração](/docs/infrastructure/install-configure-infr ## Atualizar o agente [#update] -Para atualizar para a versão mais recente, siga os procedimentos padrão para [atualizar o agente de infraestrutura](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent). +Para atualizar para a versão mais recente, siga os procedimentos padrão para [atualizar o agente de infraestrutura](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx index 5394ade2fbb..404f14e5185 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent.mdx @@ -24,33 +24,36 @@ Se você usou o procedimento de instalação padrão para seu agente de infraest Desinstalar com apt (Debian.webpDebian,ubuntu iconUbuntu)} + title={<>Desinstalar com apt (Debian.webpDebian,ubuntu icon + } > Execute o seguinte comando como root: - ``` + ```sh sudo apt-get remove newrelic-infra ``` Desinstale com yum (amazon linux.webpAmazon Linux,centos iconCentOS,redhat iconRHEL)} + title={<>Desinstalar com yum (amazon linux.webpAmazon Linux,centos iconCentOS,redhat icon + } > Execute o seguinte comando como root: - ``` + ```sh sudo yum remove newrelic-infra ``` Desinstalar com Zypper (suse iconLES)} + title={<>Desinstalar com Zypper (suse icon + } > Execute o seguinte comando como root: - ``` + ```sh sudo zypper -n remove newrelic-infra ``` @@ -62,52 +65,31 @@ Se você seguiu um processo de instalação [assistida](/docs/infrastructure/ins Você também deve desinstalar qualquer monitoramento de integração de nuvem, como nossa integração Azure ou Google Cloud Platform . Caso contrário, você continuará vendo o host na sua interface sem dados. -## Desinstale oWindows Server iconAgente de infraestrutura do Windows [#uninstall-windows] +## Desinstale oWindows Server icon [#uninstall-windows] Se você usou o procedimento de instalação padrão para o agente de infraestrutura para ambientes Windows, para desinstalar: 1. Certifique-se de ter [direitos de administrador](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure#permissions) em seu grupo de administração do Windows. - 2. [Pare o agente de infraestrutura](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#windows). - -3. No Windows - - - **Control Panel** - - - , use a ferramenta - - - **Add/Remove Programs and Features** - - - para desinstalar o agente de infraestrutura. - -4. No Windows - - - **Program Files** - - - , exclua manualmente a pasta New Relic para excluir todos os arquivos associados ao agente de infraestrutura para Windows. +3. No Windows **Control Panel**, use a ferramenta **Add/Remove Programs and Features** para desinstalar o agente de infraestrutura. +4. No Windows **Program Files**, exclua manualmente a pasta New Relic para excluir todos os arquivos associados ao agente de infraestrutura para Windows. Se você seguiu um processo de instalação [assistida](/docs/infrastructure/install-configure-infrastructure/windows-installation/assisted-install-infrastructure-windows) ou [manual](/docs/infrastructure/install-configure-infrastructure/windows-installation/manual-install-infrastructure-windows), será necessário excluir manualmente todos os arquivos criados ao descompactar o arquivo do agente. -## Desinstale omacOS iconagente de infraestrutura macOS [#uninstall-macos] +## Desinstale omacOS icon [#uninstall-macos] Se você usou o procedimento de instalação padrão do agente de infraestrutura para ambientes macOS, para desinstalar: 1. [Pare o agente de infraestrutura](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#macOS): - ``` - brew services stop newrelic-infra-agent + ```sh + brew services stop newrelic-infra-agent ``` 2. No terminal, execute o comando de desinstalação: - ``` - brew uninstall newrelic-infra-agent + ```sh + brew uninstall newrelic-infra-agent ``` ## Desinstalar usando ferramentas de gerenciamento de configuração [#uninstall-other] @@ -146,4 +128,4 @@ Para desinstalar o agente de infraestrutura se você usou uma ferramenta de gere ## Opcional: limpar os arquivos restantes [#leftover-files] -Se você usar ferramentas de gerenciamento de pacotes padrão para a plataforma selecionada, o processo de desinstalação normalmente deixa arquivos de configuração e outros arquivos diversos. Se você precisar limpar completamente qualquer um dos arquivos restantes após desinstalar o agente New Relic Infrastructure , siga os procedimentos padrão para o seu sistema operacional. +Se você usar ferramentas de gerenciamento de pacotes padrão para a plataforma selecionada, o processo de desinstalação normalmente deixa arquivos de configuração e outros arquivos diversos. Se você precisar limpar completamente qualquer um dos arquivos restantes após desinstalar o agente New Relic Infrastructure , siga os procedimentos padrão para o seu sistema operacional. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx index 257853c69a8..eb49c5ad145 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-integrations.mdx @@ -20,10 +20,7 @@ Se você utilizou o pacote integração, [consulte as instruções do pacote int Aqui estão alguns exemplos: - + @@ -75,10 +72,7 @@ Aqui estão alguns exemplos:
- + @@ -130,41 +124,35 @@ Aqui estão alguns exemplos:
- + Certifique-se de usar o contexto apropriado na máquina onde executará o Helm e `kubectl`: Você pode verificar os contextos disponíveis com: - ``` + ```sh kubectl config get-contexts ``` E mude para o contexto desejado usando: - ``` + ```sh kubectl config use-context CONTEXT_NAME ``` Se você usou o Helm para instalar a integração do Kubernetes, basta desinstalá-lo usando o Helm: - ``` + ```sh helm uninstall --namespace NAMESPACE_USED_DURING_INSTALLATION RELEASE_NAME ``` Se você instalou a integração do Kubernetes usando um manifesto, use o mesmo manifesto para desinstalá-la: - ``` + ```sh kubectl delete -f newrelic-infrastructure.yaml ``` - + @@ -216,10 +204,7 @@ Aqui estão alguns exemplos:
- + @@ -271,10 +256,7 @@ Aqui estão alguns exemplos:
- + @@ -326,10 +308,7 @@ Aqui estão alguns exemplos:
- + 1. `cd /path/to/statsd` 2. `npm uninstall @newrelic/statsd-infra-backend` 3. No StatsD config.js, remova a entrada `"@newrelic/statsd-infra-backend"` da lista de back-end. @@ -354,10 +333,7 @@ Se você remover o pacote integração e quiser continuar usando o pacote integr 1. Remova o pacote de integração seguindo estas instruções. Os arquivos de configuração da integração antiga não serão excluídos, portanto você não precisará configurá-los novamente. - + @@ -404,7 +380,7 @@ Se você remover o pacote integração e quiser continuar usando o pacote integr @@ -414,4 +390,4 @@ Se você remover o pacote integração e quiser continuar usando o pacote integr -2. Instale sua integração uma por uma seguindo [estas instruções](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic). Para replicar o pacote de integração, você precisará instalar novamente toda a integração disponível. +2. Instale sua integração uma por uma seguindo [estas instruções](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic). Para replicar o pacote de integração, você precisará instalar novamente toda a integração disponível. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx index 00285405239..94358702c06 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent.mdx @@ -22,7 +22,7 @@ Para visualizar a versão atual do agente de infraestrutura para um host na inte * Hosts únicos: veja a tag `agentVersion` em qualquer [entidade de host](/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#find) ou procure seu `Agent version` na interface **Infrastructure**. * Vários hosts: acesse **Infrastructure > Navigator** e agrupe a entidade de relatório por `agentVersion` para ver uma lista de hosts ativos por versão. * Consulta: Utilize o atributo `agentVersion` em qualquer métrica de agente padrão para gerar um relatório. Por exemplo, a seguinte consulta NRQL mostra o número de grupos de hosts ativos exclusivos por versão do agente: - ``` + ```sql FROM SystemSample SELECT uniqueCount(hostname) FACET agentVersion LIMIT MAX diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx index fa28b5ad36f..9196225c82c 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-assisted-install-infrastructure-agent-windows.mdx @@ -17,7 +17,7 @@ Para instalar o agente: 1. Baixe o [arquivo empacotado do agente](https://download.newrelic.com/infrastructure_agent/binaries/windows/) ou use o comando a seguir que busca automaticamente uma versão específica do agente, sua soma de verificação e a verifica após o download. Substitua `$arch=amd64` pela arquitetura desejada (AMD64, 386) e `$v=1.27.4` pela [versão mais recente ou específica](https://github.com/newrelic/infrastructure-agent/releases/latest). - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -25,21 +25,17 @@ Para instalar o agente: 3. Certifique-se de que o arquivo seja descompactado com a seguinte estrutura: - Infra-windows-files.png + Infra-windows-files.png 4. Depois de descompactado, acesse e edite o script de instalação do PowerShell `installer.ps1`. -5. Atualize seu . +5. Atualize seu . 6. Opcional: atualize qualquer outro [parâmetro](#parameters). 7. Execute `installer.ps1` com direitos de administrador. - + ## Configure sua instalação [#parameters] @@ -123,7 +119,7 @@ Você pode configurar o seguinte parâmetro durante a instalação assistida par @@ -198,4 +194,4 @@ Você também pode querer: * [Adicione um atributo personalizado](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) para anotar seus dados de infraestrutura. * [Conecte sua conta AWS](/docs/infrastructure-amazon-aws-ec2-integration#connect) se seus servidores estiverem hospedados no Amazon EC2. * Adicione outras [integrações New Relic Infrastructure ](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations)para coletar dados de serviços externos. -* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure-start-stop-restart-check-agent-status#linux). +* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure-start-stop-restart-check-agent-status#linux). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx index 9cfccb234ef..99b5311bd3d 100644 --- a/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx +++ b/src/i18n/content/pt/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx @@ -21,7 +21,7 @@ Para instalar o agente: 1. Baixe o [arquivo empacotado do agente](https://download.newrelic.com/infrastructure_agent/binaries/windows/) ou use o comando a seguir que busca automaticamente uma versão específica do agente, sua soma de verificação e a verifica após o download. Substitua `$arch=amd64` pela arquitetura desejada (AMD64, 386) e `$v=1.27.4` pela [versão mais recente ou específica](https://github.com/newrelic/infrastructure-agent/releases/latest). - ``` + ```sh $v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"}) ``` @@ -29,11 +29,7 @@ Para instalar o agente: 3. Certifique-se de que o arquivo seja descompactado com a seguinte estrutura: - Infra-windows-files.png + Infra-windows-files.png 4. [Instale o script de serviço](#install-service-script). @@ -116,7 +112,7 @@ Para substituir o local predefinido do arquivo de log, use um dos seguintes mét * Defina o caminho personalizado no arquivo de configuração `newrelic-infra.yml` usando o campo `log_file` . * Passe-o como um argumento de linha de comando usando `-log_file` ao executar o binário `newrelic-infra` . - + ## Qual é o próximo? [#what-next] @@ -125,4 +121,4 @@ Você também pode querer: * [Adicione um atributo personalizado](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes) para anotar seus dados de infraestrutura. * [Conecte sua conta AWS](/docs/integrations/amazon-integrations/get-started/connect-aws-new-relic-infrastructure-monitoring/) se seus servidores estiverem hospedados no Amazon EC2. * Adicione outra [integração New Relic Infrastructure ](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations/)para coletar dados de serviços externos. -* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows). +* [Inicie, pare, reinicie ou verifique manualmente o status do agente](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx index 4d94ef14060..3343f942e93 100644 --- a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx +++ b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/agent-not-starting-there-are-no-logs.mdx @@ -44,6 +44,6 @@ Para resolver isso, tente uma destas opções: * Altere a entrada `log_file` no arquivo de configuração `/etc/newrelic-infra.yml` . Nosso script de instalação cria a pasta `/var/log/newrelic-infra/` para esse fim, por isso recomendamos o seguinte valor: - ``` + ```yml log_file: /var/log/newrelic-infra/newrelic-infra.log - ``` + ``` \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx index d4298b93788..3bdaad33b6e 100644 --- a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx +++ b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/incorrect-data-reported.mdx @@ -19,63 +19,51 @@ O agente de infraestrutura inclui log de nível de trace que pode ser habilitado 1. Edite o arquivo de configuração [newrelic-infra.yml](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#logging-variables) e adicione os sinalizadores necessários para ativar o log. Por exemplo, para ativar todos os logs trace no caminho padrão do arquivo de log: - ``` - log: - level: trace + ```yml + log: + level: trace ``` O agente de infraestrutura versão 1.26.0 ou anterior requer uma configuração de registro diferente: -``` - verbose: 1 - trace: - # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. - - v3.submission - # dm.submission enables detailed logging for integrations using Dimensional Metric format. - - dm.submission +```yml +verbose: 1 +trace: + # v3.submission enables detailed logging for events, examples: SystemSample, NetworkSample, etc. + - v3.submission + # dm.submission enables detailed logging for integrations using Dimensional Metric format. + - dm.submission ``` 2. Use [seu sistema init](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) para reiniciar o serviço do agente: - + Use comandos SystemD com CentOS 7, Debian 8, RHEL 7 e Ubuntu 15.04 ou superior: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Use comandos do System V com Debian 7: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Use comandos Upstart com Amazon Linux, CentOS 6, RHEL 6 e Ubuntu 14.10 ou inferior: - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -86,9 +74,9 @@ O agente de infraestrutura versão 1.26.0 ou anterior requer uma configuração Exemplo de log quando v3.submission está habilitado: -``` +```log time="2021-12-28T09:27:28Z" level=debug msg="Sending events to metrics-ingest." component=MetricsIngestSender key=... numEvents=3 postCount=1 timestamps="[2021-01-01 09:27:28 +0000 UTC]" time="2021-12-28T09:27:28Z" level=debug msg="Preparing metrics post." component=MetricsIngestSender postCount=1 time="2021-12-28T09:27:28Z" level=trace msg="[{\"EntityID\":111,\"IsAgent\":true,\"Events\":[{\"eventType\":\"SystemSample\",\"timestamp\":1640683648,\"entityKey\":\"...\",\"cpuPercent\":0.2004008016032026, ...}]" feature=v3.submission time="2021-12-28T09:27:29Z" level=debug msg="Metrics post succeeded." component=MetricsIngestSender postCount=1 -``` +``` \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx index 5ddd2957c83..33179e08aae 100644 --- a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx +++ b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/reduce-infrastructure-agents-cpu-footprint.mdx @@ -110,22 +110,19 @@ A tabela abaixo lista alguns samplers para configurar:
- ``` + ```sh sudo zypper -n remove newrelic-infra-integrations --clean-deps ``` - A New Relic . + A New Relic .
-### Reduzir relatórios de plug-ins de agente [#reduce_plugins] +### Reduzir relatórios de plug-ins de agente [#reduce\_plugins][#reduce_plugins] O agente de infraestrutura possui plug-in integrado que coleta dados de inventário (configuração específica do sistema e informações de estado). Para alguns sistemas, o consumo de CPU pode ser relativamente alto se o plug-in estiver coletando muitos dados. Para reduzir o espaço ocupado, você pode desativar ou diminuir a frequência de amostragem para plug-ins específicos que relatam dados indesejados. - + * **Disable a single plugin:** Para desativar um plug-in, defina o valor da propriedade correspondente como `-1`. * **Disable all plugins:** `disable_all_plugins: true` * **Enable selected plugins:** Para ativar determinado plug-in, insira uma exceção em `disable_all_plugins`. Por exemplo, a configuração a seguir desativa todos os plug-ins e reativa as interfaces de rede e o plug-in SELinus para reportar a cada 120 segundos: - ``` + ```yml disable_all_plugins: true network_interface_interval_sec: 120 selinux_interval_sec: 120 @@ -134,7 +131,10 @@ O agente de infraestrutura possui plug-in integrado que coleta dados de inventá Desativar SELinux semodule -l (somente Linux)} + title={<>Desativar SELinux + semodule -l + (somente Linux) + } > O plug-in SELinux invoca periodicamente o comando do sistema `semodule -l` para obter informações sobre os módulos SELinux existentes. Na maioria das distribuições CentOS/RedHat, este comando irá gerar picos de consumo de CPU. @@ -143,33 +143,27 @@ O agente de infraestrutura possui plug-in integrado que coleta dados de inventá `selinux_enable_semodule: false` - + O plug-in Sysctl percorre toda a estrutura de diretórios `/sys` e lê os valores de todos os arquivos lá. Desativá-lo ou reduzir o intervalo pode diminuir algum tempo de CPU do sistema no agente de infraestrutura. Você pode desativar a frequência do inventário definindo-a como um número negativo ou reduzir a frequência definindo o valor de configuração `sysctl_interval_sec` como o número de segundos entre execuções consecutivas do plug-in. Por exemplo, para executar o plug-in uma vez a cada 10 minutos: - ``` + ```yml sysctl_interval_sec: 600 ``` Para desativar o plug-in Sysctl: - ``` + ```yml sysctl_interval_sec: -1 ``` O valor padrão atual da propriedade `sysctl_interval_sec` é `60`. - + Os plug-ins de inventário a seguir não consomem muito CPU, mas você ainda pode reduzir sua frequência ou desativá-los configurando as opções de configuração correspondentes. @@ -222,11 +216,11 @@ O agente de infraestrutura possui plug-in integrado que coleta dados de inventá -### Comentário integração no host [#on_host_integrations] +### Comentário integração no host [#on\_host\_integrations][#on_host_integrations] Se você usar infraestrutura de integração no host, isso poderá ter impactos adicionais no uso da CPU. A natureza do impacto e os métodos para ajustá-lo dependem da integração que você está usando. Aqui estão algumas maneiras de ajustar o uso da CPU de integração no host: * Veja se sua [integração](/docs/integrations/host-integrations/host-integrations-list) possui opções de configuração que você pode ajustar. -* Se possível, distribua a carga de monitoramento adicionando agente de infraestrutura adicional. Por exemplo, a integração Kafka permite uma [implantação multiagente](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents). +* Se possível, distribua a carga de monitoramento adicionando agente de infraestrutura adicional. Por exemplo, a integração Kafka permite uma [implantação multiagente](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration#multiple-agents). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx index 54604a445e9..fcbc2501226 100644 --- a/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx +++ b/src/i18n/content/pt/docs/infrastructure/new-relic-infrastructure/troubleshooting/time-gaps-missing-data.mdx @@ -23,28 +23,22 @@ As etapas a seguir atenuam o problema de lacunas de dados: 1. Remova o limite de um thread para o agente, permitindo um thread por núcleo. - - 1. Abra o seguinte arquivo em seu editor de texto simples favorito: C:\\Program Files\\New Relic\\newrelic-infra\\newrelic-infra.yml + + 1. Abra o seguinte arquivo no seu editor de texto simples favorito: `C:\Program Files\New Relic\newrelic-infra\newrelic-infra.yml` 2. Adicione a seguinte opção de configuração: - ``` + ```yml max_procs: -1 ``` - - 1. Abra o seguinte arquivo em seu editor de texto simples favorito: /etc/newrelic-infra.yml + + 1. Abra o seguinte arquivo no seu editor de texto simples favorito: `/etc/newrelic-infra.yml` 2. Adicione a seguinte opção de configuração: - ``` + ```yml max_procs: -1 ``` @@ -53,44 +47,32 @@ As etapas a seguir atenuam o problema de lacunas de dados: 2. Use [seu sistema init](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#init-system) para reiniciar o serviço do agente: - + Use comandos SystemD com CentOS 7, Debian 8, RHEL 7 e Ubuntu 15.04 ou superior: - ``` + ```sh sudo systemctl restart newrelic-infra ``` - + Use comandos do System V com Debian 7: - ``` + ```sh sudo /etc/init.d/newrelic-infra restart ``` - + Use comandos Upstart com Amazon Linux, CentOS 6, RHEL 6 e Ubuntu 14.10 ou inferior: - ``` + ```sh sudo initctl restart newrelic-infra ``` - - ``` + + ```sh net stop newrelic-infra net start newrelic-infra ``` @@ -101,4 +83,4 @@ As etapas a seguir atenuam o problema de lacunas de dados: O agente New Relic Infrastructure , por padrão, é executado em um único thread do sistema operacional. Isso pode significar que, especialmente em ambientes Windows, o agendador de processos oferece poucas chances de obter tempo de CPU quando o sistema está sobrecarregado. -A opção de configuração `max_procs: -1` remove essa limitação e permite que o agente use um thread por núcleo de CPU (no máximo). +A opção de configuração `max_procs: -1` remove essa limitação e permite que o agente use um thread por núcleo de CPU (no máximo). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx index 5e2319c92bd..f3588b0bc70 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/overview.mdx @@ -12,7 +12,7 @@ translationType: machine A versão 2 da integração do Kubernetes tem algumas configurações e requisitos diferentes da versão 3. Este documento aborda as configurações que são diferentes da versão 3 e que você precisará para a versão 2. Se não especificarmos nada diferente, você poderá usar as configurações da versão 3. - Tenha em mente que substituímos a versão 2 e você não deve usá-la. Mantemos esta documentação para usuários que ainda utilizam a versão 2. + A New Relic tornou a versão 2 obsoleta e recomenda não utilizá-la. Mantemos esta documentação para usuários que ainda usam a versão 2, embora não ofereçamos mais suporte a ela. Consulte [Introdução à integração do Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/) para começar a usar a versão atual do Kubernetes. @@ -289,10 +289,7 @@ Para configurar o monitoramento do plano de controle no OpenShift, remova o come Se você deseja gerar log detalhado e obter informações de versão e configuração, basta conferir as informações abaixo. - + Para a integração Kubernetes , o agente de infraestrutura apenas adiciona uma entrada log em caso de erro. Os erros mais comuns são exibidos no log padrão (não detalhado). Se estiver fazendo uma investigação mais aprofundada por conta própria ou com o suporte da New Relic, você pode ativar o modo detalhado. @@ -336,11 +333,7 @@ Se você deseja gerar log detalhado e obter informações de versão e configura 9. [Recuperar `kube-state-metrics` configuração de serviço](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + Para a integração Kubernetes , o agente de infraestrutura apenas adiciona uma entrada log em caso de erro. Os erros mais comuns são exibidos no log padrão (não detalhado). Se você estiver fazendo uma investigação mais aprofundada por conta própria ou com o suporte da New Relic, poderá ativar o modo detalhado. @@ -386,10 +379,7 @@ Se você deseja gerar log detalhado e obter informações de versão e configura 8. [Recuperar `kube-state-metrics` configuração de serviço](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/get-logs-version/#kube-state-metrics-version). - + Para obter o registro do pod conectado a `kube-state-metrics`: 1. Execute este comando: @@ -425,10 +415,7 @@ Se você deseja gerar log detalhado e obter informações de versão e configura ``` - + Para obter o log de um pod em execução em um nó mestre: 1. Obtenha os nós rotulados como mestres: @@ -500,4 +487,4 @@ Verifique o documento [Habilitar monitoramento de serviços usando o Helm Chart] ### Adicione um YAML de serviço à configuração de integração do Kubernetes [#add-service-yaml] -Se você estiver usando a versão 2 da integração do Kubernetes, será necessário adicionar uma entrada para este ConfigMap na seção `volumes` e `volumeMounts` do `spec` do DaemonSet, para garantir que todos os arquivos no ConfigMap sejam montados em `/etc/newrelic-infra/integrations.d/`. +Se você estiver usando a versão 2 da integração do Kubernetes, será necessário adicionar uma entrada para este ConfigMap na seção `volumes` e `volumeMounts` do `spec` do DaemonSet, para garantir que todos os arquivos no ConfigMap sejam montados em `/etc/newrelic-infra/integrations.d/`. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx index 417555e10eb..5fe2cbb05f7 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx @@ -82,7 +82,7 @@ Um segredo Kubernetes será replicado automaticamente do namespace do operador p * [.NET](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-init/general) * [Ruby](https://hub.docker.com/repository/docker/newrelic/newrelic-ruby-init/general) -Para .NET +Para .NET: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -96,7 +96,7 @@ spec: # env: ... ``` -Para Java +Para Java: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -111,7 +111,7 @@ spec: # env: ... ``` -Para NodeJS +Para Node.js: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -126,7 +126,7 @@ spec: # env: ... ``` -Para Python +Para Python: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -141,7 +141,7 @@ spec: # env: ... ``` -Para Ruby +Para Ruby: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -156,7 +156,7 @@ spec: # env: ... ``` -Para configuração específica do ambiente +Para configuração específica do ambiente: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -180,7 +180,7 @@ spec: value: "$(NEW_RELIC_LABELS)-$(NEW_RELIC_POD_NAME)" ``` -Segmentando tudo em um namespace específico com um rótulo +Segmentando tudo em um namespace específico com um rótulo: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -197,7 +197,7 @@ spec: values: ["java"] ``` -Segmentando um pod com um rótulo específico +Segmentando um pod com um rótulo específico: ```yaml apiVersion: newrelic.com/v1alpha2 @@ -214,7 +214,7 @@ spec: values: ["dotnet"] ``` -Usando um segredo com um nome não padrão +Usando um segredo com um nome não padrão: ```yaml apiVersion: newrelic.com/v1alpha2 diff --git a/src/i18n/content/pt/docs/logs/forward-logs/enable-log-management-new-relic.mdx b/src/i18n/content/pt/docs/logs/forward-logs/enable-log-management-new-relic.mdx index 8b862aebd17..933f65afda9 100644 --- a/src/i18n/content/pt/docs/logs/forward-logs/enable-log-management-new-relic.mdx +++ b/src/i18n/content/pt/docs/logs/forward-logs/enable-log-management-new-relic.mdx @@ -9,13 +9,9 @@ freshnessValidatedDate: never translationType: machine --- -Nossos recursos ajudam você a coletar, processar, explorar, consultar e alertar sobre seus dados log . Para obter seu login no New Relic, você pode usar qualquer uma destas opções: +Nossos recursos ajudam você a coletar, processar, explorar, consultar e alertar sobre seus dados log . Para obter seu login no New Relic, você pode usar qualquer uma destas opções: -Diagram of options to get your logs into New Relic +Diagram of options to get your logs into New Relic Para obter uma visão geral de nossas diversas soluções de log, consulte [Introdução aos logs](/docs/logs/get-started/get-started-log-management#integrate-logs). @@ -73,8 +69,8 @@ Aqui estão alguns detalhes sobre como realizar casos de uso específicos: * Use nosso agente de infraestrutura para coletar logs no nível do host. No arquivo de configuração `logging.yml` , certifique-se de seguir o diretório `/var/log/containers/*.log` . Por exemplo: ```yml logs: - - name: Docker-logs - file: /var/log/containers/*.log # Path to Docker log files + - name: Docker-logs + file: /var/log/containers/*.log # Path to Docker log files ``` * Use nossa [imagem Docker autônoma](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) @@ -86,7 +82,7 @@ Aqui estão alguns detalhes sobre como realizar casos de uso específicos: - Use nosso agente e agente de infraestrutura. Deixe o agente APM do seu aplicativo encaminhar os dados log diretamente para o New Relic com [o logAPM no contexto](/docs/apm/new-relic-apm/getting-started/get-started-logs-context). Não há necessidade de instalar ou manter software adicional de terceiros! + Use nosso agente e agente de infraestrutura. Deixe o agente APM do seu aplicativo encaminhar os dados log diretamente para o New Relic com [o logAPM no contexto](/docs/apm/new-relic-apm/getting-started/get-started-logs-context). Não há necessidade de instalar ou manter software adicional de terceiros! @@ -110,11 +106,11 @@ Aqui estão alguns detalhes sobre como realizar casos de uso específicos: Você pode encaminhar logs por meio de nosso agente de infraestrutura ou de um de nossos serviços log de terceiros com suporte. Veja como: -1. Tenha seu New Relic pronto para a conta para a qual deseja relatar o registro. +1. Tenha seu New Relic pronto para a conta para a qual deseja relatar o registro. 2. Instale um [direcionador de logs compatível](#log-forwarding). 3. Certifique-se de que a conectividade de saída na porta TCP 443 seja permitida para o [intervalo CIDR](/docs/using-new-relic/cross-product-functions/install-configure/networks/#infrastructure) que corresponde à sua [região](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers). 4. Dependendo de onde os dados da sua conta estão armazenados no New Relic, use o nome DNS `log-api.newrelic.com` ou `log-api.eu.newrelic.com` para configuração. -5. Se aplicável, configure o agente do seu aplicativo seguindo os [logs contextualizados manuais nos procedimentos](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/) . +5. Se aplicável, configure o agente do seu aplicativo seguindo os [logs contextualizados manuais nos procedimentos](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/) . ## Opções de encaminhamento de logs [#log-forwarding] @@ -149,7 +145,7 @@ Oferecemos suporte ao seguinte direcionador de logs da Microsoft: ### Outros encaminhadores de logs suportados [#forward-other] -Apoiamos o seguinte encaminhador de logs. Algumas dessas opções vêm com guias de início rápido, que fornecem e alertas prontos para uso. Você pode instalar os guias de início rápido após configurar o encaminhamento de logs. +Apoiamos o seguinte encaminhador de logs. Algumas dessas opções vêm com guias de início rápido, que fornecem e alertas prontos para uso. Você pode instalar os guias de início rápido após configurar o encaminhamento de logs. * Akamai DataStream 2: @@ -171,7 +167,7 @@ Apoiamos o seguinte encaminhador de logs. Algumas dessas opções vêm com guias * [Plug-in vetorial](/docs/logs/forward-logs/vector-output-sink-log-forwarding) - + ## EndpointTCP [#enable-endpoint] @@ -183,13 +179,9 @@ Se você preferir se conectar ao New Relic sem instalar um plug-in, oferecemos i ## Como funciona o encaminhamento de logs [#enable] -O diagrama a seguir mostra o ciclo de vida de uma mensagem do log para um aplicativo, desde o enriquecimento com metadados do agente (registro de logs em contexto) até a formatação e encaminhamento dos dados log para o New Relic. +O diagrama a seguir mostra o ciclo de vida de uma mensagem do log para um aplicativo, desde o enriquecimento com metadados do agente (registro de logs em contexto) até a formatação e encaminhamento dos dados log para o New Relic. -Diagram of how your logs flow into New Relic +Diagram of how your logs flow into New Relic
Este diagrama ilustra o fluxo de mensagem do log através do New Relic. @@ -209,4 +201,4 @@ Depois de habilitar seu roteador de logs, aproveite ao máximo seus dados no New * Veja seu logs contextualizados do desempenho do seu aplicativo na [interface do APM](/docs/logs/ui-data/use-logs-ui/#links). Solucione [erros](/docs/apm/apm-ui-pages/error-analytics/errors-page-find-fix-verify-problems/) com [distributed tracing](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data), rastreamento de pilha, registro de aplicativo e muito mais. * Obtenha visibilidade mais profunda do seu aplicativo e dos dados de desempenho da plataforma se estiver encaminhando seu log com nosso [agente de infraestrutura](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/). Revise seu [log de infraestrutura](/docs/logs/ui-data/use-logs-ui/#links) na interface. * Configure [o alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/). -* [consulte seus dados](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) e [crie dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/). Por exemplo, consulte nossos tutoriais do NerdGraph para consultar e gerenciar suas [regras de partição de dados](/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial) e suas [regras de análise de log](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). +* [consulte seus dados](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) e [crie dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/). Por exemplo, consulte nossos tutoriais do NerdGraph para consultar e gerenciar suas [regras de partição de dados](/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial) e suas [regras de análise de log](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx b/src/i18n/content/pt/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx index 8373490bfc3..e01d04acb95 100644 --- a/src/i18n/content/pt/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx +++ b/src/i18n/content/pt/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx @@ -29,9 +29,9 @@ Para encaminhar seu log do Kubernetes para o New Relic com nosso plug-in: Se você estiver [usando um segredo Kubernetes ](https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging/values.yaml#L8-L25)para armazenar o New Relic , o gráfico `newrelic-logging` enviará o log por padrão para o endpointdos EUA da API. Se a chave de licença pertencer a uma conta da UE ou FedRAMP e um segredo for usado para armazenamento de chaves, você deverá atualizar a configuração do endpoint com o valor apropriado dos [documentos de referência da API](/docs/logs/log-api/introduction-log-api/#endpoint). Aqui está um exemplo de como definir isso para contas da UE: ```yml - newrelic-logging: - enabled: true - endpoint: https://log-api.eu.newrelic.com/log/v1 + newrelic-logging: + enabled: true + endpoint: https://log-api.eu.newrelic.com/log/v1 ``` @@ -67,8 +67,8 @@ Para configurar seu cluster do Kubernetes para enviar os logmétricos internos e ```yml newrelic-logging: - fluentBit: - sendMetrics: true + fluentBit: + sendMetrics: true ``` Você só precisa ativar a configuração `newrelic-logging.fluentBit.sendMetrics` quando houver resolução de problemas em um cluster do Kubernetes. Recomendamos habilitá-lo para um único cluster do Kubernetes por vez para facilitar a resolução de problemas. diff --git a/src/i18n/content/pt/docs/logs/get-started/live-archives.mdx b/src/i18n/content/pt/docs/logs/get-started/live-archives.mdx index e1fbda60eef..822de984fb8 100644 --- a/src/i18n/content/pt/docs/logs/get-started/live-archives.mdx +++ b/src/i18n/content/pt/docs/logs/get-started/live-archives.mdx @@ -118,13 +118,13 @@ O recurso Live Archives oferece armazenamento de dados log de longo prazo que vo Aqui está um exemplo de consulta: - ``` + ```graphql query { actor { account(id: 1234567) { nrql( query: "SELECT count(*) FROM Log SINCE '2024-02-01 12:00:00' UNTIL '2024-02-01 13:00:00'" - options: {eventNamespaces: "Logging:Archive"} + options: { eventNamespaces: "Logging:Archive" } async: true ) { results diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index a3800c3cf6f..36520641528 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -7,11 +7,7 @@ translationType: machine Depois de vincular com êxito suas contas New Relic e AWS você pode instrumentar sua função AWS não conteinerizada do Lambda adicionando a camada New Relic Lambda. Isso integra o agente New Relic, permitindo o monitoramento automático sempre que suas funções são invocadas. -a diagram depicting non-containerized lambda function instrumentation +a diagram depicting non-containerized lambda function instrumentation ## Antes de você começar [#begin] @@ -33,10 +29,7 @@ Independentemente do método escolhido, a camada New Relic adiciona o agente New Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver apenas a telemetria no CloudWatch, ignorar o CloudWatch ou usar o CloudWatch como substituto. A seção [CloudWatch](#CloudWatch-only) no final deste documento orientará você em cada opção. - + Você pode instrumentar sua função do Lambda com o `newrelic-lambda` CLI início rápido. Para instalar ou atualizar a camada de instrumentação New Relic, execute este comando: @@ -52,10 +45,7 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver Observe que a CLI pode operar em muitas funções em um lote: use `--function all`, `--function installed` ou `--function not-installed` para operar em todas as funções em uma região ou apenas naquelas com ou sem instrumentação New Relic existente. - + O modelo de aplicativo serverless da AWS, ou SAM, é uma variante dos modelos CloudFormation que simplifica o relacionamento de funções com os recursos dos quais dependem e o gerenciamento do ciclo de vida de um aplicativo inteiro. Usamos SAM e CloudFormation para a maioria de nossas funções de exemplo do Lambda, e muitas outras ferramentas são construídas sobre modelos do CloudFormation, fornecendo uma camada adicional de abstração. CloudFormation é um serviço da AWS que simplifica o provisionamento e gerenciamento de recursos AWS . Ao definir o estado desejado dos recursos em modelos YAML ou JSON, o CloudFormation lida automaticamente com a chamada de API subjacente para criar, atualizar ou excluir recursos conforme necessário. Esta abordagem declarativa automatiza o gerenciamento da infraestrutura, garantindo consistência e reprodutibilidade. @@ -99,10 +89,7 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver Normalmente, você terá um arquivo chamado `template.yaml` que descreve sua função e seus recursos. - + framework sem servidor é uma ferramenta popular de desenvolvimento e implantação de aplicativos sem servidor. Ele foi escrito para AWS em Node.js e atua principalmente como uma abstração de alto nível sobre modelos CloudFormation. Funciona bem para funções Node, Python, Ruby, Java e .NET. A New Relic oferece um [plug-in framework Serverless](https://github.com/newrelic/serverless-newrelic-lambda-layers) para simplificar a instrumentação de seu aplicativo framework Serverless. @@ -134,19 +121,13 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver ``` - + Terraform é uma infraestrutura popular de uso geral como ferramenta de código. Ele pode ser usado para gerenciar recursos da AWS. Oferecemos [alguns exemplos](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) de New Relic instrumentado com função de implantação Lambda usando script Terraform. Você pode usar o [provedor New Relic Terraform](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) para configurar sua integração AWS . - + Embora seja mais propenso a erros e trabalhoso do que as abordagens acima, você pode alterar manualmente a configuração de uma função do Lambda para usar New Relic do AWS Lambda Console, para Node.js, Python, Ruby e Java. Aqui está um exemplo de como configurar o monitoramento Lambda do New Relic para um runtime Ruby : @@ -159,7 +140,7 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver 4. Vá para **Choose a layer** e selecione a opção **Specify an ARN** . - 5. Vá para a [New Relic's list of layers](https://layers.newrelic-external.com/) e use a lista suspensa para selecionar a região AWS onde sua função do Lambda está hospedada. A partir daí, localize o ARN que corresponde à versão e arquitetura Ruby da sua Função do Lambda. Deve haver duas opções: X86 e ARM64. Use o botão **Copy to clipboard** ou copie manualmente a string ARN. + 5. Vá para a [New Relic's list of layers](https://layers.newrelic-external.com/) e use a lista suspensa para selecionar a região AWS onde sua função do Lambda está hospedada. A partir daí, localize o ARN que corresponde à versão e arquitetura Ruby da sua Função do Lambda. Deve haver duas opções: X86 e ARM64. Use o botão **Copy to clipboard** ou copie manualmente a string ARN. 6. Na seção **Specify an ARN** do formulário do console AWS, cole o ARN da camada New Relic Lambda. @@ -190,7 +171,9 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver 15. Modifique a função de execução para permitir acesso ao segredo da chave de licença do New Relic. * Encontre o ARN do segredo chamado `NEW_RELIC_LICENSE_KEY`. + * Adicione uma nova política embutida na função de execução da função semelhante ao código abaixo. Substitua `SECRET_ARN` pelo valor encontrado acima. + ```json "Statement": [ { @@ -203,11 +186,11 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver ] ``` - - A camada New Relic entregará automaticamente o agente New Relic Ruby e será carregada por meio de um Ruby `require` antes da invocação da sua função do Lambda. Para evitar conflitos, não inclua uma cópia do agente Ruby em nenhum outro lugar. Sinta-se à vontade para realizar qualquer chamada de API do agente New Relic Ruby desejada em sua função para aproveitar a presença do agente. - + + A camada New Relic entregará automaticamente o agente New Relic Ruby e será carregada por meio de um Ruby `require` antes da invocação da sua função do Lambda. Para evitar conflitos, não inclua uma cópia do agente Ruby em nenhum outro lugar. Sinta-se à vontade para realizar qualquer chamada de API do agente New Relic Ruby desejada em sua função para aproveitar a presença do agente. + - Os tempos de execução Java, Python, Node.js e .Net seguirão o mesmo fluxo de instrumentação do Ruby, mas com alguns manipuladores diferentes. Veja como atualizar o manipulador da sua função para apontar para a camada recém-anexada no console da sua função: + Os tempos de execução Java, Python, Node.js e .Net seguirão o mesmo fluxo de instrumentação do Ruby, mas com alguns manipuladores diferentes. Veja como atualizar o manipulador da sua função para apontar para a camada recém-anexada no console da sua função: * Java: @@ -220,17 +203,14 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver * Para .Net você não precisa definir o manipulador. - Observe que para o Go, você deve fazer alterações no código-fonte da sua função do Lambda para instrumentá-lo. As alterações de configuração não são suficientes. + Observe que para o Go, você deve fazer alterações no código-fonte da sua função do Lambda para instrumentá-lo. As alterações de configuração não são suficientes. ## Métodos de Envio - + Cada camada de agente também contém uma extensão para enviar log e carga para o New Relic, ignorando o CloudWatch. Isso pode ajudar a reduzir a latência e os custos. No entanto, corre o risco de afetar o desempenho e a confiabilidade de sua função. Depois de adicionar uma camada New Relic Lambda, a extensão é habilitada e tem o envio de log desabilitado por padrão. @@ -240,10 +220,7 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver É importante observar que o log da função é apenas o log registrado pela função durante sua invocação. A extensão não enviará log de tempo de execução do Lambda como `START`, `END` e `REPORT` linhas. - + Você pode optar por enviar dados apenas para o CloudWatch ou como substituto. Para saber mais, consulte nossa [documentação de substituto do CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloudwatch-fallback). @@ -251,4 +228,4 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver ## Qual é o próximo? [#find-data] * Depois de concluir essas etapas, você poderá ver o relatório de dados na [interface de monitoramento do Lambda](/docs/lambda-monitoring-ui). -* Se você estiver tendo problemas para encontrar seus dados, consulte [Lambda permitir resolução de problemas](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot). +* Se você estiver tendo problemas para encontrar seus dados, consulte [Lambda permitir resolução de problemas](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot). \ No newline at end of file From 874f3ce21c60a5b619823731b18d98752e7b3099 Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Tue, 22 Oct 2024 12:05:40 +0000 Subject: [PATCH 38/49] chore: add translations --- .../user-management-concepts.mdx | 150 +----- .../alert-conditions.mdx | 2 +- .../rest-api/rest-api-calls-alerts.mdx | 244 +++++---- .../java-agent-configuration-config-file.mdx | 32 ++ .../compatibility-requirements-java-agent.mdx | 22 + .../configuration/php-agent-configuration.mdx | 150 ++++-- .../install-new-relic-ruby-agent.mdx | 35 +- .../security-browser-monitoring.mdx | 33 +- ...-requirements-limits-custom-event-data.mdx | 2 + .../get-started/intro-new-relic.mdx | 94 +--- .../get-started/networks.mdx | 20 +- .../nrql/nrql-syntax-clauses-functions.mdx | 488 ++++++++++-------- ...filter-new-relic-one-dashboards-facets.mdx | 52 +- .../write-synthetic-api-tests.mdx | 148 +++--- .../using-monitors/add-edit-monitors.mdx | 4 +- 15 files changed, 783 insertions(+), 693 deletions(-) diff --git a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx index 281a47cb499..9107893344e 100644 --- a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx +++ b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx @@ -35,11 +35,7 @@ New Relicへの初回サインアップでは、組織にはデフォルトの[< ユーザーがNew Relicにアクセスする方法を制御する場合は、[こちら](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/)で認証ドメインを管理します。 -New Relic user mgmt groups UI - default group assignments +New Relic user mgmt groups UI - default group assignments
[**Access management** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks#where)のビューで、デフォルトのグループ（**Admin**と**User** ）にロール、アカウント、管理設定へのアクセス権がどのように付与されるかを表示します。 @@ -47,11 +43,7 @@ New Relicへの初回サインアップでは、組織にはデフォルトの[< 以下は、グループアクセスがどのように機能するか、また、より大規模な組織にどのように関連しているかを示す図です。 -New Relic user management diagram +New Relic user management diagram
グループが、そのグループのユーザーにロールとアカウントへのアクセス権を付与する方法を示す図。 @@ -75,29 +67,8 @@ New Relicの機能にアクセスするには、ユーザーがロールと1つ 2つのデフォルトのユーザーグループがあります。 -* - **User** - - - ：このグループのユーザーはオブザーバビリティおよびモニタリングの使用と設定ができますが、請求の管理や他のユーザーの管理などのアカウントレベルのタスクを実行することは**できません**。これは、 - - - [**All product admin**](#standard-roles) - - - ロールにアクセスできます。このロールは、当社のオブザーバビリティプラットフォームツールの制御を許可しますが、より高いレベルのアカウントおよびユーザー管理機能へのアクセスを許可する[管理設定](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#admin-settings)はありません。 - -* - **Admin** - - - ： - - - [**All product admin**](#standard-roles) - - - [ロール](#standard-roles)があり、さらに使用可能なすべての[管理設定](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#admin-settings)があります。その結果、このグループは、より高いレベルの管理者機能を含むすべての機能にアクセスできます。 +* **User**：このグループのユーザーはオブザーバビリティおよびモニタリングの使用と設定ができますが、請求の管理や他のユーザーの管理などのアカウントレベルのタスクを実行することは**できません**。これは、[**All product admin**](#standard-roles)ロールにアクセスできます。このロールは、当社のオブザーバビリティプラットフォームツールの制御を許可しますが、より高いレベルのアカウントおよびユーザー管理機能へのアクセスを許可する[管理設定](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#admin-settings)はありません。 +* **Admin**：[**All product admin**ロール](#standard-roles)があり、さらに使用可能なすべての[管理設定](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#admin-settings)があります。その結果、このグループは、より高いレベルの管理者機能を含むすべての機能にアクセスできます。 ユーザーが所属するグループを編集するには、 **Access management** UI に移動してグループを編集するか、 **User management** UI に移動してユーザーを編集します。 @@ -149,7 +120,7 @@ New Relicの機能にアクセスするには、ユーザーがロールと1つ - このロールには、組織レベルの設定、ユーザー、請求を管理する機能を**except**、すべてのNew Relicプラットフォーム権限が含まれています。これは、プラットフォーム機能（設定を構成する機能など）の設定を許可するという意味で管理者ロールですが、組織レベルの管理者権限（[管理者設定](#admin-settings)を要する権限）は提供しません。 + このロールには、組織レベルの設定、ユーザー、請求を管理する機能を**except**、すべてのNew Relicプラットフォーム権限が含まれています。これは、プラットフォーム機能（設定を構成する機能など）の設定を許可するという意味で管理者ロールですが、組織レベルの管理者権限（[管理者設定](#admin-settings)を要する権限）は提供しません。 このロールは、基本的には下記の**Standard user**ロールに加えて、オブザーバビリティ機能を設定する機能が追加されています。 @@ -167,7 +138,7 @@ New Relicの機能にアクセスするには、ユーザーがロールと1つ - 当社のプラットフォーム機能（APM UIやUIなど）へのアクセスを提供しますが、これらの機能を設定するための権限や、組織レベルおよびユーザー管理の権限はありません。 + 当社のプラットフォーム機能（APM UIやUIなど）へのアクセスを提供しますが、これらの機能を設定するための権限や、組織レベルおよびユーザー管理の権限はありません。 アクセス管理UIを使用して、プラットフォーム全体の標準ユーザーロールに含まれる機能を表示します。 @@ -203,53 +174,16 @@ New Relicの機能にアクセスするには、ユーザーがロールと1つ 設定には以下の項目が含まれています。 -* - **Organization settings** - - - : アカウントの追加、組織とアカウントの名前の変更など、組織の設定に関連する権限。 - -* - **Authentication domain settings** - - - : 認証ドメインの構成やグループとロールのカスタマイズなど、ユーザーの追加と管理に関連する権限。 このオプションには次のものが含まれます。 - - * - **Manage** - - - : ドメインの構成やユーザーの追加など、認証ドメインのあらゆる側面を管理できます。 - - * - **Read only** - - - ：認証ドメインとユーザー情報を表示できます。 - - * - **Add users** - - - : ユーザー情報を表示し、組織にユーザーを追加できますが、その他の認証ドメイン設定や管理機能はありません。 - - * - **Read users** - - - : ユーザー情報のみ表示可能です。 +* **Organization settings**: アカウントの追加、組織とアカウントの名前の変更など、組織の設定に関連する権限。 -* - **Billing** - +* **Authentication domain settings**: 認証ドメインの構成やグループとロールのカスタマイズなど、ユーザーの追加と管理に関連する権限。 このオプションには次のものが含まれます。 - ：ユーザーは請求と使用状況、データ保持期間を表示および管理できます。複数のアカウントを持つ組織の場合、請求は + * **Manage**: ドメインの構成やユーザーの追加など、認証ドメインのあらゆる側面を管理できます。 + * **Read only**：認証ドメインとユーザー情報を表示できます。 + * **Add users**: ユーザー情報を表示し、組織にユーザーを追加できますが、その他の認証ドメイン設定や管理機能はありません。 + * **Read users**: ユーザー情報のみ表示可能です。 - - **reporting account** - - - （通常は組織で最初に作成されたアカウント）に集約されます。 +* **Billing**：ユーザーは請求と使用状況、データ保持期間を表示および管理できます。複数のアカウントを持つ組織の場合、請求は**reporting account** （通常は組織で最初に作成されたアカウント）に集約されます。 ### グループ管理者 [#group-admin] @@ -259,11 +193,6 @@ New Relicの機能にアクセスするには、ユーザーがロールと1つ **Group admin**ロールを使用するには、ユーザーは少なくとも 1 つの認証ドメイン管理者設定を有するグループに属している必要があります。 -