diff --git a/src/content/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes.mdx b/src/content/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes.mdx index 4327399f65a..9c9eceb93ba 100644 --- a/src/content/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes.mdx +++ b/src/content/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes.mdx @@ -476,4 +476,4 @@ Additional restrictions include: ## Restricted metric values [#restricted-metric-values] -Any metric data submitted to the Metric API with a `value` equal to `NaN` (not a number), `positive infinity`, or `negative infinity` will be dropped. +Any metric data submitted to the Metric API with a `value` equal to `NaN` (not a number), `positive infinity`, or `negative infinity` will be dropped. Non-finite values may cause [`NrIntegrationError`](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/troubleshoot-nrintegrationerror-events/) events to be emitted. diff --git a/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088.mdx b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088.mdx new file mode 100644 index 00000000000..a2043aff267 --- /dev/null +++ b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088.mdx @@ -0,0 +1,14 @@ +--- +subject: Mobile app for iOS +releaseDate: '2025-01-23' +version: '6.8.8' +downloadLink: 'https://itunes.apple.com/us/app/new-relic/id594038638?mt=8' +redirects: + - /docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088 +--- + +### Analytics & Fixes + +* Added Page Session Tracking Events +* Added click events +* Bug fix related to incorrect page session creation via bottom tabs. diff --git a/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089.mdx b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089.mdx new file mode 100644 index 00000000000..40530bca300 --- /dev/null +++ b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089.mdx @@ -0,0 +1,13 @@ +--- +subject: Mobile app for iOS +releaseDate: '2025-02-10' +version: '6.8.9' +downloadLink: 'https://itunes.apple.com/us/app/new-relic/id594038638?mt=8' +redirects: + - /docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089 +--- + +### Analytics & Fixes +* Measure time taken by pages of Top Flows in :Requesting and Loading API Response, and Page Rendering +* Page Session Time Instrumentation for Explorer and Logs +* Fix to stop the Page Session when app goes to background and start again when app comes to foreground diff --git a/src/content/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx b/src/content/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx index 3c16656c759..6118df7799f 100644 --- a/src/content/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx +++ b/src/content/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx @@ -38,6 +38,18 @@ Minions are deployed on servers, and the agents are activated using non-personal IP addresses for released locations are subject to change. If a change is needed, we'll attempt to proactively notify customers prior to any changes via e-mail. You can also check the [Support Forum](https://discuss.newrelic.com/) for updates. The IP ranges listed are reserved for use by New Relic and cannot be used by anyone else. + + If you are adding Synthetics traffic to the allowlist from any public locations using IP addresses, you must update your allowlists with the new IP ranges. New IP ranges to allowlist: + + * 152.38.128.0/19 + * 212.32.0.0/20 + * 64.251.192.0/20 + + **If no action is taken** + + If you do not update your allowlists by **April 14, 2025**, your Synthetics checks may fail to connect to your applications, which may result in failed connections and trigger alerts. + + @@ -54,6 +66,10 @@ IP addresses for released locations are subject to change. If a change is needed
+ + The IP range list in JSON format will change after **April 14, 2025** as some older IPs will be replaced by the new ranges specified above. Please ensure you whitelist the newly mentioned ranges. + + ## Public minion locations and location labels [#location] The following table cross-references the synthetic's public minion locations with their location labels. You can [query](/docs/query-your-data) the `location` and `locationLabel` attributes from the [SyntheticCheck](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticcheck-table) and [SyntheticRequest](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticrequest-table) events. diff --git a/src/content/eol/2025/02/eol-01-31-25-synthetics-ip.md b/src/content/eol/2025/02/eol-01-31-25-synthetics-ip.md new file mode 100644 index 00000000000..feae05e8929 --- /dev/null +++ b/src/content/eol/2025/02/eol-01-31-25-synthetics-ip.md @@ -0,0 +1,89 @@ +--- +title: 'Update to New Relic Synthetics IP ranges' +summary: 'Updating Synthetics IP ranges.' +publishDate: '2025-02-11' +eolEffectiveDate: '2025-04-14' +--- + +In order to ensure the best service to our customers, New Relic will change the IP ranges for New Relic Synthetics checks **effective April 14, 2025.** + +If Synthetics traffic is part of your allowlist, **you will need to update your configurations** to maintain monitor connectivity. + +Failure to update your allowlist by **April 14, 2025**, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts. + +**NOTE:** If you do not allowlist by IP range, no action is required. + +## What's changing? +We will be migrating the IP address range for the New Relic service used by Synthetics public locations to align with our standard IP ranges used across other data ingest. + +## What action is required? + +* Before **April 14, 2025**, update your allow lists with the new IP ranges provided below. + + **New IP ranges to allowlist:** + + * `152.38.128.0/19` + + * `212.32.0.0/20` + + * `64.251.192.0/20` + +* After **April 14, 2025**, remove the old IP ranges from the allowlist. Failure to do so may result in failed connections and trigger alerts. + +**Old IP ranges to remove:** Please refer to the table below for a complete list of current IP ranges **that need to be removed after April 14, 2025**. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Region NameRegion LocationCurrent CIDR Block Range
us-east-1Washington, DC, USA44.202.178.0/24
44.202.180.0/23
44.210.68.0/24
44.210.110.0/25
us-east-2Columbus, OH, USA3.145.224.0/24
3.145.225.0/25
3.145.234.0/24
us-west-1San Francisco, CA, USA3.101.204.0/23
3.101.212.0/24
3.101.209.192/26
us-west-2Portland, OR, USA35.89.46.0/23
35.92.27.0/24
ap-southeast-2Sydney, AU3.26.252.0/24
3.26.245.128/25
3.27.51.0/25
eu-central-1Frankfurt, DE3.71.170.0/24
3.71.103.96/27
3.75.4.128/25
eu-west-1Dublin, IE3.251.231.0/24
3.251.230.64/26
3.252.47.0/25
eu-west-2London, England, UK13.40.201.0/24
13.40.208.0/25
13.41.206.128/25
13.41.206.64/26
+ +## Additional Support + +We understand that these changes may require some adjustments to your routine. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our [support team](https://support.newrelic.com/s/). \ No newline at end of file diff --git a/src/content/whats-new/2025/02/whats-new-01-31-synthetics-ip.md b/src/content/whats-new/2025/02/whats-new-01-31-synthetics-ip.md new file mode 100644 index 00000000000..13f9ecb0781 --- /dev/null +++ b/src/content/whats-new/2025/02/whats-new-01-31-synthetics-ip.md @@ -0,0 +1,89 @@ +--- +title: 'Update to New Relic Synthetics IP ranges' +summary: 'Updating Synthetics IP ranges change' +releaseDate: '2025-02-11' +learnMoreLink: 'https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#synthetics' +--- + +In order to ensure the best service to our customers, New Relic will change the IP ranges for New Relic Synthetics checks **effective April 14, 2025.** + +If Synthetics traffic is part of your allowlist, **you will need to update your configurations** to maintain monitor connectivity. + +Failure to update your allowlist by **April 14, 2025**, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts. + +**NOTE:** If you do not allowlist by IP range, no action is required. + +## What’s changing? +We will be migrating the IP address range for the New Relic service used by Synthetics public locations to align with our standard IP ranges used across other data ingest. + +## What action is required? + +* Before **April 14, 2025**, update your allow lists with the new IP ranges provided below. + + **New IP ranges to allowlist:** + + * `152.38.128.0/19` + + * `212.32.0.0/20` + + * `64.251.192.0/20` + +* After **April 14, 2025**, remove the old IP ranges from the allowlist. Failure to do so may result in failed connections and trigger alerts. + +**Old IP ranges to remove:** Please refer to the table below for a complete list of current IP ranges **that need to be removed after April 14, 2025**. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Region NameRegion LocationCurrent CIDR Block Range
us-east-1Washington, DC, USA44.202.178.0/24
44.202.180.0/23
44.210.68.0/24
44.210.110.0/25
us-east-2Columbus, OH, USA3.145.224.0/24
3.145.225.0/25
3.145.234.0/24
us-west-1San Francisco, CA, USA3.101.204.0/23
3.101.212.0/24
3.101.209.192/26
us-west-2Portland, OR, USA35.89.46.0/23
35.92.27.0/24
ap-southeast-2Sydney, AU3.26.252.0/24
3.26.245.128/25
3.27.51.0/25
eu-central-1Frankfurt, DE3.71.170.0/24
3.71.103.96/27
3.75.4.128/25
eu-west-1Dublin, IE3.251.231.0/24
3.251.230.64/26
3.252.47.0/25
eu-west-2London, England, UK13.40.201.0/24
13.40.208.0/25
13.41.206.128/25
13.41.206.64/26
+ +## Additional Support + +We understand that these changes may require some adjustments to your routine. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our [support team](https://support.newrelic.com/s/). \ No newline at end of file diff --git a/src/data/whats-new-ids.json b/src/data/whats-new-ids.json index 2c720ab7e1c..0b352607965 100644 --- a/src/data/whats-new-ids.json +++ b/src/data/whats-new-ids.json @@ -360,5 +360,6 @@ "/whats-new/2025/01/whats-new-01-17-cross-account-alerts": "43017", "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018", "/whats-new/2025/01/whats-new-01-22-React18-upgrade": "43019", - "/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020" + "/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020", + "/whats-new/2025/02/what-new-10-02-sessions-replay": "43021" } \ No newline at end of file diff --git a/src/i18n/content/jp/docs/data-apis/manage-data/view-system-limits.mdx b/src/i18n/content/jp/docs/data-apis/manage-data/view-system-limits.mdx index 575aa7427ac..4838290fbc3 100644 --- a/src/i18n/content/jp/docs/data-apis/manage-data/view-system-limits.mdx +++ b/src/i18n/content/jp/docs/data-apis/manage-data/view-system-limits.mdx @@ -69,7 +69,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース - カテゴリ + `category` @@ -79,7 +79,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース - limitName + `limitName` @@ -89,7 +89,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース - メッセージ + `message` diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx index a7ea3943f70..f8a41f6d23a 100644 --- a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx +++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx @@ -11,6 +11,8 @@ translationType: machine [AWS CloudWatch Metric Streams統合](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/)を有効にして、カスタムネームスペースを含むAWSサービスからのすべてのCloudWatchメトリクスをモニターします。個別の統合は、もはや推奨されるオプションではありません。 + + 現在、 AWS CloudWatchメトリクスはAWS Glue Spark ETL ジョブのみをサポートしています。 AWS Glue Python Shell ジョブはサポートされていません。 このサポートを含めるためのアクティブな機能リクエストが AWS Glue チームに送信されました。 New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレポートするための統合を提供しています。このドキュメントでは、この統合を有効にする方法と、レポート可能なデータについて説明します。 @@ -30,7 +32,7 @@ New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレ ## データを見つけて使用する [#find-data] -インテグレーションデータを検索するには、 **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**に移動してインテグレーションを選択してください。 +インテグレーションデータを検索するには、 **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**に移動してインテグレーションを選択してください。 次の[イベントタイプ](/docs/data-apis/understand-data/new-relic-data-types/#event-data)を使用して、[データのクエリと探索](/docs/using-new-relic/data/understand-data/query-new-relic-data)を行うことができます。 @@ -402,4 +404,4 @@ New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレ - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index a577c04952b..9c243e58e43 100644 --- a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -166,7 +166,7 @@ include 変数の制限: * **Query**: ドロップダウン メニューで使用されるオプションの動的なリストを返すクエリを作成できます。 たとえば、次のクエリは`country`値の動的なリストを返します。 ```sql - SELECT uniques(countryCode) FROM PageAction since 2 days ago + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago ``` クエリを作成する際の規則とヒントについては、「[クエリ型変数](#query-variable-rules)」を参照してください。 @@ -317,8 +317,8 @@ FROM PageAction SELECT uniques(countryCode) ``` ```sql - -- you can use the second param to define the maximum number of results to be listed. - From PageAction select uniques(countryCode, 10000) --> this will return up to 10k results +-- you can use the second param to define the maximum number of results to be listed. +FROM PageAction SELECT uniques(countryCode, 10000) --> this will return up to 10k results ``` [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset)の場合: @@ -484,7 +484,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago 次に、次のクエリを使用してウィジェットを作成します。 ```sql - SELECT percentile(duration,{{percentile}}) FROM PageAction + SELECT percentile(duration, {{percentile}}) FROM PageAction ``` Adding the widget for dynamically change the percentile @@ -494,7 +494,8 @@ FROM PageAction SELECT keyset() SINCE 1 day ago フィルタリングに変数を使用するには、次のように、作成した変数を`WHERE`句の右側に追加するだけです。 ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) ``` Use variables to filter diff --git a/src/i18n/content/kr/docs/data-apis/manage-data/view-system-limits.mdx b/src/i18n/content/kr/docs/data-apis/manage-data/view-system-limits.mdx index 8dfaa845a17..acbbb07a1b5 100644 --- a/src/i18n/content/kr/docs/data-apis/manage-data/view-system-limits.mdx +++ b/src/i18n/content/kr/docs/data-apis/manage-data/view-system-limits.mdx @@ -69,7 +69,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용 - 범주 + `category` @@ -79,7 +79,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용 - 제한 이름 + `limitName` @@ -89,7 +89,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용 - 메시지 + `message` diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx index a32fad7d4d0..ddd4c020a71 100644 --- a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx +++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx @@ -11,6 +11,8 @@ translationType: machine [AWS CloudWatch Metric Streams 통합](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) 을 활성화하여 사용자 지정 네임스페이스를 포함하여 AWS 서비스의 모든 CloudWatch 지표를 모니터링합니다. 개별 통합은 더 이상 권장되는 옵션이 아닙니다. + + 현재 AWS CloudWatch 지표는 AWS Glue Spark ETL 작업만 지원합니다. AWS Glue 웹 Shell 작업은 지원하지 않습니다. 이 지원을 포함하기 위해 AWS Glue 팀에 활성 기능 요청이 제출되었습니다. New Relic은 [AWS Glue](https://aws.amazon.com/glue/) 데이터 보고를 위한 통합을 제공합니다. 이 문서에서는 이 통합을 활성화하는 방법과 보고할 수 있는 데이터에 대해 설명합니다. @@ -30,7 +32,7 @@ AWS Glue 통합에 대한 기본 [폴링](/docs/infrastructure/amazon-integratio ## 데이터 찾기 및 사용 [#find-data] -통합 데이터를 찾으려면 **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** 으로 이동하여 통합을 선택하세요. +통합 데이터를 찾으려면 **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** 으로 이동하여 통합을 선택하세요. 다음 [이벤트 유형](/docs/data-apis/understand-data/new-relic-data-types/#event-data) 을 사용 [하여 데이터를 쿼리하고 탐색할](/docs/using-new-relic/data/understand-data/query-new-relic-data) 수 있습니다. @@ -402,4 +404,4 @@ AWS Glue 통합에 대한 기본 [폴링](/docs/infrastructure/amazon-integratio - + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 8d5331c08c9..48ce0ff357d 100644 --- a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -166,7 +166,7 @@ WHERE true AND appName = 'Test App' FACET countryCode * **Query**: 드롭다운 메뉴에 사용되는 옵션의 동적 목록을 반환하는 쿼리를 작성할 수 있습니다. 예를 들어 다음 쿼리는 `country` 값의 동적 목록을 반환합니다. ```sql - SELECT uniques(countryCode) FROM PageAction since 2 days ago + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago ``` 쿼리 작성에 대한 규칙 및 팁은 [쿼리 유형 변수](#query-variable-rules) 를 참조하십시오. @@ -317,8 +317,8 @@ FROM PageAction SELECT uniques(countryCode) ``` ```sql - -- you can use the second param to define the maximum number of results to be listed. - From PageAction select uniques(countryCode, 10000) --> this will return up to 10k results +-- you can use the second param to define the maximum number of results to be listed. +FROM PageAction SELECT uniques(countryCode, 10000) --> this will return up to 10k results ``` [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset) 사용: @@ -484,7 +484,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. ```sql - SELECT percentile(duration,{{percentile}}) FROM PageAction + SELECT percentile(duration, {{percentile}}) FROM PageAction ``` Adding the widget for dynamically change the percentile @@ -494,7 +494,8 @@ FROM PageAction SELECT keyset() SINCE 1 day ago 필터링에 변수를 사용하려면 다음과 같이 `WHERE` 절의 오른쪽에 생성된 변수를 추가하기만 하면 됩니다. ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) ``` Use variables to filter diff --git a/src/i18n/content/pt/docs/data-apis/manage-data/view-system-limits.mdx b/src/i18n/content/pt/docs/data-apis/manage-data/view-system-limits.mdx index 6712c210479..4ea52cc021b 100644 --- a/src/i18n/content/pt/docs/data-apis/manage-data/view-system-limits.mdx +++ b/src/i18n/content/pt/docs/data-apis/manage-data/view-system-limits.mdx @@ -69,7 +69,7 @@ Para cada incidente importante de limite, a New Relic cria um [evento`NrIntegrat - categoria + `category` @@ -79,7 +79,7 @@ Para cada incidente importante de limite, a New Relic cria um [evento`NrIntegrat - limitName + `limitName` @@ -89,7 +89,7 @@ Para cada incidente importante de limite, a New Relic cria um [evento`NrIntegrat - mensagem + `message` diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx index 1a8a5884826..84c81872fe9 100644 --- a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx +++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-glue-monitoring-integration.mdx @@ -11,6 +11,8 @@ translationType: machine Habilite a [integração do AWS CloudWatch Metric Streams ](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/)para monitor todas as métricas do CloudWatch de seus serviços da AWS, incluindo namespace personalizado. A integração individual não é mais nossa opção recomendada. + + Atualmente, as métricas AWS do CloudWatch oferecem suporte apenas a trabalhos ETL AWS Glue Spark. Eles não oferecem suporte a trabalhos do AWS Glue Python Shell. Uma solicitação de recurso ativa foi enviada à equipe do AWS Glue para incluir esse suporte. A New Relic oferece uma integração para relatar seus dados [do AWS Glue](https://aws.amazon.com/glue/) . Este documento explica como ativar esta integração e descreve os dados que podem ser reportados. @@ -30,7 +32,7 @@ Informações [de pesquisa](/docs/infrastructure/amazon-integrations/aws-integra ## Encontre e use dados [#find-data] -Para encontrar seus dados de integração, acesse **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** e selecione uma integração. +Para encontrar seus dados de integração, acesse **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** e selecione uma integração. Você pode [consultar e explorar seus dados](/docs/using-new-relic/data/understand-data/query-new-relic-data) usando o seguinte [tipo de evento](/docs/data-apis/understand-data/new-relic-data-types/#event-data): @@ -402,4 +404,4 @@ Essa integração coleta dados do AWS Glue para o trabalho. - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 0d942862da2..64bff5328e2 100644 --- a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -166,7 +166,7 @@ A criação de uma variável de modelo consiste em duas etapas. * **Query**: você pode escrever uma consulta que retornará uma lista dinâmica de opções usadas no menu dropdown . Por exemplo, a consulta a seguir retornaria uma lista dinâmica de valores `country` : ```sql - SELECT uniques(countryCode) FROM PageAction since 2 days ago + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago ``` Para regras e dicas sobre como escrever consultas, consulte [variáveis do tipo consulta](#query-variable-rules). @@ -317,8 +317,8 @@ FROM PageAction SELECT uniques(countryCode) ``` ```sql - -- you can use the second param to define the maximum number of results to be listed. - From PageAction select uniques(countryCode, 10000) --> this will return up to 10k results +-- you can use the second param to define the maximum number of results to be listed. +FROM PageAction SELECT uniques(countryCode, 10000) --> this will return up to 10k results ``` Com [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset): @@ -484,7 +484,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Então você criaria um widget com a seguinte consulta: ```sql - SELECT percentile(duration,{{percentile}}) FROM PageAction + SELECT percentile(duration, {{percentile}}) FROM PageAction ``` Adding the widget for dynamically change the percentile @@ -494,7 +494,8 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Para usar variáveis para filtragem você só precisa adicionar a variável criada no lado direito de uma cláusula `WHERE` , assim: ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) ``` Use variables to filter