diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx index 458584e5f90..2dac9b5bb51 100644 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx +++ b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx @@ -117,7 +117,7 @@ More on these two options: To enable this setting, your authentication domain **Source of users** must have [SCIM enabled](#source-users). - Currently, we only have instructions for [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration). For other identity provider services, you can configure your identity provider to send us user type information using our [SCIM API user type specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type). + Currently, we have instructions for [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration) and [Azure](https://forum.newrelic.com/s/hubtopic/aAX8W0000008d6MWAQ/relic-solution-make-full-core-basic-users-in-azure-active-directory-w-scim). For other identity provider services, you can configure your identity provider to send us user type information using our [SCIM API user type specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type). How users upgrade requests are handled: diff --git a/src/content/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration.mdx b/src/content/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration.mdx index 88b5731fe8c..8597c1872c3 100644 --- a/src/content/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration.mdx +++ b/src/content/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration.mdx @@ -1,5 +1,5 @@ --- -title: Azure AD SCIM/SSO application configuration +title: Microsoft Entra ID SCIM /SSO application configuration tags: - Accounts - Accounts and billing @@ -31,14 +31,14 @@ For that authentication domain, under **Source of users**, select **SCIM**. Copy ## Step 2. Set up Azure's New Relic app [#azure-app] -Next, you'll set up Azure's New Relic SAML/SCIM app. Azure AD provides an application gallery, which includes various integrations for Azure AD, including the ones that New Relic offers. To set this up: +Next, you'll set up Azure's New Relic SAML/SCIM app. Microsoft Entra ID, formerly know as Azure AD, provides an application gallery, which includes various integrations for Microsoft Entra ID, including the ones that New Relic offers. To set this up: -1. Go to the Azure Active Directory admin center, and sign in if necessary. [aad.portal.azure.com/](https://aad.portal.azure.com/) -2. Click on **All services** in the left hand menu. -3. In the main pane, click on **Enterprise applications**. +1. Go to the Microsoft Entra ID admin center, and sign in if necessary. [aad.portal.azure.com/](https://aad.portal.azure.com/) +2. Click on **Applications** in the left hand menu. +3. In the drop down, click on **Enterprise applications**. 4. Click on **+New Application**. 5. Find our SCIM/SSO application by entering **New Relic** in the name search box, and click on the application **New Relic by organization** (not **New Relic by account**). -6. Click on **Add**. +6. Click on **Create**. ## Step 3. Configure connection [#configure] @@ -56,14 +56,15 @@ The New Relic SCIM/SSO application can now connect with New Relic. Continue with ## Step 4. Configure provisioning rules [#configure-rules] -Initially, nothing is configured to be sent to New Relic. You must configure Azure AD to send changes for user creation, updates, and deactivation. +Initially, nothing is configured to be sent to New Relic. You must configure Microsoft Entra ID to send changes for user creation, updates, and deactivation. Go to the **Provisioning** page and complete the following: -1. Expand the **Mappings** section. -2. Click **Provision Azure Active Directory Users**. -3. Verify the **Target Object Actions**, **Create**, **Update**, and **Delete** checkboxes are all checked. -4. Verify the **Attribute Mappings** look correct for your environment. Each of the New Relic attributes shown in the list must receive a value. +1. In the overview page click on **Edit attribute mappings**. +2. Expand the **Mappings** section. +3. Click **Provision Azure Active Directory Users**. +4. Verify the **Target Object Actions**, **Create**, **Update**, and **Delete** checkboxes are all checked. +5. Verify the **Attribute Mappings** look correct for your environment. Each of the New Relic attributes shown in the list must receive a value. Ensure that the Azure Active Directory attributes shown in the list on the left are good sources for the information to send to New Relic. In particular, not all environments set the **mail** attribute. If your environment does not set the **mail** attribute, **userPrincipalName** could be a good alternative. diff --git a/src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response.mdx b/src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response.mdx index f47281337a3..165b792a4bd 100644 --- a/src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response.mdx +++ b/src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response.mdx @@ -231,16 +231,6 @@ To view the issues in a text format, in the right hand corner, click **Switch to src={accountsIssueSummary} /> -**Golden signals** - -Here you will find an indication about which of the 4 golden signals is related to issue, it means that there is a problem affecting the performance or availability of your distributed system in one or more of the key areas. - -**Related components** - -We're analyzing the title and based on that we get value from the list components. - -We also present a list of tags that are derived from the stack trace, based on Stack Overflow tags analysis. - ## Use decisions [#decisions] To further reduce noise or get improved incident correlation, you can change or customize your decisions. Decisions determine how incidents are grouped together. diff --git a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx index f2eb87f383f..723fd7cf9a2 100644 --- a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx +++ b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx @@ -438,7 +438,7 @@ Not every field listed in this glossary is required for every condition type. Th In the UI, under **Advanced signal settings**, this is the **Aggregation window** field. - Default is **60 seconds**. Maximum is 120 minutes. + Default is **60 seconds**. Maximum is 6 hours. Used for: diff --git a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes.mdx b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes.mdx index c74b5461d51..49330904370 100644 --- a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes.mdx +++ b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes.mdx @@ -253,7 +253,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a - `incidentID` + `incidentId` @@ -273,7 +273,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a - `mutingRuleID` + `mutingRuleId` diff --git a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts.mdx b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts.mdx index 331c521a79e..2f3fa4427b2 100644 --- a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts.mdx +++ b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts.mdx @@ -258,7 +258,7 @@ In order to make loss of signal detection more effective and to reduce unnecessa An [aggregation window](/docs/using-new-relic/welcome-new-relic/get-started/glossary#aggregation-window) is a specific block of time. We gather data points together in an aggregation window, before evaluating the data. A longer aggregation window can smooth out the data, since an outlier data point will have more data points to be aggregated with, giving it less of an influence on the aggregated data point that is sent for evaluation. When a data point arrives, its timestamp is used to put it in the proper aggregation window. -You can set your aggregation window to anything between **30 seconds** and **2 hours**. The default is **1 minute**. +You can set your aggregation window to anything between **30 seconds** and **6 hours**. The default is **1 minute**. ### Delay/timer [#delay-timer] diff --git a/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx b/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx index 5f8323cad62..677ccc5fab3 100644 --- a/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx +++ b/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx @@ -513,7 +513,7 @@ Set these options in the `common` stanza. To [override](#System_Properties) any Event ingest URI used by some agent features. Defaults to the US production ingest endpoint. Can be manually configured to send events to other ingest endpoints (for example, EU production: [`https://insights-collector.eu01.nr-data.net/v1/accounts/events`](https://insights-collector.eu01.nr-data.net/v1/accounts/events)). - FedRAMP compliant customers should use the [FedRAMP compliant endpoint](https://docs.newrelic.com/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#event-api): `https://gov-insights-collector.newrelic.com/v1/accounts/events` + FedRAMP compliant customers should use the [FedRAMP compliant endpoint](docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#event-api): `https://gov-insights-collector.newrelic.com/v1/accounts/events` +## Kafka message queues [#kafka-message-queues] + +Detailed information on Kafka instrumentation configuration and can be found on the [Instrument Kafka message queues](docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/) page. +- [Kafka event collection(/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-events) +- [Kafka node metrics](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#kafka-node-metrics) +- [Kafka config events](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#kafka-config) +- [Kafka streams transactions](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-streams-transactions) +- [Kafka connect transactions](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-connect-transactions) +- [Kafka distributed traces](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-distributed-traces) + + ## Logs in context [#logs-in-context] Starting with Java agent version `7.6.0`, support for [logs in context](/docs/logs/logs-context/java-configure-logs-context-all) has been added to the agent, making it easy to use for supported logging frameworks. For tips on using the Java agent for logs in context, see [Java logs in context](/docs/logs/logs-context/java-configure-logs-context-all). @@ -4017,7 +4028,7 @@ These options are set in the `message_tracer` stanza and can be [overridden](#Sy ## Security Agent [#sec-agent] -[New Relic Security agent interactive applications security testing](https://docs.newrelic.com/docs/iast/use-iast/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. +[New Relic Security agent interactive applications security testing](docs/iast/use-iast/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. Run IAST with non-production deployments only to avoid exposing vulnerabilities on your production software. diff --git a/src/content/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx b/src/content/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx index c5b2b7a0837..3038afc7909 100644 --- a/src/content/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx +++ b/src/content/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx @@ -17,15 +17,17 @@ When a security scan is performed, it reports back vulnerabilities for the New R ## Cause -While any software product has the potential to have security vulnerabilities, the New Relic Java agent may be erroneously identified by security products that scan for certain string patterns in files due to instrumentation jar files that are a part of the agent. +While any software product can potentially have security vulnerabilities, the New Relic Java agent may be erroneously identified by security products. Security products that scan for certain string patterns in files may mistakenly flag instrumentation modules that are a part of the agent as vulnerable libraries. -The modules in the `instrumentation` package are named after the software frameworks they are designed to instrument. They are packaged as JAR files inside the agent jar file, `newrelic.jar`. Some security scanning tools detect these names and interpret them as being the actual software framework itself, when it's just an instrumentation module. +These instrumentation modules are JAR files named after the software frameworks designed to instrument and their versions. They don't contain code from the frameworks but may contain classes with the same name. Some security scanning tools detect these names/versions and interpret them as being the actual software framework itself, when it's just an instrumentation module. -Warnings for all jar files within the `newrelic.jar` file are false positives, and should be suppressed. +They're found inside `newrelic.jar` under the `instrumentation` package, or inside `newrelic-security-agent.jar` under the `instrumentation-security` package. + +Warnings for any jar files within `newrelic.jar` or `newrelic-security-agent.jar` are false positives, and should be suppressed. ## Solution -Suppress the false positive warnings coming from the `instrumentation` package in the `newrelic.jar` file with your scanning tool, including all JAR files whose names match the modules listed in the [New Relic Java agent repository](https://github.com/newrelic/newrelic-java-agent/tree/main/instrumentation). +Suppress the false positive warnings coming from the `instrumentation` package in `newrelic.jar` and the `instrumentation-security` package in `newrelic-security-agent.jar` with your scanning tool, including all JAR files whose names match the modules listed in the [New Relic Java agent repository](https://github.com/newrelic/newrelic-java-agent/tree/main/instrumentation) or in the [New Relic SecurityAgent for Java](https://github.com/newrelic/csec-java-agent/tree/main/instrumentation-security). For example, false positives discovered by the `DependencyCheck` project at [github.com/jeremylong/DependencyCheck](https://github.com/jeremylong/DependencyCheck) can be suppressed with: diff --git a/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx b/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx index ca33d1cccf4..91f0d9531f7 100644 --- a/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx +++ b/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx @@ -1040,7 +1040,8 @@ The `proxy` element supports the following attributes: The `log` element is a child of the `configuration` element. The `log` element configures New Relic's logging . The agent generates its own log file to keep its logging information separate from your application's logs. ```xml - - Send log messages to the console, in addition to the log file. + Send log messages to the console, in addition to the log file. Alternatively, set the `NEWRELIC_LOG_CONSOLE` environment variable in the application's environment. + + + + + + + + + + + + + + + + + +
+ Type + + Boolean +
+ Default + + `true` +
+ + If disabled, no logging is attempted. Intended for read-only file systems. Alternatively, set the `NEWRELIC_LOG_ENABLED` environment variable in the application's environment. All capabilities](https://one.newrelic.com/all-capabilities) > Add data**. + 1. Go to **[one.newrelic.com](https://one.newrelic.com) > Add data**. 2. Search for and click on **Elasticsearch**. 3. Select an account and follow the guided install steps. @@ -110,7 +110,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo * Path to the configuration file: `/etc/newrelic-infra/integrations.d/` * Configuration file name: `mysql-database-config.yml` - 2. Add this code snippet to the configuration file: + 2. Add the following code snippet to the configuration file. Be sure to change replace `USERNAME`, `PASSWORD`, AND `DATABASE_NAME`: ``` # NOTE: 'database' is an experimental API at this time @@ -124,7 +124,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo apis: - database: mysql # connection string for an rds mysql instance. Be sure to use the writer endpoint here. /sys is the default database. newrelic:Password is the user:pass. - db_conn: magento2:password@tcp(localhost:3306)/magento2 + db_conn::@tcp(localhost:3306)/ logging: open: true # custom_attributes: # applies to all queries @@ -213,7 +213,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo ## Install the Magento business insights dashboard [#install-dashboard] - 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**. + 1. Go to **[one.newrelic.com > Add Data](https://one.newrelic.com) > Dashboards**. 2. In the search bar, type "Magento business insights". The dashboard should appear. 3. Click on it to install. @@ -227,7 +227,7 @@ Your Magento dashboard is considered a custom dashboard and can be found in the Interested in querying your Magento app data? Here's an example NRQL query checking the total registered customers on your Magento platform: ```sql -SELECT LATEST(`Registered Accounts`) AS ‘Registered Accounts’ FROM MYSQLCustomerEntityRegisteredUsers +SELECT LATEST(`Registered Accounts`) AS 'Registered Accounts' FROM MYSQLCustomerEntityRegisteredUsers ``` ## What's next? [#whats-next] diff --git a/src/content/docs/logs/ui-data/lookup-tables-ui.mdx b/src/content/docs/logs/ui-data/lookup-tables-ui.mdx index 62e9d96274d..adb5143e26b 100644 --- a/src/content/docs/logs/ui-data/lookup-tables-ui.mdx +++ b/src/content/docs/logs/ui-data/lookup-tables-ui.mdx @@ -230,7 +230,9 @@ Some more details about lookup tables: * Tables can only be queried from the [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/#organization-accounts) in which the table was uploaded. * Each [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/#organization-accounts) has a limit of 20 lookup tables. -* Lookup table data can't be used in NRQL alert conditions. +* Lookup table data can't be used in NRQL alert conditions. +* Lookup tables have indefinite data retention by default. + In addition to [the general requirements for a CSV file](https://www.rfc-editor.org/rfc/rfc4180), here are our requirements for uploading lookup table files: diff --git a/src/content/docs/network-performance-monitoring/setup-performance-monitoring/cloud-flow-logs/aws-vpc-flow-log-monitoring.mdx b/src/content/docs/network-performance-monitoring/setup-performance-monitoring/cloud-flow-logs/aws-vpc-flow-log-monitoring.mdx index 34b07529cff..ec08daf4e73 100644 --- a/src/content/docs/network-performance-monitoring/setup-performance-monitoring/cloud-flow-logs/aws-vpc-flow-log-monitoring.mdx +++ b/src/content/docs/network-performance-monitoring/setup-performance-monitoring/cloud-flow-logs/aws-vpc-flow-log-monitoring.mdx @@ -33,14 +33,24 @@ Amazon Virtual Private Cloud Flow (VPC) Logs via Amazon Kinesis Data Firehose he Amazon Virtual Private Cloud (VPC) enables you to launch AWS resources into an isolated and secure virtual network with the benefits of using scalable AWS infrastructure. - - Add Amazon VPC Flow Logs - + + + Add Amazon VPC Flow Logs + + + + Guided install, EU region + + ## Prerequisites [#prerequisites] diff --git a/src/content/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-0.mdx b/src/content/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-0.mdx new file mode 100644 index 00000000000..09c056dad2b --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-0.mdx @@ -0,0 +1,42 @@ +--- +subject: .NET agent +releaseDate: '2023-11-28' +version: 10.20.0 +downloadLink: 'https://download.newrelic.com/dot_net_agent/latest_release' +features: ['Allow the agent to run in environments with read-only filesystems.'] +bugs: ['Defensively handle null source address in MassTransit instrumentation.','During browser agent injection, don''t set ContentLength if headers have already been sent.','Remove dependency on Serilog.Expressions.'] +security: [] +--- + +### New features + +* Allow the agent to run in environments with read-only filesystems. ([#2085](https://github.com/newrelic/newrelic-dotnet-agent/issues/2085)) ([09ab29d](https://github.com/newrelic/newrelic-dotnet-agent/commit/09ab29dabeef358cb8c6c035c4d726f5c14f0029)) + + +### Fixes + +* Defensively handle null source address in MassTransit instrumentation. ([#2055](https://github.com/newrelic/newrelic-dotnet-agent/issues/2055)) ([0249582](https://github.com/newrelic/newrelic-dotnet-agent/commit/024958260f628da018be883eb1b446713091760e)) +* During browser agent injection, don't set ContentLength if headers have already been sent. Resolves [#2051](https://github.com/newrelic/newrelic-dotnet-agent/issues/2051) ([#2059](https://github.com/newrelic/newrelic-dotnet-agent/issues/2059)) ([c191aa6](https://github.com/newrelic/newrelic-dotnet-agent/commit/c191aa6035de4d0d95b94d8adbc80560745d06e0)) +* Remove dependency on Serilog.Expressions. Resolves [#2083](https://github.com/newrelic/newrelic-dotnet-agent/issues/2083). ([9e355f3](https://github.com/newrelic/newrelic-dotnet-agent/commit/9e355f3507130394e0660e1eb7c99e6d368f6bfc)) + +### Checksums +| File | SHA - 256 Hash | +| ---| ---| +| newrelic-dotnet-agent-10.20.0-1.x86_64.rpm | 05CCBF42D85A7110DDE9506910004067E1086A2AE1ED96522173BF8FAC3CF97A | +| newrelic-dotnet-agent_10.20.0_amd64.deb | 7093B6A0AAA1D06C5C9588C604D9BD3BE599AB5FD7ED75910434420DE708347C | +| newrelic-dotnet-agent_10.20.0_amd64.tar.gz | 16C88CC03A54FE6A5564EBC3247975FFFE77BDDC171F2C34F93139CAB858300D | +| newrelic-dotnet-agent_10.20.0_arm64.deb | C6C2E16258F25AB948515168631184E165D6BD995C8D37714113063272510D3D | +| newrelic-dotnet-agent_10.20.0_arm64.tar.gz | 3168B6FF8E970BD986C6815BEECAE6C9F8A69F837712A900C97652EF2FC3C9B8 | +| NewRelicDotNetAgent_10.20.0_x64.msi | 4C297A6475DADD9B522AD2587303F5E13A3A5DB1C8479A91C4C4A773C6C4C678 | +| NewRelicDotNetAgent_10.20.0_x64.zip | 55C4C9D350857F140C1A5DFFDF04E68089195AADA5F1843DF1718E95713A42FD | +| NewRelicDotNetAgent_10.20.0_x86.msi | 7903FE9C3D6222CF5226831685CD89527BC0CE95CEC4D3E1836E83B7B03807D2 | +| NewRelicDotNetAgent_10.20.0_x86.zip | 64572F6373AB5550260A19BA27CA97750802BE4F672EC6B96E5E02439A997304 | + + +### Updating + +* Follow standard procedures to [update the .NET agent](/docs/agents/net-agent/installation-configuration/update-net-agent). +* If you're using a particularly old agent, review the list of major changes and procedures for [updating legacy .NET agents](/docs/agents/net-agent/troubleshooting/upgrade-legacy-net-agents). + +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 your agent up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent). +See the New Relic .NET agent [EOL policy doc](/docs/apm/agents/net-agent/getting-started/net-agent-eol-policy) for information about agent releases and support dates. diff --git a/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-6-1.mdx b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-6-1.mdx new file mode 100644 index 00000000000..ce7af660002 --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-6-1.mdx @@ -0,0 +1,37 @@ +--- +subject: Node.js agent +releaseDate: '2023-12-07' +version: 11.6.1 +downloadLink: 'https://www.npmjs.com/package/newrelic' +security: [] +bugs: ["Updated @newrelic/aws-sdk to 7.0.3","Updated shimmer to handle instrumenting named and default exports of CommonJS modules in ESM"] +features: [] +--- + +## Notes + +#### Bug fixes + +* **deps:** Updated @newrelic/aws-sdk to 7.0.3 ([#1902](https://github.com/newrelic/node-newrelic/pull/1902)) ([bf22ae5](https://github.com/newrelic/node-newrelic/commit/bf22ae502ee74d5071dc5578cc77c38039e68778)) +* Updated shimmer to handle instrumenting named and default exports of CommonJS modules in ESM ([#1894](https://github.com/newrelic/node-newrelic/pull/1894)) ([9f7979c](https://github.com/newrelic/node-newrelic/commit/9f7979cd41dcb3735e553cbd4837ad455836e3ff)) + +#### Code refactoring + +* Fixed cognitive complexity violations of openai instrumentation by moving functions outside of the parent function scope ([#1895](https://github.com/newrelic/node-newrelic/pull/1895)) ([31dc717](https://github.com/newrelic/node-newrelic/commit/31dc71797c4798793b1bba8ca15733482ba3e7d6)) +* Updated span names of openai actions to allow AI O11y team to locate relevant spans ([#1896](https://github.com/newrelic/node-newrelic/pull/1896)) ([b7a644d](https://github.com/newrelic/node-newrelic/commit/b7a644d1ef56bf88171fb74868ae78d24745dd19)) + +#### Miscellaneous chores + +* Improve OpenAI mock server streams ([#1890](https://github.com/newrelic/node-newrelic/pull/1890)) ([d12bfe4](https://github.com/newrelic/node-newrelic/commit/d12bfe45f2c8d01277a1f8186844f0dd3598cbd7)) + +#### Tests + +* Fix winston-esm versioned tests ([#1898](https://github.com/newrelic/node-newrelic/pull/1898)) ([6e02e57](https://github.com/newrelic/node-newrelic/commit/6e02e57a2b4ed8351e39e5fb8d47e2702bcafde0)) +* pin undici versioned below 6.0.0 on Node 16 ([#1900](https://github.com/newrelic/node-newrelic/pull/1900)) ([9973b24](https://github.com/newrelic/node-newrelic/commit/9973b24067211f5fcc06adae79e02df8f599d735)) + + +### Support statement: + +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. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) + +See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/) diff --git a/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-310.mdx b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-310.mdx new file mode 100644 index 00000000000..139a3913920 --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-310.mdx @@ -0,0 +1,11 @@ +--- +subject: Job manager +releaseDate: '2023-11-09' +version: '310' +--- + +### Security patches +* CVE-2023-44487 +* CVE-2023-36478 +* CVE-2023-40167 +* CVE-2023-36479 diff --git a/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-315.mdx b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-315.mdx new file mode 100644 index 00000000000..f54d54f2e61 --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-315.mdx @@ -0,0 +1,11 @@ +--- +subject: Job manager +releaseDate: '2023-11-30' +version: '315' +--- + +### Improvements +* Upgrade Job Manager Ubuntu minor version + +### Security fixes +* CVE-2023-34462 diff --git a/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-321.mdx b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-321.mdx new file mode 100644 index 00000000000..34eef48beec --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-321.mdx @@ -0,0 +1,11 @@ +--- +subject: Job manager +releaseDate: '2023-12-06' +version: '321' +--- + +### Security fixes +* CVE-2023-4586 +* CVE-2023-2976 +* CWE-611 +* CVE-2023-3635 diff --git a/src/content/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.5.mdx b/src/content/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.5.mdx new file mode 100644 index 00000000000..24e4e0261d8 --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.5.mdx @@ -0,0 +1,14 @@ +--- +subject: Node API runtime +releaseDate: '2023-12-06' +version: 1.2.5 +--- + +### Fixes +* When running in K8 mode, unhealthy Runtimes now exit if they cannot reach SJM's 'Job' Endpoint. +* Upgrade base Ubuntu image. + + +### Security patches +* CVE-2023-43646 +* CVE-2023-28155 diff --git a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.1.5.mdx b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.1.5.mdx new file mode 100644 index 00000000000..b19b90f6068 --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.1.5.mdx @@ -0,0 +1,18 @@ +--- +subject: Node browser runtime +releaseDate: '2023-12-06' +version: 2.1.5 +--- + +### Fixes +* When running in K8 mode, unhealthy Runtimes now exit if they cannot reach SJM's 'Job' endpoint. +* Pinning Yarn to version 2.4.3. +* Truncates script logs to expected size. +* Upgrade base Ubuntu image. +* Set minimum TLS version to accommodate upgraded Ubuntu base image OpenSSL. + +### Security patches +* CVE-2023-43646 +* CVE-2023-46233 +* CVE-2023-28155 +* CVE-2023-45857 diff --git a/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx index c3e420cba69..eafa58ae7aa 100644 --- a/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx +++ b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx @@ -1001,4 +1001,243 @@ translationType: machine } ``` + + +## モニターのダウンタイムを管理する [#monitor-downtimes] + +ダウンタイムを監視すると、合成繊維の実行を停止する時間を指定できます。合成製品のモニターのダウンタイムをスケジュールする方法を示すさまざまなスニペットを提供しました。タイムゾーン、開始時刻、終了時刻を指定するには、これらのスニペットを更新する必要があります。モニターのダウンタイムをいつスケジュールするかについて詳しくは、ドキュメント[「スケジュールされたメンテナンス時間中の監視を無効にする」を](docs/synthetics/synthetic-monitoring/using-monitors/monitor-downtimes-disable-monitoring-during-scheduled-maintenance-times/)参照してください。タイムゾーンの値を見つけるには、 [tz タイムゾーンのデータベース](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)を参照してください。たとえば、アメリカ/ロサンゼルスでは PDT の略語が使用されます。 + + + + ``` + mutation { + syntheticsCreateOnceMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "OptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss" + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime + } + } + ``` + + + + ``` + mutation { + syntheticsCreateDailyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + } + } + } + ``` + + + + ``` + mutation { + syntheticsCreateWeeklyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + maintenanceDays: [WeekDaysEnums] + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + maintenanceDays + } + } + ``` + + + + ``` + mutation { + syntheticsCreateMonthlyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + frequency: { + daysOfWeek: { + weekDay: WeekDaysEnum, + ordinalDayOfMonth: DayOfMonthOrdinal + }, + daysOfMonth: [Int] + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + frequency { + daysOfWeek { + weekDay, + ordinalDayOfMonth + }, + daysOfMonth + } + } + } + ``` + + + + ``` + mutation { + syntheticsEditMonitorDowntime ( + guid: "MonitorDowntimeEntityGuid", + name: "MONITOR_DOWNTIME_NAME", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + once: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss" + }, + daily: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + } + }, + weekly: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + maintenanceDays: [WeekDaysEnums] + }, + monthly: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + frequency: { + daysOfWeek: { + weekDay: WeekDaysEnum, + ordinalDayOfMonth: DayOfMonthOrdinal + }, + daysOfMonth: [Int] + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + maintenanceDays, + frequency { + daysOfWeek { + weekDay, + ordinalDayOfMonth + }, + daysOfMonth + } + } + } + ``` + + + + ``` + mutation { + syntheticsDeleteMonitorDowntime ( + guid: DOWNTIME_ENTITY_GUID + ) { + guid + } + } + ``` + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/apm/agents/go-agent/features/create-custom-events-go.mdx b/src/i18n/content/jp/docs/apm/agents/go-agent/features/create-custom-events-go.mdx index 77f7a5f43cb..d1cc0a837fb 100644 --- a/src/i18n/content/jp/docs/apm/agents/go-agent/features/create-custom-events-go.mdx +++ b/src/i18n/content/jp/docs/apm/agents/go-agent/features/create-custom-events-go.mdx @@ -45,7 +45,7 @@ RecordCustomEvent(eventType string, params map[string]interface{}) * 英数字、アンダースコア`_`またはコロン`:`で構成する必要があります。 * 255バイト以下であること。 - * [の名前、制限、および制限された文字に関する New Relic のデータ要件に従わなければなりません](/docs/insights/insights-data-sources/custom-data/data-requirements) 。 + * [名前、制限、および制限された文字](/docs/insights/insights-data-sources/custom-data/data-requirements)に関する New Relic データ要件に従う必要があります。 diff --git a/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx b/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx index b9f22202469..4e342aebee5 100644 --- a/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx +++ b/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx @@ -30,8 +30,8 @@ translationType: machine ```jar - .*newrelic-agent-.*\.jar[\\\/]instrumentation.*\.jar - .* + .*newrelic.*\.jar[\\\/]instrumentation.*\.jar + .* ``` diff --git a/src/i18n/content/jp/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-logs.mdx b/src/i18n/content/jp/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-logs.mdx index aa030002474..e57e154bc80 100644 --- a/src/i18n/content/jp/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-logs.mdx +++ b/src/i18n/content/jp/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-logs.mdx @@ -23,14 +23,14 @@ OpenTelemetryツールを使ってログを送信し、アプリケーション ### アプリケーションログを関連付けます [#log-correlation] -アプリケーションログは、アプリケーションによって生成された他のテレメトリデータと相関している場合にさらに役立ちます。 [サービスのOpenTelemetryセマンティック規則では](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource/semantic_conventions#service)、必須フィールドとして`service.name`が指定されています。同じ`service.name`でNewRelicに送信されるすべてのアプリケーションメトリック、トレース、およびログデータは、同じ[エンティティ](/docs/new-relic-one/use-new-relic-one/core-concepts/what-entity-new-relic)に関連付けられます。 +アプリケーション ログは、アプリケーションによって生成された他のテレメトリ データと関連付けられている場合にさらに役立ちます。[サービスの OpenTelemetry 意味規則では、](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/README.md)必須フィールドとして`service.name`が指定されています。同じ`service.name`で New Relic に送信されるすべてのアプリケーション メトリック、トレース、ログ データは、同じ[エンティティ](/docs/new-relic-one/use-new-relic-one/core-concepts/what-entity-new-relic)に関連付けられます。 ログに`service.name`リソース属性の注釈を付ける方法の詳細は、アプリケーションの環境によって異なります。 * アプリケーションは構造化されたJSONログを生成する場合があります。これは、別のフィールドとして`service.name`を含めるように構成できます。 -* `service.name`属性でログに注釈を付けるように[リソース プロセッサ](https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/resourceprocessor)で構成できる、専用の[コレクタ エージェント](https://opentelemetry.io/docs/collector/getting-started/#agent)インスタンスと一緒にアプリケーションをデプロイできます。 +* 専用の[コレクタ エージェント](https://opentelemetry.io/docs/collector/getting-started/#agent)インスタンスと一緒にアプリケーションをデプロイできます。これを[リソース プロセッサ](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource)で構成して、ログに`service.name`属性の注釈を付けることができます。 -必要に応じて、追加のアプリケーション[トレース コンテキスト](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/overview.md#log-correlation)(実行コンテキストと呼ばれることもあります) をログ メッセージに伝達できます。これのセットアップと可用性は、アプリケーションで使用される言語とロギング フレームワークによって異なります。一般的な戦略は、構造化された JSON ログを書き込むようにアプリケーションをセットアップし、使用可能なログ メッセージの指定された[トレース コンテキスト フィールド](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#trace-context-fields)にトレース コンテキストを抽出するようにアプリケーションを構成することです。詳細について[は、UI: ログ ページの OpenTelemetry を](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/view-your-data/opentelemetry-logs-page)参照してください。 +オプションで、追加のアプリケーション[トレース コンテキスト](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/sdk_exporters)(実行コンテキストと呼ばれることもあります) をログ メッセージに伝播できます。これのセットアップと可用性は、アプリケーションで使用される言語とロギング フレームワークによって異なります。一般的な戦略は、構造化された JSON ログを書き込むようにアプリケーションをセットアップし、利用可能なログ メッセージの指定された[トレース コンテキスト フィールド](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#trace-context-fields)にトレース コンテキストを抽出するようにアプリケーションを構成することです。詳細については、 [「UI: ログ」ページの「OpenTelemetry」](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/view-your-data/opentelemetry-logs-page)を参照してください。 [GitHub の Log4j2 を使用したコンテキスト内のログの例は、](https://github.com/newrelic/newrelic-opentelemetry-examples/tree/main/other-examples/java/logs-in-context-log4j2) Log4j2 を使用した単純な Java アプリケーションのエンドツーエンドの動作例を示しています。 diff --git a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx index c81ef7f9dcb..a2dff5e3c7f 100644 --- a/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx +++ b/src/i18n/content/jp/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx @@ -92,7 +92,7 @@ Synthetics ジョブ マネージャーをホストするには、システム - CPUコアあたり2.5GiBのRAM（専用） + CPU コアあたり 3.256 GiB の RAM (専用) diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx index fd4709e90a6..095a41567f4 100644 --- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx +++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing.mdx @@ -21,9 +21,11 @@ New Relic 가격 책정 모델은 간단하며 두 가지 기본 청구 요소, 아직 New Relic 고객이 아니고 가격에 대한 개요를 보려면 먼저 [기본 가격 페이지를](https://newrelic.com/pricing)참조하십시오. 가격 책정에 대한 자세한 내용을 보려면 계속 읽으십시오. -## 청구 및 사용 UI [#usage-ui] +## UI에서 사용량 확인 [#usage-ui] -New Relic 고객인 경우 청구를 이해하는 가장 좋은 방법은 [사용량 UI 페이지](https://one.newrelic.com/admin-portal/consumption-usage/home)로 이동하는 것입니다. 그것을 찾으려면 **[one.newrelic.com](https://one.newrelic.com)**으로 이동하십시오. [사용자 메뉴를](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings)클릭한 다음 **Administration** \[관리를] 클릭합니다. 사용량 개요를 보여주는 **Plan & usage** \[계획 및 사용량] UI 페이지로 이동합니다. +New Relic 고객인 경우 **Plan & usage** \[플랜 및 사용량] 페이지에서 사용량을 확인할 수 있습니다. 수치는 대략적인 수치이지만 이러한 보기를 사용하여 소비가 청구서에 어떤 영향을 미칠 수 있는지에 대한 일반적인 아이디어를 얻을 수 있습니다. + +사용법 UI를 찾으려면 **[one.newrelic.com](https://one.newrelic.com)** 으로 이동하세요. [사용자 메뉴를](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings) 클릭한 다음 **Administration** \[관리를] 클릭합니다. **Plan & usage** \[계획 및 사용량] UI 페이지에는 다음과 같은 사용량 개요가 표시됩니다. -
- **[one.newrelic.com](https://one.newrelic.com) > User menu > Administration > Plan & usage:** **Plan & usage** \[계획 및 사용] 페이지는 사용에 대한 세부 정보를 제공합니다. -
- ## New Relic 청구 요소 [#how-pricing-works] 사용량 기반 가격 책정 모델은 간단하므로 청구를 쉽게 예측할 수 있습니다. 다음 두 가지 기본 요소에 대해 비용을 청구합니다. diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx index 5c73316fc7d..4637b59623c 100644 --- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx +++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx @@ -11,11 +11,20 @@ freshnessValidatedDate: never translationType: machine --- -[New Relic 사용량 및 청구에](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing)대한 이해를 돕기 위해 청구 관련 사용량을 이해할 수 [있는 사용량 UI를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) 제공합니다. 또한 사용자 지정 NRQL 쿼리를 실행하여 추가 세부 정보를 얻을 수 있으며 사용량이 특정 수준에 도달했을 때 알림을 생성할 수 있습니다. +[New Relic 사용량 및 청구에](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing) 대한 이해를 돕기 위해 청구 관련 사용량을 이해할 수 [있는 사용량 UI를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) 제공합니다. 또한 사용자 정의 NRQL 쿼리를 실행하여 추가 세부 정보를 얻을 수 있으며 사용량이 특정 수준에 도달했을 때 경고 알림을 만들 수 있습니다. + +사용량 UI를 사용하거나 소비 쿼리를 수행할 때 다음 사항에 유의하세요. + +* 결과는 대략적인 것이며 인보이스 금액을 계산하는 데 사용된 값과 정확히 일치하지 않습니다. +* 이러한 도구를 사용하여 사용량이 많은 영역을 찾고 추적하세요. +* 쿼리를 사용하여 경고를 생성하면 한도에 가까워졌는지 알 수 있습니다. ## 데이터 수집 사용 쿼리 [#data-queries] -[사용량 UI는](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) 시간 경과에 따른 데이터 수집을 표시합니다. UI가 제공하는 것보다 더 자세한 정보가 필요한 경우 다음과 같은 NRQL 쿼리를 사용할 수 있습니다. +[사용량 UI에는](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) 시간 경과에 따른 데이터 수집이 표시됩니다. UI가 제공하는 것보다 더 자세한 내용이 필요한 경우 다양한 NRQL 쿼리를 사용할 수 있습니다. 아래 예에는 두 가지 데이터 유형이 포함되어 있습니다. + +* `NrConsumption`: 시간별 사용량 세부정보를 자세히 알아보려면 이 기능을 사용하세요. 청구서를 대신하는 데에는 도움이 되지 않습니다. +* `NrMTDConsumption`: 이를 사용하면 월간 집계 사용량에 대한 대략적인 수치를 확인할 수 있습니다. + + +## 모니터 가동 중지 시간 관리 [#monitor-downtimes] + +가동 중지 시간을 모니터링하면 합성 제품의 실행을 중지해야 하는 시간을 지정할 수 있습니다. 우리는 합성 물질에 대한 모니터 가동 중지 시간을 예약하는 방법을 보여주는 다양한 스니펫을 제공했습니다. 시간대, 시작 시간 및 종료 시간을 지정하려면 이러한 조각을 업데이트해야 합니다. 모니터 가동 중지 시간을 예약할 수 있는 시기에 대해 자세히 알아보려면 [예정된 유지 관리 시간 동안 모니터링 비활성화](docs/synthetics/synthetic-monitoring/using-monitors/monitor-downtimes-disable-monitoring-during-scheduled-maintenance-times/) 문서를 확인하세요. 시간대 값을 찾으려면 [시간대의 tz 데이터베이스를](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) 참조하세요. 예를 들어 America/Los Angeles는 PDT 약어를 사용합니다. + + + + ``` + mutation { + syntheticsCreateOnceMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "OptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss" + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime + } + } + ``` + + + + ``` + mutation { + syntheticsCreateDailyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + } + } + } + ``` + + + + ``` + mutation { + syntheticsCreateWeeklyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + maintenanceDays: [WeekDaysEnums] + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + maintenanceDays + } + } + ``` + + + + ``` + mutation { + syntheticsCreateMonthlyMonitorDowntime ( + accountId: NR_ACCOUNT_ID, + name: "MonitorDowntimeName", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + frequency: { + daysOfWeek: { + weekDay: WeekDaysEnum, + ordinalDayOfMonth: DayOfMonthOrdinal + }, + daysOfMonth: [Int] + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + frequency { + daysOfWeek { + weekDay, + ordinalDayOfMonth + }, + daysOfMonth + } + } + } + ``` + + + + ``` + mutation { + syntheticsEditMonitorDowntime ( + guid: "MonitorDowntimeEntityGuid", + name: "MONITOR_DOWNTIME_NAME", + monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], + once: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss" + }, + daily: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + } + }, + weekly: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + maintenanceDays: [WeekDaysEnums] + }, + monthly: { + timezone: "Timezone", + startTime: "yyyy-MM-ddTHH:mm:ss", + endTime: "yyyy-MM-ddTHH:mm:ss", + endRepeat: { + onDate: "yyyy-MM-ddTHH:mm:ss", + onRepeat: Int + }, + frequency: { + daysOfWeek: { + weekDay: WeekDaysEnum, + ordinalDayOfMonth: DayOfMonthOrdinal + }, + daysOfMonth: [Int] + } + ) { + guid, + accountId, + name, + monitorGuids, + timezone, + startTime, + endTime, + endRepeat { + onDate, + onRepeat + }, + maintenanceDays, + frequency { + daysOfWeek { + weekDay, + ordinalDayOfMonth + }, + daysOfMonth + } + } + } + ``` + + + + ``` + mutation { + syntheticsDeleteMonitorDowntime ( + guid: DOWNTIME_ENTITY_GUID + ) { + guid + } + } + ``` + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apm/agents/go-agent/features/create-custom-events-go.mdx b/src/i18n/content/kr/docs/apm/agents/go-agent/features/create-custom-events-go.mdx index ff6a3c523c0..b8705202718 100644 --- a/src/i18n/content/kr/docs/apm/agents/go-agent/features/create-custom-events-go.mdx +++ b/src/i18n/content/kr/docs/apm/agents/go-agent/features/create-custom-events-go.mdx @@ -45,7 +45,7 @@ RecordCustomEvent(eventType string, params map[string]interface{}) * 영숫자, 밑줄 `_` 또는 콜론 `:` 으로 구성되어야 합니다. * 255바이트를 넘지 않아야 합니다. - * [이름, 제한 및 제한된 문자에](/docs/insights/insights-data-sources/custom-data/data-requirements) 대한 New Relic 데이터 요구 사항을 따라야 합니다. + * [이름, 제한 및 제한된 문자](/docs/insights/insights-data-sources/custom-data/data-requirements) 에 대한 New Relic 데이터 요구 사항을 따라야 합니다. diff --git a/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx b/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx index 49d5fcf5535..8619712b709 100644 --- a/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx +++ b/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx @@ -30,8 +30,8 @@ translationType: machine ```jar - .*newrelic-agent-.*\.jar[\\\/]instrumentation.*\.jar - .* + .*newrelic.*\.jar[\\\/]instrumentation.*\.jar + .* ``` diff --git a/src/i18n/content/kr/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx b/src/i18n/content/kr/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx index d190b43a75a..afa7db87a47 100644 --- a/src/i18n/content/kr/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx +++ b/src/i18n/content/kr/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx @@ -92,7 +92,7 @@ import synthetick8s from 'images/synthetic_logo_k8logo.webp' - CPU 코어당 2.5GiB RAM(전용) + CPU 코어당 3.256GiB RAM(전용) diff --git a/src/install/java/whatsNext.mdx b/src/install/java/whatsNext.mdx index c59e4aab6a7..0f4b8f86165 100644 --- a/src/install/java/whatsNext.mdx +++ b/src/install/java/whatsNext.mdx @@ -9,7 +9,7 @@ headingText: What's next? - Now that you've installed the Python agent, [learn how to solve perfomance issues](/docs/journey-app-slow/root-causes/) with our tutorial series. + Now that you've installed the Java agent, [learn how to solve performance issues](/docs/journey-app-slow/root-causes/) with our tutorial series. #### See your app data in the UI. diff --git a/src/nav/tutorial-create-alerts.yml b/src/nav/tutorial-create-alerts.yml deleted file mode 100644 index 3a1a59f2217..00000000000 --- a/src/nav/tutorial-create-alerts.yml +++ /dev/null @@ -1,11 +0,0 @@ -title: Create and manage alerts -path: /docs/tutorial-create-alerts -pages: - - title: Getting started with New Relic alerts - path: /docs/tutorial-create-alerts/create-new-relic-alerts - - title: Create your alerts - path: /docs/tutorial-create-alerts/create-an-alert - - title: Improve your stack with alerts - path: /docs/tutorial-create-alerts/improve-with-alerts - - title: Manage your alert quality - path: /docs/tutorial-create-alerts/manage-alert-quality \ No newline at end of file diff --git a/src/nav/tutorial-data-ingest-gov.yml b/src/nav/tutorial-data-ingest-gov.yml deleted file mode 100644 index 7d41b3c104b..00000000000 --- a/src/nav/tutorial-data-ingest-gov.yml +++ /dev/null @@ -1,13 +0,0 @@ -title: Optimize your telemetry -path: /docs/tutorial-data-ingest-gov -pages: - - title: Introduction to data ingest - path: /docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry - - title: 1. Create a baseline report - path: /docs/tutorial-optimize-telemetry/create-baseline-report - - title: 2. Detect data anomalies - path: /docs/tutorial-optimize-telemetry/detect-anomalies - - title: 3. Develop your optimization plan - path: /docs/tutorial-optimize-telemetry/develop-optimize-plan - - title: 4. Optimize your data ingest - path: /docs/tutorial-optimize-telemetry/data-optimize-techniques \ No newline at end of file diff --git a/src/nav/tutorial-dd-migration.yml b/src/nav/tutorial-dd-migration.yml deleted file mode 100644 index cf092d00e5c..00000000000 --- a/src/nav/tutorial-dd-migration.yml +++ /dev/null @@ -1,11 +0,0 @@ -title: Migrate from Datadog -path: /docs/tutorial-dd-migration -pages: - - title: Migrate from Datadog - path: /docs/tutorial-dd-migration/migrating-from-dd - - title: 1. Start ingesting data - path: /docs/tutorial-dd-migration/installing-monitor - - title: 2. Setup dashboards and alerts - path: /docs/tutorial-dd-migration/migrating-dashboards - - title: 3. Making the switch - path: /docs/tutorial-dd-migration/making-the-switch diff --git a/src/nav/tutorial-error-tracking.yml b/src/nav/tutorial-error-tracking.yml deleted file mode 100644 index 8655c8fc3af..00000000000 --- a/src/nav/tutorial-error-tracking.yml +++ /dev/null @@ -1,9 +0,0 @@ -title: Find errors in your failing app -path: /docs/tutorial-error-tracking -pages: - - title: 1. Respond to outages with error tracking - path: /docs/tutorial-error-tracking/respond-outages - - title: 2. Solve critical errors - path: /docs/tutorial-error-tracking/solve-critical-errors - - title: 3. Assign errors to the correct team - path: /docs/tutorial-error-tracking/route-teams \ No newline at end of file diff --git a/src/nav/tutorial-improve-app-performance.yml b/src/nav/tutorial-improve-app-performance.yml deleted file mode 100644 index 77c433d8669..00000000000 --- a/src/nav/tutorial-improve-app-performance.yml +++ /dev/null @@ -1,13 +0,0 @@ -title: My app is slow -path: /docs/tutorial-improve-app-performance -pages: - - title: 1. Prepare to triage your application - path: /docs/tutorial-improve-app-performance/root-causes - - title: 2. Diagnose problematic transactions - path: /docs/tutorial-improve-app-performance/problematic-transactions - - title: 3. Diagnose slow database queries - path: /docs/tutorial-improve-app-performance/slow-database-queries - - title: 4. Diagnose slow external services - path: /docs/tutorial-improve-app-performance/external-services - - title: 5. Create performance benchmarks - path: /docs/tutorial-improve-app-performance/create-benchmarks \ No newline at end of file diff --git a/src/nav/tutorial-improve-customer-experience.yml b/src/nav/tutorial-improve-customer-experience.yml deleted file mode 100644 index a5440a87155..00000000000 --- a/src/nav/tutorial-improve-customer-experience.yml +++ /dev/null @@ -1,11 +0,0 @@ -title: Improve your customer experience -path: /docs/tutorial-improve-customer-experience -pages: - - title: Introduction to customer experience - path: /docs/tutorial-improve-customer-experience/intro-to-customer-experience - - title: 1. Establish your current state - path: /docs/tutorial-improve-customer-experience/establish-current-state - - title: 2. Improve your customer experience - path: /docs/tutorial-improve-customer-experience/improve-customer-experience - - title: 3. Analyze the bottom of the funnel - path: /docs/tutorial-improve-customer-experience/bottom-funnel-analysis \ No newline at end of file diff --git a/src/nav/tutorial-improve-site-performance.yml b/src/nav/tutorial-improve-site-performance.yml deleted file mode 100644 index 7a2509b5869..00000000000 --- a/src/nav/tutorial-improve-site-performance.yml +++ /dev/null @@ -1,13 +0,0 @@ -title: Improve your website's performance -path: /docs/tutorial-improve-site-performance -pages: - - title: 1. Instrument your site - path: /docs/tutorial-improve-site-performance/improve-website-performance - - title: 2. Monitor your core web vitals - path: /docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals - - title: 3. Fix high latency - path: /docs/tutorial-improve-site-performance/fixing-high-latency - - title: 4. Reduce JavaScript errors - path: /docs/tutorial-improve-site-performance/reduce-javascript-errors - - title: 5. Create performance benchmarks - path: /docs/tutorial-improve-site-performance/performance-benchmarks \ No newline at end of file diff --git a/src/nav/tutorial-innovation.yml b/src/nav/tutorial-innovation.yml deleted file mode 100644 index c40b6d4c33e..00000000000 --- a/src/nav/tutorial-innovation.yml +++ /dev/null @@ -1,9 +0,0 @@ -title: Improve your development and release quality -path: /docs/tutorial-innovation-and-growth -pages: - - title: Improve with New Relic - path: /docs/tutorial-innovation-and-growth/innovate-with-new-relic - - title: 1. Improve your code base - path: /docs/tutorial-innovation-and-growth/development-quality-mgmt - - title: 2. Improve the quality of your releases - path: /docs/tutorial-innovation-and-growth/release-quality-mgmt \ No newline at end of file diff --git a/src/nav/tutorial-manage-large-log-volume.yml b/src/nav/tutorial-manage-large-log-volume.yml deleted file mode 100644 index 754cde8e021..00000000000 --- a/src/nav/tutorial-manage-large-log-volume.yml +++ /dev/null @@ -1,9 +0,0 @@ -title: Manage large volume of logs -path: /docs/tutorial-manage-large-log-volume -pages: - - title: 1. Get started - path: /docs/tutorial-manage-large-log-volume/get-started-managing-large-logs - - title: 2. Filter your logs - path: /docs/tutorial-manage-large-log-volume/filter-large-logs - - title: 3. Organize your logs - path: /docs/tutorial-manage-large-log-volume/organize-large-logs \ No newline at end of file diff --git a/src/nav/tutorial-peak-demand.yml b/src/nav/tutorial-peak-demand.yml deleted file mode 100644 index 103975fc8e1..00000000000 --- a/src/nav/tutorial-peak-demand.yml +++ /dev/null @@ -1,13 +0,0 @@ -title: Prepare for peak demand -path: /docs/tutorial-peak-demand -pages: - - title: 1. Get started - path: /docs/tutorial-peak-demand/get-started - - title: 2. Find your baselines - path: /docs/tutorial-peak-demand/find-your-baseline - - title: 3. Reduce alert noise - path: /docs/tutorial-peak-demand/create-quality-alerts - - title: 4. Align your teams - path: /docs/tutorial-peak-demand/organize-data-workloads - - title: 5. Autoscale your infrastructure - path: /docs/tutorial-peak-demand/autoscale-your-infra \ No newline at end of file diff --git a/src/nav/tutorial-reporting-data.yml b/src/nav/tutorial-reporting-data.yml deleted file mode 100644 index 3f5e21ea646..00000000000 --- a/src/nav/tutorial-reporting-data.yml +++ /dev/null @@ -1,9 +0,0 @@ -title: Capture the right data -path: /docs/tutorial-reporting-data -pages: - - title: Capture the right data with New Relic - path: /docs/tutorial-reporting-data/capture-the-right-data - - title: Capture service telemetry - path: /docs/tutorial-reporting-data/capture-service-telemetry - - title: Capture web telemetry - path: /docs/tutorial-reporting-data/capture-web-telemetry \ No newline at end of file diff --git a/src/nav/tutorial-troubleshoot-external-services-apis.yml b/src/nav/tutorial-troubleshoot-external-services-apis.yml deleted file mode 100644 index b2d6f861bff..00000000000 --- a/src/nav/tutorial-troubleshoot-external-services-apis.yml +++ /dev/null @@ -1,7 +0,0 @@ -title: Solve API issues -path: /docs/tutorial-troubleshoot-external-services-apis -pages: - - title: 1. Respond to API issues - path: /docs/tutorial-troubleshoot-external-services-apis/respond-external - - title: 2. Resolve API issues - path: /docs/tutorial-troubleshoot-external-services-apis/solve-external \ No newline at end of file diff --git a/src/nav/tutorial-troubleshoot-infra-hosts.yml b/src/nav/tutorial-troubleshoot-infra-hosts.yml deleted file mode 100644 index 37449096daa..00000000000 --- a/src/nav/tutorial-troubleshoot-infra-hosts.yml +++ /dev/null @@ -1,11 +0,0 @@ -title: Troubleshoot hosts with infra data -path: /docs/tutorial-troubleshoot-infra-hosts -pages: - - title: 1. Capture your infrastructure data - path: /docs/tutorial-troubleshoot-infra-hosts/collect-your-data - - title: 2. Diagnose app failure with host data - path: /docs/tutorial-troubleshoot-infra-hosts/diagnose-app-infra-data - - title: 3. Make resource decisions with your data - path: /docs/tutorial-troubleshoot-infra-hosts/investigate-your-resources - - title: 4. Create dashboards with infra metrics - path: /docs/tutorial-troubleshoot-infra-hosts/create-metrics-dashboards \ No newline at end of file diff --git a/src/nav/tutorial-understand-k8s.yml b/src/nav/tutorial-understand-k8s.yml deleted file mode 100644 index dc8b835d731..00000000000 --- a/src/nav/tutorial-understand-k8s.yml +++ /dev/null @@ -1,11 +0,0 @@ -title: Understand and monitor Kubernetes -path: /docs/kubernetes-pixie -pages: - - title: 1. Understand your Kubernetes system - path: /docs/tutorial-kubernetes-learn/tutorial-k8s-intro - - title: 2. Monitor Kubernetes clusters - path: /docs/tutorial-kubernetes-learn/tutorial-k8s-layers - - title: 3. Monitor Kubernetes orchestrated components - path: /docs/tutorial-kubernetes-learn/tutorial-k8s-orchestrated - - title: 4. Monitor Kubernetes services and apps - path: /docs/tutorial-kubernetes-learn/tutorial-k8s-services