From d8309f458acbe479b2c293cfba8b01a1bf5d29bb Mon Sep 17 00:00:00 2001 From: ndesai Date: Mon, 12 Aug 2024 15:51:32 -0500 Subject: [PATCH 01/18] docs:adding mobile logs syntax and example for all native and hybrid platforms --- .../mobile-monitoring-ui/mobile-logs.mdx | 715 +++++++++++++++++- 1 file changed, 682 insertions(+), 33 deletions(-) diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index 00175de3f5b..12a70f01d4b 100644 --- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -12,21 +12,287 @@ You can use our APIs to send your mobile apps logs to New Relic. Your logs will ## APIs to capture logs [#logs-apis] -APIs are available for iOS and Android. +APIs are available for iOS and Android. Note that there may be some mobile logging delays: - * It will take up to 15 minutes for logs to appear in New Relics **Logs** tab. + * It will take up to 15 minutes for logs to appear in New Relics **Logs** tab. * It will take up to 15 minutes for changes to mobile logs toggle, sampling rate, and log level to be reflected within your mobile application. +## Enable mobile logs [#enable-mobile-logs] + +By default, our mobile agent doesn't collect logs. To enable mobile logs: + +1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities)**. +2. Click **Mobile**. +3. Click on your mobile app. +4. In the left pane under **Settings**, click **Application**. +5. Toggle **Mobile Logs** on. +6. Click **Save**. + +## Configure your logs [#configure-mobile-logs] + +To configure your mobile logs sampling rate or log level: + +1. In New Relic, navigate to your mobile app. +2. In the left pane under **Settings**, click **Application**. +3. To change the sample rate, select a new value in the field under **Sample rate of total sessions**. +4. To change the log level, select your preferred log level in the dropdown under **Logs verbosity**. The debug log level should only be used if you want to see agent debugging logs. + +## View logs in New Relic [#view-logs-in-new-relic] + +To view your logs, continue in the New Relic UI: + +1. Navigate to your mobile app. +2. In the left pane under **Triage**, click **Logs**. + Keep in mind that when you use the logging APIs, you should only use the debug log level if you want to see agent debugging logs. -### iOS agent [#ios-agent-apis] + + + + Android + + + iOS + + + Capacitor + + + Cordova + + + .NET MAUI + + + Flutter + + + React Native + + + Xamarin + + + Unreal + + + + + +## Syntax [#syntax] + +## Description [#description] + +Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + + +### Java [#java] + +```java -To use the logging APIs add the following: +NewRelic.logInfo(String message) + +NewRelic.logWarning(String message) + +NewRelic.logDebug(String message) + +NewRelic.logVerbose(String message) + +NewRelic.logError(String message) + +NewRelic.log(LogLevel logLevel, String message) + +NewRelic.logThrowable(LogLevel logLevel, String message, Throwable throwable) + +NewRelic.logAttributes(Map attributes) + +NewRelic.logAll(Throwable throwable, Map attributes) ``` + +### Kotlin [#kotlin] + +```kotlin + +NewRelic.logInfo(String message) + +NewRelic.logWarning(String message) + +NewRelic.logDebug(String message) + +NewRelic.logVerbose(String message) + +NewRelic.logError(String message) + +NewRelic.log(LogLevel logLevel, String message) + +NewRelic.logThrowable(LogLevel logLevel, String message, Throwable throwable) + +NewRelic.logAttributes(Map attributes) + +NewRelic.logAll(Throwable throwable, Map attributes) + +``` + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + +### Java [#java] + +```java + + NewRelic.logInfo("This is an info message"); + + // Log warning + NewRelic.logWarning("This is a warning message"); + + // Log debug + NewRelic.logDebug("This is a debug message"); + + // Log verbose + NewRelic.logVerbose("This is a verbose message"); + + // Log error + NewRelic.logError("This is an error message"); + + // Log with specific log level + NewRelic.log(LogLevel.INFO, "This is a log message with INFO level"); + + // Log throwable with specific log level + try { + throw new Exception("This is a test exception"); + } catch (Exception e) { + NewRelic.logThrowable(LogLevel.ERROR, "Exception occurred", e); + } + + // Log attributes + Map attributes = new HashMap<>(); + attributes.put("key1", "value1"); + attributes.put("key2", 123); + NewRelic.logAttributes(attributes); + + // Log all with throwable and attributes + try { + throw new Exception("This is another test exception"); + } catch (Exception e) { + NewRelic.logAll(e, attributes); + } + +``` + +### Kotlin [#kotlin] + +```kotlin + + NewRelic.logInfo("This is an info message") + + // Log warning + NewRelic.logWarning("This is a warning message") + + // Log debug + NewRelic.logDebug("This is a debug message") + + // Log verbose + NewRelic.logVerbose("This is a verbose message") + + // Log error + NewRelic.logError("This is an error message") + + // Log with specific log level + NewRelic.log(LogLevel.INFO, "This is a log message with INFO level") + + // Log throwable with specific log level + try { + throw Exception("This is a test exception") + } catch (e: Exception) { + NewRelic.logThrowable(LogLevel.ERROR, "Exception occurred", e) + } + + // Log attributes + val attributes = mapOf("key1" to "value1", "key2" to 123) + NewRelic.logAttributes(attributes) +``` + + + + +## Syntax [#syntax] + +### Objective-c + +```objectivec + (void) logInfo:(NSString* __nonnull) message; + (void) logError:(NSString* __nonnull) message; + (void) logVerbose:(NSString* __nonnull) message; + (void) logWarning:(NSString* __nonnull) message; + (void) logAudit:(NSString* __nonnull) message; + (void) logDebug:(NSString* __nonnull) message; + (void) log:(NSString* __nonnull) message level:(NRLogLevels)level; + (void) logAll:(NSDictionary* __nonnull) dict; + (void) logAttributes:(NSDictionary* __nonnull) dict; + (void) logErrorObject:(NSError* __nonnull) error; + +``` + +### Swift [#swift] + +```swift +func logInfo(_ message: String) +func logError(_ message: String) +func logVerbose(_ message: String) +func logWarning(_ message: String) +func logAudit(_ message: String) +func logDebug(_ message: String) +func log(_ message: String, level: NRLogLevels) +func logAll(_ dict: [String: Any]) +func logAttributes(_ dict: [String: Any]) +func logErrorObject(_ error: NSError) +``` + + +## Description [#description] + +This API Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + +```objectivec + + [NewRelic logInfo:@"This is an info message"]; + + [NewRelic logError:@"This is an error message"]; + + [NewRelic logVerbose:@"This is a verbose message"]; + + [NewRelic logWarning:@"This is a warning message"]; + + [NewRelic logAudit:@"This is an audit message"]; + + [NewRelic logDebug:@"This is a debug message"]; + + [NewRelic log:@"This is a custom log level message" level:NRLogLevelsCustom]; + + NSDictionary *logDict = @{@"key1": @"value1", @"key2": @"value2"}; + [NewRelic logAll:logDict]; + + NSDictionary *attributesDict = @{@"attribute1": @"value1", @"attribute2": @"value2"}; + [NewRelic logAttributes:attributesDict]; + + NSError *error = [NSError errorWithDomain:@"com.example" code:100 userInfo:@{NSLocalizedDescriptionKey: @"This is an error description"}]; + [NewRelic logErrorObject:error]; + +``` + +```swift NewRelic.logError("Encountered error=error=\(error.localizedDescription).") NewRelic.logWarning("Warning text.") @@ -56,53 +322,436 @@ NewRelic.logAttributes([ ]) ``` -### Android agent [#android-agent-apis] + + +## Syntax [#syntax] + +### Typescript [#typescript] + +```js +NewRelicCapacitorPlugin.logInfo(options: { message: string}) => void + +NewRelicCapacitorPlugin.logVerbose(options: { message: string}) => void + +NewRelicCapacitorPlugin.logError(options: { message: string}) => void -To use the logging APIs add the following: +NewRelicCapacitorPlugin.logWarn(options: { message: string}) => void +NewRelicCapacitorPlugin.logDebug(options: { message: string}) => void + +NewRelicCapacitorPlugin.logAll(options: { error: string; attributes: object; }): void + +NewRelicCapacitorPlugin.logAttributes(options: { attributes: object; }): void ``` -NewRelic.logInfo(String message) -NewRelic.logWarning(String message) -NewRelic.logDebug(String message) +## Description [#description] -NewRelic.logVerbose(String message) +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. -NewRelic.logError(String message) -NewRelic.log(LogLevel logLevel, String message) +## Examples [#examples] -NewRelic.logThrowable(LogLevel logLevel, String message, Throwable throwable) +Here's an example of adding some HTTP header fields: -NewRelic.logAttributes(Map attributes) +### Typescript [#typescript] + +```ts + NewRelicCapacitorPlugin.logInfo( + {message: "User profile loaded successfully"}); + + NewRelicCapacitorPlugin.logVerbose({message:"Verbose logging example"}); + + NewRelicCapacitorPlugin.logError({message:"Error loading user profile"}); + + NewRelicCapacitorPlugin.logWarn({message: "Low disk space warning"}); + + NewRelicCapacitorPlugin.logDebug({message:"Debugging session started"}); + +NewRelicCapacitorPlugin.logAll({ + error: "UnexpectedError", + attributes: { "errorCode": "500", "errorMessage": "Internal Server Error" ,level:"WARN"} +}); + +NewRelicCapacitorPlugin.logAttributes({attributes:{ + "userID": 12345, + "sessionID": "abcde12345", + "isLoggedIn": true, + "message":"this is test", + "level":"INFO" +}}); -NewRelic.logAll(Throwable throwable, Map attributes) ``` + -## Enable mobile logs [#enable-mobile-logs] + +## Syntax [#syntax] -By default, our mobile agent doesn't collect logs. To enable mobile logs: +### Javascript [#javascript] -1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities)**. -2. Click **Mobile**. -3. Click on your mobile app. -4. In the left pane under **Settings**, click **Application**. -5. Toggle **Mobile Logs** on. -6. Click **Save**. +```js +NewRelic.logInfo(message: string): void; -## Configure your logs [#configure-mobile-logs] +NewRelic.logDebug(message: string): void; -To configure your mobile logs sampling rate or log level: +NewRelic.logVerbose(message: string): void; -1. In New Relic, navigate to your mobile app. -2. In the left pane under **Settings**, click **Application**. -3. To change the sample rate, select a new value in the field under **Sample rate of total sessions**. -4. To change the log level, select your preferred log level in the dropdown under **Logs verbosity**. The debug log level should only be used if you want to see agent debugging logs. +NewRelic.logWarn(message: string): void; -## View logs in New Relic [#view-logs-in-new-relic] +NewRelic.logError(message: string): void; + +NewRelic.log(level: string, message: string): void; + +NewRelic.logAttributes(attributes: {[key: string]: boolean | number | string}): void; + +``` + + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + +### Javascript [#javascript] + +```js + + NewRelic.logInfo("User logged in successfully"); + + NewRelic.logDebug("Debug message"); + + NewRelic.logVerbose("Verbose message detailing step-by-step execution"); + + NewRelic.logWarn("Warning message indicating a potential issue"); + + NewRelic.logError("Error message indicating a failure"); + + NewRelic.log("INFO", "User logged in successfully"); + + NewRelic.logAttributes({ + "userID": 12345, + "sessionID": "abcde12345", + "isLoggedIn": true, + "message":"this is test", + "level":"INFO" +}); +``` + + + +## Syntax [#syntax] + +```csharp +CrossNewRelic.Current.LogInfo(String message) : void + +CrossNewRelic.Current.LogError(String message) : void + +CrossNewRelic.Current.LogVerbose(String message) : void + +CrossNewRelic.Current.LogWarning(String message) : void + +CrossNewRelic.Current.LogDebug(String message) : void + +CrossNewRelic.Current.Log(LogLevel level, String message) : void + +CrossNewRelic.Current.LogAttributes(Dictionary attributes) : void + +``` + + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + +```csharp + + CrossNewRelic.Current.LogInfo("This is an informational message"); + + CrossNewRelic.Current.LogError("This is an error message"); + + CrossNewRelic.Current.LogVerbose("This is a verbose message"); + + CrossNewRelic.Current.LogWarning("This is a warning message"); + + CrossNewRelic.Current.LogDebug("This is a debug message"); + + CrossNewRelic.Current.Log(LogLevel.Info, "This is an informational message"); + + CrossNewRelic.Current.LogAttributes(new Dictionary() + { + {"BreadNumValue", 12.3 }, + {"BreadStrValue", "MAUIBread" }, + {"BreadBoolValue", true }, + {"message", "This is a message with attributes" } + } + ); + +``` + + + + +## Syntax [#syntax] + + +```dart +NewrelicMobile.instance.logInfo(String message) : void + +NewrelicMobile.instance.logError(String message) : void + +NewrelicMobile.instance.logVerbose(String message) : void + +NewrelicMobile.instance.logWarning(String message) : void + +NewrelicMobile.instance.logDebug(String message) : void + +NewrelicMobile.instance.log(LogLevel level, String message) : void + +NewrelicMobile.instance.logAll(Exception exception,Map? attributes) : void + +NewrelicMobile.instance.logAttributes(Dictionary attributes) : void + +``` + + + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + + + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + + +```dart + NewrelicMobile.instance.logInfo("This is an informational message"); + + NewrelicMobile.instance.logError("This is an error message"); + + NewrelicMobile.instance.logVerbose("This is a verbose message"); + + NewrelicMobile.instance.logWarning("This is a warning message"); + + NewrelicMobile.instance.logDebug("This is a debug message"); + + NewrelicMobile.instance.log(LogLevel.Info, "This is an informational message"); + + NewrelicMobile.instance.logAll(Exception("This is an exception"), + {"BreadNumValue": 12.3 , + "BreadStrValue": "FlutterBread", + "BreadBoolValue": true , + "message": "This is a message with attributes" } + ); + + NewrelicMobile.instance.logAttributes( + {"BreadNumValue": 12.3 , + "BreadStrValue": "FlutterBread", + "BreadBoolValue": true , + "message": "This is a message with attributes" } + ); + +``` + + + + +## Syntax [#syntax] + +```js +NewRelic.logInfo(String message) : void + +NewRelic.logError(String message) : void + +NewRelic.logVerbose(String message) : void + +NewRelic.logWarning(String message) : void + +NewRelic.logDebug(String message) : void + +NewRelic.log(LogLevel level, String message) : void + +NewRelic.logAll(Error error,attributes?: {[key: string]: any}) : void + +NewRelic.logAttributes(attributes?: {[key: string]: any}) : void + +``` + + + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + + +```js + NewRelic.logInfo(); + + NewRelic.logError("This is an error message"); + + NewRelic.logVerbose("This is a verbose message"); + + NewRelic.logWarning("This is a warning message"); + + NewRelic.logDebug("This is a debug message"); + + NewRelic.log(LogLevel.INFO, "This is an informational message"); + + Newrelic.logAll(new Error("This is an exception"), + {"BreadNumValue": 12.3 , + "BreadStrValue": "FlutterBread", + "BreadBoolValue": true , + "message": "This is a message with attributes" } + ); + + + Newrelic.logAttributes( + {"BreadNumValue": 12.3 , + "BreadStrValue": "FlutterBread", + "BreadBoolValue": true , + "message": "This is a message with attributes", + level:newRelic.LogLevel.INFO }); +``` + + + + +## Syntax [#syntax] + +```csharp +CrossNewRelicClient.Current.LogInfo(String message) : void + +CrossNewRelicClient.Current.LogError(String message) : void + +CrossNewRelicClient.Current.LogVerbose(String message) : void + +CrossNewRelicClient.Current.LogWarning(String message) : void + +CrossNewRelicClient.Current.LogDebug(String message) : void + +CrossNewRelicClient.Current.Log(LogLevel level, String message) : void + +CrossNewRelicClient.Current.LogAttributes(Dictionary attributes) : void +``` + + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + + +## Examples [#examples] + +Here's an example of adding some HTTP header fields: + +## Example [#example] + +```csharp + + CrossNewRelicClient.Current.LogInfo("This is an informational message"); + + CrossNewRelicClient.Current.LogError("This is an error message"); + + CrossNewRelicClient.Current.LogVerbose("This is a verbose message"); + + CrossNewRelicClient.Current.LogWarning("This is a warning message"); + + CrossNewRelicClient.Current.LogDebug("This is a debug message"); + + CrossNewRelicClient.Current.Log(LogLevel.Info, "This is an informational message"); + + CrossNewRelicClient.Current.LogAttributes(new Dictionary() + { + {"BreadNumValue", 12.3 }, + {"BreadStrValue", "XamBread" }, + {"BreadBoolValue", true }, + {"message", "This is a message with attributes" } + } + ); + +``` + + + + + + ## Syntax [#syntax] + +```c +UNewRelicBPLibrary::logInfo(FString message) : void + +UNewRelicBPLibrary::logError(FString message) : void + +UNewRelicBPLibrary::logVerbose(FString message) : void + +UNewRelicBPLibrary::logWarning(FString message) : void + +UNewRelicBPLibrary::logDebug(FString message) : void + +UNewRelicBPLibrary::log(AgentLogLevel level, FString message) : void + +UNewRelicBPLibrary::logAttributes(TMap attributes) : void + +``` + +## Description [#description] + +This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + + +## Example [#example] + +```c + + #include "NewRelicBPLibrary.h" + + UNewRelicBPLibrary::logInfo("This is an informational message"); + + UNewRelicBPLibrary::logError("This is an error message"); + + UNewRelicBPLibrary::logVerbose("This is a verbose message"); + + UNewRelicBPLibrary::logDebug("This is a debug message"); + + UNewRelicBPLibrary::logWarning("This is a warning message"); + + UNewRelicBPLibrary::log(AgentLogLevel::Debug, "This is a debug message"); + + TMap attributes; + attributes.Add("place", TEXT("Robots")); + attributes.Add("user", TEXT("user1")); + attributes.Add("level", TEXT("DEBUG")); + attributes.Add("message", TEXT("This is a debug message")); + + UNewRelicBPLibrary::logAttributes(attributes); + + + +``` + + + -To view your logs, continue in the New Relic UI: -1. Navigate to your mobile app. -2. In the left pane under **Triage**, click **Logs**. \ No newline at end of file From 539fc368ff8e7be409295b86b351fba729f886ea Mon Sep 17 00:00:00 2001 From: ndesai Date: Mon, 12 Aug 2024 16:06:21 -0500 Subject: [PATCH 02/18] docs:sentry incompability for android --- .../sentry-incompatibility-android.mdx | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx new file mode 100644 index 00000000000..02179deed17 --- /dev/null +++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx @@ -0,0 +1,28 @@ +--- +title: Sentry incompatibility (Android) +type: troubleshooting +tags: + - Mobile monitoring + - New Relic Mobile Android + - Troubleshoot +metaDescription: 'New Relic Android agent Log instrumentation cannot coexist with Sentry Android' +freshnessValidatedDate: never +--- + +## Problem + +Conflicts, crashes, or errors will show when both the New Relic Android agent and Sentry's [Sentry Monitoring SDK](https://docs.sentry.io/platforms/android/) are included within an app. + +Known errors: + - `java.lang.StackOverflowError` + +## Solution + +Our Android agent Should not Instrument Sentry Android SDK. you can avoid it using this configuration + +newrelic { +// Don't instrument sample classes +excludePackageInstrumentation("io.sentry.*") +} + +If you need additional help, get support at [support.newrelic.com](https://support.newrelic.com). From 9e5b29fa2460684807845a888011815e69dec354 Mon Sep 17 00:00:00 2001 From: ndesai Date: Tue, 13 Aug 2024 09:45:29 -0500 Subject: [PATCH 03/18] Update Mobile docs document --- .idea/other.xml | 252 ++++++++++++++++++ .../mobile-monitoring-ui/mobile-logs.mdx | 24 +- src/nav/mobile-monitoring.yml | 4 +- 3 files changed, 267 insertions(+), 13 deletions(-) create mode 100644 .idea/other.xml diff --git a/.idea/other.xml b/.idea/other.xml new file mode 100644 index 00000000000..4604c44601d --- /dev/null +++ b/.idea/other.xml @@ -0,0 +1,252 @@ + + + + + + \ No newline at end of file diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index 12a70f01d4b..58eaff4ab69 100644 --- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -84,10 +84,6 @@ Keep in mind that when you use the logging APIs, you should only use the debug l ## Syntax [#syntax] -## Description [#description] - -Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - ### Java [#java] @@ -138,10 +134,14 @@ NewRelic.logAll(Throwable throwable, Map attributes) ``` +## Description [#description] + +Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ### Java [#java] @@ -263,7 +263,7 @@ This API Provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ```objectivec @@ -352,7 +352,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ### Typescript [#typescript] @@ -416,7 +416,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ### Javascript [#javascript] @@ -472,7 +472,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ```csharp @@ -536,7 +536,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ```dart @@ -602,7 +602,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ```js @@ -664,7 +664,7 @@ This API provides a comprehensive set of logging methods to capture various type ## Examples [#examples] -Here's an example of adding some HTTP header fields: +Here's an example of Logging: ## Example [#example] diff --git a/src/nav/mobile-monitoring.yml b/src/nav/mobile-monitoring.yml index c1f3ab1a3c7..136b0fbe6ae 100644 --- a/src/nav/mobile-monitoring.yml +++ b/src/nav/mobile-monitoring.yml @@ -45,6 +45,8 @@ pages: path: /docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/event-limits-sampling - title: Firebase incompatibility path: /docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/firebase-incompatibility-android + - title: Sentry incompatibility + path: /docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android - title: iOS pages: - title: Install and get started @@ -121,7 +123,7 @@ pages: - title: Summary page path: /docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/summary-page - title: Logs page - path: /docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs + path: /docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs - title: Interactions page path: /docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page - title: Devices page From 293b1187836e79e1c65a951602921835a3580c2d Mon Sep 17 00:00:00 2001 From: Chris <49290076+wildcardlinux@users.noreply.github.com> Date: Wed, 21 Aug 2024 13:48:26 -0500 Subject: [PATCH 04/18] Update use-nerdgraph-manage-license-keys-user-keys.mdx The INGEST_KEY_ID needs to be in double quotes to work correctly. Confirmed this syntax myself today. --- .../examples/use-nerdgraph-manage-license-keys-user-keys.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx b/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx index e68d09adaa2..545460da8bb 100644 --- a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx +++ b/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx @@ -172,7 +172,7 @@ Single key example query: query { actor { apiAccess { - key(id: INGEST_KEY_ID, keyType: INGEST) { + key(id: "INGEST_KEY_ID", keyType: INGEST) { key name type From 5c55f745fd29cda66ec3614007fda08fa950968d Mon Sep 17 00:00:00 2001 From: Niju George <62609604+nijugeorge173@users.noreply.github.com> Date: Thu, 22 Aug 2024 09:51:52 +0100 Subject: [PATCH 05/18] Update unix-monitoring-integration.mdx Mention the attributes that can be obfuscated --- .../host-integrations-list/unix-monitoring-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx index 399d0b5fe34..65838ddacc2 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx @@ -151,7 +151,7 @@ If using a proxy, the optional `proxy` object should be added to the `global` ob ## Credential obfuscation -For additional security, this integration supports obfuscated values for any attribute. To do so, append `_obfuscated` to the attribute name and provide an obfuscated value that was produced by the [New Relic CLI](https://github.com/newrelic/newrelic-cli): +For additional security, this integration supports obfuscated values for the attributes like insights_insert_key, proxy_username, proxy_password and any other attributes under the parent attribute 'agents'. To do so, append `_obfuscated` to the attribute name and provide an obfuscated value that was produced by the [New Relic CLI](https://github.com/newrelic/newrelic-cli): 1. Install the [New Relic CLI](https://github.com/newrelic/newrelic-cli#installation) on any supported platform. It doesn't need to be installed on the same host as the Unix integration. It is only used to generate the obfuscated keys, this integration handles deobfuscation independently. From d65b2c13c7c94d3c357b320a0456a54d719c2770 Mon Sep 17 00:00:00 2001 From: Ruben Ruiz de Gauna Date: Thu, 22 Aug 2024 11:33:22 +0200 Subject: [PATCH 06/18] infra agent: RH 7 minimum support 7.9 --- .../get-started/requirements-infrastructure-agent.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent.mdx b/src/content/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent.mdx index e922ac069cb..3e421565cce 100644 --- a/src/content/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent.mdx +++ b/src/content/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent.mdx @@ -102,7 +102,7 @@ The infrastructure agent supports these operating systems up to their manufactur - Version 7 or higher + Version 7.9 or higher @@ -112,7 +112,7 @@ The infrastructure agent supports these operating systems up to their manufactur - Version 7 or higher + Version 7.9 or higher From 6b7448eab80568f99c77a00603510b73d26f2574 Mon Sep 17 00:00:00 2001 From: newrelic-ruby-agent-bot Date: Thu, 22 Aug 2024 18:21:32 +0000 Subject: [PATCH 07/18] chore(ruby agent): Update config docs --- .../ruby-agent-configuration.mdx | 4651 +++++------------ 1 file changed, 1272 insertions(+), 3379 deletions(-) diff --git a/src/content/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration.mdx b/src/content/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration.mdx index fa1ec85129b..40ac596085a 100644 --- a/src/content/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration.mdx +++ b/src/content/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never This file is automatically generated from values defined in `lib/new_relic/agent/configuration/default_source.rb`. Make all changes directly to `default_source.rb.` - Submit PRs or raise issues at: [https://github.com/newrelic/newrelic-ruby-agent](https://github.com/newrelic/newrelic-ruby-agent) + Submit PRs or raise issues at: https://github.com/newrelic/newrelic-ruby-agent You can configure the New Relic Ruby agent with settings in a configuration file, environment variables, or programmatically with server-side configuration. This document summarizes the configuration options available for the Ruby agent. @@ -92,763 +92,417 @@ To update `newrelic.yml` file after a new release, use the template in the base Updating the gem does not automatically update `config/newrelic.yml`. + ## General [#general] These settings are available for agent configuration. Some settings depend on your New Relic subscription level. - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_AGENT_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_AGENT_ENABLED`
- If `true`, allows the Ruby agent to run. + If `true`, allows the Ruby agent to run. - + - - - - - - - - - - - + + +
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_APP_NAME`
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_APP_NAME`
- Specify the [application name](/docs/apm/new-relic-apm/installation-configuration/name-your-application) used to aggregate data in the New Relic UI. To report data to [multiple apps at the same time](/docs/apm/new-relic-apm/installation-configuration/using-multiple-names-app), specify a list of names separated by a semicolon `;`. For example, `MyApp` or `MyStagingApp;Instance1`. + Specify the [application name](/docs/apm/new-relic-apm/installation-configuration/name-your-application) used to aggregate data in the New Relic UI. To report data to [multiple apps at the same time](/docs/apm/new-relic-apm/installation-configuration/using-multiple-names-app), specify a list of names separated by a semicolon `;`. For example, `MyApp` or `MyStagingApp;Instance1`. - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_LICENSE_KEY`
TypeString
Default`""`
Environ variable`NEW_RELIC_LICENSE_KEY`
- Your New Relic . + Your New Relic . - + - - - - - - - - - - - + + +
TypeString
Default`"info"`
Environ variable`NEW_RELIC_LOG_LEVEL`
TypeString
Default`"info"`
Environ variable`NEW_RELIC_LOG_LEVEL`
- Sets the level of detail of log messages. Possible log levels, in increasing verbosity, are: `error`, `warn`, `info` or `debug`. + Sets the level of detail of log messages. Possible log levels, in increasing verbosity, are: `error`, `warn`, `info` or `debug`. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ACTIVE_SUPPORT_CUSTOM_EVENTS_NAMES`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ACTIVE_SUPPORT_CUSTOM_EVENTS_NAMES`
- An array of ActiveSupport custom event names to subscribe to and instrument. For example, + An array of ActiveSupport custom event names to subscribe to and instrument. For example, + - one.custom.event + - another.event + - a.third.event - * one.custom.event - * another.event - * a.third.event - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_API_KEY`
TypeString
Default`""`
Environ variable`NEW_RELIC_API_KEY`
- Your New Relic . Required when using the New Relic REST API v2 to record deployments using the `newrelic deployments` command. + Your New Relic . Required when using the New Relic REST API v2 to record deployments using the `newrelic deployments` command. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_BACKPORT_FAST_ACTIVE_RECORD_CONNECTION_LOOKUP`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_BACKPORT_FAST_ACTIVE_RECORD_CONNECTION_LOOKUP`
- Backports the faster ActiveRecord connection lookup introduced in Rails 6, which improves agent performance when instrumenting ActiveRecord. Note that this setting may not be compatible with other gems that patch ActiveRecord. + Backports the faster ActiveRecord connection lookup introduced in Rails 6, which improves agent performance when instrumenting ActiveRecord. Note that this setting may not be compatible with other gems that patch ActiveRecord. - + - - - - - - - - - - - + + +
TypeString
Default`nil`
Environ variable`NEW_RELIC_CA_BUNDLE_PATH`
TypeString
Default`nil`
Environ variable`NEW_RELIC_CA_BUNDLE_PATH`
- Manual override for the path to your local CA bundle. This CA bundle will be used to validate the SSL certificate presented by New Relic's data collection service. + Manual override for the path to your local CA bundle. This CA bundle will be used to validate the SSL certificate presented by New Relic's data collection service. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CAPTURE_MEMCACHE_KEYS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CAPTURE_MEMCACHE_KEYS`
- Enable or disable the capture of memcache keys from transaction traces. + Enable or disable the capture of memcache keys from transaction traces. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CAPTURE_PARAMS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CAPTURE_PARAMS`
- When `true`, the agent captures HTTP request parameters and attaches them to transaction traces, traced errors, and [`TransactionError` events](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8241). + When `true`, the agent captures HTTP request parameters and attaches them to transaction traces, traced errors, and [`TransactionError` events](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8241). When using the `capture_params` setting, the Ruby agent will not attempt to filter secret information. `Recommendation:` To filter secret information from request parameters, use the [`attributes.include` setting](/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby) instead. For more information, see the Ruby attribute examples. + - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CLEAR_TRANSACTION_STATE_AFTER_FORK`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CLEAR_TRANSACTION_STATE_AFTER_FORK`
- If `true`, the agent will clear `Tracer::State` in `Agent.drop_buffered_data`. + If `true`, the agent will clear `Tracer::State` in `Agent.drop_buffered_data`. - + - - - - - - - - - - - + + +
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_CONFIG_PATH`
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_CONFIG_PATH`
- Path to `newrelic.yml`. If undefined, the agent checks the following directories (in order): - + Path to `newrelic.yml`. If undefined, the agent checks the following directories (in order): * `config/newrelic.yml` * `newrelic.yml` * `$HOME/.newrelic/newrelic.yml` * `$HOME/newrelic.yml` + - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_EXCLUDE_NEWRELIC_HEADER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_EXCLUDE_NEWRELIC_HEADER`
- Allows newrelic distributed tracing headers to be suppressed on outbound requests. + Allows newrelic distributed tracing headers to be suppressed on outbound requests. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_FORCE_INSTALL_EXIT_HANDLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_FORCE_INSTALL_EXIT_HANDLER`
- The exit handler that sends all cached data to the collector before shutting down is forcibly installed. This is true even when it detects scenarios where it generally should not be. The known use case for this option is when Sinatra runs as an embedded service within another framework. The agent detects the Sinatra app and skips the `at_exit` handler as a result. Sinatra classically runs the entire application in an `at_exit` block and would otherwise misbehave if the agent's `at_exit` handler was also installed in those circumstances. Note: `send_data_on_exit` should also be set to `true` in tandem with this setting. + The exit handler that sends all cached data to the collector before shutting down is forcibly installed. This is true even when it detects scenarios where it generally should not be. The known use case for this option is when Sinatra runs as an embedded service within another framework. The agent detects the Sinatra app and skips the `at_exit` handler as a result. Sinatra classically runs the entire application in an `at_exit` block and would otherwise misbehave if the agent's `at_exit` handler was also installed in those circumstances. Note: `send_data_on_exit` should also be set to `true` in tandem with this setting. + - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_HIGH_SECURITY`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_HIGH_SECURITY`
- If `true`, enables [high security mode](/docs/accounts-partnerships/accounts/security/high-security). Ensure you understand the implications of high security mode before enabling this setting. + If `true`, enables [high security mode](/docs/accounts-partnerships/accounts/security/high-security). Ensure you understand the implications of high security mode before enabling this setting. - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_LABELS`
TypeString
Default`""`
Environ variable`NEW_RELIC_LABELS`
- A dictionary of [label names](/docs/data-analysis/user-interface-functions/labels-categories-organize-your-apps-servers) and values that will be applied to the data sent from this agent. May also be expressed as a semicolon-delimited `;` string of colon-separated `:` pairs. For example, `Server:One;Data Center:Primary`. + A dictionary of [label names](/docs/data-analysis/user-interface-functions/labels-categories-organize-your-apps-servers) and values that will be applied to the data sent from this agent. May also be expressed as a semicolon-delimited `;` string of colon-separated `:` pairs. For example, `Server:One;Data Center:Primary`. - + - - - - - - - - - - - + + +
TypeString
Default`"newrelic_agent.log"`
Environ variable`NEW_RELIC_LOG_FILE_NAME`
TypeString
Default`"newrelic_agent.log"`
Environ variable`NEW_RELIC_LOG_FILE_NAME`
- Defines a name for the log file. + Defines a name for the log file. - + - - - - - - - - - - - + + +
TypeString
Default`"log/"`
Environ variable`NEW_RELIC_LOG_FILE_PATH`
TypeString
Default`"log/"`
Environ variable`NEW_RELIC_LOG_FILE_PATH`
- Defines a path to the agent log file, excluding the filename. + Defines a path to the agent log file, excluding the filename. - + - - - - - - - - - - - + + +
TypeString
Default`"json"`
Environ variable`NEW_RELIC_MARSHALLER`
TypeString
Default`"json"`
Environ variable`NEW_RELIC_MARSHALLER`
- Specifies a marshaller for transmitting data to the New Relic [collector](/docs/apm/new-relic-apm/getting-started/glossary#collector). Currently `json` is the only valid value for this setting. + Specifies a marshaller for transmitting data to the New Relic [collector](/docs/apm/new-relic-apm/getting-started/glossary#collector). Currently `json` is the only valid value for this setting. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MONITOR_MODE`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MONITOR_MODE`
- When `true`, the agent transmits data about your app to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector). + When `true`, the agent transmits data about your app to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector). - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_PREPEND_ACTIVE_RECORD_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_PREPEND_ACTIVE_RECORD_INSTRUMENTATION`
- If `true`, uses `Module#prepend` rather than `alias_method` for ActiveRecord instrumentation. + If `true`, uses `Module#prepend` rather than `alias_method` for ActiveRecord instrumentation. - + - - - - - - - - - - - + + +
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_HOST`
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_HOST`
- Defines a host for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. + Defines a host for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. - + - - - - - - - - - - - + + +
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_PASS`
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_PASS`
- Defines a password for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. + Defines a password for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. - + - - - - - - - - - - - + + +
TypeInteger
Default`8080`
Environ variable`NEW_RELIC_PROXY_PORT`
TypeInteger
Default`8080`
Environ variable`NEW_RELIC_PROXY_PORT`
- Defines a port for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. + Defines a port for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. - + - - - - - - - - - - - + + +
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_USER`
TypeString
Default`nil`
Environ variable`NEW_RELIC_PROXY_USER`
- Defines a user for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. + Defines a user for communicating with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) via a proxy server. - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_SECURITY_POLICIES_TOKEN`
TypeString
Default`""`
Environ variable`NEW_RELIC_SECURITY_POLICIES_TOKEN`
- Applies Language Agent Security Policy settings. + Applies Language Agent Security Policy settings. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SEND_DATA_ON_EXIT`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SEND_DATA_ON_EXIT`
- If `true`, enables the exit handler that sends data to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) before shutting down. + If `true`, enables the exit handler that sends data to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) before shutting down. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SYNC_STARTUP`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SYNC_STARTUP`
- When set to `true`, forces a synchronous connection to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) during application startup. For very short-lived processes, this helps ensure the New Relic agent has time to report. + When set to `true`, forces a synchronous connection to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector) during application startup. For very short-lived processes, this helps ensure the New Relic agent has time to report. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_THREAD_LOCAL_TRACER_STATE`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_THREAD_LOCAL_TRACER_STATE`
- If `true`, tracer state storage is thread-local, otherwise, fiber-local + If `true`, tracer state storage is thread-local, otherwise, fiber-local - + - - - - - - - - - - - + + +
TypeInteger
Default`120`
Environ variable`NEW_RELIC_TIMEOUT`
TypeInteger
Default`120`
Environ variable`NEW_RELIC_TIMEOUT`
- Defines the maximum number of seconds the agent should spend attempting to connect to the collector. + Defines the maximum number of seconds the agent should spend attempting to connect to the collector. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_ALLOW_ALL_HEADERS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_ALLOW_ALL_HEADERS`
- If `true`, enables capture of all HTTP request headers for all destinations. + If `true`, enables capture of all HTTP request headers for all destinations. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DEFER_RAILS_INITIALIZATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DEFER_RAILS_INITIALIZATION`
- If `true`, when the agent is in an application using Ruby on Rails, it will start after `config/initializers` run. + If `true`, when the agent is in an application using Ruby on Rails, it will start after `config/initializers` run. + + + This option may only be set by environment variable. + - - This option may only be set by environment variable. - + ## Transaction Tracer [#transaction-tracer] @@ -856,195 +510,109 @@ These settings are available for agent configuration. Some settings depend on yo The [transaction traces](/docs/apm/traces/transaction-traces/transaction-traces) feature collects detailed information from a selection of transactions, including a summary of the calling sequence, a breakdown of time spent, and a list of SQL queries and their query plans (on mysql and postgresql). Available features depend on your New Relic subscription level. - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ENABLED`
- If `true`, enables collection of [transaction traces](/docs/apm/traces/transaction-traces/transaction-traces). + If `true`, enables collection of [transaction traces](/docs/apm/traces/transaction-traces/transaction-traces). - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_EXPLAIN_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_EXPLAIN_ENABLED`
- If `true`, enables the collection of explain plans in transaction traces. This setting will also apply to explain plans in slow SQL traces if [`slow_sql.explain_enabled`](#slow_sql-explain_enabled) is not set separately. + If `true`, enables the collection of explain plans in transaction traces. This setting will also apply to explain plans in slow SQL traces if [`slow_sql.explain_enabled`](#slow_sql-explain_enabled) is not set separately. - + - - - - - - - - - - - + + +
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_EXPLAIN_THRESHOLD`
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_EXPLAIN_THRESHOLD`
- Threshold (in seconds) above which the agent will collect explain plans. Relevant only when [`explain_enabled`](#transaction_tracer.explain_enabled) is true. + Threshold (in seconds) above which the agent will collect explain plans. Relevant only when [`explain_enabled`](#transaction_tracer.explain_enabled) is true. - + - - - - - - - - - - - + + +
TypeInteger
Default`4000`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_LIMIT_SEGMENTS`
TypeInteger
Default`4000`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_LIMIT_SEGMENTS`
- Maximum number of transaction trace nodes to record in a single transaction trace. + Maximum number of transaction trace nodes to record in a single transaction trace. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_RECORD_REDIS_ARGUMENTS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_RECORD_REDIS_ARGUMENTS`
- If `true`, the agent records Redis command arguments in transaction traces. + If `true`, the agent records Redis command arguments in transaction traces. - + - - - - - - - - - - - + + +
TypeString
Default`"obfuscated"`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_RECORD_SQL`
TypeString
Default`"obfuscated"`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_RECORD_SQL`
- Obfuscation level for SQL queries reported in transaction trace nodes. + Obfuscation level for SQL queries reported in transaction trace nodes. - By default, this is set to `obfuscated`, which strips out the numeric and string literals. + By default, this is set to `obfuscated`, which strips out the numeric and string literals. - * If you do not want the agent to capture query information, set this to `none`. - * If you want the agent to capture all query information in its original form, set this to `raw`. - * When you enable [high security mode](/docs/agents/manage-apm-agents/configuration/high-security-mode), this is automatically set to `obfuscated`. + - If you do not want the agent to capture query information, set this to `none`. + - If you want the agent to capture all query information in its original form, set this to `raw`. + - When you enable [high security mode](/docs/agents/manage-apm-agents/configuration/high-security-mode), this is automatically set to `obfuscated`. - + - - - - - - - - - - - + + +
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_STACK_TRACE_THRESHOLD`
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_STACK_TRACE_THRESHOLD`
- Specify a threshold in seconds. The agent includes stack traces in transaction trace nodes when the stack trace duration exceeds this threshold. + Specify a threshold in seconds. The agent includes stack traces in transaction trace nodes when the stack trace duration exceeds this threshold. - + - - - - - - - - - - - + + +
TypeFloat
Default`(Dynamic)`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_TRANSACTION_THRESHOLD`
TypeFloat
Default`(Dynamic)`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_TRANSACTION_THRESHOLD`
- Specify a threshold in seconds. Transactions with a duration longer than this threshold are eligible for transaction traces. Specify a float value or the string `apdex_f`. + Specify a threshold in seconds. Transactions with a duration longer than this threshold are eligible for transaction traces. Specify a float value or the string `apdex_f`. + ## Error Collector [#error-collector] @@ -1054,353 +622,211 @@ The agent collects and reports all uncaught exceptions by default. These configu For information on ignored and expected errors, [see this page on Error Analytics in APM](/docs/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected/). To set expected errors via the `NewRelic::Agent.notice_error` Ruby method, [consult the Ruby agent API](/docs/agents/ruby-agent/api-guides/sending-handled-errors-new-relic/). - + + - - - - - - - - - - - + + +
TypeArray
Default`["ActionController::RoutingError", "Sinatra::NotFound"]`
Environ variable`None`
TypeArray
Default`["ActionController::RoutingError", "Sinatra::NotFound"]`
Environ variable`None`
- A list of error classes that the agent should ignore. + A list of error classes that the agent should ignore. + + + This option can't be set via environment variable. + - - This option can't be set via environment variable. - - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_CAPTURE_EVENTS`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_CAPTURE_EVENTS`
- If `true`, the agent collects [`TransactionError` events](/docs/insights/new-relic-insights/decorating-events/error-event-default-attributes-insights). + If `true`, the agent collects [`TransactionError` events](/docs/insights/new-relic-insights/decorating-events/error-event-default-attributes-insights). - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ENABLED`
- If `true`, the agent captures traced errors and error count metrics. + If `true`, the agent captures traced errors and error count metrics. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`None`
TypeArray
Default`[]`
Environ variable`None`
- A list of error classes that the agent should treat as expected. + A list of error classes that the agent should treat as expected. + + + This option can't be set via environment variable. + - - This option can't be set via environment variable. - - + - - - - - - - - - - - + + +
TypeHash
Default`{}`
Environ variable`None`
TypeHash
Default`{}`
Environ variable`None`
- A map of error classes to a list of messages. When an error of one of the classes specified here occurs, if its error message contains one of the strings corresponding to it here, that error will be treated as expected. + A map of error classes to a list of messages. When an error of one of the classes specified here occurs, if its error message contains one of the strings corresponding to it here, that error will be treated as expected. + + + This option can't be set via environment variable. + - - This option can't be set via environment variable. - - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_EXPECTED_STATUS_CODES`
TypeString
Default`""`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_EXPECTED_STATUS_CODES`
- A comma separated list of status codes, possibly including ranges. Errors associated with these status codes, where applicable, will be treated as expected. + A comma separated list of status codes, possibly including ranges. Errors associated with these status codes, where applicable, will be treated as expected. - + - - - - - - - - - - - + + +
TypeHash
Default`{}`
Environ variable`None`
TypeHash
Default`{}`
Environ variable`None`
- A map of error classes to a list of messages. When an error of one of the classes specified here occurs, if its error message contains one of the strings corresponding to it here, that error will be ignored. + A map of error classes to a list of messages. When an error of one of the classes specified here occurs, if its error message contains one of the strings corresponding to it here, that error will be ignored. + + + This option can't be set via environment variable. + - - This option can't be set via environment variable. - - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_IGNORE_STATUS_CODES`
TypeString
Default`""`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_IGNORE_STATUS_CODES`
- A comma separated list of status codes, possibly including ranges. Errors associated with these status codes, where applicable, will be ignored. + A comma separated list of status codes, possibly including ranges. Errors associated with these status codes, where applicable, will be ignored. - + - - - - - - - - - - - + + +
TypeInteger
Default`50`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_MAX_BACKTRACE_FRAMES`
TypeInteger
Default`50`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_MAX_BACKTRACE_FRAMES`
- Defines the maximum number of frames in an error backtrace. Backtraces over this amount are truncated in the middle, preserving the beginning and the end of the stack trace. + Defines the maximum number of frames in an error backtrace. Backtraces over this amount are truncated in the middle, preserving the beginning and the end of the stack trace. - + - - - - - - - - - - - + + +
TypeInteger
Default`100`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_MAX_EVENT_SAMPLES_STORED`
TypeInteger
Default`100`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_MAX_EVENT_SAMPLES_STORED`
- Defines the maximum number of [`TransactionError` events](/docs/insights/new-relic-insights/decorating-events/error-event-default-attributes-insights) reported per harvest cycle. + Defines the maximum number of [`TransactionError` events](/docs/insights/new-relic-insights/decorating-events/error-event-default-attributes-insights) reported per harvest cycle. + ## Browser Monitoring [#browser-monitoring] -The [page load timing](/docs/browser/new-relic-browser/page-load-timing/page-load-timing-process) feature (sometimes referred to as real user monitoring or RUM) gives you insight into the performance real users are experiencing with your website. This is accomplished by measuring the time it takes for your users' browsers to download and render your web pages by injecting a small amount of JavaScript code into the header and footer of each page. +The [page load timing](/docs/browser/new-relic-browser/page-load-timing/page-load-timing-process) feature (sometimes referred to as real user monitoring or RUM) gives you insight into the performance real users are experiencing with your website. This is accomplished by measuring the time it takes for your users' browsers to download and render your web pages by injecting a small amount of JavaScript code into the header and footer of each page. - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT`
- If `true`, enables [auto-injection](/docs/browser/new-relic-browser/installation-configuration/adding-apps-new-relic-browser#select-apm-app) of the JavaScript header for page load timing (sometimes referred to as real user monitoring or RUM). + If `true`, enables [auto-injection](/docs/browser/new-relic-browser/installation-configuration/adding-apps-new-relic-browser#select-apm-app) of the JavaScript header for page load timing (sometimes referred to as real user monitoring or RUM). - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_BROWSER_MONITORING_CONTENT_SECURITY_POLICY_NONCE`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_BROWSER_MONITORING_CONTENT_SECURITY_POLICY_NONCE`
- If `true`, enables auto-injection of [Content Security Policy Nonce](https://content-security-policy.com/nonce/) in browser monitoring scripts. For now, auto-injection only works with Rails 5.2+. + If `true`, enables auto-injection of [Content Security Policy Nonce](https://content-security-policy.com/nonce/) in browser monitoring scripts. For now, auto-injection only works with Rails 5.2+. + ## Transaction Events [#transaction-events] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ENABLED`
- If `true`, enables transaction event sampling. + If `true`, enables transaction event sampling. - + - - - - - - - - - - - + + +
TypeInteger
Default`1200`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_MAX_SAMPLES_STORED`
TypeInteger
Default`1200`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_MAX_SAMPLES_STORED`
- Defines the maximum number of transaction events reported from a single harvest. + Defines the maximum number of transaction events reported from a single harvest. + ## Application Logging [#application-logging] @@ -1410,244 +836,147 @@ The Ruby agent supports [APM logs in context](/docs/apm/new-relic-apm/getting-st Available logging-related config options include: - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_ENABLED`
- If `true`, enables log decoration and the collection of log events and metrics. + If `true`, enables log decoration and the collection of log events and metrics. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED`
- If `true`, the agent captures log records emitted by your application. + If `true`, the agent captures log records emitted by your application. - + - - - - - - - - - - - + + +
TypeString
Default`"debug"`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LOG_LEVEL`
TypeString
Default`"debug"`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LOG_LEVEL`
- Sets the minimum level a log event must have to be forwarded to New Relic. + Sets the minimum level a log event must have to be forwarded to New Relic. - This is based on the integer values of Ruby's `Logger::Severity` constants: [https://github.com/ruby/ruby/blob/master/lib/logger/severity.rb](https://github.com/ruby/ruby/blob/master/lib/logger/severity.rb) +This is based on the integer values of Ruby's `Logger::Severity` constants: https://github.com/ruby/ruby/blob/master/lib/logger/severity.rb - The intention is to forward logs with the level given to the configuration, as well as any logs with a higher level of severity. +The intention is to forward logs with the level given to the configuration, as well as any logs with a higher level of severity. - For example, setting this value to "debug" will forward all log events to New Relic. Setting this value to "error" will only forward log events with the levels "error", "fatal", and "unknown". +For example, setting this value to "debug" will forward all log events to New Relic. Setting this value to "error" will only forward log events with the levels "error", "fatal", and "unknown". - Valid values (ordered lowest to highest): +Valid values (ordered lowest to highest): + * "debug" + * "info" + * "warn" + * "error" + * "fatal" + * "unknown" - * "debug" - * "info" - * "warn" - * "error" - * "fatal" - * "unknown" - + - - - - - - - - - - - + + +
TypeHash
Default`{}`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CUSTOM_ATTRIBUTES`
TypeHash
Default`{}`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CUSTOM_ATTRIBUTES`
- A hash with key/value pairs to add as custom attributes to all log events forwarded to New Relic. If sending using an environment variable, the value must be formatted like: "key1=value1,key2=value2" + A hash with key/value pairs to add as custom attributes to all log events forwarded to New Relic. If sending using an environment variable, the value must be formatted like: "key1=value1,key2=value2" - + - - - - - - - - - - - + + +
TypeInteger
Default`10000`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_MAX_SAMPLES_STORED`
TypeInteger
Default`10000`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_FORWARDING_MAX_SAMPLES_STORED`
- Defines the maximum number of log records to buffer in memory at a time. + Defines the maximum number of log records to buffer in memory at a time. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_LOCAL_DECORATING_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_LOCAL_DECORATING_ENABLED`
- If `true`, the agent decorates logs with metadata to link to entities, hosts, traces, and spans. + If `true`, the agent decorates logs with metadata to link to entities, hosts, traces, and spans. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_METRICS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_APPLICATION_LOGGING_METRICS_ENABLED`
- If `true`, the agent captures metrics related to logging for your application. + If `true`, the agent captures metrics related to logging for your application. + ## AI Monitoring [#ai-monitoring] This section includes Ruby agent configurations for setting up AI monitoring. - - You need to enable distributed tracing to capture trace and feedback data. It is turned on by default in Ruby agents 8.0.0 and higher. - +You need to enable distributed tracing to capture trace and feedback data. It is turned on by default in Ruby agents 8.0.0 and higher. - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_AI_MONITORING_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_AI_MONITORING_ENABLED`
- If `false`, all LLM instrumentation (OpenAI only for now) will be disabled and no metrics, events, or spans will be sent. AI Monitoring is automatically disabled if `high_security` mode is enabled. + If `false`, all LLM instrumentation (OpenAI only for now) will be disabled and no metrics, events, or spans will be sent. AI Monitoring is automatically disabled if `high_security` mode is enabled. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_AI_MONITORING_RECORD_CONTENT_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_AI_MONITORING_RECORD_CONTENT_ENABLED`
- If `false`, LLM instrumentation (OpenAI only for now) will not capture input and output content on specific LLM events. - - The excluded attributes include: + If `false`, LLM instrumentation (OpenAI only for now) will not capture input and output content on specific LLM events. + The excluded attributes include: * `content` from LlmChatCompletionMessage events * `input` from LlmEmbedding events - This is an optional security setting to prevent recording sensitive data sent to and received from your LLMs. + This is an optional security setting to prevent recording sensitive data sent to and received from your LLMs. + + ## Attributes [#attributes] @@ -1655,819 +984,476 @@ This section includes Ruby agent configurations for setting up AI monitoring. [Attributes](/docs/features/agent-attributes) are key-value pairs containing information that determines the properties of an event or transaction. These key-value pairs can be viewed within transaction traces in APM, traced errors in APM, transaction events in dashboards, and page views in dashboards. You can customize exactly which attributes will be sent to each of these destinations - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ATTRIBUTES_ENABLED`
- If `true`, enables capture of attributes for all destinations. + If `true`, enables capture of attributes for all destinations. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from all destinations. Allows `*` as wildcard at end. + Prefix of attributes to exclude from all destinations. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include in all destinations. Allows `*` as wildcard at end. + Prefix of attributes to include in all destinations. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes from browser monitoring. + If `true`, the agent captures attributes from browser monitoring. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from browser monitoring. Allows `*` as wildcard at end. + Prefix of attributes to exclude from browser monitoring. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include in browser monitoring. Allows `*` as wildcard at end. + Prefix of attributes to include in browser monitoring. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes from error collection. + If `true`, the agent captures attributes from error collection. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from error collection. Allows `*` as wildcard at end. + Prefix of attributes to exclude from error collection. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include in error collection. Allows `*` as wildcard at end. + Prefix of attributes to include in error collection. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes on span events. + If `true`, the agent captures attributes on span events. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from span events. Allows `*` as wildcard at end. + Prefix of attributes to exclude from span events. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include on span events. Allows `*` as wildcard at end. + Prefix of attributes to include on span events. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes from transaction events. + If `true`, the agent captures attributes from transaction events. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from transaction events. Allows `*` as wildcard at end. + Prefix of attributes to exclude from transaction events. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include in transaction events. Allows `*` as wildcard at end. + Prefix of attributes to include in transaction events. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes on transaction segments. + If `true`, the agent captures attributes on transaction segments. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from transaction segments. Allows `*` as wildcard at end. + Prefix of attributes to exclude from transaction segments. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include on transaction segments. Allows `*` as wildcard at end. + Prefix of attributes to include on transaction segments. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_ENABLED`
- If `true`, the agent captures attributes from transaction traces. + If `true`, the agent captures attributes from transaction traces. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_EXCLUDE`
- Prefix of attributes to exclude from transaction traces. Allows `*` as wildcard at end. + Prefix of attributes to exclude from transaction traces. Allows `*` as wildcard at end. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_INCLUDE`
- Prefix of attributes to include in transaction traces. Allows `*` as wildcard at end. + Prefix of attributes to include in transaction traces. Allows `*` as wildcard at end. + ## Audit Log [#audit-log] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_AUDIT_LOG_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_AUDIT_LOG_ENABLED`
- If `true`, enables an audit log which logs communications with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector). + If `true`, enables an audit log which logs communications with the New Relic [collector](/docs/using-new-relic/welcome-new-relic/get-started/glossary/#collector). - + - - - - - - - - - - - + + +
TypeArray
Default`[".*"]`
Environ variable`NEW_RELIC_AUDIT_LOG_ENDPOINTS`
TypeArray
Default`[".*"]`
Environ variable`NEW_RELIC_AUDIT_LOG_ENDPOINTS`
- List of allowed endpoints to include in audit log. + List of allowed endpoints to include in audit log. - + - - - - - - - - - - - + + +
TypeString
Default`log/newrelic_audit.log`
Environ variable`NEW_RELIC_AUDIT_LOG_PATH`
TypeString
Default`log/newrelic_audit.log`
Environ variable`NEW_RELIC_AUDIT_LOG_PATH`
- Specifies a path to the audit log file (including the filename). + Specifies a path to the audit log file (including the filename). + ## Autostart [#autostart] + + - + + - - - - - - - - - - - + + +
TypeString
Default`"Rails::Command::ConsoleCommand,Rails::Command::CredentialsCommand,Rails::Command::Db::System::ChangeCommand,Rails::Command::DbConsoleCommand,Rails::Command::DestroyCommand,Rails::Command::DevCommand,Rails::Command::EncryptedCommand,Rails::Command::GenerateCommand,Rails::Command::InitializersCommand,Rails::Command::NotesCommand,Rails::Command::RoutesCommand,Rails::Command::RunnerCommand,Rails::Command::SecretsCommand,Rails::Console,Rails::DBConsole"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_CONSTANTS`
TypeString
Default`"Rails::Command::ConsoleCommand,Rails::Command::CredentialsCommand,Rails::Command::Db::System::ChangeCommand,Rails::Command::DbConsoleCommand,Rails::Command::DestroyCommand,Rails::Command::DevCommand,Rails::Command::EncryptedCommand,Rails::Command::GenerateCommand,Rails::Command::InitializersCommand,Rails::Command::NotesCommand,Rails::Command::RoutesCommand,Rails::Command::RunnerCommand,Rails::Command::SecretsCommand,Rails::Console,Rails::DBConsole"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_CONSTANTS`
- Specify a list of constants that should prevent the agent from starting automatically. Separate individual constants with a comma `,`. For example, `"Rails::Console,UninstrumentedBackgroundJob"`. + Specify a list of constants that should prevent the agent from starting automatically. Separate individual constants with a comma `,`. For example, `"Rails::Console,UninstrumentedBackgroundJob"`. - + - - - - - - - - - - - + + +
TypeString
Default`"irb,rspec"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_EXECUTABLES`
TypeString
Default`"irb,rspec"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_EXECUTABLES`
- Defines a comma-delimited list of executables that the agent should not instrument. For example, `"rake,my_ruby_script.rb"`. + Defines a comma-delimited list of executables that the agent should not instrument. For example, `"rake,my_ruby_script.rb"`. - + - - - - - - - - - - - + + +
TypeString
Default`"about,assets:clean,assets:clobber,assets:environment,assets:precompile,assets:precompile:all,db:create,db:drop,db:fixtures:load,db:migrate,db:migrate:status,db:rollback,db:schema:cache:clear,db:schema:cache:dump,db:schema:dump,db:schema:load,db:seed,db:setup,db:structure:dump,db:version,doc:app,log:clear,middleware,notes,notes:custom,rails:template,rails:update,routes,secret,spec,spec:features,spec:requests,spec:controllers,spec:helpers,spec:models,spec:views,spec:routing,spec:rcov,stats,test,test:all,test:all:db,test:recent,test:single,test:uncommitted,time:zones:all,tmp:clear,tmp:create,webpacker:compile"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_RAKE_TASKS`
TypeString
Default`"about,assets:clean,assets:clobber,assets:environment,assets:precompile,assets:precompile:all,db:create,db:drop,db:fixtures:load,db:migrate,db:migrate:status,db:rollback,db:schema:cache:clear,db:schema:cache:dump,db:schema:dump,db:schema:load,db:seed,db:setup,db:structure:dump,db:version,doc:app,log:clear,middleware,notes,notes:custom,rails:template,rails:update,routes,secret,spec,spec:features,spec:requests,spec:controllers,spec:helpers,spec:models,spec:views,spec:routing,spec:rcov,stats,test,test:all,test:all:db,test:recent,test:single,test:uncommitted,time:zones:all,tmp:clear,tmp:create,webpacker:compile"`
Environ variable`NEW_RELIC_AUTOSTART_DENYLISTED_RAKE_TASKS`
- Defines a comma-delimited list of Rake tasks that the agent should not instrument. For example, `"assets:precompile,db:migrate"`. + Defines a comma-delimited list of Rake tasks that the agent should not instrument. For example, `"assets:precompile,db:migrate"`. + ## Code Level Metrics [#code-level-metrics] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CODE_LEVEL_METRICS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CODE_LEVEL_METRICS_ENABLED`
- If `true`, the agent will report source code level metrics for traced methods. - See: [https://docs.newrelic.com/docs/apm/agents/ruby-agent/features/ruby-codestream-integration/](https://docs.newrelic.com/docs/apm/agents/ruby-agent/features/ruby-codestream-integration/) + If `true`, the agent will report source code level metrics for traced methods. +See: https://docs.newrelic.com/docs/apm/agents/ruby-agent/features/ruby-codestream-integration/ + ## Cross Application Tracer [#cross-application-tracer] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CROSS_APPLICATION_TRACER_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_CROSS_APPLICATION_TRACER_ENABLED`
- **DEPRECATED** Please see: [distributed_tracing.enabled](#distributed_tracing-enabled). + **DEPRECATED** Please see: [distributed_tracing.enabled](#distributed_tracing-enabled). - If `true`, enables [cross-application tracing](/docs/agents/ruby-agent/features/cross-application-tracing-ruby/) when `distributed_tracing.enabled` is set to `false`. +If `true`, enables [cross-application tracing](/docs/agents/ruby-agent/features/cross-application-tracing-ruby/) when `distributed_tracing.enabled` is set to `false`. + ## Custom Attributes [#custom-attributes] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CUSTOM_ATTRIBUTES_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CUSTOM_ATTRIBUTES_ENABLED`
- If `false`, custom attributes will not be sent on events. + If `false`, custom attributes will not be sent on events. + ## Custom Events [#custom-events] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CUSTOM_INSIGHTS_EVENTS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_CUSTOM_INSIGHTS_EVENTS_ENABLED`
- If `true`, the agent captures [custom events](/docs/insights/new-relic-insights/adding-querying-data/inserting-custom-events-new-relic-apm-agents). + If `true`, the agent captures [custom events](/docs/insights/new-relic-insights/adding-querying-data/inserting-custom-events-new-relic-apm-agents). - + - - - - - - - - - - - + + +
TypeInteger
Default`3000`
Environ variable`NEW_RELIC_CUSTOM_INSIGHTS_EVENTS_MAX_SAMPLES_STORED`
TypeInteger
Default`3000`
Environ variable`NEW_RELIC_CUSTOM_INSIGHTS_EVENTS_MAX_SAMPLES_STORED`
- * Specify a maximum number of custom events to buffer in memory at a time. - * When configuring the agent for [AI monitoring](/docs/ai-monitoring/intro-to-ai-monitoring), set to max value `100000`. This ensures the agent captures the maximum amount of LLM events. + * Specify a maximum number of custom events to buffer in memory at a time. + * When configuring the agent for [AI monitoring](/docs/ai-monitoring/intro-to-ai-monitoring), set to max value `100000`. This ensures the agent captures the maximum amount of LLM events. + + ## Datastore Tracer [#datastore-tracer] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DATASTORE_TRACER_DATABASE_NAME_REPORTING_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DATASTORE_TRACER_DATABASE_NAME_REPORTING_ENABLED`
- If `false`, the agent will not add `database_name` parameter to transaction or slow sql traces. + If `false`, the agent will not add `database_name` parameter to transaction or slow sql traces. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DATASTORE_TRACER_INSTANCE_REPORTING_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DATASTORE_TRACER_INSTANCE_REPORTING_ENABLED`
- If `false`, the agent will not report datastore instance metrics, nor add `host` or `port_path_or_id` parameters to transaction or slow SQL traces. + If `false`, the agent will not report datastore instance metrics, nor add `host` or `port_path_or_id` parameters to transaction or slow SQL traces. + ## Disabling [#disabling] @@ -2475,445 +1461,238 @@ This section includes Ruby agent configurations for setting up AI monitoring. Use these settings to toggle instrumentation types during agent startup. - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_CABLE_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_CABLE_INSTRUMENTATION`
- If `true`, disables Action Cable instrumentation. + If `true`, disables Action Cable instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_CONTROLLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_CONTROLLER`
- If `true`, disables Action Controller instrumentation. + If `true`, disables Action Controller instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_MAILBOX`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_MAILBOX`
- If `true`, disables Action Mailbox instrumentation. + If `true`, disables Action Mailbox instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_MAILER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTION_MAILER`
- If `true`, disables Action Mailer instrumentation. + If `true`, disables Action Mailer instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVEJOB`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVEJOB`
- If `true`, disables Active Job instrumentation. + If `true`, disables Active Job instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_STORAGE`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_STORAGE`
- If `true`, disables Active Storage instrumentation. + If `true`, disables Active Storage instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_SUPPORT`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_SUPPORT`
- If `true`, disables Active Support instrumentation. + If `true`, disables Active Support instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_RECORD_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_RECORD_INSTRUMENTATION`
- If `true`, disables Active Record instrumentation. + If `true`, disables Active Record instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_RECORD_NOTIFICATIONS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_ACTIVE_RECORD_NOTIFICATIONS`
- If `true`, disables instrumentation for Active Record 4+ + If `true`, disables instrumentation for Active Record 4+ - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_CPU_SAMPLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_CPU_SAMPLER`
- If `true`, the agent won't sample the CPU usage of the host process. + If `true`, the agent won't sample the CPU usage of the host process. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_DELAYED_JOB_SAMPLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_DELAYED_JOB_SAMPLER`
- If `true`, the agent won't measure the depth of Delayed Job queues. + If `true`, the agent won't measure the depth of Delayed Job queues. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_GC_PROFILER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_GC_PROFILER`
- If `true`, disables the use of `GC::Profiler` to measure time spent in garbage collection + If `true`, disables the use of `GC::Profiler` to measure time spent in garbage collection - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_MEMORY_SAMPLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_MEMORY_SAMPLER`
- If `true`, the agent won't sample the memory usage of the host process. + If `true`, the agent won't sample the memory usage of the host process. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_MIDDLEWARE_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_MIDDLEWARE_INSTRUMENTATION`
- If `true`, the agent won't wrap third-party middlewares in instrumentation (regardless of whether they are installed via `Rack::Builder` or Rails). + If `true`, the agent won't wrap third-party middlewares in instrumentation (regardless of whether they are installed via `Rack::Builder` or Rails). + + + When middleware instrumentation is disabled, if an application is using middleware that could alter the response code, the HTTP status code reported on the transaction may not reflect the altered value. + - - When middleware instrumentation is disabled, if an application is using middleware that could alter the response code, the HTTP status code reported on the transaction may not reflect the altered value. - - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SAMPLERS`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SAMPLERS`
- If `true`, disables the collection of sampler metrics. Sampler metrics are metrics that are not event-based (such as CPU time or memory usage). + If `true`, disables the collection of sampler metrics. Sampler metrics are metrics that are not event-based (such as CPU time or memory usage). - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SEQUEL_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SEQUEL_INSTRUMENTATION`
- If `true`, disables [Sequel instrumentation](/docs/agents/ruby-agent/frameworks/sequel-instrumentation). + If `true`, disables [Sequel instrumentation](/docs/agents/ruby-agent/frameworks/sequel-instrumentation). - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SIDEKIQ`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SIDEKIQ`
- If `true`, disables [Sidekiq instrumentation](/docs/agents/ruby-agent/background-jobs/sidekiq-instrumentation). + If `true`, disables [Sidekiq instrumentation](/docs/agents/ruby-agent/background-jobs/sidekiq-instrumentation). - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_RODA_AUTO_MIDDLEWARE`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_RODA_AUTO_MIDDLEWARE`
- If `true`, disables agent middleware for Roda. This middleware is responsible for advanced feature support such as [page load timing](/docs/browser/new-relic-browser/getting-started/new-relic-browser) and [error collection](/docs/apm/applications-menu/events/view-apm-error-analytics). + If `true`, disables agent middleware for Roda. This middleware is responsible for advanced feature support such as [page load timing](/docs/browser/new-relic-browser/getting-started/new-relic-browser) and [error collection](/docs/apm/applications-menu/events/view-apm-error-analytics). - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SINATRA_AUTO_MIDDLEWARE`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_SINATRA_AUTO_MIDDLEWARE`
- If `true`, disables agent middleware for Sinatra. This middleware is responsible for advanced feature support such as [cross application tracing](/docs/apm/transactions/cross-application-traces/cross-application-tracing), [page load timing](/docs/browser/new-relic-browser/getting-started/new-relic-browser), and [error collection](/docs/apm/applications-menu/events/view-apm-error-analytics). + If `true`, disables agent middleware for Sinatra. This middleware is responsible for advanced feature support such as [cross application tracing](/docs/apm/transactions/cross-application-traces/cross-application-tracing), [page load timing](/docs/browser/new-relic-browser/getting-started/new-relic-browser), and [error collection](/docs/apm/applications-menu/events/view-apm-error-analytics). Cross application tracing is deprecated in favor of [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing). Distributed tracing is on by default for Ruby agent versions 8.0.0 and above. Middlewares are not required to support distributed tracing. @@ -2929,2208 +1708,1322 @@ Use these settings to toggle instrumentation types during agent startup. enabled: false ``` + - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_VIEW_INSTRUMENTATION`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_VIEW_INSTRUMENTATION`
- If `true`, disables view instrumentation. + If `true`, disables view instrumentation. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_VM_SAMPLER`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_DISABLE_VM_SAMPLER`
- If `true`, the agent won't [sample performance measurements from the Ruby VM](/docs/agents/ruby-agent/features/ruby-vm-measurements). + If `true`, the agent won't [sample performance measurements from the Ruby VM](/docs/agents/ruby-agent/features/ruby-vm-measurements). + ## Distributed Tracing [#distributed-tracing] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DISTRIBUTED_TRACING_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_DISTRIBUTED_TRACING_ENABLED`
- Distributed tracing lets you see the path that a request takes through your distributed system. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the [transition guide](/docs/transition-guide-distributed-tracing) before you enable this feature. + Distributed tracing lets you see the path that a request takes through your distributed system. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the [transition guide](/docs/transition-guide-distributed-tracing) before you enable this feature. + ## Elasticsearch [#elasticsearch] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ELASTICSEARCH_CAPTURE_QUERIES`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ELASTICSEARCH_CAPTURE_QUERIES`
- If `true`, the agent captures Elasticsearch queries in transaction traces. + If `true`, the agent captures Elasticsearch queries in transaction traces. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ELASTICSEARCH_OBFUSCATE_QUERIES`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_ELASTICSEARCH_OBFUSCATE_QUERIES`
- If `true`, the agent obfuscates Elasticsearch queries in transaction traces. + If `true`, the agent obfuscates Elasticsearch queries in transaction traces. + ## Heroku [#heroku] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_HEROKU_USE_DYNO_NAMES`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_HEROKU_USE_DYNO_NAMES`
- If `true`, the agent uses Heroku dyno names as the hostname. + If `true`, the agent uses Heroku dyno names as the hostname. - + - - - - - - - - - - - + + +
TypeArray
Default`["scheduler", "run"]`
Environ variable`NEW_RELIC_HEROKU_DYNO_NAME_PREFIXES_TO_SHORTEN`
TypeArray
Default`["scheduler", "run"]`
Environ variable`NEW_RELIC_HEROKU_DYNO_NAME_PREFIXES_TO_SHORTEN`
- Ordinarily the agent reports dyno names with a trailing dot and process ID (for example, `worker.3`). You can remove this trailing data by specifying the prefixes you want to report without trailing data (for example, `worker`). + Ordinarily the agent reports dyno names with a trailing dot and process ID (for example, `worker.3`). You can remove this trailing data by specifying the prefixes you want to report without trailing data (for example, `worker`). + ## Infinite Tracing [#infinite-tracing] + + - + + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_INFINITE_TRACING_TRACE_OBSERVER_HOST`
TypeString
Default`""`
Environ variable`NEW_RELIC_INFINITE_TRACING_TRACE_OBSERVER_HOST`
- Configures the hostname for the trace observer Host. When configured, enables tail-based sampling by sending all recorded spans to a trace observer for further sampling decisions, irrespective of any usual agent sampling decision. + Configures the hostname for the trace observer Host. When configured, enables tail-based sampling by sending all recorded spans to a trace observer for further sampling decisions, irrespective of any usual agent sampling decision. - + - - - - - - - - - - - + + +
TypeInteger
Default`443`
Environ variable`NEW_RELIC_INFINITE_TRACING_TRACE_OBSERVER_PORT`
TypeInteger
Default`443`
Environ variable`NEW_RELIC_INFINITE_TRACING_TRACE_OBSERVER_PORT`
- Configures the TCP/IP port for the trace observer Host + Configures the TCP/IP port for the trace observer Host - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_INFINITE_TRACING_BATCHING`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_INFINITE_TRACING_BATCHING`
- If `true` (the default), data sent to the trace observer is batched instead of sending each span individually. + If `true` (the default), data sent to the trace observer is batched instead of sending each span individually. - + - - - - - - - - - - - + + +
TypeSymbol
Default`:high`
Environ variable`NEW_RELIC_INFINITE_TRACING_COMPRESSION_LEVEL`
TypeSymbol
Default`:high`
Environ variable`NEW_RELIC_INFINITE_TRACING_COMPRESSION_LEVEL`
- Configure the compression level for data sent to the trace observer. + Configure the compression level for data sent to the trace observer. - May be one of: `:none`, `:low`, `:medium`, `:high`. + May be one of: `:none`, `:low`, `:medium`, `:high`. + + Set the level to `:none` to disable compression. - Set the level to `:none` to disable compression. + ## Instrumentation [#instrumentation] + + - + + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ACTIVE_SUPPORT_BROADCAST_LOGGER`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ACTIVE_SUPPORT_BROADCAST_LOGGER`
- Controls auto-instrumentation of `ActiveSupport::BroadcastLogger` at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Used in Rails versions >= 7.1. + Controls auto-instrumentation of `ActiveSupport::BroadcastLogger` at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Used in Rails versions >= 7.1. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ACTIVE_SUPPORT_LOGGER`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ACTIVE_SUPPORT_LOGGER`
- Controls auto-instrumentation of `ActiveSupport::Logger` at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Used in Rails versions below 7.1. + Controls auto-instrumentation of `ActiveSupport::Logger` at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Used in Rails versions below 7.1. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ASYNC_HTTP`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ASYNC_HTTP`
- Controls auto-instrumentation of Async::HTTP at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Async::HTTP at start up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_BUNNY`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_BUNNY`
- Controls auto-instrumentation of bunny at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of bunny at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`"auto"`
Environ variable`NEW_RELIC_INSTRUMENTATION_AWS_SQS`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_OPENSEARCH`
- Controls auto-instrumentation of the aws-sdk-sqs library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the opensearch-ruby library at start-up. May be one of `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_DYNAMODB`
TypeString
Default`"auto"`
Environ variable`NEW_RELIC_INSTRUMENTATION_AWS_SQS`
- Controls auto-instrumentation of the aws-sdk-dynamodb library at start-up. May be one of `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the aws-sdk-sqs library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_FIBER`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_DYNAMODB`
- Controls auto-instrumentation of the Fiber class at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the aws-sdk-dynamodb library at start-up. May be one of `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_CONCURRENT_RUBY`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_FIBER`
- Controls auto-instrumentation of the concurrent-ruby library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the Fiber class at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_CURB`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_CONCURRENT_RUBY`
- Controls auto-instrumentation of Curb at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the concurrent-ruby library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_DELAYED_JOB`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_CURB`
- Controls auto-instrumentation of Delayed Job at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Curb at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ELASTICSEARCH`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_DELAYED_JOB`
- Controls auto-instrumentation of the elasticsearch library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Delayed Job at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ETHON`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ELASTICSEARCH`
- Controls auto-instrumentation of ethon at start up. May be one of `auto`, `prepend`, `chain`, `disabled` + Controls auto-instrumentation of the elasticsearch library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`enabled`
Environ variable`NEW_RELIC_INSTRUMENTATION_EXCON`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_ETHON`
- Controls auto-instrumentation of Excon at start-up. May be one of: `enabled`, `disabled`. + Controls auto-instrumentation of ethon at start up. May be one of `auto`, `prepend`, `chain`, `disabled` - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRAPE`
TypeString
Default`enabled`
Environ variable`NEW_RELIC_INSTRUMENTATION_EXCON`
- Controls auto-instrumentation of Grape at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Excon at start-up. May be one of: `enabled`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_CLIENT`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRAPE`
- Controls auto-instrumentation of gRPC clients at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Grape at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_HOST_DENYLIST`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_CLIENT`
- Specifies a list of hostname patterns separated by commas that will match gRPC hostnames that traffic is to be ignored by New Relic for. New Relic's gRPC client instrumentation will ignore traffic streamed to a host matching any of these patterns, and New Relic's gRPC server instrumentation will ignore traffic for a server running on a host whose hostname matches any of these patterns. By default, no traffic is ignored when gRPC instrumentation is itself enabled. For example, `"private.com$,exception.*"` + Controls auto-instrumentation of gRPC clients at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_SERVER`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_HOST_DENYLIST`
- Controls auto-instrumentation of gRPC servers at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Specifies a list of hostname patterns separated by commas that will match gRPC hostnames that traffic is to be ignored by New Relic for. New Relic's gRPC client instrumentation will ignore traffic streamed to a host matching any of these patterns, and New Relic's gRPC server instrumentation will ignore traffic for a server running on a host whose hostname matches any of these patterns. By default, no traffic is ignored when gRPC instrumentation is itself enabled. For example, `"private.com$,exception.*"` - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPCLIENT`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_GRPC_SERVER`
- Controls auto-instrumentation of HTTPClient at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of gRPC servers at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPRB`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPCLIENT`
- Controls auto-instrumentation of http.rb gem at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of HTTPClient at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPX`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPRB`
- Controls auto-instrumentation of httpx at start up. May be one of `auto`, `prepend`, `chain`, `disabled` + Controls auto-instrumentation of http.rb gem at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_LOGGER`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_HTTPX`
- Controls auto-instrumentation of Ruby standard library Logger at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of httpx at start up. May be one of `auto`, `prepend`, `chain`, `disabled` - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_LOGSTASHER`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_LOGGER`
- Controls auto-instrumentation of the LogStasher library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Ruby standard library Logger at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHE`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_LOGSTASHER`
- Controls auto-instrumentation of dalli gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the LogStasher library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHED`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHE`
- Controls auto-instrumentation of memcached gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of dalli gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHE_CLIENT`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHED`
- Controls auto-instrumentation of memcache-client gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of memcached gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`enabled`
Environ variable`NEW_RELIC_INSTRUMENTATION_MONGO`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_MEMCACHE_CLIENT`
- Controls auto-instrumentation of Mongo at start-up. May be one of: `enabled`, `disabled`. + Controls auto-instrumentation of memcache-client gem for Memcache at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_NET_HTTP`
TypeString
Default`enabled`
Environ variable`NEW_RELIC_INSTRUMENTATION_MONGO`
- Controls auto-instrumentation of `Net::HTTP` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Mongo at start-up. May be one of: `enabled`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RUBY_OPENAI`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_NET_HTTP`
- Controls auto-instrumentation of the ruby-openai gem at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Defaults to `disabled` in high security mode. + Controls auto-instrumentation of `Net::HTTP` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_PUMA_RACK`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RUBY_OPENAI`
- Controls auto-instrumentation of `Puma::Rack`. When enabled, the agent hooks into the `to_app` method in `Puma::Rack::Builder` to find gems to instrument during application startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the ruby-openai gem at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. Defaults to `disabled` in high security mode. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_PUMA_RACK_URLMAP`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_PUMA_RACK`
- Controls auto-instrumentation of `Puma::Rack::URLMap` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of `Puma::Rack`. When enabled, the agent hooks into the `to_app` method in `Puma::Rack::Builder` to find gems to instrument during application startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RACK`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_PUMA_RACK_URLMAP`
- Controls auto-instrumentation of Rack. When enabled, the agent hooks into the `to_app` method in `Rack::Builder` to find gems to instrument during application startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of `Puma::Rack::URLMap` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RACK_URLMAP`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RACK`
- Controls auto-instrumentation of `Rack::URLMap` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Rack. When enabled, the agent hooks into the `to_app` method in `Rack::Builder` to find gems to instrument during application startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RAKE`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RACK_URLMAP`
- Controls auto-instrumentation of rake at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of `Rack::URLMap` at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_REDIS`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RAKE`
- Controls auto-instrumentation of Redis at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of rake at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RESQUE`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_REDIS`
- Controls auto-instrumentation of resque at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Redis at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RODA`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RESQUE`
- Controls auto-instrumentation of Roda at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of resque at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_SINATRA`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_RODA`
- Controls auto-instrumentation of Sinatra at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Roda at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`"enabled"`
Environ variable`NEW_RELIC_INSTRUMENTATION_STRIPE`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_SINATRA`
- Controls auto-instrumentation of Stripe at startup. May be one of: `enabled`, `disabled`. + Controls auto-instrumentation of Sinatra at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_VIEW_COMPONENT`
TypeString
Default`"enabled"`
Environ variable`NEW_RELIC_INSTRUMENTATION_STRIPE`
- Controls auto-instrumentation of ViewComponent at startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Stripe at startup. May be one of: `enabled`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_THREAD`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_VIEW_COMPONENT`
- Controls auto-instrumentation of the Thread class at start-up to allow the agent to correctly nest spans inside of an asynchronous transaction. This does not enable the agent to automatically trace all threads created (see `instrumentation.thread.tracing`). May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of ViewComponent at startup. May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_INSTRUMENTATION_THREAD_TRACING`
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_THREAD`
- Controls auto-instrumentation of the Thread class at start-up to automatically add tracing to all Threads created in the application. + Controls auto-instrumentation of the Thread class at start-up to allow the agent to correctly nest spans inside of an asynchronous transaction. This does not enable the agent to automatically trace all threads created (see `instrumentation.thread.tracing`). May be one of: `auto`, `prepend`, `chain`, `disabled`. - + - - - - - - - - - - - + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_TILT`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_INSTRUMENTATION_THREAD_TRACING`
- Controls auto-instrumentation of the Tilt template rendering library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of the Thread class at start-up to automatically add tracing to all Threads created in the application. - + - - - + + + + +
TypeString
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_TILT`
- - Default`auto` - + Controls auto-instrumentation of the Tilt template rendering library at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + - - Environ variable`NEW_RELIC_INSTRUMENTATION_TYPHOEUS` - + + + + + +
TypeString
Default`auto`
Environ variable`NEW_RELIC_INSTRUMENTATION_TYPHOEUS`
- Controls auto-instrumentation of Typhoeus at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + Controls auto-instrumentation of Typhoeus at start-up. May be one of: `auto`, `prepend`, `chain`, `disabled`. + ## Message Tracer [#message-tracer] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MESSAGE_TRACER_SEGMENT_PARAMETERS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MESSAGE_TRACER_SEGMENT_PARAMETERS_ENABLED`
- If `true`, the agent will collect metadata about messages and attach them as segment parameters. + If `true`, the agent will collect metadata about messages and attach them as segment parameters. + ## Mongo [#mongo] + + - + + - - - + + + + +
TypeBoolean
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MONGO_CAPTURE_QUERIES`
- - Default`true` - + If `true`, the agent captures Mongo queries in transaction traces. + - - Environ variable`NEW_RELIC_MONGO_CAPTURE_QUERIES` - + + + + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_MONGO_OBFUSCATE_QUERIES`
- If `true`, the agent captures Mongo queries in transaction traces. + If `true`, the agent obfuscates Mongo queries in transaction traces. - + + +## Opensearch [#opensearch] + + + + + + - - - + + + + +
TypeBoolean
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_OPENSEARCH_CAPTURE_QUERIES`
- - Default`true` - + If `true`, the agent captures OpenSearch queries in transaction traces. + - - Environ variable`NEW_RELIC_MONGO_OBFUSCATE_QUERIES` - + + + + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_OPENSEARCH_OBFUSCATE_QUERIES`
- If `true`, the agent obfuscates Mongo queries in transaction traces. + If `true`, the agent obfuscates OpenSearch queries in transaction traces. + ## Process Host [#process-host] + + - + + - - - - - - - - - - - + + +
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_PROCESS_HOST_DISPLAY_NAME`
TypeString
Default`(Dynamic)`
Environ variable`NEW_RELIC_PROCESS_HOST_DISPLAY_NAME`
- Specify a custom host name for [display in the New Relic UI](/docs/apm/new-relic-apm/maintenance/add-rename-remove-hosts#display_name). + Specify a custom host name for [display in the New Relic UI](/docs/apm/new-relic-apm/maintenance/add-rename-remove-hosts#display_name). + ## Rake [#rake] + + - + + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_RAKE_TASKS`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_RAKE_TASKS`
- Specify an Array of Rake tasks to automatically instrument. This configuration option converts the Array to a RegEx list. If you'd like to allow all tasks by default, use `rake.tasks: [.+]`. No rake tasks will be instrumented unless they're added to this list. For more information, visit the [New Relic Rake Instrumentation docs](/docs/apm/agents/ruby-agent/background-jobs/rake-instrumentation). + Specify an Array of Rake tasks to automatically instrument. This configuration option converts the Array to a RegEx list. If you'd like to allow all tasks by default, use `rake.tasks: [.+]`. No rake tasks will be instrumented unless they're added to this list. For more information, visit the [New Relic Rake Instrumentation docs](/docs/apm/agents/ruby-agent/background-jobs/rake-instrumentation). - + - - - - - - - - - - - + + +
TypeInteger
Default`10`
Environ variable`NEW_RELIC_RAKE_CONNECT_TIMEOUT`
TypeInteger
Default`10`
Environ variable`NEW_RELIC_RAKE_CONNECT_TIMEOUT`
- Timeout for waiting on connect to complete before a rake task + Timeout for waiting on connect to complete before a rake task + ## Rules [#rules] + + - + + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_RULES_IGNORE_URL_REGEXES`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_RULES_IGNORE_URL_REGEXES`
- Define transactions you want the agent to ignore, by specifying a list of patterns matching the URI you want to ignore. For more detail, see [the docs on ignoring specific transactions](/docs/agents/ruby-agent/api-guides/ignoring-specific-transactions/#config-ignoring). + Define transactions you want the agent to ignore, by specifying a list of patterns matching the URI you want to ignore. For more detail, see [the docs on ignoring specific transactions](/docs/agents/ruby-agent/api-guides/ignoring-specific-transactions/#config-ignoring). + ## Security [#security] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SECURITY_AGENT_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SECURITY_AGENT_ENABLED`
- If `true`, the security agent is loaded (a Ruby 'require' is performed) + If `true`, the security agent is loaded (a Ruby 'require' is performed) - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SECURITY_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SECURITY_ENABLED`
- If `true`, the security agent is started (the agent runs in its event loop) + If `true`, the security agent is started (the agent runs in its event loop) - + - - - - - - - - - - - + + +
TypeString
Default`"IAST"`
Environ variable`NEW_RELIC_SECURITY_MODE`
TypeString
Default`"IAST"`
Environ variable`NEW_RELIC_SECURITY_MODE`
- Defines the mode for the security agent to operate in. Currently only `IAST` is supported + Defines the mode for the security agent to operate in. Currently only `IAST` is supported - + - - - - - - - - - - - + + +
TypeString
Default`"wss://csec.nr-data.net"`
Environ variable`NEW_RELIC_SECURITY_VALIDATOR_SERVICE_URL`
TypeString
Default`"wss://csec.nr-data.net"`
Environ variable`NEW_RELIC_SECURITY_VALIDATOR_SERVICE_URL`
- Defines the endpoint URL for posting security-related data + Defines the endpoint URL for posting security-related data - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_RCI_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_RCI_ENABLED`
- If `true`, enables RCI (remote code injection) detection + If `true`, enables RCI (remote code injection) detection - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_RXSS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_RXSS_ENABLED`
- If `true`, enables RXSS (reflected cross-site scripting) detection + If `true`, enables RXSS (reflected cross-site scripting) detection - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_DESERIALIZATION_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SECURITY_DETECTION_DESERIALIZATION_ENABLED`
- If `true`, enables deserialization detection + If `true`, enables deserialization detection - + - - - - - - - - - - - + + +
TypeInteger
Default`nil`
Environ variable`NEW_RELIC_SECURITY_APPLICATION_INFO_PORT`
TypeInteger
Default`nil`
Environ variable`NEW_RELIC_SECURITY_APPLICATION_INFO_PORT`
- The port the application is listening on. This setting is mandatory for Passenger servers. Other servers should be detected by default. + The port the application is listening on. This setting is mandatory for Passenger servers. Other servers should be detected by default. - + - - - - - - - - - - - + + +
TypeInteger
Default`300`
Environ variable`NEW_RELIC_SECURITY_REQUEST_BODY_LIMIT`
TypeInteger
Default`300`
Environ variable`NEW_RELIC_SECURITY_REQUEST_BODY_LIMIT`
- Defines the request body limit to process in security events (in KB). The default value is 300, for 300KB. + Defines the request body limit to process in security events (in KB). The default value is 300, for 300KB. + ## Serverless Mode [#serverless-mode] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SERVERLESS_MODE_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SERVERLESS_MODE_ENABLED`
- If `true`, the agent will operate in a streamlined mode suitable for use with short-lived serverless functions. NOTE: Only AWS Lambda functions are supported currently and this option is not intended for use without [New Relic's Ruby Lambda layer](https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/monitoring-aws-lambda-serverless-monitoring/) offering. + If `true`, the agent will operate in a streamlined mode suitable for use with short-lived serverless functions. NOTE: Only AWS Lambda functions are supported currently and this option is not intended for use without [New Relic's Ruby Lambda layer](https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/monitoring-aws-lambda-serverless-monitoring/) offering. + ## Sidekiq [#sidekiq] + + - + + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SIDEKIQ_ARGS_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SIDEKIQ_ARGS_INCLUDE`
- An array of strings that will collectively serve as an allowlist for filtering which Sidekiq job arguments get reported to New Relic. To capture any Sidekiq arguments, 'job.sidekiq.args.\*' must be added to the separate `:'attributes.include'` configuration option. Each string in this array will be turned into a regular expression via `Regexp.new` to permit advanced matching. For job argument hashes, if either a key or value matches the pair will be included. All matching job argument array elements and job argument scalars will be included. + An array of strings that will collectively serve as an allowlist for filtering which Sidekiq job arguments get reported to New Relic. To capture any Sidekiq arguments, 'job.sidekiq.args.*' must be added to the separate `:'attributes.include'` configuration option. Each string in this array will be turned into a regular expression via `Regexp.new` to permit advanced matching. For job argument hashes, if either a key or value matches the pair will be included. All matching job argument array elements and job argument scalars will be included. - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SIDEKIQ_ARGS_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_SIDEKIQ_ARGS_EXCLUDE`
- An array of strings that will collectively serve as a denylist for filtering which Sidekiq job arguments get reported to New Relic. To capture any Sidekiq arguments, 'job.sidekiq.args.\*' must be added to the separate `:'attributes.include'` configuration option. Each string in this array will be turned into a regular expression via `Regexp.new` to permit advanced matching. For job argument hashes, if either a key or value matches the pair will be excluded. All matching job argument array elements and job argument scalars will be excluded. + An array of strings that will collectively serve as a denylist for filtering which Sidekiq job arguments get reported to New Relic. To capture any Sidekiq arguments, 'job.sidekiq.args.*' must be added to the separate `:'attributes.include'` configuration option. Each string in this array will be turned into a regular expression via `Regexp.new` to permit advanced matching. For job argument hashes, if either a key or value matches the pair will be excluded. All matching job argument array elements and job argument scalars will be excluded. + ## Slow SQL [#slow-sql] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SLOW_SQL_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SLOW_SQL_ENABLED`
- If `true`, the agent collects [slow SQL queries](/docs/apm/applications-menu/monitoring/viewing-slow-query-details). + If `true`, the agent collects [slow SQL queries](/docs/apm/applications-menu/monitoring/viewing-slow-query-details). - + - - - - - - - - - - - + + +
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_SLOW_SQL_EXPLAIN_THRESHOLD`
TypeFloat
Default`0.5`
Environ variable`NEW_RELIC_SLOW_SQL_EXPLAIN_THRESHOLD`
- Specify a threshold in seconds. The agent collects [slow SQL queries](/docs/apm/applications-menu/monitoring/viewing-slow-query-details) and explain plans that exceed this threshold. + Specify a threshold in seconds. The agent collects [slow SQL queries](/docs/apm/applications-menu/monitoring/viewing-slow-query-details) and explain plans that exceed this threshold. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SLOW_SQL_EXPLAIN_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SLOW_SQL_EXPLAIN_ENABLED`
- If `true`, the agent collects explain plans in slow SQL queries. If this setting is omitted, the [`transaction_tracer.explain_enabled`](#transaction_tracer-explain_enabled) setting will be applied as the default setting for explain plans in slow SQL as well. + If `true`, the agent collects explain plans in slow SQL queries. If this setting is omitted, the [`transaction_tracer.explain_enabled`](#transaction_tracer-explain_enabled) setting will be applied as the default setting for explain plans in slow SQL as well. - + - - - - - - - - - - - + + +
TypeString
Default`obfuscated`
Environ variable`NEW_RELIC_SLOW_SQL_RECORD_SQL`
TypeString
Default`obfuscated`
Environ variable`NEW_RELIC_SLOW_SQL_RECORD_SQL`
- Defines an obfuscation level for slow SQL queries. Valid options are `obfuscated`, `raw`, or `none`. + Defines an obfuscation level for slow SQL queries. Valid options are `obfuscated`, `raw`, or `none`. - + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SLOW_SQL_USE_LONGER_SQL_ID`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_SLOW_SQL_USE_LONGER_SQL_ID`
- Generate a longer `sql_id` for slow SQL traces. `sql_id` is used for aggregation of similar queries. + Generate a longer `sql_id` for slow SQL traces. `sql_id` is used for aggregation of similar queries. + ## Span Events [#span-events] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SPAN_EVENTS_ENABLED`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_SPAN_EVENTS_ENABLED`
- If `true`, enables span event sampling. + If `true`, enables span event sampling. - + - - - - - - - - - - - + + +
TypeInteger
Default`10000`
Environ variable`NEW_RELIC_SPAN_EVENTS_QUEUE_SIZE`
TypeInteger
Default`10000`
Environ variable`NEW_RELIC_SPAN_EVENTS_QUEUE_SIZE`
- Sets the maximum number of span events to buffer when streaming to the trace observer. + Sets the maximum number of span events to buffer when streaming to the trace observer. - + - - - - - - - - - - - + + +
TypeInteger
Default`2000`
Environ variable`NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED`
TypeInteger
Default`2000`
Environ variable`NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED`
- * Defines the maximum number of span events reported from a single harvest. Any Integer between `1` and `10000` is valid.' - * When configuring the agent for [AI monitoring](/docs/ai-monitoring/intro-to-ai-monitoring), set to max value `10000`.This ensures the agent captures the maximum amount of distributed traces. + * Defines the maximum number of span events reported from a single harvest. Any Integer between `1` and `10000` is valid.' + * When configuring the agent for [AI monitoring](/docs/ai-monitoring/intro-to-ai-monitoring), set to max value `10000`.This ensures the agent captures the maximum amount of distributed traces. + + ## Strip Exception Messages [#strip-exception-messages] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_STRIP_EXCEPTION_MESSAGES_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_STRIP_EXCEPTION_MESSAGES_ENABLED`
- If true, the agent strips messages from all exceptions except those in the [allowlist](#strip_exception_messages-allowlist). Enabled automatically in [high security mode](/docs/accounts-partnerships/accounts/security/high-security). + If true, the agent strips messages from all exceptions except those in the [allowlist](#strip_exception_messages-allowlist). Enabled automatically in [high security mode](/docs/accounts-partnerships/accounts/security/high-security). - + - - - - - - - - - - - + + +
TypeString
Default`""`
Environ variable`NEW_RELIC_STRIP_EXCEPTION_MESSAGES_ALLOWED_CLASSES`
TypeString
Default`""`
Environ variable`NEW_RELIC_STRIP_EXCEPTION_MESSAGES_ALLOWED_CLASSES`
- Specify a list of exceptions you do not want the agent to strip when [strip_exception_messages](#strip_exception_messages-enabled) is `true`. Separate exceptions with a comma. For example, `"ImportantException,PreserveMessageException"`. + Specify a list of exceptions you do not want the agent to strip when [strip_exception_messages](#strip_exception_messages-enabled) is `true`. Separate exceptions with a comma. For example, `"ImportantException,PreserveMessageException"`. + ## Stripe [#stripe] + + - + + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_STRIPE_USER_DATA_INCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_STRIPE_USER_DATA_INCLUDE`
- An array of strings to specify which keys inside a Stripe event's `user_data` hash should be reported - to New Relic. Each string in this array will be turned into a regular expression via `Regexp.new` to - permit advanced matching. Setting the value to `["."]` will report all `user_data`. + An array of strings to specify which keys inside a Stripe event's `user_data` hash should be reported +to New Relic. Each string in this array will be turned into a regular expression via `Regexp.new` to +permit advanced matching. Setting the value to `["."]` will report all `user_data`. + - + - - - - - - - - - - - + + +
TypeArray
Default`[]`
Environ variable`NEW_RELIC_STRIPE_USER_DATA_EXCLUDE`
TypeArray
Default`[]`
Environ variable`NEW_RELIC_STRIPE_USER_DATA_EXCLUDE`
- An array of strings to specify which keys and/or values inside a Stripe event's `user_data` hash should - not be reported to New Relic. Each string in this array will be turned into a regular expression via - `Regexp.new` to permit advanced matching. For each hash pair, if either the key or value is matched the - pair will not be reported. By default, no `user_data` is reported, so this option should only be used if - the `stripe.user_data.include` option is being used. + An array of strings to specify which keys and/or values inside a Stripe event's `user_data` hash should +not be reported to New Relic. Each string in this array will be turned into a regular expression via +`Regexp.new` to permit advanced matching. For each hash pair, if either the key or value is matched the +pair will not be reported. By default, no `user_data` is reported, so this option should only be used if +the `stripe.user_data.include` option is being used. + + ## Thread Profiler [#thread-profiler] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_THREAD_PROFILER_ENABLED`
TypeBoolean
Default`false`
Environ variable`NEW_RELIC_THREAD_PROFILER_ENABLED`
- If `true`, enables use of the [thread profiler](/docs/apm/applications-menu/events/thread-profiler-tool). + If `true`, enables use of the [thread profiler](/docs/apm/applications-menu/events/thread-profiler-tool). + ## Utilization [#utilization] + + - + + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_AWS`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_AWS`
- If `true`, the agent automatically detects that it is running in an AWS environment. + If `true`, the agent automatically detects that it is running in an AWS environment. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_AZURE`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_AZURE`
- If `true`, the agent automatically detects that it is running in an Azure environment. + If `true`, the agent automatically detects that it is running in an Azure environment. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_DOCKER`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_DOCKER`
- If `true`, the agent automatically detects that it is running in Docker. + If `true`, the agent automatically detects that it is running in Docker. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_GCP`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_GCP`
- If `true`, the agent automatically detects that it is running in an Google Cloud Platform environment. + If `true`, the agent automatically detects that it is running in an Google Cloud Platform environment. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_KUBERNETES`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_KUBERNETES`
- If `true`, the agent automatically detects that it is running in Kubernetes. + If `true`, the agent automatically detects that it is running in Kubernetes. - + - - - - - - - - - - - + + +
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_PCF`
TypeBoolean
Default`true`
Environ variable`NEW_RELIC_UTILIZATION_DETECT_PCF`
- If `true`, the agent automatically detects that it is running in a Pivotal Cloud Foundry environment. + If `true`, the agent automatically detects that it is running in a Pivotal Cloud Foundry environment. - + + \ No newline at end of file From 96fd1c98768e9da717be03a85fe1a4f498729c53 Mon Sep 17 00:00:00 2001 From: newrelic-ruby-agent-bot Date: Thu, 22 Aug 2024 18:25:39 +0000 Subject: [PATCH 08/18] chore(ruby agent): add release notes --- .../ruby-release-notes/ruby-agent-9-13-0.mdx | 55 +++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 src/content/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-13-0.mdx diff --git a/src/content/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-13-0.mdx b/src/content/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-13-0.mdx new file mode 100644 index 00000000000..44350043a35 --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-13-0.mdx @@ -0,0 +1,55 @@ +--- +subject: Ruby agent +releaseDate: '2024-08-22' +version: 9.13.0 +downloadLink: https://rubygems.org/downloads/newrelic_rpm-9.13.0.gem +features: ["Enhance AWS Lambda function instrumentation", "Add experimental OpenSearch instrumentation", "Improve framework detection accuracy for Grape and Padrino", "Silence Bundler `all_specs` deprecation warning"] +bugs: ["Fix Falcon dispatcher detection", "Fix for a Redis instrumentation error when Redis::Cluster::Client is present", "Address JRuby concurrency issue with config hash accessing"] +security: [] +--- + + + We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about [keeping agents up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/). + + See the New Relic Ruby agent [EOL policy](https://docs.newrelic.com/docs/apm/agents/ruby-agent/getting-started/ruby-agent-eol-policy/) for information about agent releases and support dates. + + +## v9.13.0 + +Version 9.13.0 enhances support for AWS Lambda functions, adds experimental OpenSearch instrumentation, updates framework detection, silences a Bundler deprecation warning, fixes Falcon dispatcher detection, fixes a bug with Redis instrumentation installation, and addresses a JRuby-specific concurrency issue. + +- **Feature: Enhance AWS Lambda function instrumentation** + +When utilized via the latest [New Relic Ruby layer for AWS Lambda](https://layers.newrelic-external.com/), the agent now offers enhanced support for AWS Lambda function instrumentation. +* The agent's instrumentation for AWS Lambda functions now supports distributed tracing. +* Web-triggered invocations are now identified as being "web"-based when an API Gateway call is involved, with support for both API Gateway versions 1.0 and 2.0. +* Web-based calls have the HTTP method, URI, and status code recorded. +* The agent now recognizes and reports on 12 separate AWS resources that are capable of triggering a Lambda function invocation: ALB, API Gateway V1, API Gateway V2, CloudFront, CloudWatch Scheduler, DynamoStreams, Firehose, Kinesis, S3, SES, SNS, and SQS. +* The type of the triggering resource and its ARN will be recorded for each resource, and for many of them, extra resource-specific attributes will be recorded as well. For example, Lambda function invocations triggered by S3 bucket activity will now result in the S3 bucket name being recorded. +[PR#2811](https://github.com/newrelic/newrelic-ruby-agent/pull/2811) + +- **Feature: Add experimental OpenSearch instrumentation** + + The agent will now automatically instrument the `opensearch-ruby` gem. We're marking this instrumentation as experimental because more work is needed to fully test it. OpenSearch instrumentation provides telemetry similar to Elasticsearch. Thank you, [@Earlopain](https://github.com/Earlopain) for reporting the issue and [@praveen-ks](https://github.com/praveen-ks) for an initial draft of the instrumentation. [Issue#2228](https://github.com/newrelic/newrelic-ruby-agent/issues/2228) [PR#2796](https://github.com/newrelic/newrelic-ruby-agent/pull/2796) + +- **Feature: Improve framework detection accuracy for Grape and Padrino** + + Previously, applications using the Grape framework would set `ruby` as their framework within the Environment Report. Now, Grape applications will be set to `grape`. Similarly, applications using the Padrino framework would be set to `sinatra`. Now, they will be set to `padrino`. This will help the New Relic security agent compatibility checks. Thank you, [@prateeksen](https://github.com/prateeksen) for making this change. [Issue#2777](https://github.com/newrelic/newrelic-ruby-agent/issues/2777) [PR#2789](https://github.com/newrelic/newrelic-ruby-agent/pull/2789) + +- **Feature: Silence Bundler `all_specs` deprecation warning** + + `Bundler.rubygems.all_specs` was deprecated in favor of `Bundler.rubygems.installed_specs` in Bundler versions 2+, causing the agent to emit deprecation warnings. The method has been updated when Bundler 2+ is detected and warnings are now silenced. Thanks to [@jcoyne](https://github.com/jcoyne) for reporting this issue. [Issue#2733](https://github.com/newrelic/newrelic-ruby-agent/issues/2733) [PR#2823](https://github.com/newrelic/newrelic-ruby-agent/pull/2823) + +- **Bugfix: Fix Falcon dispatcher detection** + + Previously, we tried to use the object space to determine whether the [Falcon web server](https://github.com/socketry/falcon) was in use. However, Falcon is not added to the object space until after the environment report is generated, resulting in a `nil` dispatcher. Now, we revert to an earlier strategy that discovered the dispatcher using `File.basename`. Thank you, [@prateeksen](https://github.com/prateeksen) for reporting this issue and researching the problem. [Issue#2778](https://github.com/newrelic/newrelic-ruby-agent/issues/2778) [PR#2795](https://github.com/newrelic/newrelic-ruby-agent/pull/2795) + +- **Bugfix: Fix for a Redis instrumentation error when Redis::Cluster::Client is present** + + The Redis instrumentation previously contained a bug that would cause it to error out when `Redis::Cluster::Client` was present, owing to the use of a Ruby `return` outside of a method. Thanks very much to [@jdelStrother](https://github.com/jdelStrother) for not only reporting this bug but pointing us to the root cause as well. [Issue#2814](https://github.com/newrelic/newrelic-ruby-agent/issues/2814) [PR#2816](https://github.com/newrelic/newrelic-ruby-agent/pull/2816) + +- **Bugfix: Address JRuby concurrency issue with config hash accessing** + + The agent's internal configuration class maintains a hash that occassionally gets rebuilt. During the rebuild, certain previously dynamically determined instrumentation values are preserved for the benefit of the [New Relic Ruby security agent](https://github.com/newrelic/csec-ruby-agent). After reports from JRuby customers regarding concurrency issues related to the hash being accessed while being modified, two separate fixes went into the hash rebuild logic previously: a `Hash#dup` operation and a `synchronize do` block. But errors were still reported. We ourselves remain unable to reproduce these concurrency errors despite using the same exact versions of JRuby and all reported software. After confirming that the hash access code in question is only needed for the Ruby security agent (which operates only in non-production dedicated security testing environments), we have introduced a new fix for JRuby customers that will simply skip over the troublesome code when JRuby is in play but the security agent is not. [PR#2798](https://github.com/newrelic/newrelic-ruby-agent/pull/2798) + + From 3bf10fc62e9e80753e15ff63a704a23ffbf6c7d4 Mon Sep 17 00:00:00 2001 From: ndesai Date: Thu, 22 Aug 2024 14:14:38 -0500 Subject: [PATCH 09/18] docs:Hybrid Release Notes Update --- .../capacitor-agent-151.mdx | 15 +++++++++++++ .../flutter-agent-112.mdx | 21 ++++++++++++++++++ .../net-maui-agent-111.mdx | 22 +++++++++++++++++++ .../react-native-agent-143mdx | 15 +++++++++++++ 4 files changed, 73 insertions(+) create mode 100644 src/content/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-151.mdx create mode 100644 src/content/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-112.mdx create mode 100644 src/content/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-111.mdx create mode 100644 src/content/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-143mdx diff --git a/src/content/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-151.mdx b/src/content/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-151.mdx new file mode 100644 index 00000000000..e812a411a53 --- /dev/null +++ b/src/content/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-151.mdx @@ -0,0 +1,15 @@ +--- +subject: Capacitor agent +releaseDate: '2024-08-21' +version: 1.5.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/newrelic-capacitor-plugin/v/1.5.1' +--- + +## New Features + +1. **Distributed Tracing Control** + - Introducing a new feature flag: `distributedTracingEnabled`, providing the ability to enable or disable distributed tracing functionality. + +## Bug Fixes + +- Resolved an issue where the web implementation was not functioning while using the logs API. diff --git a/src/content/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-112.mdx b/src/content/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-112.mdx new file mode 100644 index 00000000000..6abafbd041c --- /dev/null +++ b/src/content/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-112.mdx @@ -0,0 +1,21 @@ +--- +subject: Flutter agent +releaseDate: '2024-08-21' +version: 1.1.2 +downloadLink: 'https://pub.dev/packages/newrelic_mobile/versions/1.1.2' +--- + +## Improvements + +1. **Agent LogLevel Configuration** + - Implemented the capability to define the agent log level as `verbose`, `info`, `warn`, `debug`, or `error` through the `loglevel` configuration. + - The default log level is set to `debug`. + +2. **Added CollectorAddress and CrashCollectorAddress Configuration** + - Introduced functionality to specify the collector address and crash collector address by utilizing the `collectorAddress` and `crashCollectorAddress` configuration options. + +3. **Added Support For Applying Gradle Plugin Using Plugins DSL** + - Added support for applying the New Relic Gradle plugin using the plugins DSL in the `build.gradle` file. + +## Bug Fixes +- Resolved an issue where the interactionTracing Feature Flag failed to prevent the collection of auto interaction metrics. diff --git a/src/content/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-111.mdx b/src/content/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-111.mdx new file mode 100644 index 00000000000..5e266873506 --- /dev/null +++ b/src/content/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-111.mdx @@ -0,0 +1,22 @@ +--- +subject: .NET MAUI agent +releaseDate: '2024-07-18' +version: 1.1.0 +downloadLink: 'https://www.nuget.org/packages/NewRelic.MAUI.Plugin' +--- + +## New Features + +1. **Support for .Net 8.0** + - The plugin now includes compatibility and support for .Net 8.0. + +2. **Added Record Handle Exception API with Attributes** + - Introduced an API to record and handle exceptions along with their respective attributes. + +## Improvements + +- **Native Android Agent Updated to Version 7.5.1** + - The native Android agent has been upgraded to version 7.5.1, incorporating the latest enhancements and optimizations. + +- **Native iOS Agent Updated to Version 7.5.1** + - The native iOS agent has been upgraded to version 7.5.1, providing improved functionality and performance optimizations. diff --git a/src/content/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-143mdx b/src/content/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-143mdx new file mode 100644 index 00000000000..ed3438f4e8f --- /dev/null +++ b/src/content/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-143mdx @@ -0,0 +1,15 @@ +--- +subject: React Native agent +releaseDate: '2024-08-21' +version: 1.4.1 +downloadLink: 'https://www.npmjs.com/package/newrelic-react-native-agent/v/1.4.3' +--- + +## New Features + +1. **Distributed Tracing Control** + - Introducing a new feature flag: `distributedTracingEnabled`, providing the ability to enable or disable distributed tracing functionality. + +## Bug Fixes + +- Addressed an issue where console debug logs were incorrectly displayed as console errors. From b48fcc9cc795b4ccac9cad3d1b443091b210e9c3 Mon Sep 17 00:00:00 2001 From: ndesai Date: Thu, 22 Aug 2024 14:16:33 -0500 Subject: [PATCH 10/18] docs: hybrid release notes update --- .idea/other.xml | 252 ------------------------------------------------ 1 file changed, 252 deletions(-) delete mode 100644 .idea/other.xml diff --git a/.idea/other.xml b/.idea/other.xml deleted file mode 100644 index 4604c44601d..00000000000 --- a/.idea/other.xml +++ /dev/null @@ -1,252 +0,0 @@ - - - - - - \ No newline at end of file From 54e2a782937e9f9b29f08272e6a06be10e421b07 Mon Sep 17 00:00:00 2001 From: Sunny Zanchi Date: Thu, 22 Aug 2024 17:29:17 -0400 Subject: [PATCH 11/18] bump `@newrelic/gatsby-theme-newrelic` to 9.8.1 --- package.json | 2 +- yarn.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index 32455b139e4..6f6732e848c 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.0", + "@newrelic/gatsby-theme-newrelic": "9.8.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 c5d02bec574..b90b3f7acc5 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.0": - version "9.8.0" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.8.0.tgz#d357c34a0180b93c278d49527ca1993cdaef5c98" - integrity sha512-LPjKvFiNxJmlNVdlzftXK2DosBZbfEfqEQwt2jVbVtVd5NJaHZ61OXr451LxfHEcI6sU5Hyg4t9qvEafCHkctg== +"@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== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" From 7a8b53fcc155f4a5fdb78ebe0d9c52d949ef3e06 Mon Sep 17 00:00:00 2001 From: Clark McAdoo Date: Thu, 22 Aug 2024 16:45:38 -0500 Subject: [PATCH 12/18] fix: update translation json to have correct links in onboarding for i18n sites --- src/i18n/translations/es/translation.json | 36 ++----------------- src/i18n/translations/jp/translation.json | 36 ++----------------- src/i18n/translations/kr/translation.json | 44 ++++++----------------- src/i18n/translations/pt/translation.json | 36 ++----------------- 4 files changed, 19 insertions(+), 133 deletions(-) diff --git a/src/i18n/translations/es/translation.json b/src/i18n/translations/es/translation.json index b7f7d5f47a3..82afbec5f82 100644 --- a/src/i18n/translations/es/translation.json +++ b/src/i18n/translations/es/translation.json @@ -49,23 +49,20 @@ "text": "¿No tienes una cuenta?", "title": "Crea una cuenta" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", + "docsHref": "https://docs.newrelic.com/es/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "Comenzar", "text": "¿Quieres obtener más información sobre las herramientas de monitoreo y observabilidad de New Relic?", "title": "Introducción a New Relic" }, - { "button": "Instalar", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "Ve directo a la IU y configura New Relic para instrumentar tu stack de tecnología.", "title": "Instala New Relic" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", + "docsHref": "https://docs.newrelic.com/es/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "Lee los tutoriales", "text": "Algunas maneras comunes de usar New Relic para resolver problemas del mundo real.", "title": "Tutoriales" @@ -95,14 +92,12 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, - { "title": "Tutoriales y recorridos", "text": "Aprovecha nuestros tutoriales elaborados cuidadosamente y descubre soluciones para problemas comunes.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, - { "title": "Guías y mejores prácticas", "text": "Obtén más información acerca de la IU de la plataforma y las aplicaciones para móviles.", @@ -120,70 +115,60 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, - { "title": "Monitoreo del rendimiento de aplicaciones (APM)", "text": "Monitorea el rendimiento de las aplicaciones en todo tu stack. Contamos con agentes para Go, Java, .NET, Node.js, PHP, Python y Ruby.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, - { "title": "Monitoreo de browser", "text": "Logra una comprensión más profunda de cómo está rindiendo tu sitio web y cómo los usuarios utilizan tu sitio.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, - { "title": "Monitoreo de infraestructura", "text": "Obtén visibilidad de los hosts, contenedores, proveedores, red e infraestructura.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, - { "title": "Monitoreo de Kubernetes", "text": "Observa el estado y el rendimiento completos de tus clústeres y cargas de trabajo.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, - { "title": "Administración de logs", "text": "Organiza todos tus logs en un solo lugar gracias a las herramientas de reenvío de logs de uso común. Incluye privacidad, análisis y archivado de logs para almacenamiento de largo plazo.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, - { "title": "Monitoreo de móviles", "text": "Conoce el rendimiento de tus aplicaciones móviles, desde la experiencia del frontend hasta las métricas de ejecución del backend.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, - { "title": "Monitoreo del rendimiento de modelos (MLOps)", "text": "Analiza el rendimiento y la eficacia de los modelos de aprendizaje automático.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, - { "title": "Monitoreo de redes", "text": "Mapea tu red para que puedas analizar, optimizar y resolver problemas de rendimiento de tus enrutadores, conmutadores y otros dispositivos de red.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, - { "title": "Monitoreo de funciones serverless", "text": "Monitorea las funciones de AWS Lambda Serverless a través de los datos de CloudWatch y la instrumentación a nivel de código.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, - { "title": "Monitoreo sintético", "text": "Simula la actividad del usuario final y las llamadas API desde distintos lugares alrededor del mundo para que puedas detectar problemas antes que tus usuarios.", @@ -201,35 +186,30 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, - { "title": "Seguimiento de cambios", "text": "Haz seguimiento de los cambios en tu sistema, como los despliegues, para ver cómo afectan el rendimiento", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, - { "title": "Gráficos, dashboards y consultas", "text": "Utiliza gráficos y dashboards para visualizar los datos. Comienza con nuestros dashboards prediseñados o utiliza nuestras potentes herramientas de consulta para crear los tuyos.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, - { "title": "Rastreo distribuido", "text": "Descubre cómo fluyen los datos a lo largo del sistema y detecta con precisión dónde se ralentizan las cosas. Detecta, corrige y optimiza el rendimiento del sistema y de la aplicación.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, - { "title": "NRQL", "text": "Profundiza en tus datos con New Relic Query Language (NRQL) y obtén respuestas precisas e información basada en datos.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, - { "title": "Administración a nivel de servicio", "text": "Establece y mide los SLI y SLO para ver cómo están rindiendo tus equipos y tus métricas de negocio clave.", @@ -247,35 +227,30 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, - { "title": "Errors Inbox", "text": "Detecta, comparte y corrige errores de desarrollo de software en un solo lugar.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, - { "title": "Pruebas de seguridad de aplicaciones interactivas (IAST)", "text": "Detecta, verifica y corrige las vulnerabilidades de alto riesgo en todo el ciclo de vida de desarrollo de software. Completamente integrado con la gestión de vulnerabilidades.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, - { "title": "Otras integraciones", "text": "Integra las tecnologías de las que dependes, como OpenTelemetry, Grafana y CloudFoundry, así como otras integraciones populares.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, - { "title": "Gestión de vulnerabilidades", "text": "Examina tus aplicaciones, entidades y bibliotecas de software en busca de vulnerabilidades de seguridad y toma las medidas necesarias para corregir y reducir los riesgos.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, - { "title": "Monitoreo del rendimiento de sitios web", "text": "Mantén tus sitios web rápidos y sin errores, mejora la experiencia del cliente y aumenta las tasas de conversión.", @@ -293,7 +268,6 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, - { "title": "¿Qué hay de nuevo?", "text": "Mantente informado sobre las nuevas características, actualizaciones y cambios en nuestra plataforma.", @@ -311,28 +285,24 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, - { "title": "Datos y API", "text": "Obtén más información sobre NRDB, nuestra base de datos de New Relic, así como detalles de métricas y tipos de datos de eventos, cómo administramos los datos y cómo usar nuestras API.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, - { "title": "Diccionario de datos", "text": "Busca definiciones para nuestros atributos en una variedad de fuentes de datos y tipos de datos.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, - { "title": "Seguridad y privacidad", "text": "Entérate de cómo New Relic gestiona la seguridad y privacidad de los datos y sobre nuestra certificación de cumplimiento.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, - { "title": "Licencias", "text": "Una biblioteca de referencia donde encontrarás nuestras licencias y otra documentación legal.", @@ -391,4 +361,4 @@ "freeTextQuestion": "¿Hay algo que tú cambiarías sobre los documentos de New Relic? Si hay algo, te agradeceríamos que nos compartieras qué es y por qué piensas así." } } -} +} \ No newline at end of file diff --git a/src/i18n/translations/jp/translation.json b/src/i18n/translations/jp/translation.json index 96d4c0b6bb1..8b936117708 100644 --- a/src/i18n/translations/jp/translation.json +++ b/src/i18n/translations/jp/translation.json @@ -49,23 +49,20 @@ "text": "まだアカウントをお持ちでありませんか？", "title": "アカウントを作成" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", + "docsHref": "https://docs.newrelic.com/jp/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "スタートガイド", "text": "New Relicの監視およびオブザーバビリティツールの詳細をご覧ください", "title": "New Relicの概要" }, - { "button": "インストール", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "UIに移動し、New Relicを設定して技術スタックを計装する", "title": "New Relicのインストール" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", + "docsHref": "https://docs.newrelic.com/jp/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "チュートリアルを読む", "text": "New Relicを使用して現実的問題を解決する一般的な方法", "title": "チュートリアル" @@ -95,14 +92,12 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, - { "title": "チュートリアルと段階的な説明", "text": "丁寧なチュートリアルを利用して、よくある問題に関するソリューションを段階的に確認。", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, - { "title": "ガイドとベストプラクティス", "text": "プラットフォームUIとモバイルアプリの詳細はこちら。", @@ -120,70 +115,60 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, - { "title": "アプリケーションパフォーマンスモニタリング（APM）", "text": "スタック全体のアプリケーションパフォーマンスを監視。Go、Java、.NET、Node.js、PHP、Python、Rubyのエージェントがサポートされています。", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, - { "title": "ブラウザのモニタリング", "text": "ウェブサイトのパフォーマンスとユーザーのサイト使用状況に関するインサイトを入手。", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, - { "title": "インフラストラクチャモニタリング", "text": "ホスト、コンテナ、プロバイダー、ネットワーク、インフラストラクチャへの可視性を獲得。", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, - { "title": "Kubernetes監視", "text": "クラスタとワークロードの完全な健全性とパフォーマンスを監視。", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, - { "title": "ログ管理", "text": "一般的なログ転送ツールのサポートですべてのログを1か所に集約。プライバシー、解析、ログアーカイブを長期保存に含めましょう。", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, - { "title": "モバイルのモニタリング", "text": "フロントのエクスペリエンスからバックエンドの実行メトリクスまで、モバイルアプリのパフォーマンスに関するインサイトを獲得。", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, - { "title": "モデルパフォーマンスモニタリング（MLOps）", "text": "機械学習モデルのパフォーマンスと効果性を分析。", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, - { "title": "ネットワークモニタリング", "text": "ネットワークをマッピングして、ルーター、スイッチその他ネットワークデバイスのパフォーマンスの分析、最適化、トラブルシューティングが行えます。", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, - { "title": "サーバーレス機能の監視", "text": "CloudWatchデータとコードレベルの計装を使用して、サーバレスAWS Lambda関数を監視。", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, - { "title": "合成モニタリング", "text": "世界各地のロケーションのエンドユーザーアクティビティとAPIコールをシミュレーションし、ユーザーよりも早く問題を発見できます。", @@ -201,35 +186,30 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, - { "title": "Change Tracking (変更追跡機能)", "text": "デプロイメントなどのシステム内の変更を追跡し、パフォーマンスにどう影響するかを確認", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, - { "title": "チャート、ダッシュボード、クエリ", "text": "チャートやダッシュボードを使用してデータを可視化。ビルド済みダッシュボードで始めるか、パワフルなクエリツールを使用して独自に構築。", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, - { "title": "ディストリビューティッド（分散）トレーシング", "text": "システム全体のデータフローを確認し、遅延している箇所を特定。システムとアプリケーションパフォーマンスを特定、修正、最適化。", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, - { "title": "NRQL", "text": "New Relicクエリ言語（NRQL）でデータの詳細を確認し、正確な答えとデータドリブンなインサイトを入手。", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, - { "title": "サービスレベル管理", "text": "SLIとSLOを設定、測定し、チームと主要なビジネスメトリクスのパフォーマンスを確認。", @@ -247,35 +227,30 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, - { "title": "エラーインボックス", "text": "ソフトウェア開発時のエラーを1か所で特定、共有、修正。", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, - { "title": "インタラクティブ・アプリケーション・セキュリティ・テスト（IAST）", "text": "ソフトウェア開発ライフサイクル全体にわたるハイリスクな脆弱性を発見、検証、修正。脆弱性管理との完全なインテグレーション。", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, - { "title": "その他のインテグレーション", "text": "OpenTelemetry、Grafana、CloudFoundry、その他一般的なインテグレーションなど、使用しているテクノロジーとの統合が可能。", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, - { "title": "脆弱性管理", "text": "アプリケーション、エンティティ、ソフトウェアライブラリのセキュリティに関する脆弱性を監査し、修正アクションを実行してリスクを低減。", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, - { "title": "ウェブサイトパフォーマンスの監視", "text": "ウェブサイトを動作が早くエラーのない状態に保ち、顧客エクスペリエンスとコンバージョン率を向上。", @@ -293,7 +268,6 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, - { "title": "新機能", "text": "新機能、アップデート、プラットフォームの変更に関し、最新の状態を維持。", @@ -311,28 +285,24 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, - { "title": "データとAPI", "text": "New RelicのデータベースであるNRDBについて、またメトリクスやイベントのデータタイプの詳細、データの管理方法、APIの使用方法について確認。", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, - { "title": "データ辞書", "text": "さまざまなデータソースとデータタイプの属性の定義を確認。", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, - { "title": "セキュリティとプライバシー", "text": "New Relicがデータセキュリティとプライバシーにどう対応しているか、またNew Relicのコンプライアンス認証について確認しましょう。", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, - { "title": "ライセンス", "text": "ライセンスとその他の法的ドキュメンテーションの参照ライブラリ。", @@ -391,4 +361,4 @@ "freeTextQuestion": "New Relicのドキュメントについて何か変更のご希望はありますか？ある場合は、その内容とその理由を教えてください。" } } -} +} \ No newline at end of file diff --git a/src/i18n/translations/kr/translation.json b/src/i18n/translations/kr/translation.json index c5b17cadb1b..ee10ca9da17 100644 --- a/src/i18n/translations/kr/translation.json +++ b/src/i18n/translations/kr/translation.json @@ -30,7 +30,13 @@ "pageTitle": "뉴렐릭 문서에 오신 것을 환영합니다.", "search": { "popularSearches": { - "options": ["NRQL", "로그", "알림", "모범 사례", "쿠버네티스"], + "options": [ + "NRQL", + "로그", + "알림", + "모범 사례", + "쿠버네티스" + ], "title": "자주 찾는 검색" }, "placeholder": "검색" @@ -43,23 +49,20 @@ "text": "계정이 없으신가요?", "title": "계정 생성하기" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", + "docsHref": "https://docs.newrelic.com/kr/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "시작하기", "text": "뉴렐릭의 모니터링 및 옵저버빌리티 툴에 대해 자세히 알고 싶으신가요?", "title": "뉴렐릭 소개" }, - { "button": "설치", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "UI로 이동하여 뉴렐릭을 설정하고 기술 스택을 계측해 보십시오.", "title": "뉴렐릭 설치" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", + "docsHref": "https://docs.newrelic.com/kr/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "튜토리얼 보기", "text": "뉴렐릭은 실질적인 문제를 해결하는 보편적인 방법입니다.", "title": "튜토리얼" @@ -89,14 +92,12 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, - { "title": "튜토리얼 및 도움말", "text": "뉴렐릭의 튜토리얼에서 자주 발생하는 문제를 어떻게 해결할 수 있는지 살펴보십시오.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, - { "title": "가이드 및 모범 사례", "text": "플랫폼 UI와 모바일 앱에 대해 자세히 알아보십시오.", @@ -114,70 +115,60 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, - { "title": "애플리케이션 성능 모니터링(APM)", "text": "전체 스택에서 애플리케이션 성능을 모니터링할 수 있습니다.뉴렐릭은 Go, Java, .NET, Node.js,PHP, Python, Ruby를 위한 에이전트를 제공합니다.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, - { "title": "브라우저 모니터링", "text": "웹사이트의 성능과 사용자가 사이트를 사용하는 방식에 대한 인사이트를 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, - { "title": "인프라 모니터링", "text": "호스트, 컨테이너, 공급자, 네트워크 및 인프라에 대한 가시성을 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, - { "title": "쿠버네티스 모니터링", "text": "클러스터와 워크로드의 전체 상태와 성능을 자세히 살펴볼 수 있습니다.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, - { "title": "로그 관리", "text": "보편적인 로그 전달 툴을 모두 지원하기 때문에 모든 로그를 한 곳에 모아 확인할 수 있습니다. 개인정보 보호, 구문 분석, 장기 보관을 위한 로그 아카이브도 포함됩니다.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, - { "title": "모바일 모니터링", "text": "프런트엔드 경험부터 백엔드 실행 지표까지 모바일 앱의 성능에 대한 인사이트를 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, - { "title": "모델 성능 모니터링(MLOps)", "text": "머신 러닝 모델의 성능과 효율성을 분석할 수 있습니다.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, - { "title": "네트워크 모니터링", "text": "네트워크를 매핑하여 라우터, 스위치 및 기타 네트워킹 장치의 성능을 분석, 문제 해결, 최적화할 수 있습니다.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, - { "title": "서버리스 기능 모니터링", "text": "CloudWatch 데이터와 코드 레벨 계측을 사용해 서버리스 AWS Lambda 함수를 모니터링할 수 있습니다.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, - { "title": "신세틱 모니터링", "text": "전 세계 위치에서 엔드유저 활동과 API 호출을 시뮬레이션하여 사용자보다 먼저 문제를 발견할 수 있습니다.", @@ -195,35 +186,30 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, - { "title": "변경 추적", "text": "새로운 배포를 포함해 시스템의 변경 사항을 추적하여 성능에 미치는 영향을 파악할 수 있습니다.", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, - { "title": "차트, 대시보드 및 쿼리", "text": "차트와 대시보드를 사용해 데이터를 시각화할 수 있습니다. 사전 구축된 대시보드로 시작하거나 강력한 쿼리 툴을 사용해 맞춤화된 대시보드를 구축할 수 있습니다.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, - { "title": "분산 추적", "text": "시스템 전체에서 데이터 흐름을 확인하고 속도가 느려지고 있는 위치를 식별할 수 있습니다. 시스템과 애플리케이션의 성능을 확인하고 문제를 수정하여 최적화할 수 있습니다.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, - { "title": "NRQL", "text": "뉴렐릭 쿼리 언어(NRQL)을 사용해 데이터를 심층적으로 분석하고 정확한 답변과 데이터 기반 인사이트를 얻을 수 있습니다.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, - { "title": "서비스 레벨 관리", "text": "SLI과 SLO를 설정하고 측정하여 팀과 주요 비즈니스 메트릭의 상태를 확인할 수 있습니다.", @@ -241,35 +227,30 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, - { "title": "Errors inbox", "text": "한 곳에서 소프트웨어 개발 오류를 찾아 공유하고 수정할 수 있습니다.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, - { "title": "인터랙티브 애플리케이션 보안 테스트(IAST)", "text": "소프트웨어 개발 수명주기 전반에서 고위험 취약점을 찾아 확인하고 수정할 수 있습니다. 취약점 관리와 완전하게 통합됩니다.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, - { "title": "기타 통합", "text": "OpenTelemetry, Grafana, CloudFoundry 및 기타 널리 사용되는 기술을 통합할 수 있습니다.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, - { "title": "취약점 관리", "text": "애플리케이션, 엔터티 및 소프트웨어 라이브러리에서 보안 취약점 여부를 감사하고 위험을 해결 및 완화할 수 있는 조치를 취할 수 있습니다.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, - { "title": "웹사이트 성능 모니터링", "text": "웹사이트가 오류 없이 신속하게 로드되도록 하여 고객 경험과 구매 전환율을 향상할 수 있습니다.", @@ -287,7 +268,6 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, - { "title": "새로운 사항", "text": "플랫폼의 새로운 기능, 업데이트 및 변경 사항에 대한 최신 정보를 받아볼 수 있습니다.", @@ -305,28 +285,24 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, - { "title": "데이터 및 API", "text": "뉴렐릭 데이터베이스(NRDB)에 대해 자세히 알아보고 메트릭과 이벤트 데이터 유형, 데이터 관리 방법, API 사용 방법에 대한 세부 정보를 확인할 수 있습니다.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, - { "title": "데이터 사전", "text": "다양한 데이터 소스와 데이터 유형에서 속성의 정의를 확인할 수 있습니다.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, - { "title": "보안 및 개인정보 보호", "text": "뉴렐릭의 개인정보 처리 및 데이터 보안 방법을 확인하고 규정 준수 인증에 대해 알아볼 수 있습니다.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, - { "title": "라이선스", "text": "라이선스와 기타 법률 문서가 포함된 참조 라이브러리입니다.", @@ -385,4 +361,4 @@ "freeTextQuestion": "뉴렐릭 문서와 관련해 바뀌었으면 하는 점이 있으신가요? 있으시면, 어떤 점인지 그리고 왜 그렇게 생각하는지를 말씀해주세요." } } -} +} \ No newline at end of file diff --git a/src/i18n/translations/pt/translation.json b/src/i18n/translations/pt/translation.json index d1a2339d9e4..5b0d7b67eb4 100644 --- a/src/i18n/translations/pt/translation.json +++ b/src/i18n/translations/pt/translation.json @@ -49,23 +49,20 @@ "text": "Ainda não tem uma conta?", "title": "Criar uma conta" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", + "docsHref": "https://docs.newrelic.com/pt/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "Começar", "text": "Quer saber mais sobre as ferramentas de monitoramento e observabilidade da New Relic?", "title": "Introdução à New Relic" }, - { "button": "Instalar", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "Acesse a interface e configure a New Relic para instrumentar seu stack de tecnologia.", "title": "Instale a New Relic" }, - { - "docsHref": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", + "docsHref": "https://docs.newrelic.com/pt/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "Ler nossos tutoriais", "text": "Maneiras comuns de usar a New Relic para resolver problemas do mundo real.", "title": "Tutoriais" @@ -95,14 +92,12 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, - { "title": "Tutoriais e guias passo a passo", "text": "Use nossos tutoriais com orientações passo a passo para a solução de problemas comuns.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, - { "title": "Guias e práticas recomendadas", "text": "Saiba mais sobre a interface da plataforma e os aplicativos para dispositivos móveis.", @@ -120,70 +115,60 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, - { "title": "Monitoramento do desempenho de aplicativos (APM)", "text": "Monitore o desempenho do aplicativo em todo o seu stack. Temos agentes para Go, Java, .NET, Node.js, PHP, Python e Ruby.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, - { "title": "Monitoramento de Browser", "text": "Tenha insights sobre como está o desempenho do seu website e como os usuários estão interagindo com ele.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, - { "title": "Monitoramento de infraestrutura", "text": "Tenha visibilidade de hosts, contêineres, fornecedores, rede e infraestrutura.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, - { "title": "Monitoramento de Kubernetes", "text": "Observe a saúde completa e o desempenho de seus clusters e workloads.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, - { "title": "Gerenciamento de logs", "text": "Organize todos os seus logs em um só lugar, com suporte para ferramentas comuns de encaminhamento de logs. Inclui privacidade, análise e arquivos de logs para armazenamento a longo prazo.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, - { "title": "Monitoramento de Mobile", "text": "Tenha insights de desempenho dos seus aplicativos para dispositivos móveis, desde a experiência de frontend até as métricas de execução de backend.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, - { "title": "Monitoramento de desempenho do modelo (MLOps)", "text": "Analise o desempenho e a eficácia dos modelos de machine learning.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, - { "title": "Monitoramento de rede", "text": "Mapeie sua rede para analisar, otimizar e resolver problemas de desempenho dos seus roteadores, comutadores e outros dispositivos de rede.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, - { "title": "Monitoramento de função serverless", "text": "Monitore suas funções do AWS Lambda serverless usando dados do CloudWatch e instrumentação no nível do código.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, - { "title": "Monitoramento sintético", "text": "Simule atividades do usuário final e chamadas de API de locais ao redor do mundo para encontrar problemas antes que os usuários os encontrem.", @@ -201,35 +186,30 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, - { "title": "Monitoramento de alterações", "text": "Monitore as alterações no seu sistema, como implantações, para saber como afetam o desempenho.", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, - { "title": "Gráficos, dashboards e consultas", "text": "Use gráficos e dashboards para visualizar seus dados. Comece com nossos dashboards predefinidos ou use nossas ferramentas de consulta poderosas para criar seus próprios dashboards.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, - { "title": "Trace distribuído (Distributed Tracing)", "text": "Veja como os dados fluem no seu sistema e identifique onde estão ficando mais lentos. Encontre, corrija e otimize o desempenho do aplicativo e do sistema.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, - { "title": "NRQL", "text": "Aprofunde-se nos seus dados com nossa New Relic Query Language (NRQL) e tenha respostas precisas e insights orientados por dados.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, - { "title": "Gerenciamento a nível de serviço", "text": "Defina e meça SLIs e SLOs para saber como está o desempenho das suas equipes e principais métricas de negócios.", @@ -247,35 +227,30 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, - { "title": "Errors Inbox", "text": "Encontre, compartilhe e corrija erros de desenvolvimento de software em um só lugar.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, - { "title": "Teste de segurança de aplicativo interativo (IAST)", "text": "Encontre, verifique e corrija vulnerabilidades de alto risco ao longo do ciclo de vida de desenvolvimento do seu software. Totalmente integrado com o gerenciamento de vulnerabilidades.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, - { "title": "Outras integrações", "text": "Integre tecnologias das quais você depende, como OpenTelemetry, Grafana, CloudFoundry e outras integrações populares.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, - { "title": "Gerenciamento de vulnerabilidades", "text": "Faça a auditoria de seus aplicativos, entidades e bibliotecas de software em busca de vulnerabilidades de segurança e aja para corrigir e reduzir erros.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, - { "title": "Monitoramento do desempenho de sites", "text": "Mantenha seus websites rápidos e sem erros, melhore a experiência do cliente e suas taxas de conversão.", @@ -293,7 +268,6 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, - { "title": "O que há de novo?", "text": "Fique por dentro de novos recursos, atualizações e alterações na nossa plataforma.", @@ -311,28 +285,24 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, - { "title": "Dados e APIs", "text": "Saiba mais sobre o NRDB, nosso banco de dados da New Relic, além de detalhes sobre métricas e tipos de dados de eventos, como gerenciamos os dados e como usar nossas APIs.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, - { "title": "Dicionário de dados", "text": "Procure definições para nossos atributos em uma variedade de fontes e tipos de dados.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, - { "title": "Segurança e privacidade", "text": "Saiba como a New Relic lida com a segurança de dados e privacidade, e sobre nossa certificação de conformidade.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, - { "title": "Licenças", "text": "Uma biblioteca de referência das nossas licenças e outros documentos jurídicos.", @@ -391,4 +361,4 @@ "freeTextQuestion": "Você mudaria algo na documentação da New Relic? Se sim, diga o quê e o porquê." } } -} +} \ No newline at end of file From 9a681346efcd0cd47da5c958763a292bd8257070 Mon Sep 17 00:00:00 2001 From: Clark McAdoo Date: Thu, 22 Aug 2024 16:52:32 -0500 Subject: [PATCH 13/18] fix: formatting --- src/i18n/translations/es/translation.json | 32 +++++++++++++++++- src/i18n/translations/jp/translation.json | 32 +++++++++++++++++- src/i18n/translations/kr/translation.json | 40 ++++++++++++++++++----- src/i18n/translations/pt/translation.json | 32 +++++++++++++++++- 4 files changed, 125 insertions(+), 11 deletions(-) diff --git a/src/i18n/translations/es/translation.json b/src/i18n/translations/es/translation.json index 82afbec5f82..43c7e932c89 100644 --- a/src/i18n/translations/es/translation.json +++ b/src/i18n/translations/es/translation.json @@ -49,18 +49,21 @@ "text": "¿No tienes una cuenta?", "title": "Crea una cuenta" }, + { "docsHref": "https://docs.newrelic.com/es/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "Comenzar", "text": "¿Quieres obtener más información sobre las herramientas de monitoreo y observabilidad de New Relic?", "title": "Introducción a New Relic" }, + { "button": "Instalar", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "Ve directo a la IU y configura New Relic para instrumentar tu stack de tecnología.", "title": "Instala New Relic" }, + { "docsHref": "https://docs.newrelic.com/es/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "Lee los tutoriales", @@ -92,12 +95,14 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, + { "title": "Tutoriales y recorridos", "text": "Aprovecha nuestros tutoriales elaborados cuidadosamente y descubre soluciones para problemas comunes.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, + { "title": "Guías y mejores prácticas", "text": "Obtén más información acerca de la IU de la plataforma y las aplicaciones para móviles.", @@ -115,60 +120,70 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, + { "title": "Monitoreo del rendimiento de aplicaciones (APM)", "text": "Monitorea el rendimiento de las aplicaciones en todo tu stack. Contamos con agentes para Go, Java, .NET, Node.js, PHP, Python y Ruby.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, + { "title": "Monitoreo de browser", "text": "Logra una comprensión más profunda de cómo está rindiendo tu sitio web y cómo los usuarios utilizan tu sitio.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, + { "title": "Monitoreo de infraestructura", "text": "Obtén visibilidad de los hosts, contenedores, proveedores, red e infraestructura.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, + { "title": "Monitoreo de Kubernetes", "text": "Observa el estado y el rendimiento completos de tus clústeres y cargas de trabajo.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, + { "title": "Administración de logs", "text": "Organiza todos tus logs en un solo lugar gracias a las herramientas de reenvío de logs de uso común. Incluye privacidad, análisis y archivado de logs para almacenamiento de largo plazo.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, + { "title": "Monitoreo de móviles", "text": "Conoce el rendimiento de tus aplicaciones móviles, desde la experiencia del frontend hasta las métricas de ejecución del backend.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, + { "title": "Monitoreo del rendimiento de modelos (MLOps)", "text": "Analiza el rendimiento y la eficacia de los modelos de aprendizaje automático.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, + { "title": "Monitoreo de redes", "text": "Mapea tu red para que puedas analizar, optimizar y resolver problemas de rendimiento de tus enrutadores, conmutadores y otros dispositivos de red.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, + { "title": "Monitoreo de funciones serverless", "text": "Monitorea las funciones de AWS Lambda Serverless a través de los datos de CloudWatch y la instrumentación a nivel de código.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, + { "title": "Monitoreo sintético", "text": "Simula la actividad del usuario final y las llamadas API desde distintos lugares alrededor del mundo para que puedas detectar problemas antes que tus usuarios.", @@ -186,30 +201,35 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, + { "title": "Seguimiento de cambios", "text": "Haz seguimiento de los cambios en tu sistema, como los despliegues, para ver cómo afectan el rendimiento", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, + { "title": "Gráficos, dashboards y consultas", "text": "Utiliza gráficos y dashboards para visualizar los datos. Comienza con nuestros dashboards prediseñados o utiliza nuestras potentes herramientas de consulta para crear los tuyos.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, + { "title": "Rastreo distribuido", "text": "Descubre cómo fluyen los datos a lo largo del sistema y detecta con precisión dónde se ralentizan las cosas. Detecta, corrige y optimiza el rendimiento del sistema y de la aplicación.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, + { "title": "NRQL", "text": "Profundiza en tus datos con New Relic Query Language (NRQL) y obtén respuestas precisas e información basada en datos.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, + { "title": "Administración a nivel de servicio", "text": "Establece y mide los SLI y SLO para ver cómo están rindiendo tus equipos y tus métricas de negocio clave.", @@ -227,30 +247,35 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, + { "title": "Errors Inbox", "text": "Detecta, comparte y corrige errores de desarrollo de software en un solo lugar.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, + { "title": "Pruebas de seguridad de aplicaciones interactivas (IAST)", "text": "Detecta, verifica y corrige las vulnerabilidades de alto riesgo en todo el ciclo de vida de desarrollo de software. Completamente integrado con la gestión de vulnerabilidades.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, + { "title": "Otras integraciones", "text": "Integra las tecnologías de las que dependes, como OpenTelemetry, Grafana y CloudFoundry, así como otras integraciones populares.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, + { "title": "Gestión de vulnerabilidades", "text": "Examina tus aplicaciones, entidades y bibliotecas de software en busca de vulnerabilidades de seguridad y toma las medidas necesarias para corregir y reducir los riesgos.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, + { "title": "Monitoreo del rendimiento de sitios web", "text": "Mantén tus sitios web rápidos y sin errores, mejora la experiencia del cliente y aumenta las tasas de conversión.", @@ -268,6 +293,7 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, + { "title": "¿Qué hay de nuevo?", "text": "Mantente informado sobre las nuevas características, actualizaciones y cambios en nuestra plataforma.", @@ -285,24 +311,28 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, + { "title": "Datos y API", "text": "Obtén más información sobre NRDB, nuestra base de datos de New Relic, así como detalles de métricas y tipos de datos de eventos, cómo administramos los datos y cómo usar nuestras API.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, + { "title": "Diccionario de datos", "text": "Busca definiciones para nuestros atributos en una variedad de fuentes de datos y tipos de datos.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, + { "title": "Seguridad y privacidad", "text": "Entérate de cómo New Relic gestiona la seguridad y privacidad de los datos y sobre nuestra certificación de cumplimiento.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, + { "title": "Licencias", "text": "Una biblioteca de referencia donde encontrarás nuestras licencias y otra documentación legal.", @@ -361,4 +391,4 @@ "freeTextQuestion": "¿Hay algo que tú cambiarías sobre los documentos de New Relic? Si hay algo, te agradeceríamos que nos compartieras qué es y por qué piensas así." } } -} \ No newline at end of file +} diff --git a/src/i18n/translations/jp/translation.json b/src/i18n/translations/jp/translation.json index 8b936117708..ab56fd2be7d 100644 --- a/src/i18n/translations/jp/translation.json +++ b/src/i18n/translations/jp/translation.json @@ -49,18 +49,21 @@ "text": "まだアカウントをお持ちでありませんか？", "title": "アカウントを作成" }, + { "docsHref": "https://docs.newrelic.com/jp/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "スタートガイド", "text": "New Relicの監視およびオブザーバビリティツールの詳細をご覧ください", "title": "New Relicの概要" }, + { "button": "インストール", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "UIに移動し、New Relicを設定して技術スタックを計装する", "title": "New Relicのインストール" }, + { "docsHref": "https://docs.newrelic.com/jp/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "チュートリアルを読む", @@ -92,12 +95,14 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, + { "title": "チュートリアルと段階的な説明", "text": "丁寧なチュートリアルを利用して、よくある問題に関するソリューションを段階的に確認。", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, + { "title": "ガイドとベストプラクティス", "text": "プラットフォームUIとモバイルアプリの詳細はこちら。", @@ -115,60 +120,70 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, + { "title": "アプリケーションパフォーマンスモニタリング（APM）", "text": "スタック全体のアプリケーションパフォーマンスを監視。Go、Java、.NET、Node.js、PHP、Python、Rubyのエージェントがサポートされています。", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, + { "title": "ブラウザのモニタリング", "text": "ウェブサイトのパフォーマンスとユーザーのサイト使用状況に関するインサイトを入手。", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, + { "title": "インフラストラクチャモニタリング", "text": "ホスト、コンテナ、プロバイダー、ネットワーク、インフラストラクチャへの可視性を獲得。", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, + { "title": "Kubernetes監視", "text": "クラスタとワークロードの完全な健全性とパフォーマンスを監視。", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, + { "title": "ログ管理", "text": "一般的なログ転送ツールのサポートですべてのログを1か所に集約。プライバシー、解析、ログアーカイブを長期保存に含めましょう。", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, + { "title": "モバイルのモニタリング", "text": "フロントのエクスペリエンスからバックエンドの実行メトリクスまで、モバイルアプリのパフォーマンスに関するインサイトを獲得。", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, + { "title": "モデルパフォーマンスモニタリング（MLOps）", "text": "機械学習モデルのパフォーマンスと効果性を分析。", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, + { "title": "ネットワークモニタリング", "text": "ネットワークをマッピングして、ルーター、スイッチその他ネットワークデバイスのパフォーマンスの分析、最適化、トラブルシューティングが行えます。", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, + { "title": "サーバーレス機能の監視", "text": "CloudWatchデータとコードレベルの計装を使用して、サーバレスAWS Lambda関数を監視。", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, + { "title": "合成モニタリング", "text": "世界各地のロケーションのエンドユーザーアクティビティとAPIコールをシミュレーションし、ユーザーよりも早く問題を発見できます。", @@ -186,30 +201,35 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, + { "title": "Change Tracking (変更追跡機能)", "text": "デプロイメントなどのシステム内の変更を追跡し、パフォーマンスにどう影響するかを確認", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, + { "title": "チャート、ダッシュボード、クエリ", "text": "チャートやダッシュボードを使用してデータを可視化。ビルド済みダッシュボードで始めるか、パワフルなクエリツールを使用して独自に構築。", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, + { "title": "ディストリビューティッド（分散）トレーシング", "text": "システム全体のデータフローを確認し、遅延している箇所を特定。システムとアプリケーションパフォーマンスを特定、修正、最適化。", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, + { "title": "NRQL", "text": "New Relicクエリ言語（NRQL）でデータの詳細を確認し、正確な答えとデータドリブンなインサイトを入手。", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, + { "title": "サービスレベル管理", "text": "SLIとSLOを設定、測定し、チームと主要なビジネスメトリクスのパフォーマンスを確認。", @@ -227,30 +247,35 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, + { "title": "エラーインボックス", "text": "ソフトウェア開発時のエラーを1か所で特定、共有、修正。", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, + { "title": "インタラクティブ・アプリケーション・セキュリティ・テスト（IAST）", "text": "ソフトウェア開発ライフサイクル全体にわたるハイリスクな脆弱性を発見、検証、修正。脆弱性管理との完全なインテグレーション。", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, + { "title": "その他のインテグレーション", "text": "OpenTelemetry、Grafana、CloudFoundry、その他一般的なインテグレーションなど、使用しているテクノロジーとの統合が可能。", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, + { "title": "脆弱性管理", "text": "アプリケーション、エンティティ、ソフトウェアライブラリのセキュリティに関する脆弱性を監査し、修正アクションを実行してリスクを低減。", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, + { "title": "ウェブサイトパフォーマンスの監視", "text": "ウェブサイトを動作が早くエラーのない状態に保ち、顧客エクスペリエンスとコンバージョン率を向上。", @@ -268,6 +293,7 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, + { "title": "新機能", "text": "新機能、アップデート、プラットフォームの変更に関し、最新の状態を維持。", @@ -285,24 +311,28 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, + { "title": "データとAPI", "text": "New RelicのデータベースであるNRDBについて、またメトリクスやイベントのデータタイプの詳細、データの管理方法、APIの使用方法について確認。", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, + { "title": "データ辞書", "text": "さまざまなデータソースとデータタイプの属性の定義を確認。", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, + { "title": "セキュリティとプライバシー", "text": "New Relicがデータセキュリティとプライバシーにどう対応しているか、またNew Relicのコンプライアンス認証について確認しましょう。", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, + { "title": "ライセンス", "text": "ライセンスとその他の法的ドキュメンテーションの参照ライブラリ。", @@ -361,4 +391,4 @@ "freeTextQuestion": "New Relicのドキュメントについて何か変更のご希望はありますか？ある場合は、その内容とその理由を教えてください。" } } -} \ No newline at end of file +} diff --git a/src/i18n/translations/kr/translation.json b/src/i18n/translations/kr/translation.json index ee10ca9da17..3767f7fdba7 100644 --- a/src/i18n/translations/kr/translation.json +++ b/src/i18n/translations/kr/translation.json @@ -30,13 +30,7 @@ "pageTitle": "뉴렐릭 문서에 오신 것을 환영합니다.", "search": { "popularSearches": { - "options": [ - "NRQL", - "로그", - "알림", - "모범 사례", - "쿠버네티스" - ], + "options": ["NRQL", "로그", "알림", "모범 사례", "쿠버네티스"], "title": "자주 찾는 검색" }, "placeholder": "검색" @@ -49,18 +43,21 @@ "text": "계정이 없으신가요?", "title": "계정 생성하기" }, + { "docsHref": "https://docs.newrelic.com/kr/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "시작하기", "text": "뉴렐릭의 모니터링 및 옵저버빌리티 툴에 대해 자세히 알고 싶으신가요?", "title": "뉴렐릭 소개" }, + { "button": "설치", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "UI로 이동하여 뉴렐릭을 설정하고 기술 스택을 계측해 보십시오.", "title": "뉴렐릭 설치" }, + { "docsHref": "https://docs.newrelic.com/kr/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "튜토리얼 보기", @@ -92,12 +89,14 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, + { "title": "튜토리얼 및 도움말", "text": "뉴렐릭의 튜토리얼에서 자주 발생하는 문제를 어떻게 해결할 수 있는지 살펴보십시오.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, + { "title": "가이드 및 모범 사례", "text": "플랫폼 UI와 모바일 앱에 대해 자세히 알아보십시오.", @@ -115,60 +114,70 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, + { "title": "애플리케이션 성능 모니터링(APM)", "text": "전체 스택에서 애플리케이션 성능을 모니터링할 수 있습니다.뉴렐릭은 Go, Java, .NET, Node.js,PHP, Python, Ruby를 위한 에이전트를 제공합니다.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, + { "title": "브라우저 모니터링", "text": "웹사이트의 성능과 사용자가 사이트를 사용하는 방식에 대한 인사이트를 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, + { "title": "인프라 모니터링", "text": "호스트, 컨테이너, 공급자, 네트워크 및 인프라에 대한 가시성을 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, + { "title": "쿠버네티스 모니터링", "text": "클러스터와 워크로드의 전체 상태와 성능을 자세히 살펴볼 수 있습니다.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, + { "title": "로그 관리", "text": "보편적인 로그 전달 툴을 모두 지원하기 때문에 모든 로그를 한 곳에 모아 확인할 수 있습니다. 개인정보 보호, 구문 분석, 장기 보관을 위한 로그 아카이브도 포함됩니다.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, + { "title": "모바일 모니터링", "text": "프런트엔드 경험부터 백엔드 실행 지표까지 모바일 앱의 성능에 대한 인사이트를 확보할 수 있습니다.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, + { "title": "모델 성능 모니터링(MLOps)", "text": "머신 러닝 모델의 성능과 효율성을 분석할 수 있습니다.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, + { "title": "네트워크 모니터링", "text": "네트워크를 매핑하여 라우터, 스위치 및 기타 네트워킹 장치의 성능을 분석, 문제 해결, 최적화할 수 있습니다.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, + { "title": "서버리스 기능 모니터링", "text": "CloudWatch 데이터와 코드 레벨 계측을 사용해 서버리스 AWS Lambda 함수를 모니터링할 수 있습니다.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, + { "title": "신세틱 모니터링", "text": "전 세계 위치에서 엔드유저 활동과 API 호출을 시뮬레이션하여 사용자보다 먼저 문제를 발견할 수 있습니다.", @@ -186,30 +195,35 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, + { "title": "변경 추적", "text": "새로운 배포를 포함해 시스템의 변경 사항을 추적하여 성능에 미치는 영향을 파악할 수 있습니다.", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, + { "title": "차트, 대시보드 및 쿼리", "text": "차트와 대시보드를 사용해 데이터를 시각화할 수 있습니다. 사전 구축된 대시보드로 시작하거나 강력한 쿼리 툴을 사용해 맞춤화된 대시보드를 구축할 수 있습니다.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, + { "title": "분산 추적", "text": "시스템 전체에서 데이터 흐름을 확인하고 속도가 느려지고 있는 위치를 식별할 수 있습니다. 시스템과 애플리케이션의 성능을 확인하고 문제를 수정하여 최적화할 수 있습니다.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, + { "title": "NRQL", "text": "뉴렐릭 쿼리 언어(NRQL)을 사용해 데이터를 심층적으로 분석하고 정확한 답변과 데이터 기반 인사이트를 얻을 수 있습니다.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, + { "title": "서비스 레벨 관리", "text": "SLI과 SLO를 설정하고 측정하여 팀과 주요 비즈니스 메트릭의 상태를 확인할 수 있습니다.", @@ -227,30 +241,35 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, + { "title": "Errors inbox", "text": "한 곳에서 소프트웨어 개발 오류를 찾아 공유하고 수정할 수 있습니다.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, + { "title": "인터랙티브 애플리케이션 보안 테스트(IAST)", "text": "소프트웨어 개발 수명주기 전반에서 고위험 취약점을 찾아 확인하고 수정할 수 있습니다. 취약점 관리와 완전하게 통합됩니다.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, + { "title": "기타 통합", "text": "OpenTelemetry, Grafana, CloudFoundry 및 기타 널리 사용되는 기술을 통합할 수 있습니다.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, + { "title": "취약점 관리", "text": "애플리케이션, 엔터티 및 소프트웨어 라이브러리에서 보안 취약점 여부를 감사하고 위험을 해결 및 완화할 수 있는 조치를 취할 수 있습니다.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, + { "title": "웹사이트 성능 모니터링", "text": "웹사이트가 오류 없이 신속하게 로드되도록 하여 고객 경험과 구매 전환율을 향상할 수 있습니다.", @@ -268,6 +287,7 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, + { "title": "새로운 사항", "text": "플랫폼의 새로운 기능, 업데이트 및 변경 사항에 대한 최신 정보를 받아볼 수 있습니다.", @@ -285,24 +305,28 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, + { "title": "데이터 및 API", "text": "뉴렐릭 데이터베이스(NRDB)에 대해 자세히 알아보고 메트릭과 이벤트 데이터 유형, 데이터 관리 방법, API 사용 방법에 대한 세부 정보를 확인할 수 있습니다.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, + { "title": "데이터 사전", "text": "다양한 데이터 소스와 데이터 유형에서 속성의 정의를 확인할 수 있습니다.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, + { "title": "보안 및 개인정보 보호", "text": "뉴렐릭의 개인정보 처리 및 데이터 보안 방법을 확인하고 규정 준수 인증에 대해 알아볼 수 있습니다.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, + { "title": "라이선스", "text": "라이선스와 기타 법률 문서가 포함된 참조 라이브러리입니다.", @@ -361,4 +385,4 @@ "freeTextQuestion": "뉴렐릭 문서와 관련해 바뀌었으면 하는 점이 있으신가요? 있으시면, 어떤 점인지 그리고 왜 그렇게 생각하는지를 말씀해주세요." } } -} \ No newline at end of file +} diff --git a/src/i18n/translations/pt/translation.json b/src/i18n/translations/pt/translation.json index 5b0d7b67eb4..44e4b2c72f9 100644 --- a/src/i18n/translations/pt/translation.json +++ b/src/i18n/translations/pt/translation.json @@ -49,18 +49,21 @@ "text": "Ainda não tem uma conta?", "title": "Criar uma conta" }, + { "docsHref": "https://docs.newrelic.com/pt/docs/new-relic-solutions/get-started/intro-new-relic/", "hrefText": "Começar", "text": "Quer saber mais sobre as ferramentas de monitoramento e observabilidade da New Relic?", "title": "Introdução à New Relic" }, + { "button": "Instalar", "buttonHref": "https://one.newrelic.com/marketplace?state=7ca7c800-845d-8b31-4677-d21bcc061961", "text": "Acesse a interface e configure a New Relic para instrumentar seu stack de tecnologia.", "title": "Instale a New Relic" }, + { "docsHref": "https://docs.newrelic.com/pt/docs/new-relic-solutions/tutorial-landing-page/", "hrefText": "Ler nossos tutoriais", @@ -92,12 +95,14 @@ "to": "https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic/", "icon": "nr-monitoring" }, + { "title": "Tutoriais e guias passo a passo", "text": "Use nossos tutoriais com orientações passo a passo para a solução de problemas comuns.", "to": "https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/", "icon": "nr-doc-link" }, + { "title": "Guias e práticas recomendadas", "text": "Saiba mais sobre a interface da plataforma e os aplicativos para dispositivos móveis.", @@ -115,60 +120,70 @@ "to": "https://docs.newrelic.com/docs/ai-monitoring/intro-to-ai-monitoring/", "icon": "nr-ai-monitoring" }, + { "title": "Monitoramento do desempenho de aplicativos (APM)", "text": "Monitore o desempenho do aplicativo em todo o seu stack. Temos agentes para Go, Java, .NET, Node.js, PHP, Python e Ruby.", "to": "https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/", "icon": "nr-apm" }, + { "title": "Monitoramento de Browser", "text": "Tenha insights sobre como está o desempenho do seu website e como os usuários estão interagindo com ele.", "to": "https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/", "icon": "nr-browser" }, + { "title": "Monitoramento de infraestrutura", "text": "Tenha visibilidade de hosts, contêineres, fornecedores, rede e infraestrutura.", "to": "https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/", "icon": "nr-infrastructure" }, + { "title": "Monitoramento de Kubernetes", "text": "Observe a saúde completa e o desempenho de seus clusters e workloads.", "to": "https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration/", "icon": "nr-k8s-cluster" }, + { "title": "Gerenciamento de logs", "text": "Organize todos os seus logs em um só lugar, com suporte para ferramentas comuns de encaminhamento de logs. Inclui privacidade, análise e arquivos de logs para armazenamento a longo prazo.", "to": "https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/", "icon": "nr-logs" }, + { "title": "Monitoramento de Mobile", "text": "Tenha insights de desempenho dos seus aplicativos para dispositivos móveis, desde a experiência de frontend até as métricas de execução de backend.", "to": "https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/", "icon": "nr-mobile" }, + { "title": "Monitoramento de desempenho do modelo (MLOps)", "text": "Analise o desempenho e a eficácia dos modelos de machine learning.", "to": "https://docs.newrelic.com/docs/mlops/get-started/intro-mlops/", "icon": "nr-learning-models" }, + { "title": "Monitoramento de rede", "text": "Mapeie sua rede para analisar, otimizar e resolver problemas de desempenho dos seus roteadores, comutadores e outros dispositivos de rede.", "to": "https://docs.newrelic.com/docs/network-performance-monitoring/get-started/npm-introduction/", "icon": "nr-network-monitoring" }, + { "title": "Monitoramento de função serverless", "text": "Monitore suas funções do AWS Lambda serverless usando dados do CloudWatch e instrumentação no nível do código.", "to": "https://docs.newrelic.com/docs/serverless-function-monitoring/overview/", "icon": "nr-ml-endpoints" }, + { "title": "Monitoramento sintético", "text": "Simule atividades do usuário final e chamadas de API de locais ao redor do mundo para encontrar problemas antes que os usuários os encontrem.", @@ -186,30 +201,35 @@ "to": "https://docs.newrelic.com/docs/alerts-applied-intelligence/overview/", "icon": "nr-alerts-ai" }, + { "title": "Monitoramento de alterações", "text": "Monitore as alterações no seu sistema, como implantações, para saber como afetam o desempenho.", "to": "https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction/", "icon": "nr-upstream-deployment" }, + { "title": "Gráficos, dashboards e consultas", "text": "Use gráficos e dashboards para visualizar seus dados. Comece com nossos dashboards predefinidos ou use nossas ferramentas de consulta poderosas para criar seus próprios dashboards.", "to": "https://docs.newrelic.com/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/", "icon": "nr-dashboard" }, + { "title": "Trace distribuído (Distributed Tracing)", "text": "Veja como os dados fluem no seu sistema e identifique onde estão ficando mais lentos. Encontre, corrija e otimize o desempenho do aplicativo e do sistema.", "to": "https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/", "icon": "nr-service-map" }, + { "title": "NRQL", "text": "Aprofunde-se nos seus dados com nossa New Relic Query Language (NRQL) e tenha respostas precisas e insights orientados por dados.", "to": "https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/", "icon": "nr-query" }, + { "title": "Gerenciamento a nível de serviço", "text": "Defina e meça SLIs e SLOs para saber como está o desempenho das suas equipes e principais métricas de negócios.", @@ -227,30 +247,35 @@ "to": "https://docs.newrelic.com/docs/codestream/start-here/what-is-codestream/", "icon": "nr-notes-edit" }, + { "title": "Errors Inbox", "text": "Encontre, compartilhe e corrija erros de desenvolvimento de software em um só lugar.", "to": "https://docs.newrelic.com/docs/tutorial-error-tracking/respond-outages/", "icon": "nr-inbox" }, + { "title": "Teste de segurança de aplicativo interativo (IAST)", "text": "Encontre, verifique e corrija vulnerabilidades de alto risco ao longo do ciclo de vida de desenvolvimento do seu software. Totalmente integrado com o gerenciamento de vulnerabilidades.", "to": "https://docs.newrelic.com/docs/iast/introduction/", "icon": "nr-iast" }, + { "title": "Outras integrações", "text": "Integre tecnologias das quais você depende, como OpenTelemetry, Grafana, CloudFoundry e outras integrações populares.", "to": "https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/", "icon": "nr-needs-instrumentation" }, + { "title": "Gerenciamento de vulnerabilidades", "text": "Faça a auditoria de seus aplicativos, entidades e bibliotecas de software em busca de vulnerabilidades de segurança e aja para corrigir e reduzir erros.", "to": "https://docs.newrelic.com/docs/vulnerability-management/overview/", "icon": "nr-vulnerability" }, + { "title": "Monitoramento do desempenho de sites", "text": "Mantenha seus websites rápidos e sem erros, melhore a experiência do cliente e suas taxas de conversão.", @@ -268,6 +293,7 @@ "to": "https://docs.newrelic.com/docs/release-notes/", "icon": "nr-notes-edit" }, + { "title": "O que há de novo?", "text": "Fique por dentro de novos recursos, atualizações e alterações na nossa plataforma.", @@ -285,24 +311,28 @@ "to": "https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account/", "icon": "nr-user" }, + { "title": "Dados e APIs", "text": "Saiba mais sobre o NRDB, nosso banco de dados da New Relic, além de detalhes sobre métricas e tipos de dados de eventos, como gerenciamos os dados e como usar nossas APIs.", "to": "https://docs.newrelic.com/docs/data-apis/get-started/nrdb-horsepower-under-hood/", "icon": "nr-area-chart" }, + { "title": "Dicionário de dados", "text": "Procure definições para nossos atributos em uma variedade de fontes e tipos de dados.", "to": "https://docs.newrelic.com/attribute-dictionary/", "icon": "nr-bookmark" }, + { "title": "Segurança e privacidade", "text": "Saiba como a New Relic lida com a segurança de dados e privacidade, e sobre nossa certificação de conformidade.", "to": "https://docs.newrelic.com/docs/security/overview/", "icon": "nr-private" }, + { "title": "Licenças", "text": "Uma biblioteca de referência das nossas licenças e outros documentos jurídicos.", @@ -361,4 +391,4 @@ "freeTextQuestion": "Você mudaria algo na documentação da New Relic? Se sim, diga o quê e o porquê." } } -} \ No newline at end of file +} From 99af643a8528feab9a240d3ba3424d7ccec12dcc Mon Sep 17 00:00:00 2001 From: Qryuu Date: Fri, 23 Aug 2024 11:40:19 +0900 Subject: [PATCH 14/18] Update fluentd-plugin-log-forwarding.mdx Added annotation comments to SampleConfiguration. --- .../logs/forward-logs/fluentd-plugin-log-forwarding.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/logs/forward-logs/fluentd-plugin-log-forwarding.mdx b/src/content/docs/logs/forward-logs/fluentd-plugin-log-forwarding.mdx index 507bda37b3a..bbc59e341b9 100644 --- a/src/content/docs/logs/forward-logs/fluentd-plugin-log-forwarding.mdx +++ b/src/content/docs/logs/forward-logs/fluentd-plugin-log-forwarding.mdx @@ -232,10 +232,10 @@ Japanese log files encoded in Shift-JIS (SP932) are converted to the [required U #Tail one or more log files @type tail - path C:\opt\fluent\cp932text.log # Full path of the log file you want to collect + path C:¥opt¥fluent¥cp932text.log # Full path of the log file you want to collect tag example.service - from_encoding CP932 - encoding UTF-8 + from_encoding CP932 #logFile character encoding + encoding UTF-8 #Character encoding when sending to New Relic @type none From f58c67b1b6b01e532f5ba03545f744bbbb330e33 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Fri, 23 Aug 2024 11:25:52 +0530 Subject: [PATCH 15/18] Update unix-monitoring-integration.mdx minor editorial edit --- .../host-integrations-list/unix-monitoring-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx index 65838ddacc2..9153eba29ad 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/unix-monitoring-integration.mdx @@ -151,7 +151,7 @@ If using a proxy, the optional `proxy` object should be added to the `global` ob ## Credential obfuscation -For additional security, this integration supports obfuscated values for the attributes like insights_insert_key, proxy_username, proxy_password and any other attributes under the parent attribute 'agents'. To do so, append `_obfuscated` to the attribute name and provide an obfuscated value that was produced by the [New Relic CLI](https://github.com/newrelic/newrelic-cli): +For additional security, this integration supports obfuscated values for the attributes like insights_insert_key, proxy_username, proxy_password, and any other attributes under the parent attribute 'agents'. To do so, append `_obfuscated` to the attribute name and provide an obfuscated value that was produced by the [New Relic CLI](https://github.com/newrelic/newrelic-cli): 1. Install the [New Relic CLI](https://github.com/newrelic/newrelic-cli#installation) on any supported platform. It doesn't need to be installed on the same host as the Unix integration. It is only used to generate the obfuscated keys, this integration handles deobfuscation independently. From c3423ff916f7b85401c890598d3f3ed1c66f06be Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Fri, 23 Aug 2024 12:04:55 +0000 Subject: [PATCH 16/18] chore: add translations --- .../net-agent-approaches-lambda.mdx | 19 ++++-- .../apm-monitoring/opentelemetry-apm-ui.mdx | 16 ++--- .../net-agent-approaches-lambda.mdx | 17 +++-- .../apm-monitoring/opentelemetry-apm-ui.mdx | 16 ++--- .../compatibility-requirements-java-agent.mdx | 67 +++++-------------- .../net-agent-approaches-lambda.mdx | 19 ++++-- .../apm-monitoring/opentelemetry-apm-ui.mdx | 16 ++--- .../compatibility-requirements-java-agent.mdx | 67 +++++-------------- .../net-agent-approaches-lambda.mdx | 19 ++++-- .../apm-monitoring/opentelemetry-apm-ui.mdx | 16 ++--- 10 files changed, 119 insertions(+), 153 deletions(-) diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx index b72e6043ef9..7c2678578c9 100644 --- a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx +++ b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx @@ -25,7 +25,7 @@ La siguiente tabla describe los diferentes requisitos y capacidades de cada enfo -
+ Agente .NET New Relic @@ -324,7 +324,7 @@ La siguiente tabla describe los diferentes requisitos y capacidades de cada enfo - Sí\* + Sí @@ -348,20 +348,27 @@ La siguiente tabla describe los diferentes requisitos y capacidades de cada enfo
-\* Logs en el contexto será capturado por la extensión Lambda o CloudWatch, no por el reenvío de logdel agente. + + Logs-in-context será capturado por la extensión Lambda o CloudWatch, no por el agente de reenvío de log . + ## Agente .NET New Relic [#dot-net-agent] A partir de la versión 10.26.0 del agente, el agente .NET New Relic admite la función Lambda instrumentada AWS. En la mayoría de los casos, el agente .NET instrumentará automáticamente su función Lambda AWS. El beneficio de emplear el agente es que, en la mayoría de los casos, no se requieren cambios de código para monitor su función Lambda. -En una función Lambda, el agente cambiará a un "modo sin servidor" que deshabilitará el envío de datos directamente a New Relic, así como también deshabilitará alguna otra característica. Para enviar datos a New Relic, debe emplear la extensión New Relic Lambda (incluida en nuestra capa de agente .NET) o CloudWatch. +En una función Lambda, el agente cambiará a un "modo sin servidor" que deshabilitará el envío de datos directamente a New Relic, así como también deshabilitará alguna otra característica. Para enviar datos a New Relic, debe emplear la extensión New Relic Lambda (incluida en nuestra capa de agente .NET) o CloudWatch. Dado que el agente instrumentó automáticamente la mayoría de las funciones Lambda, puede emplear el [paquete agente NuGet](https://www.nuget.org/packages/NewRelic.Agent#readme-body-tab) para monitor su función Lambda. Debe configurar manualmente las variables de entorno para el método de implementación elegido (consulte nuestra [guía de instalación](/install/dotnet/?deployment=nuget#nuget-linux)). Esto aún requiere que configure la [extensión Lambda de New Relic o la integración de CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#how) para enviar sus datos a New Relic. +La instrumentación automática está disponible para los siguientes tipos de funciones Lambda AWS (a partir de la versión del agente 10.29.0): + +* Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction +* Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction +* Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction + Limitaciones: * Los métodos lambda genéricos no se instrumentan automáticamente. Si su método lambda es un método genérico, como `Task MyMethod(TRequest, ILambdaContext)`, el agente .NET actualmente no puede implementar ese método. -* Actualmente no se admite la función Lambda de AspNetCore. La función Lambda de AspNetCore se basa en un método genérico que está registrado como controlador lambda. * Actualmente [, Lambda Annotations Framework](https://aws.amazon.com/blogs/developer/net-lambda-annotations-framework/) no es compatible. * Al evento [ApiGatewayV2](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html#http-api-develop-integrations-lambda.proxy-format) le falta algún contexto requerido para el rastreo distribuido. * No se admite el rastreo saliente distribuido para diferentes llamadas del SDK AWS (como SQS). @@ -378,4 +385,4 @@ La instrumentación OpenTelemetry Lambda para .NET proporciona extensión y API Este método requiere alguna configuración manual inicial dependiendo de su método de implementación. -Para detalles de instalación, consulte [trazar su función Lambda .NET con New Relic y OpenTelemetry](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/). +Para detalles de instalación, consulte [trazar su función Lambda .NET con New Relic y OpenTelemetry](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/). \ No newline at end of file diff --git a/src/i18n/content/es/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx b/src/i18n/content/es/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx index efa2f4a3a52..254eca1c732 100644 --- a/src/i18n/content/es/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx +++ b/src/i18n/content/es/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx @@ -33,7 +33,7 @@ Los siguientes conceptos de New Relic se repiten o se superponen en todas las p ## Encuentre servicios OpenTelemetry APM [#find-apm-services] -Para encontrar los servicios OpenTelemetry APM , navegue a **All entities > Services > OpenTelemetry** o **APM & Services**. Haga clic en un servicio para navegar a la [página de resumen](#summary-page) del servicio. +Para encontrar los servicios OpenTelemetry APM , navegue a **All entities > Services > OpenTelemetry** o **APM & Services**. Haga clic en un servicio para navegar a la [página de resumen](#summary-page) del servicio. Dentro del explorador de entidades, puedes filtrar por [etiqueta de entidad](/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data/). Para obtener detalles sobre cómo se calculan las etiquetas de entidad, consulte [los recursosOpenTelemetry en New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources). @@ -53,13 +53,13 @@ La página de rastreo distribuido proporciona información detallada y valiosa s Al igual que con [las señales doradas](#golden-signals), los intervalos se clasifican como errores si el estado del intervalo se establece en `ERROR` (por ejemplo, `otel.status_code = ERROR`). Si el intervalo es un error, la descripción del estado del intervalo (por ejemplo, `otel.status_description`) se muestra en **los detalles del error**. -OpenTelemetry span evento adjunta información de contexto de evento adicional a un lapso en individuo. Se emplean más comúnmente para capturar información de excepciones. Si está disponible, puedes ver el evento de un tramo en **los detalles de la traza**. Tenga en cuenta que la presencia de un evento de excepción de intervalo no considera que el intervalo sea un error por sí solo. Sólo los intervalos con estado de intervalo establecido en `ERROR` se clasifican como errores. +OpenTelemetry span evento adjunta información de contexto de evento adicional a un lapso particular. Se emplean más comúnmente para capturar información de excepciones. Si está disponible, puede ver el evento de un lapso en **trace details**. -Screenshot showing the right pane showing the two links for span events + + La presencia de un evento de excepción de lapso no califica el lapso como un error por sí solo. Sólo los intervalos con estado de intervalo establecido en `ERROR` se clasifican como errores. + + +Screenshot showing the right pane showing the two links for span events ## Página: Mapa de servicios [#service-map-page] @@ -145,4 +145,4 @@ Varias páginas incluyen un interruptor métrico o de tramos. Esto le permite al Las métricas no están sujetas a ejemplificación y, por lo tanto, son más precisas, especialmente cuando se calculan tasas como el rendimiento. Sin embargo, las métricas están sujetas a restricciones de cardinalidad y pueden carecer de ciertos atributos importantes para el análisis. Por el contrario, los tramos están muestreados y, por lo tanto, están sujetos a problemas de precisión, pero tienen atributos más ricos ya que no están sujetos a restricciones de cardinalidad. -Históricamente, OpenTelemetry API/SDK del lenguaje y la instrumentación priorizaron la instrumentación de traza. Sin embargo, el proyecto avanzó mucho y métrica está disponible en casi todos los idiomas. Consulte la [documentación](https://opentelemetry.io/docs/languages/) del idioma y la instrumentación relevantes para obtener más detalles. +Históricamente, OpenTelemetry API/SDK del lenguaje y la instrumentación priorizaron la instrumentación de traza. Sin embargo, el proyecto avanzó mucho y métrica está disponible en casi todos los idiomas. Consulte la [documentación](https://opentelemetry.io/docs/languages/) del idioma y la instrumentación relevantes para obtener más detalles. \ No newline at end of file diff --git a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx index 71237e73a18..4b85e1a5482 100644 --- a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx +++ b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx @@ -25,7 +25,7 @@ translationType: machine -
+ New Relic .NET エージェント @@ -324,7 +324,7 @@ translationType: machine - はい\* + はい @@ -348,7 +348,9 @@ translationType: machine
-\*コンテキスト内ログは、エージェント内ログ転送ではなく、Lambda 拡張機能または CloudWatch によってキャプチャされます。 + + コンテキスト内のログは、エージェント内ログ転送ではなく、Lambda 拡張機能または CloudWatch によってキャプチャされます。 + ## New Relic .NET エージェント [#dot-net-agent] @@ -358,10 +360,15 @@ Lambda関数では、エージェントが「サーバーレスモード」に ほとんどの Lambda 関数はエージェントによって自動的にインストゥルメントされたため、[エージェント NuGet パッケージを](https://www.nuget.org/packages/NewRelic.Agent#readme-body-tab)使用して Lambda 関数を監視できます。 選択したデプロイメント方法に応じて環境変数を手動で構成する必要があります ([導入ガイド](/install/dotnet/?deployment=nuget#nuget-linux)を参照)。 ただし、データを に送信するには 、[New Relic Lambda Extension または CloudWatch 統合の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#how)New Relic いずれかを設定する必要があります。 +自動インストゥルメンテーションは、次のAWS Lambda関数タイプで利用できます (エージェント バージョン 10.29.0 以降)。 + +* Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction +* Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction +* Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction + 制限事項: * ジェネリック ラムダ メソッドは自動的にはインストゥルメントされません。 ラムダ メソッドが`Task MyMethod(TRequest, ILambdaContext)`などのジェネリック メソッドである場合、.NET エージェントは現在そのメソッドを計算できません。 -* AspNetCore Lambda関数は現在サポートされていません。 AspNetCore Lambda関数は、ラムダ ハンドラーとして登録されている汎用メソッドに依存します。 * [Lambda アノテーション フレームワーク](https://aws.amazon.com/blogs/developer/net-lambda-annotations-framework/)は現在サポートされていません。 * [ApiGatewayV2](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html#http-api-develop-integrations-lambda.proxy-format)イベントには、ディストリビューティッド（分散）トレーシングに必要な一部のコンテキストがありません。 * さまざまなAWS SDK 呼び出し (SQS など) のアウトバウンド ディストリビューティッド（分散）トレーシングはサポートされていません。 @@ -378,4 +385,4 @@ OpenTelemetry Lambda インストゥルメンテーション for .NET は、Lamb この方法では、デプロイメント方法に応じて、初期の手動設定が必要になります。 -インストールの詳細については、 [「.NET Lambda関数をNew RelicとOpenTelemetryでレースする」](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/)を参照してください。 +インストールの詳細については、 [「.NET Lambda関数をNew RelicとOpenTelemetryでレースする」](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/)を参照してください。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx b/src/i18n/content/jp/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx index 5c112239e67..6925bf0725b 100644 --- a/src/i18n/content/jp/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx +++ b/src/i18n/content/jp/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx @@ -33,7 +33,7 @@ OpenTelemetry APM UI ページは、問題を迅速に特定して診断でき ## OpenTelemetry APM サービスを探す [#find-apm-services] -OpenTelemetry APM サービスを見つけるには、 **All entities > Services > OpenTelemetry**または**APM & Services** \[APM とサービス]に移動します。 サービスをクリックすると、サービスの[概要ページ](#summary-page)に移動します。 +OpenTelemetry APM サービスを見つけるには、 **All entities > Services > OpenTelemetry**または**APM & Services** \[APM とサービス]に移動します。 サービスをクリックすると、サービスの[概要ページ](#summary-page)に移動します。 エンティティ エクスプローラー内では、 [エンティティ タグ](/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data/)でフィルターできます。 エンティティ タグの計算方法の詳細については、 [New Relic の OpenTelemetry リソース](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources)を参照してください。 @@ -53,13 +53,13 @@ OpenTelemetry APM サービスを見つけるには、 **All entities > Services [ゴールデンシグナル](#golden-signals)と同様に、スパンのステータスが`ERROR`に設定されている場合 (たとえば、 `otel.status_code = ERROR` )、スパンはエラーとして分類されます。 スパンはエラーの場合、**エラーの詳細**にスパンのステータスの説明（たとえば、 `otel.status_description` ）が表示されます。 -OpenTelemetry span イベントは、特定のスパンに追加のイベント コンテキスト情報を添付します。 これらは例外情報をキャプチャするために最もよく使用されます。 利用可能な場合は、**トレースの詳細**でスパンのイベントを表示できます。 注意: スパンの例外イベントが存在するだけでは、スパン自体がエラーとして分類されるわけではありません。 スパン ステータスが`ERROR`に設定されているスパンのみがエラーとして分類されます。 +OpenTelemetryスパン イベントは、追加のイベント コンテキスト情報を特定のスパンに添付します。 これらは例外情報をキャプチャするために最もよく使用されます。 利用可能な場合は、**trace details** \[トレースの詳細]でスパンのイベントを表示できます。 -Screenshot showing the right pane showing the two links for span events + + スパンの例外イベントが存在するだけでは、スパン自体がエラーであるとはみなされません。 スパン ステータスが`ERROR`に設定されているスパンのみがエラーとして分類されます。 + + +Screenshot showing the right pane showing the two links for span events ## ページ: サービスマップ [#service-map-page] @@ -145,4 +145,4 @@ Errors Inboxページはトレース データによって駆動されます。 メトリックはサンプリングの対象ではないため、特に中間率などのレートを計算する場合はより正確です。 ただし、メトリックはカーディナリティ制約の対象であり、分析に重要な特定の属性が欠落している可能性があります。 対照的に、スパンはサンプリングされるため、精度の問題が生じますが、カーディナリティ制約の対象ではないため、より豊富な属性を持ちます。 -歴史的に、 OpenTelemetry言語API /SDK と インストゥルメンテーション は、トレース インストゥルメンテーションを優先してきました。 しかし、プロジェクトは長い道のりを歩んでおり、メトリクスはほぼすべての言語で利用できるようになりました。 詳細については、関連する言語およびインストゥルメンテーションの[ドキュメント](https://opentelemetry.io/docs/languages/)を確認してください。 +歴史的に、 OpenTelemetry言語API /SDK と インストゥルメンテーション は、トレース インストゥルメンテーションを優先してきました。 しかし、プロジェクトは長い道のりを歩んでおり、メトリクスはほぼすべての言語で利用できるようになりました。 詳細については、関連する言語およびインストゥルメンテーションの[ドキュメント](https://opentelemetry.io/docs/languages/)を確認してください。 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx b/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx index d32e6171ac8..11c016ac0b0 100644 --- a/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx +++ b/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx @@ -18,10 +18,7 @@ New Relic의 Java 에이전트를 사용해 보고 싶으십니까? 무료 [로 Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 충족하는지 확인하십시오. - + Java 에이전트는 Java, Scala, Kotlin 및 Clojure를 비롯한 모든 JVM 기반 언어와 호환됩니다. 언어별 기능에 대한 계측 지원은 아래의 [자동으로 계측된 프레임워크 및 라이브러리](#auto-instrumented) 섹션을 참조하세요. @@ -93,17 +90,11 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 이 표의 일부 Java 에이전트 버전은 더 이상 지원되지 않지만 참조용으로 포함되었습니다. 지원되는 Java 에이전트 버전 목록은 [Java 에이전트 EOL 정책](/docs/apm/agents/java-agent/getting-started/java-agent-eol-policy/)을 확인하시기 바랍니다. - + [데이터 수집을 위한 표준 보안 수단으로](/docs/accounts-partnerships/accounts/security/data-security) 앱 서버는 SHA-2(256비트)를 지원해야 합니다. SHA-1은 지원되지 않습니다. - + 귀하의 애플리케이션이 당사 에이전트 이외의 다른 애플리케이션 모니터링 소프트웨어를 사용하는 경우 당사 에이전트가 올바르게 작동한다고 보장할 수 없으며 기술 지원을 제공할 수 없습니다. 자세한 내용은 [다른 모니터링 소프트웨어 사용 중 오류를](/docs/apm/new-relic-apm/troubleshooting/errors-while-using-new-relic-apm-alongside-other-apm-software) 참조하십시오. @@ -115,10 +106,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 에이전트는 다음 프레임워크 및 라이브러리를 자동으로 계측합니다. - + 에이전트는 다음 앱/웹 서버를 자동으로 계측합니다. 지원되는 앱/웹 서버에 Java 에이전트를 설치 [하려면 Java 에이전트 설치](/docs/agents/java-agent/installation/java-agent-manual-installation) 를 참조하십시오. * 콜드퓨전 10 @@ -138,10 +126,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * WildFly 8.0.0.최종에서 최신으로 - + 에이전트는 다음 프레임워크를 자동으로 계측합니다. 지원되는 프레임워크에 Java 에이전트를 설치하려면 Java 에이전트 [설치](/docs/agents/java-agent/installation/java-agent-manual-installation) 를 참조하십시오. * Akka 2.2.0-RC1 최신 버전 @@ -236,10 +221,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * 스칼라 2.13: 1.0.9부터 최신까지 - + 에이전트는 다음 HTTP 클라이언트 및 메시징 서비스를 자동으로 계측합니다. 지침 [은 Java 에이전트 설치](/docs/agents/java-agent/installation/java-agent-manual-installation) 를 참조하십시오. * Akka HTTP 2.4.5 최신 버전 @@ -268,7 +250,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * JMS 1.1에서 최신 버전 - * [Kafka 클라이언트 메트릭](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.10.0.0-3.6.x (기준용) + * [Kafka 클라이언트 지표](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.10.0.0부터 최신 버전까지(지수용) * [Kafka 클라이언트 스팬](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.11.0.0 to 3.6.x (분산 추적용) @@ -304,10 +286,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * 스칼라 2.13: 2.2.3에서 최신 2.x, 3.0.0에서 최신 3.x - + New Relic은 현재 느린 데이터베이스 쿼리에 대한 설명 계획을 캡처하기 위해 MySQL 및 PostgreSQL을 지원합니다. * Amazon v1 DynamoDB 1.11.106 최신 버전 @@ -337,7 +316,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * INet MERLIA 7.0.3, 8.04.03 및 8.06 - * Jedis Redis 드라이버 1.4.0-2.10.x, 3.0.0-4.x + * Jedis Redis 드라이버 1.4.0->2.10.x, 3.0.0 -> 4.x, 5.x -> 최신 * jTDS 1.2 최신 버전 @@ -378,12 +357,11 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * Spymemcached 2.11 최신 버전 * Sybase(jConnect) JDBC 3 드라이버 6.0 최신 버전 + + * Vert.x SQL Client 4.4.2 최신 버전 - + New Relic은 [다양한 데이터베이스 및 데이터베이스 드라이버에 대한 인스턴스 세부 정보를](/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues) 수집합니다. APM에서 특정 인스턴스 및 데이터베이스 정보 유형을 보는 기능은 New Relic 에이전트 버전에 따라 다릅니다. New Relic의 Java 에이전트 [버전 3.33.0 이상](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-3330) 은 다음을 지원합니다. @@ -396,7 +374,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * DataStax Cassandra 드라이버 3.0.0-최신 버전 - * Jedis Redis 드라이버 1.4-2.10.x, 3.0.0-4.x + * Jedis Redis 드라이버 1.4->2.10.x, 3.0.0 -> 4.x, 5.x -> 최신 * MongoDB @@ -410,27 +388,18 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 Java 에이전트는 이러한 데이터베이스 드라이버에 대한 느린 쿼리 추적 및 트랜잭션 추적에 대한 데이터베이스 이름 및 데이터베이스 서버/식별자 특성을 보고합니다. 추가 데이터 저장소에서 인스턴스 수준 정보를 요청하려면 [support.newrelic.com](https://support.newrelic.com) 에서 지원을 받으십시오. - + 아래에 나열되지 않은 서비스를 포함하여 다양한 호스팅 서비스에 Java 에이전트를 설치할 수 있습니다. 특정 호스팅 서비스에 대한 자세한 설치 가이드는 다음과 같습니다. * [Google App Engine(GAE) 가변형 환경](/docs/agents/java-agent/additional-installation/google-app-engine-flexible-installation-java#tomcat-example) * [헤로쿠](/docs/agents/java-agent/heroku/java-agent-heroku) - + 지원되는 프레임워크의 경우 Java 에이전트 [는 일반적으로 비동기 작업을 자동으로 계측](/docs/agents/java-agent/async-instrumentation/asynchronous-applications-monitoring-considerations) 합니다. 그러나 Java 에이전트 API를 사용하여 [이 계측을 확장](/docs/agents/java-agent/async-instrumentation/java-agent-api-asynchronous-applications) 할 수 있습니다. - + * EJB Session Beans 3.0 이상 * JMX * JSP(Java Server Pages) 2.0부터 최신 버전까지 @@ -474,7 +443,7 @@ Java 에이전트는 다른 New Relic 제품과 통합되어 엔드 투 엔드 @@ -508,4 +477,4 @@ Java 에이전트는 다른 New Relic 제품과 통합되어 엔드 투 엔드 -
- 중력 에이전트는 [자동 측정, 자동 로그를 활성화](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent#select-apm-app) 할 때 브라우저 JavaScript 에이전트를 자동으로 주입합니다. 브라우저를 활성화한 후 [APM 요약 페이지](/docs/apm/applications-menu/monitoring/apm-overview-page) 에서 브라우저 데이터를 보고 특정 앱에 대한 APM 과 브라우저 데이터 간에 빠르게 전환할 수 있습니다. 설정 옵션 및 수동 측정, 로그는 [및 에이전트를](/docs/agents/java-agent/instrumentation/page-load-timing-java) 참조하세요. + 중력 에이전트는 [자동 측정, 자동 로그를 활성화](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent#select-apm-app) 할 때 브라우저 JavaScript 에이전트를 자동으로 주입합니다. 브라우저를 활성화한 후 [APM 요약 페이지](/docs/apm/applications-menu/monitoring/apm-overview-page) 에서 브라우저 데이터를 보고 특정 앱에 대한 APM 과 브라우저 데이터 간에 빠르게 전환할 수 있습니다. 설정 옵션 및 수동 측정, 로그는 [및 에이전트를](/docs/agents/java-agent/instrumentation/page-load-timing-java) 참조하세요.
+ \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx index 5878b06082e..8ded82373fb 100644 --- a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx +++ b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx @@ -25,7 +25,7 @@ translationType: machine -
+ 뉴렐릭 .NET 에이전트 @@ -324,7 +324,7 @@ translationType: machine - 예\* + 네 @@ -348,20 +348,27 @@ translationType: machine
-\* 컨텍스트 내 로그인은 in-에이전트 로그인 포워딩이 아닌 Lambda 확장 또는 CloudWatch에 의해 캡처됩니다. + + 컨텍스트 내는 in-에이전트 로그인 포워딩이 아닌 Lambda 확장 또는 CloudWatch에 의해 캡처됩니다. + ## 뉴렐릭 .NET 에이전트 [#dot-net-agent] 에이전트 버전 10.26.0부터 뉴렐릭 .NET 에이전트는 AWS Lambda 함수를 지원합니다. 대부분의 경우 .NET 에이전트는 AWS Lambda 함수를 자동으로 호출합니다. 에이전트를 사용하면 대부분의 경우 Lambda 함수를 모니터링하는 데 코드 변경이 필요하지 않다는 이점이 있습니다. -Lambda 함수에서 에이전트는 뉴렐릭으로 직접 데이터 전송을 비활성화하고 일부 다른 기능을 비활성화하는 "서버리스 모드"로 전환합니다. 뉴렐릭으로 데이터를 보내려면 뉴렐릭 Lambda Extension(.NET 에이전트 계층에 포함됨) 또는 CloudWatch를 사용해야 합니다. +Lambda 함수에서 에이전트는 뉴렐릭으로 직접 데이터 전송을 비활성화하고 일부 다른 기능을 비활성화하는 "서버리스 모드"로 전환합니다. 뉴렐릭으로 데이터를 보내려면 뉴렐릭 Lambda Extension(.NET 에이전트 계층에 포함됨) 또는 CloudWatch를 사용해야 합니다. 대부분의 Lambda 함수는 [에이전트 NuGet 패키지를](https://www.nuget.org/packages/NewRelic.Agent#readme-body-tab) 사용하여 Lambda 함수를 모니터링할 수 있습니다. 선택한 배포 방법에 대한 환경 변수를 수동으로 구성해야 합니다( [설치 가이드](/install/dotnet/?deployment=nuget#nuget-linux) 참조). 이를 위해서는 [뉴렐릭 Lambda Extension 또는 CloudWatch 통합을](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#how) 설정하여 데이터를 뉴렐릭으로 보내야 합니다. +다음 AWS Lambda 함수 유형에 대해 자동 계측을 사용할 수 있습니다(에이전트 버전 10.29.0 기준): + +* Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction +* Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction +* Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction + 제한 사항: * 일반 람다 메서드는 자동으로 다운로드되지 않습니다. 람다 메서드가 `Task MyMethod(TRequest, ILambdaContext)` 와 같은 일반 메서드인 경우 .NET 에이전트는 현재 해당 메서드를 렌더링할 수 없습니다. -* AspNetCore Lambda 함수는 현재 지원되지 않습니다. AspNetCore Lambda 함수는 람다 핸들러로 등록된 일반 메서드를 사용합니다. * [Lambda 주석 프레임워크](https://aws.amazon.com/blogs/developer/net-lambda-annotations-framework/) 는 현재 지원되지 않습니다. * [ApiGatewayV2](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html#http-api-develop-integrations-lambda.proxy-format) 이벤트에는 분산 추적에 필요한 일부 컨텍스트가 누락되었습니다. * 다양한 AWS SDK 호출(예: SQS)에 대한 아웃바운드 분산 추적은 지원되지 않습니다. @@ -378,4 +385,4 @@ Lambda 함수에서 에이전트는 뉴렐릭으로 직접 데이터 전송을 이 방법을 사용하려면 배포 방법에 따라 일부 초기 수동 설정이 필요합니다. -설치에 대한 자세한 내용은 [뉴렐릭 및 OpenTelemetry사용하여 .NET Lambda 함수를 트레이스](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/) 하세요. +설치에 대한 자세한 내용은 [뉴렐릭 및 OpenTelemetry사용하여 .NET Lambda 함수를 트레이스](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/) 하세요. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx b/src/i18n/content/kr/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx index 320f2dd8161..b4fe2b08f94 100644 --- a/src/i18n/content/kr/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx +++ b/src/i18n/content/kr/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx @@ -33,7 +33,7 @@ OpenTelemetry APM UI 페이지는 문제를 신속하게 식별하고 진단하 ## OpenTelemetry APM 서비스 찾기 [#find-apm-services] -OpenTelemetry APM 서비스를 찾으려면 **All entities > Services > OpenTelemetry** 또는 **APM & Services** \[APM & 서비스] 로 이동합니다. 서비스를 클릭하면 서비스 [요약 페이지](#summary-page) 로 이동합니다. +OpenTelemetry APM 서비스를 찾으려면 **All entities > Services > OpenTelemetry** 또는 **APM & Services** \[APM &amp; 서비스] 로 이동합니다. 서비스를 클릭하면 서비스 [요약 페이지](#summary-page) 로 이동합니다. 엔터티 탐색기 내에서 [엔터티 태그](/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data/) 별로 필터링할 수 있습니다. 엔터티 태그가 컴퓨트인 방법에 대한 자세한 내용은 [뉴렐릭의OpenTelemetry 리소스를](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources) 참조하세요. @@ -53,13 +53,13 @@ OpenTelemetry APM 서비스를 찾으려면 **All entities > Services > OpenTele [골든 시그널](#golden-signals) 과 마찬가지로 스팬 상태가 `ERROR` (예: `otel.status_code = ERROR`)로 설정된 경우 스팬은 오류로 분류됩니다. 범위가 오류인 경우 범위 상태 설명(예: `otel.status_description`)이 **오류 세부정보** 에 표시됩니다. -OpenTelemetry 범위 이벤트는 추가 이벤트 컨텍스트 정보를 특정 범위에 연결합니다. 예외 정보를 캡처하는 데 가장 일반적으로 사용됩니다. 가능한 경우 **트레이스 세부정보** 에서 범위의 이벤트를 볼 수 있습니다. 범위 예외 이벤트가 있다고 해서 범위 자체가 오류로 분류되는 것은 아닙니다. 스팬 상태가 `ERROR` 로 설정된 스팬만 오류로 분류됩니다. +OpenTelemetry 범위 이벤트는 추가 이벤트 컨텍스트 정보를 특정 범위에 연결합니다. They are most commonly used to capture exception information. 사용 가능한 경우 **trace details** \[추적 세부 정보] 에서 스팬 이벤트를 볼 수 있습니다. -Screenshot showing the right pane showing the two links for span events + + 스팬 예외 이벤트가 존재한다고 해서 그 자체로 스팬이 오류로 간주되는 것은 아닙니다. `ERROR` 으로 설정된 스팬 상태만 오류로 분류됩니다. + + +Screenshot showing the right pane showing the two links for span events ## 페이지: 서비스 맵 [#service-map-page] @@ -145,4 +145,4 @@ Go 런타임 페이지에는 Go 런타임 지표와 함께 황금 아이콘이 지표는 샘플링 대상이 아니므로 특히 처리량과 같은 속도를 계산할 때 더 정확합니다. 그러나 지표에는 카디널리티 제약이 적용되며 분석에 중요한 특정 속성이 부족할 수 있습니다. 이와 대조적으로 범위는 샘플링되므로 정확도 문제가 발생하지만 카디널리티 제약 조건이 적용되지 않으므로 더 풍부한 속성을 갖습니다. -역사적으로 OpenTelemetry 언어 API/SDK 및 리소스 우선순위는 트레이스 리소스입니다. 그러나 이 프로젝트는 많은 발전을 이루었으며 지표는 거의 모든 언어로 제공됩니다. 자세한 내용은 해당 언어의 [설명서](https://opentelemetry.io/docs/languages/) 와 리뷰를 확인하세요. +역사적으로 OpenTelemetry 언어 API/SDK 및 리소스 우선순위는 트레이스 리소스입니다. 그러나 이 프로젝트는 많은 발전을 이루었으며 지표는 거의 모든 언어로 제공됩니다. 자세한 내용은 해당 언어의 [설명서](https://opentelemetry.io/docs/languages/) 와 리뷰를 확인하세요. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx b/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx index 3ddb9ac2aef..351c0dc806f 100644 --- a/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx +++ b/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx @@ -18,10 +18,7 @@ Quer experimentar o agente Java da New Relic? [Crie uma conta New Relic](https:/ Antes de instalar o agente Java, certifique-se de que seu sistema atenda a estes requisitos: - + O agente Java é compatível com qualquer linguagem baseada em JVM, incluindo: Java, Scala, Kotlin e Clojure. Para obter suporte de instrumentação para recursos específicos de linguagem, consulte a seção [Estrutura e biblioteca instrumentada automaticamente](#auto-instrumented) abaixo. @@ -93,17 +90,11 @@ Antes de instalar o agente Java, certifique-se de que seu sistema atenda a estes Algumas versões do agente Java nesta tabela não são mais suportadas, mas ainda estão listadas para referência. A lista de versões suportadas do agente Java está na [política EOL do agente Java](/docs/apm/agents/java-agent/getting-started/java-agent-eol-policy/). - + Como [medida de segurança padrão para coleta de dados](/docs/accounts-partnerships/accounts/security/data-security), o servidor do seu aplicativo deve oferecer suporte a SHA-2 (256 bits). SHA-1 não é compatível. - + Se o seu aplicativo usa outro software de monitoramento de aplicativo além do nosso agente, não podemos garantir que nosso agente funcionará corretamente e não podemos oferecer suporte técnico. Para obter mais informações, consulte [Erros ao usar outro software de monitoramento](/docs/apm/new-relic-apm/troubleshooting/errors-while-using-new-relic-apm-alongside-other-apm-software). @@ -115,10 +106,7 @@ Depois de [instalar o agente Java](/docs/agents/java-agent/installation/install- O agente automaticamente utiliza estes frameworks e bibliotecas: - + O agente instrumenta automaticamente os seguintes servidores de aplicativos/web. Para instalar o agente Java em servidores de aplicativos/web suportados, consulte [Instalar o agente Java](/docs/agents/java-agent/installation/java-agent-manual-installation). * ColdFusion 10 @@ -138,10 +126,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * WildFly 8.0.0.Final até o mais recente - + O agente automaticamente utiliza o seguinte framework. Para instalar o agente Java na estrutura suportada, consulte [Instalar o agente Java](/docs/agents/java-agent/installation/java-agent-manual-installation). * Akka 2.2.0-RC1 até o mais recente @@ -236,10 +221,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * Scala 2.13: 1.0.9 até o mais recente - + O agente utiliza automaticamente os seguintes clientes HTTP e serviços de mensagens. Para obter instruções, consulte [Instalar o agente Java](/docs/agents/java-agent/installation/java-agent-manual-installation). * Akka HTTP 2.4.5 até o mais recente @@ -268,7 +250,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * JMS de 1.1 até o mais recente - * [Kafka Client Metrics](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.10.0.0 a 3.6.x (para métrica) + * [Métrica do cliente Kafka](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.10.0.0 até a mais recente (para métrica) * [Kafka Client Spans](/docs/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues) 0.11.0.0 a 3.6.x (para distributed tracing) @@ -304,10 +286,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * Scala 2.13: 2.2.3 até 2.x mais recente, 3.0.0 até 3.x mais recente - + Atualmente, o New Relic oferece suporte a MySQL e PostgreSQL para capturar planos de explicação para consulta lenta ao banco de dados. * Amazon v1 DynamoDB 1.11.106 até o mais recente @@ -337,7 +316,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * INet MERLIA 7.0.3, 8.04.03 e 8.06 - * Jedis Redis driver 1.4.0 a 2.10.x, 3.0.0 a 4.x + * Driver Jedis Redis 1.4.0 a 2.10.x, 3.0.0 para 4.x, 5.x para o mais recente * jTDS 1.2 até o mais recente @@ -378,12 +357,11 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * Spymemcached 2.11 até o mais recente * Driver Sybase (jConnect) JDBC 3 6.0 até o mais recente + + * Vert.x SQL Client 4.4.2 para o mais recente - + New Relic coleta [detalhes de instância para uma variedade de bancos de dados e drivers do banco de dados](/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues). A capacidade de visualizar instâncias específicas e os tipos de informações do banco de dados no APM depende da versão do agente New Relic. [As versões 3.33.0 ou superior](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-3330) do agente Java da New Relic oferecem suporte ao seguinte: @@ -396,7 +374,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * Driver DataStax Cassandra 3.0.0 até o mais recente - * Jedis Redis driver 1.4 a 2.10.x, 3.0.0 a 4.x + * Driver Jedis Redis 1.4 a 2.10.x, 3.0.0 para 4.x, 5.x para o mais recente * MongoDB @@ -410,27 +388,18 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: O agente Java relata o nome do banco de dados e o atributo do servidor/identificador do banco de dados na consulta lenta trace e trace da transação para esses drivers do banco de dados. Para solicitar informações em nível de instância de datastores adicionais, obtenha suporte em [support.newrelic.com](https://support.newrelic.com). - + Você pode instalar o agente Java em vários serviços de hospedagem, incluindo aqueles não listados abaixo. Aqui estão guias de instalação detalhados para serviços de hospedagem específicos: * [Ambiente flexível do Google App Engine (GAE)](/docs/agents/java-agent/additional-installation/google-app-engine-flexible-installation-java#tomcat-example) * [Heroku](/docs/agents/java-agent/heroku/java-agent-heroku) - + Para frameworks suportados, o agente Java [geralmente funciona automaticamente como instrumento assíncrono](/docs/agents/java-agent/async-instrumentation/asynchronous-applications-monitoring-considerations). No entanto, você pode usar a API do agente Java para [estender essa instrumentação](/docs/agents/java-agent/async-instrumentation/java-agent-api-asynchronous-applications). - + * Beans de sessão EJB 3.0 ou superior * JMX * JSP (Java Server Pages) 2.0 até o mais recente @@ -474,7 +443,7 @@ O agente Java se integra a outros produtos New Relic para oferecer visibilidade @@ -508,4 +477,4 @@ O agente Java se integra a outros produtos New Relic para oferecer visibilidade -
- O agente Java injeta automaticamente o agente JavaScript do browser quando você [ativa a instrumentação automática](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent#select-apm-app). Depois de ativar a injeção do browser, você pode visualizar os dados do browser na [página Resumo do APM](/docs/apm/applications-menu/monitoring/apm-overview-page) e alternar rapidamente entre o APM e os dados do browser para um aplicativo específico. Para opções de configuração e instrumentação manual, consulte [e o agente Java](/docs/agents/java-agent/instrumentation/page-load-timing-java). + O agente Java injeta automaticamente o agente JavaScript do browser quando você [ativa a instrumentação automática](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent#select-apm-app). Depois de ativar a injeção do browser, você pode visualizar os dados do browser na [página Resumo do APM](/docs/apm/applications-menu/monitoring/apm-overview-page) e alternar rapidamente entre o APM e os dados do browser para um aplicativo específico. Para opções de configuração e instrumentação manual, consulte [e o agente Java](/docs/agents/java-agent/instrumentation/page-load-timing-java).
+ \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx index 79d7ff6600f..fc7d1ac5578 100644 --- a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx +++ b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-approaches-lambda.mdx @@ -25,7 +25,7 @@ A tabela a seguir descreve os diferentes requisitos e capacidades de cada aborda -
+ Agente New Relic .NET @@ -324,7 +324,7 @@ A tabela a seguir descreve os diferentes requisitos e capacidades de cada aborda - Sim\* + Sim @@ -348,20 +348,27 @@ A tabela a seguir descreve os diferentes requisitos e capacidades de cada aborda
-\* Logs contextualizados será capturado pela extensão Lambda ou CloudWatch, e não por encaminhamento de logs in-agente. + + Logs-in-context será capturado pela extensão Lambda ou CloudWatch, não pelo in-agente encaminhamento de logs. + ## Agente New Relic .NET [#dot-net-agent] A partir da versão 10.26.0 do agente, o agente New Relic .NET oferece suporte à função AWS instrumentada do Lambda. Na maioria dos casos, o agente .NET instrumentará automaticamente sua função AWS do Lambda. A vantagem de usar o agente é que, na maioria dos casos, nenhuma alteração de código é necessária para monitor sua função do Lambda. -Na função do Lambda, o agente mudará para um "modo serverless" que desabilitará o envio de dados diretamente para New Relic, bem como desabilitará algum outro recurso. Para enviar dados para a New Relic, você deve usar a extensão New Relic Lambda (incluída em nossa camada de agente .NET) ou o CloudWatch. +Na função do Lambda, o agente mudará para um "modo serverless" que desabilitará o envio de dados diretamente para New Relic, bem como desabilitará algum outro recurso. Para enviar dados para a New Relic, você deve usar a extensão New Relic Lambda (incluída em nossa camada de agente .NET) ou o CloudWatch. Como o agente é automaticamente o instrumento mais função do Lambda, você pode usar o [pacote agente NuGet](https://www.nuget.org/packages/NewRelic.Agent#readme-body-tab) para monitor sua função do Lambda. Você precisa configurar manualmente as variáveis de ambiente para o método de implantação escolhido (consulte nosso [guia de instalação](/install/dotnet/?deployment=nuget#nuget-linux)). Isso ainda requer que você configure a [extensão Lambda da New Relic ou a integração do CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#how) para enviar seus dados para a New Relic. +A instrumentação automática está disponível para os seguintes tipos de função do Lambda AWS (a partir da versão do agente 10.29.0): + +* Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction +* Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction +* Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction + Limitações: * Métodos lambda genéricos não são instrumentados automaticamente. Se o seu método lambda for um método genérico, como `Task MyMethod(TRequest, ILambdaContext)`, o agente .NET atualmente não é capaz de instrumentar esse método. -* AspNetCore função do Lambda não são suportadas atualmente. A função AspNetCore do Lambda depende de um método genérico registrado como manipulador lambda. * O [Lambda Annotations Framework](https://aws.amazon.com/blogs/developer/net-lambda-annotations-framework/) atualmente não é compatível. * O evento [ApiGatewayV2](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html#http-api-develop-integrations-lambda.proxy-format) está faltando algum contexto necessário para distributed tracing. * distributed tracing de saída para diferentes chamadas AWS SDK (como SQS) não é compatível. @@ -378,4 +385,4 @@ A instrumentação OpenTelemetry Lambda para .NET fornece API de extensão e ras Este método requer alguma configuração manual inicial, dependendo do seu método de implantação. -Para obter detalhes de instalação, consulte [trace sua função .NET do Lambda com New Relic e OpenTelemetry](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/). +Para obter detalhes de instalação, consulte [trace sua função .NET do Lambda com New Relic e OpenTelemetry](/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet/). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx b/src/i18n/content/pt/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx index 32a1272dfc3..584ac2b6a3e 100644 --- a/src/i18n/content/pt/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx +++ b/src/i18n/content/pt/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui.mdx @@ -33,7 +33,7 @@ Os seguintes conceitos da New Relic são recorrentes ou se sobrepõem nas págin ## Encontre serviços OpenTelemetry APM [#find-apm-services] -Para encontrar os serviços OpenTelemetry APM , navegue até **All entities > Services > OpenTelemetry** ou **APM & Services**. Clique em um serviço para navegar até a [página de resumo](#summary-page) do serviço. +Para encontrar os serviços OpenTelemetry APM , navegue até **All entities > Services > OpenTelemetry** ou **APM & Services**. Clique em um serviço para navegar até a [página de resumo](#summary-page) do serviço. Dentro do explorador de entidades você pode filtrar por [tag entidade](/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data/). Para obter detalhes sobre como as tags entidade são computadas, consulte [RecursosOpenTelemetry no New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources). @@ -53,13 +53,13 @@ A distributed tracing página fornece detalhados insights OpenTelemetry trace so Assim como acontece com [os sinais clássicos](#golden-signals), os spans serão classificados como erros se o status do span estiver definido como `ERROR` (por exemplo, `otel.status_code = ERROR`). Se o intervalo for um erro, a descrição do status do intervalo (por exemplo, `otel.status_description`) será exibida em **detalhes do erro**. -OpenTelemetry span evento anexa informações adicionais de contexto de evento a um determinado intervalo. Eles são mais comumente usados para capturar informações de exceção. Se disponível, você poderá visualizar o evento de um período nos **detalhes de trace**. Observe que a presença de um evento de exceção de intervalo não qualifica o intervalo como um erro por si só. Somente períodos com status de período definido como `ERROR` são classificados como erros. +OpenTelemetry span evento anexa informações de contexto de evento adicionais a um intervalo específico. Eles são mais comumente usados para capturar informações de exceção. Se disponível, você pode visualizar o evento de um intervalo nos **trace details**. -Screenshot showing the right pane showing the two links for span events + + A presença de um evento de exceção de intervalo não qualifica o intervalo como um erro por si só. Somente intervalos com status de intervalo definido como `ERROR` são classificados como erros. + + +Screenshot showing the right pane showing the two links for span events ## Página: Mapa de serviços [#service-map-page] @@ -145,4 +145,4 @@ Várias páginas incluem uma alternância métrica ou de spans. Isso permite alt As métricas não estão sujeitas a amostragem e, portanto, são mais precisas, especialmente no cálculo de taxas como taxas de transferência. No entanto, as métricas estão sujeitas a restrições de cardinalidade e podem carecer de determinados atributos importantes para análise. Em contraste, os vãos são amostrados e, portanto, sujeitos a problemas de precisão, mas possuem atributos mais ricos, uma vez que não estão sujeitos a restrições de cardinalidade. -Historicamente, OpenTelemetry API/SDKs e instrumentação da linguagem priorizaram trace a instrumentação. No entanto, o projeto já percorreu um longo caminho e as métricas estão disponíveis em quase todos os idiomas. Verifique a [documentação](https://opentelemetry.io/docs/languages/) da linguagem e instrumentação relevantes para obter mais detalhes. +Historicamente, OpenTelemetry API/SDKs e instrumentação da linguagem priorizaram trace a instrumentação. No entanto, o projeto já percorreu um longo caminho e as métricas estão disponíveis em quase todos os idiomas. Verifique a [documentação](https://opentelemetry.io/docs/languages/) da linguagem e instrumentação relevantes para obter mais detalhes. \ No newline at end of file From 3920e22960ab1bb487515b951e70e788f5562b28 Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Fri, 23 Aug 2024 12:05:06 +0000 Subject: [PATCH 17/18] chore: add translations --- .../create-manage-accounts.mdx | 75 +- .../user-type.mdx | 669 ++++-------------- ...thetic-monitoring-best-practices-guide.mdx | 340 +++------ .../get-started/networks.mdx | 34 +- .../get-started-synthetic-monitoring.mdx | 54 +- .../using-monitors/add-edit-monitors.mdx | 249 ++----- .../intro-synthetic-monitoring.mdx | 36 +- 7 files changed, 378 insertions(+), 1079 deletions(-) diff --git a/src/i18n/content/jp/docs/accounts/accounts-billing/account-structure/create-manage-accounts.mdx b/src/i18n/content/jp/docs/accounts/accounts-billing/account-structure/create-manage-accounts.mdx index 1fe1628959a..6a179ac7ef4 100644 --- a/src/i18n/content/jp/docs/accounts/accounts-billing/account-structure/create-manage-accounts.mdx +++ b/src/i18n/content/jp/docs/accounts/accounts-billing/account-structure/create-manage-accounts.mdx @@ -15,7 +15,7 @@ New Relicのアカウント構造を使用すると、次のことが可能に * 組織のさまざまな領域にわたる請求を管理する * アカウントレベルでデータアクセスを制御する -このドキュメントでは、アカウント構造の設定について説明します。複数のアカウントを作成する場合は、データの取り込みを開始する_前に_作成することをお勧めします。New Relicをアプリケーションに接続した後は、これまでのコンテキストが失われるおそれがあるため、変更を加えるのが難しくなる場合があります。複数のアカウントの作成を待つ場合、ダウンタイムが警告される可能性もあります。 +このドキュメントでは、アカウント構造の設定について説明します。複数のアカウントを作成する場合は、データの取り込みを開始する*前に*作成することをお勧めします。New Relicをアプリケーションに接続した後は、これまでのコンテキストが失われるおそれがあるため、変更を加えるのが難しくなる場合があります。複数のアカウントの作成を待つ場合、ダウンタイムが警告される可能性もあります。 無料エディションまたはStandardエディションを使用している場合、使用できるアカウントは1つだけなので、このドキュメントは必要ありません。[ProまたはEnterprise](https://newrelic.com/pricing)に変更する場合は、お気軽にこのページに再度アクセスしてください。 @@ -25,23 +25,9 @@ New Relicのアカウント構造を使用すると、次のことが可能に 追加のアカウントを作成するかどうかを決定する際に重要となる、いくつかの用語をよく理解しておいてください。 -* - **Organization** - - - ：組織はNew Relicの顧客を表します。New Relic組織には、アカウント、ユーザー、データが含まれています。 - -* - **Account** - - - ：New Relicにサインアップすると、組織に1つのアカウントが自動的に割り当てられます。アカウントには、レポートする多くのデータソースがあります。たとえば、1つのアカウントで、当社のInfrastructureエージェント、APM エージェント、およびその他のインテグレーションからのデータレポートを作成できます。New RelicにレポートされるすべてのデータにはアカウントIDが必要です。これにより、New Relicは対象アカウントに属するデータを把握できます。このIDは、API呼び出しなどのアカウント固有のタスクにも使用されます。 - -* - **User** - - - : お客様の組織の[New Relicユーザー](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users/)には、職務と責任に関連する特定のアカウントへのアクセス権が付与されます。ユーザーのアカウントへのアクセスを管理するには、特定のアカウントの特定の役割にグループアクセスを許可します。当社のユーザー管理システムでは、いくつかのアカウントでの役割が少数の場合でも、多くのアカウントで多くの役割を持つ複雑な場合でも、必要なユーザーアクセスを作成できます +* **Organization**：組織はNew Relicの顧客を表します。New Relic組織には、アカウント、ユーザー、データが含まれています。 +* **Account**：New Relicにサインアップすると、組織に1つのアカウントが自動的に割り当てられます。アカウントには、レポートする多くのデータソースがあります。たとえば、1つのアカウントで、当社のInfrastructureエージェント、APM エージェント、およびその他のインテグレーションからのデータレポートを作成できます。New RelicにレポートされるすべてのデータにはアカウントIDが必要です。これにより、New Relicは対象アカウントに属するデータを把握できます。このIDは、API呼び出しなどのアカウント固有のタスクにも使用されます。 +* **User**: お客様の組織の[New Relicユーザー](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users/)には、職務と責任に関連する特定のアカウントへのアクセス権が付与されます。ユーザーのアカウントへのアクセスを管理するには、特定のアカウントの特定の役割にグループアクセスを許可します。当社のユーザー管理システムでは、いくつかのアカウントでの役割が少数の場合でも、多くのアカウントで多くの役割を持つ複雑な場合でも、必要なユーザーアクセスを作成できます ## 単一アカウント構造 [#single-account-structure] @@ -62,12 +48,7 @@ New Relicにサインアップすると、組織が自動生成されます。 複数のアカウントを使用すると、複数の環境にわたるデータを観察できるため、本番環境に移行する前に変更を監視できます。アプリケーションを定期的に更新する場合は、各デプロイメントにエラーがないことを確認できる強力なテスト環境を用意することが重要です。 -A diagram demonstrating how to use New Relic with multiple environments +A diagram demonstrating how to use New Relic with multiple environments ### 固有のデータセットと複数のアカウントを持つ個別のプロジェクト [#data-sets] @@ -78,21 +59,16 @@ New Relicにサインアップすると、組織が自動生成されます。 * 複数の国で稼働する決済プロバイダーを管理しており、各国のデータ（通貨、税金規制など）が他の国のデータと混在することを望んでいません * ソーシャルメディアサイトを管理しており、地域ごとに異なるデータ収集ポリシーに準拠する必要があります -A diagram showing how to use New Relic with multiple data sets +A diagram showing how to use New Relic with multiple data sets ### アカウントを使用して大規模なデータ制限を管理する [#large-data-limits] 大量のデータを取り込む予定がある場合は、データ制限を回避するために複数のアカウントを作成することをお勧めします。金融機関や医療サービス提供者は、複数の地域にまたがる取引やユーザー情報を高速で追跡するため、大量のデータを取り込むことがよくあります。大手小売業者も複数のアカウントを作成することでメリットを得られます。単一の組織で複数の異なる店舗を運営している場合は、会社ごとにアカウントを作成することをお勧めします。 -以下に、留意すべき重要な制限をいくつか示します。 +以下の重要な制限に留意してください。 * アラート条件のデフォルトはアカウントごとに4,000条件です -* アラートワークフローのデフォルトは、アカウントごとに4,000ワークフローです +* アラートワークフローのデフォルトは、アカウントごとに1,000ワークフローです * アラートポリシーのデフォルトは、アカウントごとに10,000ポリシーです * アラートの送信先はデフォルトでアカウントごとに2,000件です * NRDBクエリで検査されるカウント制限は、標準アカウントとData Plusアカウントでは異なります @@ -102,23 +78,13 @@ New Relicにサインアップすると、組織が自動生成されます。 * [NRQLクエリの検査されたデータポイント](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#inspected-count-limits) * [アラート制限](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/rules-limits-alerts/) -A screenshot depicting how to use New Relic to manage large data limits +A screenshot depicting how to use New Relic to manage large data limits ### 複数のアカウントを使用してセキュリティを管理する [#security] ユーザー全員がすべてのデータにアクセスする必要はありません。請負業者にかなり依存しているスタートアップ企業だとしましょう。臨時従業員にすべての履歴データへのアクセスを許可したくない場合があります。ここで複数アカウントを作成するとよいでしょう。 -A diagram showing how to use New Relic to manage security +A diagram showing how to use New Relic to manage security ### 複数のアカウントとディストリビューティッド（分散）トレーシング @@ -129,18 +95,9 @@ New Relicのディストリビューティッド（分散）トレーシング ## 次のステップ - - - - - - + + + + + + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx index 2c8a0686999..5e5a18e42eb 100644 --- a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx +++ b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx @@ -23,23 +23,9 @@ New Relicユーザーの**user type**では、ユーザーがアク 3つのユーザータイプがあります。 -* - **Basic user** - - - ：いくつかの基本的でありながら強力なNew Relicプラットフォーム機能にアクセスできます。 - -* - **Core user** - - - ：ベーシックユーザーよりも多くの機能にアクセスできます。 - -* - **Full platform user** - - - ：すべての機能にアクセスできます。 +* **Basic user**：いくつかの基本的でありながら強力なNew Relicプラットフォーム機能にアクセスできます。 +* **Core user**：ベーシックユーザーよりも多くの機能にアクセスできます。 +* **Full platform user**：すべての機能にアクセスできます。 [New Relicユーザーを追加する](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model/#add-users)必要がある場合、作成するユーザータイプを決定するのが重要になります。わからない場合は、まずベーシックユーザーとして追加し、後からどのユーザーをアップグレードするか決定できます。ユーザータイプの調整方法については、[ユーザータイプの管理](#manage-user-type)を参照してください。 @@ -67,15 +53,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - ベーシックユーザーは無料です。ベーシックユーザーは、当社のオブザーバビリティツールの設定、データのクエリの実行、カスタム（7日間のクイックスタートダッシュボード）の使用、基本的なアラート機能の使用などを行うことができます。ベーシックユーザーは、キュレート済みのエクスペリエンスは使用**できません**。（ UI、 UI、モバイルUIなど）。 + ベーシックユーザーは無料です。ベーシックユーザーは、当社のオブザーバビリティツールの設定、データのクエリの実行、カスタム（7日間のクイックスタートダッシュボード）の使用、基本的なアラート機能の使用などを行うことができます。ベーシックユーザーは、キュレート済みのエクスペリエンスは使用**できません**。（ UI、 UI、モバイルUIなど）。 - コアユーザーは、ベーシックユーザーよりも多くの機能にアクセスできますが、フルプラットフォーム ユーザーに比べると機能は限定されます。New Relic CodeStream、エラー受信トレイ、ログ管理UIなど、開発者を重視した強力な機能の一部にアクセスできます。 + コアユーザーは、ベーシックユーザーよりも多くの機能にアクセスできますが、フルプラットフォーム ユーザーに比べると機能は限定されます。New Relic Errors Inbox、ログ管理UIなど、開発者を重視した強力な機能の一部にアクセスできます。 - フルプラットフォームのユーザーは、APM、infrastructureモニタリング、ブラウザモニタリング、、Syntheticsモニターを含む、さらにキュレートされたオブザーバビリティUI体験などのすべての機能にアクセスできます。 + フルプラットフォームのユーザーは、APM、infrastructureモニタリング、ブラウザモニタリング、、Syntheticsモニターを含む、さらにキュレートされたオブザーバビリティUI体験などのすべての機能にアクセスできます。 @@ -106,8 +92,7 @@ New Relicユーザーの**user type**では、ユーザーがアク * プラットフォームへのフルアクセスは必要ないが、次のようなコアユーザーに提供される特定の機能からメリットを得られる。 - * [New Relic CodeStream](/docs/codestream/start-here/what-is-codestream)を使用して、コードの問題をIDEから直接デバッグする機能。 - * [エラー受信トレイ](/docs/errors-inbox/errors-inbox)を使用して、スタック全体から1か所でエラーを表示する機能。 + * [Errors Inbox](/docs/errors-inbox/errors-inbox)を使用するとスタック全体のエラーを1か所で表示できます。 * [ログUI](/docs/logs/ui-data/use-logs-ui)を使用して、ログの問題とパターンを特定する機能。 * [New Relicアプリカタログ](https://opensource.newrelic.com/nerdpacks)のアプリを使用する機能。 @@ -117,48 +102,18 @@ New Relicユーザーの**user type**では、ユーザーがアク **Reasons to make someone a basic user:** -* キュレート済みのエクスペリエンスと - - - - を使用するために、プラットフォームへのフルアクセスは不要であるが、データのカスタムクエリやチャートを作成できるメリットがある。 - +* キュレート済みのエクスペリエンスとを使用するために、プラットフォームへのフルアクセスは不要であるが、データのカスタムクエリやチャートを作成できるメリットがある。 * アプリケーション開発ライフサイクルの企画段階で重要な役割を担っている。 - -* New Relicツールを使用および設定してデータをNew Relicに取り込み、そのデータにアクセスして設定し、 - - - - を使用している（必ずしも、ワークフローのトリアージ、トラブルシューティング、またはチームのユーザーとロールの管理を担当する必要はない）。 - +* New Relicツールを使用および設定してデータをNew Relicに取り込み、そのデータにアクセスして設定し、を使用している（必ずしも、ワークフローのトリアージ、トラブルシューティング、またはチームのユーザーとロールの管理を担当する必要はない）。 * 将来の企画（Cレベルのエグゼクティブに該当）のために高いレベルの分析とビジネスメトリクスを望んでいる。 - * ユーザーや請求を管理していない。 ## ユーザータイプのアクセス比較表 [#user-type-comparison-table] 以下は、各ユーザータイプがアクセスできる機能の詳細な比較です。この表における重要なポイント： -* この表は[当社の価格設定ページ](https://newrelic.com/pricing)を元にしています。表を検索するには、 - - - **User costs** - - - の見出しにアクセスし、 - - - **View permissions** - - - をクリックします。 - -* 機能の多くは、基礎となるデータではなく、UIエクスペリエンスへのアクセスを必要とします。すべてのユーザーは、アクセスできるアカウント内のすべてのデータをクエリし、カスタムチャートを作成して表示できます。たとえば、ベーシックユーザーは - - - - データやブラウザモニタリングデータなどにアクセスできますが、キューレート済みUIエクスペリエンスにはアクセスできません。 - +* この表は[当社の価格設定ページ](https://newrelic.com/pricing)を元にしています。表を検索するには、**User costs**の見出しにアクセスし、**View permissions**をクリックします。 +* 機能の多くは、基礎となるデータではなく、UIエクスペリエンスへのアクセスを必要とします。すべてのユーザーは、アクセスできるアカウント内のすべてのデータをクエリし、カスタムチャートを作成して表示できます。たとえば、ベーシックユーザーはデータやブラウザモニタリングデータなどにアクセスできますが、キューレート済みUIエクスペリエンスにはアクセスできません。 * ユーザータイプは長期的な設定を意図しています。ユーザータイプとロールの両方で、New Relic機能へのアクセスを管理します。[ユーザーアクセスの要因についての詳細をご覧ください](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts)。 ユーザータイプの選択に関するヒントについては、[ユーザータイプを決定する](#choose-user-type)を参照してください。 @@ -191,24 +146,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -218,24 +164,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -245,24 +182,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -272,23 +200,21 @@ New Relicユーザーの**user type**では、ユーザーがアク - リスト表示のみ
+ リストビューのみ + +
+ + - + （偏差信号を除く） - + @@ -298,24 +224,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -325,24 +242,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -352,21 +260,19 @@ New Relicユーザーの**user type**では、ユーザーがアク - 検索/閲覧のみ
+ 検索/閲覧のみ + +
+ + - + - + @@ -376,24 +282,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -403,18 +300,23 @@ New Relicユーザーの**user type**では、ユーザーがアク - 最大7日間
+ 最大7日間 + +
+ + - 最大7日間
+ 最大7日間 + +
+ + - + @@ -424,24 +326,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -451,24 +344,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -478,24 +362,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -505,21 +380,19 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - 属性分析を除く
+ 属性分析を除く + +
+ + - + @@ -529,24 +402,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -556,24 +420,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -583,24 +438,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -610,24 +456,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -637,24 +474,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -664,24 +492,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -691,24 +510,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -718,24 +528,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -745,24 +546,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -772,24 +564,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -799,24 +582,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -826,24 +600,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -853,24 +618,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -880,24 +636,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -907,24 +654,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -934,24 +672,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -961,24 +690,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -988,24 +708,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -1015,24 +726,15 @@ New Relicユーザーの**user type**では、ユーザーがアク - + - + - + @@ -1045,10 +747,7 @@ New Relicユーザーの**user type**では、ユーザーがアク いくつかの機能の権限に関する詳細は次のとおりです。 - + ユーザータイプがアラートと応用インテリジェンス機能へのアクセスにどのように影響するかについて、以下に詳しく説明します。 @@ -1058,17 +757,11 @@ New Relicユーザーの**user type**では、ユーザーがアク 何が得られるか - - @@ -1085,24 +778,15 @@ New Relicユーザーの**user type**では、ユーザーがアク @@ -1112,24 +796,15 @@ New Relicユーザーの**user type**では、ユーザーがアク @@ -1144,61 +819,36 @@ New Relicユーザーの**user type**では、ユーザーがアク * 機械学習の分類 -
+ 基本ユーザー + コアユーザー - + - + - +
- + - + - +
+ - + - +
- + [API](/docs/apis/intro-apis/introduction-new-relic-apis)へのアクセスに関する詳細： - * - **Data ingest** - - - ：すべてのユーザータイプでは、取り込みAPI経由でのデータの取り込みなど、ほぼすべてのインテグレーションとエージェントを設定できます。一部のNew Relicソリューションでは、設定にフルプラットフォームユーザーが必要です。その場合は、これらのソリューションのドキュメントの要件セクションを参照してください。 - - * - **NerdGraph** - + * **Data ingest**：すべてのユーザータイプでは、取り込みAPI経由でのデータの取り込みなど、ほぼすべてのインテグレーションとエージェントを設定できます。一部のNew Relicソリューションでは、設定にフルプラットフォームユーザーが必要です。その場合は、これらのソリューションのドキュメントの要件セクションを参照してください。 + * **NerdGraph**：ユーザーは[NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph)を使用して、UIから実行できるのと同じ操作を行うことができます。たとえば、設定を行うには、フルプラットフォームユーザーである必要があり、設定をUIまたはNerdGraph経由で行うかどうかは問題ではありません。別の例：[管理関連の権限](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings)（ユーザーの追加、アカウントの追加など）は、コアユーザーまたはフルプラットフォームユーザーである必要があります。UIまたはNerdGraph経由のいずれかで行えます。 - ：ユーザーは[NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph)を使用して、UIから実行できるのと同じ操作を行うことができます。たとえば、 - - - - 設定を行うには、フルプラットフォームユーザーである必要があり、設定をUIまたはNerdGraph経由で行うかどうかは問題ではありません。別の例：[管理関連の権限](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings)（ユーザーの追加、アカウントの追加など）は、コアユーザーまたはフルプラットフォームユーザーである必要があります。UIまたはNerdGraph経由のいずれかで行えます。 - - APIの使用時に権限がないことに関するエラーメッセージは、ユーザータイプの制限に関連している場合があります。アクセス要因の詳細については、[アクセスに影響を与える要因](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data)を参照してください。 + APIの使用時に権限がないことに関するエラーメッセージは、ユーザータイプの制限に関連している場合があります。アクセス要因の詳細については、[アクセスに影響を与える要因](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data)を参照してください。 - + [インスタントオブザーバビリティページ](https://newrelic.com/instant-observability)の利用可能なオプションへのアクセスに関する詳細： * ベーシックユーザーおよびコアユーザーは、ほぼすべてのNew Relicソリューションをインストールできますが、[ユーザータイプの表](#user-type-comparison-table)に示すように、当社のキュレート済みのエクスペリエンス（APM UI、モバイルUI、Infrastructure UIなど）にはアクセスできません。 * クイックスタートに付属するカスタムダッシュボード（たとえば、[.NETクイックスタート](https://newrelic.com/instant-observability/dotnet)に含まれるダッシュボード）の場合：ベーシックユーザーとコアユーザーは7日間アクセスできます。 - - ユーザータイプ別の機能へのアクセスに関する詳細： + + ユーザータイプ別の機能へのアクセスに関する詳細： @@ -1231,7 +881,7 @@ New Relicユーザーの**user type**では、ユーザーがアク * 保存された共有ビューの作成 * [ライブ テイルログ](/docs/logs/troubleshooting/view-log-messages-real-time-live-tail)の使用 - これらのユーザーは、アクセス可能なUIエクスペリエンスの[コンテキストでログ](/docs/logs/logs-context/configure-logs-context-apm-agents)を表示することもできます（たとえば、コアユーザーはエラー受信トレイUIでログデータを表示できます）。 + これらのユーザーは、アクセス可能なUIエクスペリエンスの[コンテキストでログ](/docs/logs/logs-context/configure-logs-context-apm-agents)を表示することもできます（たとえば、コアユーザーはエラー受信トレイUIでログデータを表示できます）。 @@ -1243,27 +893,8 @@ New Relicユーザーの**user type**では、ユーザーがアク ユーザータイプと[ロールベースのアクセス](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts)の違いについては、以下に説明します。 -* ユーザーの - - - **[user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)** - - - ：ユーザータイプは、組織がチームメンバーに対してNew Relicを使用して期待する作業、そしてその作業からどれだけの価値が得られるかを期待することで決定されます。これは主に請求関連の決定です。ユーザーがアクセスできる最大許可権限を設定します。ユーザータイプは、ユーザーのアクセスと権限を制御するために使用することを意図したもの**ではありません**。それを行うには、ロールを使用する必要があります - -* ユーザーの - - - **roles** - - - ：ロールはユーザーのアクセスを制御するものです。ロールは、New Relicで特定の作業を行うアクセスを付与する - - - **permissions** - - - （APM設定を変更する機能など）で構成されます。ロールは、[ユーザーグループ](#groups)に適用することで割り当てられ、組織内の1つ以上のアカウントに存在できます。 +* ユーザーの**[user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)**：ユーザータイプは、組織がチームメンバーに対してNew Relicを使用して期待する作業、そしてその作業からどれだけの価値が得られるかを期待することで決定されます。これは主に請求関連の決定です。ユーザーがアクセスできる最大許可権限を設定します。ユーザータイプは、ユーザーのアクセスと権限を制御するために使用することを意図したもの**ではありません**。それを行うには、ロールを使用する必要があります +* ユーザーの**roles**：ロールはユーザーのアクセスを制御するものです。ロールは、New Relicで特定の作業を行うアクセスを付与する**permissions**（APM設定を変更する機能など）で構成されます。ロールは、[ユーザーグループ](#groups)に適用することで割り当てられ、組織内の1つ以上のアカウントに存在できます。 New Relicユーザーには、a）ユーザータイプおよびb）役割権限の組み合わせによって、New Relic機能を使用する権限が与えられます。New Relicユーザーが何かにアクセスするには、そのユーザータイプと割り当てられたロール（複数可）でアクセスを許可する必要があります。 @@ -1284,4 +915,4 @@ New Relicユーザーには、a）ユーザータイプおよびb）役割権限 ## 何かにアクセスできませんか？ [#access] -New Relicアカウントまたは機能へのアクセス不能に関する質問については、[アクセスに影響する要因](/docs/accounts/accounts-billing/general-account-settings/factors-affecting-access-features-data/#account-access)を参照してください。 +New Relicアカウントまたは機能へのアクセス不能に関する質問については、[アクセスに影響する要因](/docs/accounts/accounts-billing/general-account-settings/factors-affecting-access-features-data/#account-access)を参照してください。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide.mdx b/src/i18n/content/jp/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide.mdx index 49d3dd422ea..c486121175a 100644 --- a/src/i18n/content/jp/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide.mdx +++ b/src/i18n/content/jp/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide.mdx @@ -22,66 +22,30 @@ Syntheticsモニタリングを使用すると、アプリを監視しテスト ## Syntheticモニターを追加する [#howto-1] - 1. モニターを追加するには、**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Synthetic Monitoring**の順に移動します。 + 1. モニターを追加するには、**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Synthetic Monitoring**の順に移動します。 [EUベースのアカウント](/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center)がある場合は、 **[one.eu.newrelic.com](http://one.eu.newrelic.com)**に移動します。 2. **Create monitor**をクリックします。 - A screenshot showing the location of the Create monitor button in the UI. + A screenshot showing the location of the Create monitor button in the UI. 3. モニタータイプを選択し、すべての必須フィールドに入力します。 - 4. タグの追加、期間の変更、または別の[ランタイムバージョン](/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime)の選択ができます。pingおよび単純なブラウザモニターでは、検証文字列を追加できます。高度なオプションを使用して、次のタイプの応答検証の部分文字列モニタリングを有効にすることができます。 + 4. タグの追加、期間の変更、複数のブラウザやエミュレートされたデバイスの設定からの選択、または別の[ランタイムバージョン](/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime)の選択ができます。pingおよび単純なブラウザモニターでは、検証文字列を追加できます。また、高度なオプションを使用して追加機能を有効にすることができます。 - * - **Verify SSL (for ping and simple browser).** - + * **Text validation (for ping and simple browser).** このオプションは、指定されたテキストが応答に含まれていることを確認します。 + * **Verify SSL (for ping and simple browser).** このオプションは、SSL証明書チェーンの有効性を検証します。次の構文を実行することによって複製することができます。 - このオプションは、SSL証明書チェーンの有効性を検証します。次の構文を実行することによって複製することができます。 + ```sh + openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApath /etc/ssl/certs > /dev/null + ``` -```sh -openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApath /etc/ssl/certs > /dev/null -``` - - * - **Bypass HEAD request (for ping monitors).** - - - このオプションは、デフォルトのHEADリクエストをスキップし、その代わりにpingチェックを含むGET動詞を使用します。HEADリクエストが失敗した場合、GETリクエストは常時発生します。 - - * - **Redirect is Failure (for ping).** - - - `Redirect is Failure`が有効になっているときにリダイレクト結果が発生すると、Syntheticsモニターはリダイレクトにしたがって、結果のURLをチェックするのではなく、結果をエラーとして分類します。 + * **Bypass HEAD request (for ping monitors).** このオプションは、デフォルトのHEADリクエストをスキップし、その代わりにpingチェックを含むGET動詞を使用します。HEADリクエストが失敗した場合、GETリクエストは常時発生します。 + * **Redirect is Failure (for ping).** `Redirect is Failure`が有効になっているときにリダイレクト結果が発生すると、Syntheticsモニターはリダイレクトにしたがって、結果のURLをチェックするのではなく、結果をエラーとして分類します。 5. モニターを実行するロケーションを選択します。誤検出を避けるために、少なくとも3つの場所を選択するようにしてください。つまり、少なくとも1つの場所が成功した結果を返す場合、エンドポイントは稼働しており、アラートのトリガーを回避できます。 - - 6. モニターの種類に応じて、 - - - **Save monitor** - - - 、 - - - **Validate** - - - 、 - - - **Write script** - - - のいずれかを行うよう求められます。 - + 6. モニターの種類に応じて、**Save monitor**、 **Validate**、**Write script**のいずれかを行うよう求められます。 7. 結果を受け取ったら、[概要ページ](#summary-page)で表示します。 @@ -90,11 +54,7 @@ openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApat 概要ページには、Syntheticモニターのステータスに関する情報が表示されます。アラートをトリガーするアクティブなインシデントが作成された場合は、クリティカルなアラートリンクをクリックして新しいウィンドウを開きます。 - A screenshot that shows where your critical alerts are located in the UI. + A screenshot that shows where your critical alerts are located in the UI. @@ -107,24 +67,18 @@ openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApat ### モニターをエンティティのリストで表示する [#howto-2] - + モニターのリストを表示するには： - **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities)**に移動し、次に**Synthetic monitoring**に移動します。 + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities)**に移動し、次に**Synthetic monitoring**に移動します。 詳細については、[データの探索に関するドキュメントを](/docs/query-your-data/explore-query-data/browse-data/introduction-data-explorer/)参照してください。 - + [モニターインデックス](/docs/synthetics/new-relic-synthetics/pages/synthetics-monitors-index-access-your-monitors)ページを使用してモニターのリストを表示する: - **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Synthetic Monitoring**に移動します。 + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Synthetic Monitoring**に移動します。 @@ -134,7 +88,7 @@ openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApat 世界中のさまざまな地域からアクセスされるウェブアプリのパフォーマンスを確認できます。[結果](/docs/synthetics/new-relic-synthetics/pages/synthetics-results-access-individual-monitor-runs)ページには、開発から本番までのすべてがユーザー体験にいかに影響するかが表示されます。リストされているものを並べ替えて、問題のある領域や異常結果を特定できます。場所別にフィルタリングして、さまざまな場所からのモニターのパフォーマンスを比較してみてください。これを行うには、以下を実行します。 - 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Synthetic Monitoring**に移動します。 + 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Synthetic Monitoring**に移動します。 2. **Monitor**をクリックし、**Results**をクリックします。 @@ -146,35 +100,9 @@ openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApat [Syntheticsリソース](/docs/synthetics/new-relic-synthetics/pages/synthetics-resources-understand-load-times)ページでは、サイトのさまざまなコンポーネントが全体的な負荷にどのような影響を与えるかを確認できます。これらのコンポーネントには、CSS、JavaScript、画像、HTMLなどがあります。 ランタイムに収集される詳細なメトリクスを掘り下げて調べ、サードパーティリソースによって費やされる時間に関するパフォーマンス情報を検出し、各リソースのHTTP応答コードを特定することができます。これを行うには、以下を実行します。 - 1. - **[one.newrelic.com](https://one.newrelic.com/all-capabilities)** - - - に移動し、次に - - - **Synthetic Monitoring** - - - をクリックします。 - - 2. - **Monitors** - - - ドロップダウンメニューから、モニターを選択します。 - - 3. - **Monitor** - - - をクリックし、 - - - **Resources** - - - をクリックします。 + 1. **[one.newrelic.com](https://one.newrelic.com/all-capabilities)**に移動し、次に**Synthetic Monitoring**をクリックします。 + 2. **Monitors**ドロップダウンメニューから、モニターを選択します。 + 3. **Monitor**をクリックし、**Resources**をクリックします。 @@ -182,156 +110,122 @@ openssl s_client -servername {YOUR_HOSTNAME} -connect {YOUR_HOSTNAME}:443 -CApat スクリプト化ブラウザモニターを使用すると、 Selenium JavaScript Webdriverで監視ワークフローを簡単に構築できます。たとえば、特定のページに移動し、ページ上の要素を見つけ、期待したテキストが見つかったことを確認し、スクリーンショットを撮ることができます。これを行うには、以下を実行します。 - 1. - **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Synthetic Monitoring** - - - に移動します。 - - 2. - **Create monitor** - - - ボタンをクリックします。 - - 3. - **Scripted browser** - - - モニタータイプを選択します。 - + 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Synthetic Monitoring**に移動します。 + 2. **Create monitor**ボタンをクリックします。 + 3. **Scripted browser**モニタータイプを選択します。 4. 名前を入力し、実行時間を選択し、モニターの期間を選択します。 - 5. モニターを実行する場所を選択します。たとえば、ムンバイ、ソウル、コロンバス、モントリオールなどです。 - 6. これでスクリプトを記述する準備ができました。`newrelic.com`のパフォーマンスをテストし、特定の要素が読み込まれたかどうかを確認するには、このサンプルスクリプトを参照してください。 -```js -/** - * Script Name: Best Practices Example - Chrome 100+ - * Author: New Relic - * Version: 1.0 - * Purpose: A simple New Relic Synthetics scripted browser monitor to navigate to a page, find an element, and assert on expected text. - */ + ```js + /** + * Script Name: Best Practices Example - Chrome 100+ + * Author: New Relic + * Version: 1.0 + * Purpose: A simple New Relic Synthetics scripted browser monitor to navigate to a page, find an element, and assert on expected text. + */ -// -------------------- DEPENDENCIES -const assert = require("assert") + // -------------------- DEPENDENCIES + const assert = require("assert") -// -------------------- CONFIGURATION -const PAGE_URL = "https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100/" -const TEXT_TO_CHECK = "Synthetic scripted browser reference (Chrome 100 and higher)" + // -------------------- CONFIGURATION + const PAGE_URL = "https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100/" + const TEXT_TO_CHECK = "Synthetic scripted browser reference (Chrome 100 and higher)" -// Set timeouts for page load and element finding -await $webDriver.manage().setTimeouts({ - pageLoad: 30000, // 30 seconds for page load timeout - implicit: 5000, // 5 seconds for element finding timeout -}) + // Set timeouts for page load and element finding + await $webDriver.manage().setTimeouts({ + pageLoad: 30000, // 30 seconds for page load timeout + implicit: 5000, // 5 seconds for element finding timeout + }) -// -------------------- START OF SCRIPT -console.log("Starting simplified synthetics script") + // -------------------- START OF SCRIPT + console.log("Starting simplified synthetics script") -// Navigate to the page -console.log("Navigating to: " + PAGE_URL) -await $webDriver.get(PAGE_URL) + // Navigate to the page + console.log("Navigating to: " + PAGE_URL) + await $webDriver.get(PAGE_URL) -// Find the element with the specified text -const By = $selenium.By -const textElement = By.className("css-v50zng") + // Find the element with the specified text + const By = $selenium.By + const textElement = By.className("css-v50zng") -console.log("Checking for presence of element with text: " + TEXT_TO_CHECK) -const element = await $webDriver.findElement(textElement) -const text = await element.getText() + console.log("Checking for presence of element with text: " + TEXT_TO_CHECK) + const element = await $webDriver.findElement(textElement) + const text = await element.getText() -// Assert the text is present -console.log("Found text: " + text) -assert.equal(text, TEXT_TO_CHECK, "Expected text not found on the page") + // Assert the text is present + console.log("Found text: " + text) + assert.equal(text, TEXT_TO_CHECK, "Expected text not found on the page") -// Take a screenshot -console.log("Taking screenshot") -await $webDriver.takeScreenshot() + // Take a screenshot + console.log("Taking screenshot") + await $webDriver.takeScreenshot() -console.log("Script completed successfully") -``` + console.log("Script completed successfully") + ``` スクリプト化されたAPIモニターを使用すると、Node.jsと`got`モジュールで監視ワークフローを簡単に構築できます。たとえば、APIを使用して認証し、応答コードをアサートすることができます。 - 1. - **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Synthetic Monitoring** - - - に移動します。 - - 2. - **Create monitor** - - - ボタンをクリックします。 - - 3. - **Scripted API** - - - モニタータイプを選択します。 - + 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Synthetic Monitoring**に移動します。 + 2. **Create monitor**ボタンをクリックします。 + 3. **Scripted API**モニタータイプを選択します。 4. 名前を入力し、実行時間を選択し、モニターの期間を選択します。 - 5. モニターを実行する場所を選択します。たとえば、ムンバイ、ソウル、コロンバス、モントリオールなどです。 - 6. これでスクリプトを記述する準備ができました。APIリクエストを作成して応答を処理するこのサンプルスクリプトを参照してください。 -```js -/** - * Script Name: Best Practices Example - Node 16.10.0 - * Author: New Relic - * Version: 1.0 - * Purpose: A simple New Relic Synthetics scripted API monitor to make a GET request and assert on statusCode. - */ - -const assert = require("assert") - -// Get secure credentials -const applicationId = $secure.APP_ID -const apiKey = $secure.API_KEY - -// The URL for the API endpoint to get information about a specific application -const URL = `https://api.newrelic.com/v2/applications/${applicationId}.json` - -// Define headers, including the API key for authentication -const headers = { - "X-Api-Key": apiKey, -} - -// Make a GET request -$http.get({ url: URL, headers: headers }, function (error, response, body) { - // If error handling is needed, check if an error occurred during the request - // if (error) { - // console.error("An error occurred:", error); - // Handle the error as needed, or rethrow to fail the monitor - // throw error; - // } - - // Assert the response status code is 200 - assert.equal(response.statusCode, 200, "Expected HTTP status code 200") - - // Log the status code to the console - console.log("Request Status Code:", response.statusCode) - - // If further processing of the response body is needed, it can be done here - // For example, parsing JSON response (if response is in JSON format) - // const jsonData = - // typeof body === "string" - // ? JSON.parse(body) - // : body - - // Log the parsed JSON to the console - // console.log("Parsed JSON data:", jsonData) - - // Check the application's health status - // const healthStatus = jsonData.application.health_status - // assert.equal(healthStatus, "green", "Expected the application's health status to be 'green'") - - // If the assertion passes, the script will continue; otherwise, it will fail the monitor -}) -``` + ```js + /** + * Script Name: Best Practices Example - Node 16.10.0 + * Author: New Relic + * Version: 1.0 + * Purpose: A simple New Relic Synthetics scripted API monitor to make a GET request and assert on statusCode. + */ + + const assert = require("assert") + + // Get secure credentials + const applicationId = $secure.APP_ID + const apiKey = $secure.API_KEY + + // The URL for the API endpoint to get information about a specific application + const URL = `https://api.newrelic.com/v2/applications/${applicationId}.json` + + // Define headers, including the API key for authentication + const headers = { + "X-Api-Key": apiKey, + } + + // Make a GET request + $http.get({ url: URL, headers: headers }, function (error, response, body) { + // If error handling is needed, check if an error occurred during the request + // if (error) { + // console.error("An error occurred:", error); + // Handle the error as needed, or rethrow to fail the monitor + // throw error; + // } + + // Assert the response status code is 200 + assert.equal(response.statusCode, 200, "Expected HTTP status code 200") + + // Log the status code to the console + console.log("Request Status Code:", response.statusCode) + + // If further processing of the response body is needed, it can be done here + // For example, parsing JSON response (if response is in JSON format) + // const jsonData = + // typeof body === "string" + // ? JSON.parse(body) + // : body + + // Log the parsed JSON to the console + // console.log("Parsed JSON data:", jsonData) + + // Check the application's health status + // const healthStatus = jsonData.application.health_status + // assert.equal(healthStatus, "green", "Expected the application's health status to be 'green'") + + // If the assertion passes, the script will continue; otherwise, it will fail the monitor + }) + ``` - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/new-relic-solutions/get-started/networks.mdx b/src/i18n/content/jp/docs/new-relic-solutions/get-started/networks.mdx index 6b4aa3715ec..96c55e70911 100644 --- a/src/i18n/content/jp/docs/new-relic-solutions/get-started/networks.mdx +++ b/src/i18n/content/jp/docs/new-relic-solutions/get-started/networks.mdx @@ -69,7 +69,7 @@ translationType: human @@ -95,7 +95,7 @@ translationType: human @@ -153,7 +153,11 @@ translationType: human @@ -400,10 +404,7 @@ translationType: human 上記の表のテレメトリーエンドポイントは、以下の簡単にコピーできるリストに含まれています。 - + 以下は、簡単にコピーできるリストの上のエンドポイントテーブルに含まれる、[米国データセンター地域](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)のエンドポイントのリストです。 * `collector.newrelic.com` @@ -425,10 +426,7 @@ translationType: human * `otlp.nr-data.net` - + 以下は、簡単にコピーできるリストの上のエンドポイントテーブルに含まれる、[EUデータセンター地域](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)のエンドポイントのリストです。 * `collector.eu.newrelic.com` @@ -564,7 +562,7 @@ New Relicが適切に機能するには、ブラウザが多数のドメイン @@ -176,7 +164,7 @@ Syntheticモニターには以下の7つのタイプがあります。 @@ -198,7 +186,7 @@ UIで直接[合成モニターの追加および編集](/docs/synthetics/synthet ## スクリプト化されたブラウザによる高度なテスト [#advanced] -Syntheticモニタリングの使用により、ウェブサイトまたはAPIエンドポイントをプロアクティブにモニターできます。これにより、コンテンツが確実に利用できるようになるだけでなく、完全な機能を確実に実現できます。[スクリプト化されたブラウザ](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts)は、どの場所でも常にコンテンツが稼働していることを確認するために、世界中のあらゆる場所から、Seleniumを搭載したリアルなGoogle Chromeインスタンスをサイトに送信します。 +Syntheticモニタリングの使用により、ウェブサイトまたはAPIエンドポイントをプロアクティブにモニターできます。これにより、コンテンツが確実に利用できるようになるだけでなく、完全な機能を確実に実現できます。[スクリプト化されたブラウザは](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts)、どの場所でも常にコンテンツが稼働していることを確認するために、世界中のあらゆる場所から、Seleniumを搭載したリアルなChromeまたはFirefoxのインスタンスをサイトに送信します。 スクリプト化ブラウザは、テスト機能を拡大し、一般的ではないユーザーフローまたはベータテストなどの複雑な手順もテストできます。たとえば、ニュースレターへのサインアップやアイテムのカートへの追加、または簡単なJavaScriptのような言語を使用した重要な情報の検索などをユーザーが実行していることを確認できます。APIエンドポイントに対してスクリプト化テストを実行可能にするAPIモニターで、バックエンドテストも可能です。 @@ -226,7 +214,7 @@ Syntheticモニタリングには以下の機能が含まれます。 @@ -246,7 +234,7 @@ Syntheticモニタリングには以下の機能が含まれます。 @@ -256,7 +244,7 @@ Syntheticモニタリングには以下の機能が含まれます。 @@ -349,4 +337,4 @@ Syntheticモニタリングには以下の機能が含まれます。 * [各モニターの結果](/docs/synthetics/new-relic-synthetics/using-monitors/viewing-monitor-results#understanding)がどのように分類されるかをご覧ください。 * 合成データを実際のユーザーデータで補完したいですか？ [ウェブサイトのパフォーマンス改善](/docs/journey-performance/improve-website-performance)チュートリアルをご覧ください。 * ウェブサイトまたはAPIエンドポイントがアクセス不能になった場合、[通知するアラート](/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics)を作成します。[プライベートロケーション](/docs/synthetics/new-relic-synthetics/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations)を作成することで、地理的範囲の拡大や内部ウェブサイトのモニターもできるようになります。 -* さらに詳しく見るために、[モニター結果をクエリする](/docs/using-new-relic/data/understand-data/query-new-relic-data)こともできます。New Relicは、13ヶ月間モニター結果を保持しているため、使用に関して前年と比較することも可能です。 +* さらに詳しく見るために、[モニター結果をクエリする](/docs/using-new-relic/data/understand-data/query-new-relic-data)こともできます。New Relicは、13ヶ月間モニター結果を保持しているため、使用に関して前年と比較することも可能です。 \ No newline at end of file From 070fb1913b683fe8a741951dd4b1628983df2b5e Mon Sep 17 00:00:00 2001 From: a-sassman Date: Fri, 23 Aug 2024 08:32:59 -0700 Subject: [PATCH 18/18] Merge #18461 into this PR --- .../mobile-monitoring-ui/mobile-logs.mdx | 164 +++++------------- .../sentry-incompatibility-android.mdx | 27 +-- 2 files changed, 59 insertions(+), 132 deletions(-) diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index 898fa73ada2..dd77d75ad01 100644 --- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -4,22 +4,12 @@ tags: - Mobile monitoring - Mobile monitoring UI - Logs -metaDescription: Use New Relic's Mobile Logs Monitoring UI page to view Mobile Logs -freshnessValidatedDate: 2024-06-27 +metaDescription: Use New Relic's logs UI page to view mobile logs. +freshnessValidatedDate: 2024-08-23 --- You can use our APIs to send your mobile apps logs to New Relic. Your logs will be in one place where you can analyze them. -## APIs to capture logs [#logs-apis] - -APIs are available for iOS and Android. - - - Note that there may be some mobile logging delays: - * It will take up to 15 minutes for logs to appear in New Relics **Logs** tab. - * It will take up to 15 minutes for changes to mobile logs toggle, sampling rate, and log level to be reflected within your mobile application. - - ## Enable mobile logs [#enable-mobile-logs] @@ -29,12 +19,12 @@ By default, our mobile agent doesn't collect logs. To enable mobile logs: 2. Click **Mobile**. 3. Click on your mobile app. 4. In the left pane under **Settings**, click **Application**. -5. Toggle **Mobile Logs** on. -6. Click **Save**. +5. Toggle **Mobile Logs** on. +6. Click **Save**. ## Configure your logs [#configure-mobile-logs] -To configure your mobile logs sampling rate or log level: +To configure the sampling rate or log level: 1. In New Relic, navigate to your mobile app. 2. In the left pane under **Settings**, click **Application**. @@ -43,11 +33,19 @@ To configure your mobile logs sampling rate or log level: ## View logs in New Relic [#view-logs-in-new-relic] -To view your logs, continue in the New Relic UI: +To view your logs in the UI: 1. Navigate to your mobile app. 2. In the left pane under **Triage**, click **Logs**. +Note that there may be some mobile logging delays: + * It will take up to 15 minutes for logs to appear in the **Logs** page. + * It will take up to 15 minutes for changes to the logs toggle, sampling rate, and log level to be reflected within your mobile application. + +## Use APIs to capture logs [#logs-apis] + +The API below provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. + Keep in mind that when you use the logging APIs, you should only use the debug log level if you want to see agent debugging logs. @@ -83,11 +81,11 @@ Keep in mind that when you use the logging APIs, you should only use the debug l -## Syntax [#syntax] +### Syntax [#syntax] -### Java [#java] +#### Java [#java] ```java @@ -111,7 +109,7 @@ NewRelic.logAll(Throwable throwable, Map attributes) ``` -### Kotlin [#kotlin] +#### Kotlin [#kotlin] ```kotlin @@ -135,16 +133,9 @@ NewRelic.logAll(Throwable throwable, Map attributes) ``` -## Description [#description] - -Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. +### Example [#example] - -## Examples [#examples] - -Here's an example of Logging: - -### Java [#java] +#### Java [#java] ```java @@ -187,7 +178,7 @@ Here's an example of Logging: ``` -### Kotlin [#kotlin] +#### Kotlin [#kotlin] ```kotlin @@ -223,9 +214,9 @@ Here's an example of Logging: -## Syntax [#syntax] +### Syntax [#syntax] -### Objective-c +#### Objective-c ```objectivec (void) logInfo:(NSString* __nonnull) message; @@ -241,7 +232,7 @@ Here's an example of Logging: ``` -### Swift [#swift] +#### Swift [#swift] ```swift func logInfo(_ message: String) @@ -257,14 +248,9 @@ func logErrorObject(_ error: NSError) ``` -## Description [#description] - -This API Provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. +### Example [#example] - -## Examples [#examples] - -Here's an example of Logging: +#### Objective-c [#objective-c] ```objectivec @@ -293,6 +279,8 @@ Here's an example of Logging: ``` +#### Swift [#swift] + ```swift NewRelic.logError("Encountered error=error=\(error.localizedDescription).") @@ -325,9 +313,7 @@ NewRelic.logAttributes([ -## Syntax [#syntax] - -### Typescript [#typescript] +### Syntax [#syntax] ```js NewRelicCapacitorPlugin.logInfo(options: { message: string}) => void @@ -346,20 +332,10 @@ NewRelicCapacitorPlugin.logAttributes(options: { attributes: object; }): void ``` -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - -## Examples [#examples] - -Here's an example of Logging: - -### Typescript [#typescript] +### Example [#example] ```ts - NewRelicCapacitorPlugin.logInfo( - {message: "User profile loaded successfully"}); + NewRelicCapacitorPlugin.logInfo({message: "User profile loaded successfully"}); NewRelicCapacitorPlugin.logVerbose({message:"Verbose logging example"}); @@ -386,9 +362,7 @@ NewRelicCapacitorPlugin.logAttributes({attributes:{ -## Syntax [#syntax] - -### Javascript [#javascript] +### Syntax [#syntax] ```js NewRelic.logInfo(message: string): void; @@ -408,18 +382,8 @@ NewRelic.logAttributes(attributes: {[key: string]: boolean | number | string}): ``` -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - - - -## Examples [#examples] - -Here's an example of Logging: +### Example [#example] -### Javascript [#javascript] ```js @@ -446,7 +410,7 @@ Here's an example of Logging: -## Syntax [#syntax] +### Syntax [#syntax] ```csharp CrossNewRelic.Current.LogInfo(String message) : void @@ -466,14 +430,8 @@ CrossNewRelic.Current.LogAttributes(Dictionary attributes) : voi ``` -## Description [#description] +### Example [#example] -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - -## Examples [#examples] - -Here's an example of Logging: ```csharp @@ -503,8 +461,7 @@ Here's an example of Logging: -## Syntax [#syntax] - +### Syntax [#syntax] ```dart NewrelicMobile.instance.logInfo(String message) : void @@ -525,19 +482,7 @@ NewrelicMobile.instance.logAttributes(Dictionary attributes) : v ``` - - -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - - - - -## Examples [#examples] - -Here's an example of Logging: +### Example [#example] ```dart @@ -572,7 +517,7 @@ Here's an example of Logging: -## Syntax [#syntax] +### Syntax [#syntax] ```js NewRelic.logInfo(String message) : void @@ -594,16 +539,8 @@ NewRelic.logAttributes(attributes?: {[key: string]: any}) : void ``` +### Example [#example] -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - - -## Examples [#examples] - -Here's an example of Logging: ```js @@ -638,7 +575,7 @@ Here's an example of Logging: -## Syntax [#syntax] +### Syntax [#syntax] ```csharp CrossNewRelicClient.Current.LogInfo(String message) : void @@ -657,17 +594,7 @@ CrossNewRelicClient.Current.LogAttributes(Dictionary attributes) ``` -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - - -## Examples [#examples] - -Here's an example of Logging: - -## Example [#example] +### Example [#example] ```csharp @@ -698,7 +625,7 @@ Here's an example of Logging: - ## Syntax [#syntax] + ### Syntax [#syntax] ```c UNewRelicBPLibrary::logInfo(FString message) : void @@ -717,12 +644,7 @@ UNewRelicBPLibrary::logAttributes(TMap attributes) : void ``` -## Description [#description] - -This API provides a comprehensive set of logging methods to capture various types of information and events in your application. These methods allow you to log messages with different severity levels (info, warning, debug, verbose, error), custom log levels, and additional context such as throwables (exceptions) and attributes. - - -## Example [#example] +### Example [#example] ```c @@ -753,4 +675,4 @@ This API provides a comprehensive set of logging methods to capture various type ``` - + \ No newline at end of file diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx index 02179deed17..c14b49cff86 100644 --- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx +++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/sentry-incompatibility-android.mdx @@ -5,24 +5,29 @@ tags: - Mobile monitoring - New Relic Mobile Android - Troubleshoot -metaDescription: 'New Relic Android agent Log instrumentation cannot coexist with Sentry Android' -freshnessValidatedDate: never +metaDescription: 'New Relic Android agent log instrumentation cannot coexist with Sentry Android.' +freshnessValidatedDate: 2024-08-23 --- ## Problem -Conflicts, crashes, or errors will show when both the New Relic Android agent and Sentry's [Sentry Monitoring SDK](https://docs.sentry.io/platforms/android/) are included within an app. +Integrating both the New Relic Android agent and Sentry monitoring SDK can lead to conflicts, crashes, or errors within your app. -Known errors: - - `java.lang.StackOverflowError` +This is known to cause issues like `java.lang.StackOverflowError`. ## Solution -Our Android agent Should not Instrument Sentry Android SDK. you can avoid it using this configuration +You'll need to prevent the Android agent from instrumenting the Sentry Monitoring SDK. To achieve this, configure the New Relic agent to exclude the Sentry package from instrumentation. Here's how: -newrelic { -// Don't instrument sample classes -excludePackageInstrumentation("io.sentry.*") -} +* Add the following block to your `build.gradle` file: -If you need additional help, get support at [support.newrelic.com](https://support.newrelic.com). + ``` + newrelic { + // Don't instrument sample classes + excludePackageInstrumentation("io.sentry.*") + } + ``` + +This configuration tells the New Relic agent to skip instrumenting any classes within the `io.sentry` package. + +If you encounter any issues or require additional help, you can reach New Relic support at [support.newrelic.com](https://support.newrelic.com). \ No newline at end of file
- `collector.eu.newrelic.com`
`collector.eu01.nr-data.net` + `collector.eu.newrelic.com`
`collector.eu01.nr-data.net`
- `aws-api.eu.newrelic.com`
`aws-api.eu01.nr-data.net` + `aws-api.eu.newrelic.com`
`aws-api.eu01.nr-data.net`
- 検証サービスURL
（安全なWebSocket接続が必要です） + バリデータサービスのURL + +
+ + （安全なWebSocket接続が必要です） 		@@ -255,7 +259,7 @@ translationType: human - `infra-api.eu.newrelic.com`
`infra-api.eu01.nr-data.net` + `infra-api.eu.newrelic.com`
`infra-api.eu01.nr-data.net`
- `[www.google.com](http://www.google.com)` + `www.google.com` @@ -574,7 +572,7 @@ New Relicが適切に機能するには、ブラウザが多数のドメイン
- `[www.gstatic.com](http://www.gstatic.com)` + `www.gstatic.com` @@ -638,8 +636,8 @@ New Relicにデータをレポートするためには、[Infrastructureモニ 取り込み関連以外のエンドポイントの詳細： -* `identity-api.newrelic.com` \| `identity-api.eu.newrelic.com`：エンティティ登録に必要です（`host`エンティティなど）。 -* `infrastructure-command-api.newrelic.com` \| `infrastructure-command-api.eu.newrelic.com`：エージェント動作（機能フラグの使用など）の側面を制御するためにエージェントが使用します。 +* `identity-api.newrelic.com` | `identity-api.eu.newrelic.com`：エンティティ登録に必要です（`host`エンティティなど）。 +* `infrastructure-command-api.newrelic.com` | `infrastructure-command-api.eu.newrelic.com`：エージェント動作（機能フラグの使用など）の側面を制御するためにエージェントが使用します。 ## APMエージェントの詳細 [#apm] @@ -649,7 +647,7 @@ New Relicにデータをレポートするためには、[Infrastructureモニ ## ブラウザモニタリングの詳細 [#browser] -[エージェントおよびエージェントが使用するエンドポイント](#new-relic-endpoints)に加えて、Browserエージェントが監視するアプリケーションでは、`js-agent.newrelic.com`への送信接続を使用します。 +[エージェントおよびエージェントが使用するエンドポイント](#new-relic-endpoints)に加えて、Browserエージェントが監視するアプリケーションでは、`js-agent.newrelic.com`への送信接続を使用します。 `js-agent.newrelic.com`ファイルの`bam.nr-data.net`ドメイン、またはNew Relicビーコンのいずれかに対するCDNアクセスに関する詳細については、[ブラウザモニタリングのためのセキュリティ](/docs/browser/new-relic-browser/performance-quality/security-new-relic-browser)を参照してください。 @@ -783,4 +781,4 @@ New Relic [CodeStream](/docs/codestream/start-here/what-is-codestream)は、開 * `*.pubnub.com` * `*.pubnub.net` * `*.pndsn.com` -* `*.pubnubapi.com` +* `*.pubnubapi.com` \ No newline at end of file diff --git a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring.mdx b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring.mdx index a3c29f34ee8..871eb51fff1 100644 --- a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring.mdx +++ b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring.mdx @@ -21,7 +21,7 @@ translationType: human ### New Relicアカウントにサインインします。 [#create] - New Relicアカウントにサインインしたら、**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。**Page load performance**タイルを選択します。 + New Relicアカウントにサインインしたら、**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。**Page load performance**タイルを選択します。 @@ -32,19 +32,12 @@ translationType: human テストしたいページのURLをクリックしながら移動し、**URL**フィールドにドロップします。最良の結果を得るには、以下をお勧めします。 * モニターのデプロイ元となる場所を少なくとも3つ選択します。これにより、確認における誤検知を回避できます。 - - * - **Period** - - - ドロップダウンを使用して、確認期間を調整します。お客様に応じて、デプロイする頻度を決めてください。 + * ChromeとFirefoxを組み合わせて、複数のブラウザタイプを使用します。 + * **Period**ドロップダウンを使用して、確認期間を調整します。お客様に応じてテストする頻度を決めてください。 - @@ -54,15 +47,11 @@ translationType: human - モニターがレポートを開始すると、Synthetics **Summary page**でデータを確認できます。**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** > (Select a monitor) > (View your **Summary page**)の順に移動します。 + モニターがレポートを開始すると、Synthetics **Summary page**でデータを確認できます。**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** &gt; (Select a monitor) &gt; (View your **Summary page**)の順に移動します。 - A screenshot of the summary page after a simple browser monitor reports data + A screenshot of the summary page after a simple browser monitor reports data @@ -76,7 +65,7 @@ translationType: human ### New Relicアカウントにサインインします。 [#steplogin] - New Relicアカウントにサインインしたら、**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。**User step execution**タイルを選択します。 + New Relicアカウントにサインインしたら、**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。**User step execution**タイルを選択します。 @@ -84,16 +73,13 @@ translationType: human - モニターに名前を付け、モニターによるワークフローの実行頻度を選択し、モニターのデプロイ元を選択します。 + モニターに名前を付け、モニターがワークフローを実行する頻度を選択し、使用可能なブラウザとエミュレートされたデバイスの種類を選択してから、モニターのデプロイ元を選択します。 - **[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動し、次に**User step execution**を選択します。 + **[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動し、次に**User step execution**を選択します。 - @@ -111,14 +97,11 @@ translationType: human 4. このページで何か（購入するアイテムなど）を選択する 5. 安全な認証情報をフォームに入力してそのアイテムを購入し、それらのフォームを送信する - 構築する内容が何であれ、モニターを保存する前に必ず**Validate**をクリックしてください。検証では、組み合わせたステップが正常に実行されることを確認します。 + 構築する内容にかかわらず、モニターを保存する前に必ず**Validate**をクリックしてください。検証では、組み合わせたステップが正常に実行されることを確認します。 - @@ -128,15 +111,11 @@ translationType: human - モニターがレポートを開始すると、Synthetics **Summary page**でデータを確認できます。**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** > (Select a monitor) > (View your **Summary page**)の順に移動します。 + モニターがレポートを開始すると、Synthetics **Summary page**でデータを確認できます。**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** &gt; (Select a monitor) &gt; (View your **Summary page**)の順に移動します。 - A screenshot of the summary page after a simple browser monitor reports data + A screenshot of the summary page after a simple browser monitor reports data @@ -233,12 +212,11 @@ translationType: human -**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動し、スクリプト化ブラウザの場合は**User flow/functionality**を選択します。 +**[one.newrelic.com > Synthetic monitoring > Create a monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動し、スクリプト化ブラウザの場合は**User flow/functionality**を選択します。 ## 次のステップ [#next] 最初のモニターセットの作成が終わったので、その他の機能について確認しましょう。以下のドキュメントをご確認いただくことをお勧めします。 * [Syntheticモニターのアラート](/docs/synthetics/synthetic-monitoring/using-monitors/alerts-synthetic-monitoring/)を設定してチェック失敗時に通知を受け取るようにする -* 新しい合成データを補完するために実際のユーザーデータを収集して、[ウェブサイトを改善します](/docs/journey-performance/improve-website-performance)。 -* すべてがどう機能するか気になりますか？[Syntheticモニターの概要を見る](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring) +* すべてがどう機能するか気になりますか？[Syntheticモニターの概要を見る](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring) \ No newline at end of file diff --git a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors.mdx b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors.mdx index 539b35a66f2..fbc1a3aa56b 100644 --- a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors.mdx +++ b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors.mdx @@ -18,59 +18,28 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 インストレーションなしでSyntheticモニターを作成できます。開始するには： 1. [New Relicアカウントを作成します](https://newrelic.com/signup)。 - -2. - **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)** - - - に移動して、**Create a monitor**をクリックします。 - +2. **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動して、**Create a monitor**をクリックします。 3. 作成するモニターを選択します。 初めて使用する場合は、pingまたはステップモニターを作成して開始することをお勧めします。 ## モニターを作成する [#adding-monitors] 1台（または複数）の[Syntheticモニター](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring/#types-of-synthetic-monitors)でウェブアプリをモニターする準備はできていますか？ 以下の手順では、すべてのモニターのプロセスを説明します。 -A screenshot that displays the menu options when you go to create synthetic monitors +A screenshot that displays the menu options when you go to create synthetic monitors
- **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動して、**Create a monitor**をクリックします。 + **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動して、**Create a monitor**をクリックします。
- - 1. 次のパスに移動します： - - - **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)** - - - 2. pingモニターの場合は - - - **Availability** - - - タイルを、シンプルなブラウザモニターの場合は - - - **Page load performance** - - - をクリックします - + + 1. 次のパスに移動します： **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)** + 2. pingモニターの場合は **Availability** タイルを、シンプルなブラウザモニターの場合は **Page load performance** をクリックします 3. オプション：[アラート通知](/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics)を設定します。 - 数分待ってから、[**Monitors**インデックス](/docs/new-relic-one-monitors-index)からモニターを確認します。 + 数分待ってから、[**Monitors**インデックス](/docs/new-relic-one-monitors-index)からモニターを確認します。 - pingまたはシンプルなブラウザモニターには、追加の設定オプションがあります。両方のモニタータイプで、以下の設定が可能です。 + pingまたはシンプルなブラウザモニターには、追加の設定オプションがあります。両方のモニタータイプで、以下の設定が可能です。 * [応答検証](#response-validation)用のサブ文字列監視を有効にする**validation string** @@ -84,42 +53,23 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 ゼロ以外の終了コードが返される場合、モニターは失敗します。 - pingモニターのみを使用すると、次の設定を選択できます。 - - * デフォルトの`HEAD`リクエストをスキップし、代わりに`GET` + pingモニターのみを使用すると、次の設定を選択できます。 - - **Bypass HEAD request** - + * デフォルトの`HEAD`リクエストをスキップし、代わりに`GET`**Bypass HEAD request**動詞を使用します + * **Redirect is Failure**これにより、新しいURLへのリダイレクトではなく、リダイレクトを失敗として分類します + * **Custom Headers** pingおよびシンプルなブラウザモニターに追加できます。モニターが送信したリクエストにこれらのヘッダーが追加されます - 動詞を使用します - - * - **Redirect is Failure** - - - これにより、新しいURLへのリダイレクトではなく、リダイレクトを失敗として分類します - - * - **Custom Headers** - - - pingおよびシンプルなブラウザモニターに追加できます。モニターが送信したリクエストにこれらのヘッダーが追加されます - - シンプルなブラウザモニターのみを使用すると、デバイスの種類や画面の向きなどの[デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)の設定を行えます。 + シンプルブラウザモニターのみを使用すると、デバイスタイプや画面の向きなどの[デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)の設定をChromeまたはFirefoxから選択できます。 - - 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 + + 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 2. [モニタータイプ](#setting-type)と[名前](#setting-name)を指定します。 3. 各場所でモニターを実行する[期間](#setting-frequency)を選択します。 - 4. オプション：スクリプト化ブラウザモニターでは、デバイスタイプや画面の向きなど、[デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)を設定できます。 + 4. オプション：1つまたは複数のブラウザタイプを選択し、[デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)設定を有効化します。スクリプト化ブラウザモニター用にデバイスタイプや画面の向きなどを含めます。 5. モニターを実行する[場所](#setting-location)を選択します。 @@ -136,19 +86,18 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 数分待ってから、[**Monitors**インデックス](/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors)からモニターを確認します。 - - 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 + + 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 2. [モニタータイプ](#setting-type)としてステップモニターを選択します。 3. [名前](#setting-name)を指定し、[期間](#setting-frequency)を選択して、各場所でモニターを実行する頻度を選択します。 - 4. モニターを実行する[場所](#setting-location)を選択します。 + 4. オプション：1つまたは複数のブラウザタイプを選択し、[デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)設定を有効化します。スクリプト化ブラウザモニター用にデバイスタイプや画面の向きなどを含めます。 - 5. UIの下部にある事前設定済みの手順から選択して、モニターを構築します。 + 5. モニターを実行する[場所](#setting-location)を選択します。 + + 6. UIの下部にある事前設定済みの手順から選択して、モニターを構築します。 * URLに移動する * テキストを入力する @@ -159,17 +108,13 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 CSSクラス、HTML ID、リンクテキスト、またはXPath別に要素を見つけるには、UIの右側にある手順を使用します。 - 6. **Save monitor**を選択して確認します。 + 7. **Save monitor**を選択して確認します。 トラフィックを生成して数分待ってから、[**Monitors**インデックス](/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors)からモニターを確認します。 - - 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 + + 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 2. 証明書チェックモニタータイプを選択します。 @@ -186,12 +131,8 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 トラフィックを生成して数分待ってから、[**Monitors**インデックス](/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors)からモニターを確認します。 - - 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 + + 1. **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**に移動します。 2. リンク切れ確認モニターのタイプを選択します。 @@ -213,55 +154,21 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 ## モニターを編集する [#editing-monitors] -A screenshot that shows the New Relic UI when you're editing your monitor. +A screenshot that shows the New Relic UI when you're editing your monitor.
- **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) > General**：モニターを最新の状態に保ち、New Relicが常に最も適切なデータを受信できるようにします。 + **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) &gt; General**：モニターを最新の状態に保ち、New Relicが常に最も適切なデータを受信できるようにします。
モニターの作成後に、モニターの[タイプ](#setting-type)を変更することはできませんが、他のモニターの設定は編集できます。 -1. **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)**に移動し、編集するモニターを選択します +1. **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)**に移動し、編集するモニターを選択します 2. サイドメニューで、以下の[設定](#settings)を変更するリンクを選択します。 - * [名前](#setting-name)、URL、[場所](#setting-location)、[頻度](#setting-frequency)、高度なオプションを編集するには、 - - - **Settings > General** - - - の順に選択します - - * - **Scripted browser** - - - および - - - **API test** - - - モニターの場合は、 - - - **Settings > Script** - - - の順に選択してモニタースクリプトを編集します - - * 外形監視アラートについては、 - - - **Manage alerts** - - - をクリックします + * [名前](#setting-name)、URL、[場所](#setting-location)、[頻度](#setting-frequency)、高度なオプションを編集するには、 **Settings > General**の順に選択します + * **Scripted browser**および**API test**モニターの場合は、**Settings > Script**の順に選択してモニタースクリプトを編集します + * 外形監視アラートについては、**Manage alerts**をクリックします 3. **Save changes**を選択して確認します。 @@ -271,31 +178,18 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 ## モニターを削除する [#deleting-monitors] -A screenshot of the Edit a monitor page with a red arrow that shows where someone should look to delete a monitor. +A screenshot of the Edit a monitor page with a red arrow that shows where someone should look to delete a monitor.
- **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) > General**：Edit monitorページからSyntheticモニターを削除します。 + **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) &gt; General**：Edit monitorページからSyntheticモニターを削除します。
モニターを削除するには、[管理者権限](/docs/synthetics/synthetic-monitoring/administration/user-roles-synthetic-monitoring/)が必要です。 モニターを削除するには: -1. - **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** - - - に移動し、編集するモニターを選択します - -2. - **General** - - - をクリックしてから、モニターを削除ボタンをクリックします +1. **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)**に移動し、編集するモニターを選択します +2. **General**をクリックしてから、モニターを削除ボタンをクリックします また、[NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial)または[合成モニタリングREST API](/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api#delete-monitor)を使用して、モニターを削除することもできます。 @@ -304,82 +198,41 @@ Syntheticモニターは、各チェックインの詳細を記録すると同 モニターを構成するときは、次の設定を使用できます。 - + 作成するモニターのタイプを選択します。モニターを作成した後でモニターの[タイプ](/docs/synthetics/new-relic-synthetics/getting-started/types-synthetics-monitors#types-monitors)を変更することはできません。 - * - **Ping** - - - ：可用性を監視する単一のURLを指定します。New Relicでは、HEADまたはGETリクエストを使用して、このURLを確認します。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements)は60秒です - - * - **Simple browser** - - - ：実ブラウザを介して監視する単一のURLを指定します。New Relicは、[頻度の間隔](#setting-frequency)ごとに、Seleniumを使用したGoogle Chromeブラウザを介してこのURLを確認します。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers/#waiting-elements)は60秒です - - * - **Scripted browser** - - - ：Seleniumを使用したGoogle Chromeブラウザを操作する[スクリプトを作成](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts)します。ブラウザは、スクリプト内の各ステップに従って、複雑な動作が期待通りに機能していることを確認します（ウェブサイトを検索した後に、検索結果の1つをクリックするなど）。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements)は180秒です - - * - **API test** - - - ：APIスクリプトを作成して、APIエンドポイントが正しく機能していることを確認します。詳細については、[APIテストの記述](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-api-tests)をご覧ください。このモニターの設定不可能なタイムアウトは180秒です + * **Ping**：可用性を監視する単一のURLを指定します。New Relicでは、HEADまたはGETリクエストを使用して、このURLを確認します。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements)は60秒です + * **Simple browser**：実ブラウザを介して監視する単一のURLを指定します。[頻度の間隔](#setting-frequency)ごとに、New RelicがSeleniumを使用したChromeブラウザまたはFirefoxブラウザを介してこのURLを確認します。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers/#waiting-elements)は60秒です。 + * **Scripted browser**：Seleniumを使用したChromeブラウザまたはFirefoxブラウザを操作する[スクリプトを作成](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts)します。ブラウザは、スクリプト内の各ステップに従って、複雑な動作が期待通りに機能していることを確認します（ウェブサイトを検索した後に、検索結果の1つをクリックするなど）。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements)は180秒です。 + * **API test**：APIスクリプトを作成して、APIエンドポイントが正しく機能していることを確認します。詳細については、[APIテストの記述](/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-api-tests)をご覧ください。このモニターの設定不可能なタイムアウトは180秒です + * **Step monitor**：Seleniumを使用したChromeブラウザまたはFirefoxブラウザを操作する1つまたは複数のステップの設定をコードレスで作成するオプションです。ブラウザは、各ステップに従って、複雑な動作が期待通りに機能していることを確認します（ウェブサイトを検索した後に、検索結果の1つをクリックするなど）。このモニターの設定不可能な[タイムアウト](/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements)は180秒です。 + * **Certificate check**: SSL証明書が設定可能な日数以内に期限切れになるかどうかを確認します。 + * **Broken links**: URL内に存在するすべてのリンクをテストして、正常なHTTP応答コードで応答することを確認します。 - + モニターの名前を定義します。モニター名には、エンコードされていないカギ括弧（`<`と`>`）を使用することはできません。モニター名にカギ括弧を含めるには、UIまたはAPIで、それらをHTMLブラケットエンティティ（`<`の場合は`<`、`>`の場合は`>`）としてエンコードしてください。 - + モニターを実行するロケーションを選択します。世界中のユーザーがアプリケーションを使用できるようにするには、多くのロケーションを選択してください。[プライベートロケーション](/docs/synthetics/new-relic-synthetics/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations)がある場合は、ここにもリストされます。[Synthetics API `location`エンドポイント](/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api#list-locations)を使用すると、アカウントの有効なロケーションのリストを取得できます。 モニターは、[頻度の間隔](#setting-frequency)ごとに選択したそれぞれのロケーションからチェックを1回実行します。例えば、3つのロケーションを選択し、15分の頻度を定義した場合、モニターは15分ごとに3回のチェックを実行します （つまり、毎月8,640回のチェックを実行）。 - + モニターの実行頻度を、分単位、時間単位、あるいは1日単位で選択してください。この頻度は、それぞれの[ロケーション](#setting-location)に適用されます。たとえば、3つのロケーションと**15 minutes**の頻度を選択した場合、モニターは各15分間の中で平均5分間隔のチェックを3回実行します （毎月8,640回）。 - - モニターが失敗したときにアラートを受け取るメールアドレスを指定します。または、モニターを既存のアラートポリシーに接続すると、その他の通知オプションを使用できます。詳細については、[外形監視におけるアラート生成](/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics)をご覧ください。 - - - + ページDOMで検索するテキストを指定します。シンプルブラウザまたはping[モニタータイプ](/docs/synthetics/synthetic-monitoring/getting-started/types-synthetic-monitors/#types-monitors)を使用する場合、ページの読み込みは1MB（10^6バイト）に制限されています。 - + モニターの**tolerable**レスポンスタイムの閾値を指定します。デフォルトの値は7 秒（7000ms）です。詳細については、[SLAレポートのメトリクスを理解する](/docs/synthetics/synthetic-monitoring/pages/synthetic-monitoring-aggregate-monitor-metrics/#understanding)を参照してください。 ## モニターの変更履歴を表示する [#track-changes] -[New Relic UIでは、Syntheticsモニターに対する最近の変更履歴](/docs/synthetics/new-relic-synthetics/administration/audit-synthetics-account-changes)のほか、ユーザーが変更した内容を確認できます。 +[New Relic UIでは、Syntheticsモニターに対する最近の変更履歴](/docs/synthetics/new-relic-synthetics/administration/audit-synthetics-account-changes)のほか、ユーザーが変更した内容を確認できます。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx index 9f4990815d5..66dea659b7b 100644 --- a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx +++ b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx @@ -31,11 +31,7 @@ New RelicでSyntheticモニターを設定すると、次の操作が可能に 以下は、システム要件の概要、データの保護方法、権限の制御方法について説明しています。 - + Syntheticモニタリングには、[対応ブラウザ](/docs/apm/new-relic-apm/getting-started/supported-browsers)以外のソフトウェアは必要ありません。 @@ -43,19 +39,11 @@ New RelicでSyntheticモニターを設定すると、次の操作が可能に - + Syntheticモニタリングからのデータは、ウェブページまたはアプリケーションとの一般的なインタラクションを表すテストデータです。それは実際の人間からの本物のデータではないないため、個人データは含まれません。詳細については、[Syntheticモニタリングセキュリティドキュメント](/docs/synthetics/new-relic-synthetics/getting-started/security-new-relic-synthetics)を参照してください。 - + 詳細については、[権限](/docs/synthetics/synthetic-monitoring/administration/user-roles-synthetic-monitoring)を参照してください。 @@ -132,7 +120,7 @@ Syntheticモニターには以下の7つのタイプがあります。 		- ステップモニターは高度なモニターで、設定にコードは必要ありません。 + ステップモニターは高度なブラウザベースのモニターで、コードを使用せずに設定できます。 モニターは、次のように設定できます。 @@ -160,9 +148,9 @@ Syntheticモニターには以下の7つのタイプがあります。 - シンプルブラウザモニターは、シンプルで事前構築されたスクリプト化ブラウザモニターです。Google Chromeのインスタンスを使用してサイトにリクエストします。 + シンプルブラウザモニターは、シンプルで事前構築されたスクリプト化ブラウザモニターです。ChromeまたはFirefoxのインスタンスを使用してサイトにリクエストを送信します。 - シンプルなpingモニターと比較すると、実際の顧客アクセスをより正確にエミュレートします。ユーザーエージェントは、`Google Chrome`として識別されます。 + シンプルなpingモニターと比較すると、実際の顧客アクセスをより正確にエミュレートします。
スクリプト化ブラウザモニターは、より高度でカスタマイズされたモニタリングに使用されます。Webサイトをナビゲートし、特定のアクションを実行し、特定のリソースがあることを確認するカスタムスクリプトを作成できます。 - モニターはGoogle Chromeブラウザを使用します。また、さまざまな[サードパーティモジュール](/docs/synthetics/new-relic-synthetics/scripting-monitors/scripted-monitor-runtime-environment#runtime-table)を使用して、カスタムモニターを構築できます。 + モニターはChromeやFirefoxを含む複数のブラウザタイプをサポートします。また、さまざまな[サードパーティモジュール](/docs/synthetics/new-relic-synthetics/scripting-monitors/scripted-monitor-runtime-environment#runtime-table)を使用して、カスタムモニターを構築できます。
- 単純なブラウザとスクリプト化ブラウザモニターの場合、ホストが起動していることを単にチェックするだけではありません。完全に仮想化されたリアルなGoogle Chromeブラウザ（Selenium搭載）で実際のページコンテンツを読み込み、ユーザーのアクションを正確に反映するテストを行います。 + 単純なブラウザとスクリプト化ブラウザモニターの場合、ホストが起動していることを単にチェックするだけではありません。完全に仮想化されたリアルなChromeブラウザまたはFirefoxブラウザ（Selenium搭載）で実際のページコンテンツを読み込み、ユーザーのアクションを正確に反映するテストを行います。
- New Relicの[比較チャート機能](/docs/synthetics/new-relic-synthetics/administration/compare-page-load-performance-browser-synthetics)を使用して、実際のユーザー（[](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser)）のインタラクションとSyntheticモニター間の直接ページロードタイムを比較します。たとえば、ページの停止中に、傾向を対比して、問題が外形監視にも表示されているかどうか、またはその他の変数によって発生しているかどうかを確認できます。 + New Relicの[比較チャート機能](/docs/synthetics/new-relic-synthetics/administration/compare-page-load-performance-browser-synthetics)を使用して、実際のユーザー（[](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser)）のインタラクションとSyntheticモニター間の直接ページロードタイムを比較します。たとえば、ページの停止中に、傾向を対比して、問題が外形監視にも表示されているかどうか、またはその他の変数によって発生しているかどうかを確認できます。
- [デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)を使用して、シンプルブラウザモニターとスクリプト化ブラウザモニターでモバイルまたはタブレットデバイスをシミュレートします。 + [デバイスエミュレーション](/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation)を使用して、シンプルブラウザモニター、スクリプト化ブラウザモニター、ステップモニターでモバイルまたはタブレットデバイスをシミュレートします。