diff --git a/src/content/docs/workflow-automation/create-a-workflow-automation/create-your-own.mdx b/src/content/docs/workflow-automation/create-a-workflow-automation/create-your-own.mdx index fac0634876e..6040c39858b 100644 --- a/src/content/docs/workflow-automation/create-a-workflow-automation/create-your-own.mdx +++ b/src/content/docs/workflow-automation/create-a-workflow-automation/create-your-own.mdx @@ -20,9 +20,9 @@ When templates don't fit your needs, [Create Your Own](https://onenr.io/0OQM47Kg This guide shows you how to build workflows using concepts and a complete example. Choose your learning path: -- **Learn core concepts first** → Read [Core concepts](#core-concepts) and [Workflow patterns](#workflow-patterns) to understand the fundamentals, then apply them -- **Follow the example** → Jump to [Example walkthrough](#example-walkthrough) to build an EC2 auto-resize workflow step-by-step -- **Reference patterns** → Use the [Workflow patterns](#workflow-patterns) section as a quick reference when building your own workflows +- **Learn core concepts first**: Read [Core concepts](#core-concepts) and [Workflow patterns](#workflow-patterns) to understand the fundamentals, then apply them +- **Follow the example**: Jump to [Example walkthrough](#example-walkthrough) to build an EC2 auto-resize workflow step-by-step +- **Reference patterns**: Use the [Workflow patterns](#workflow-patterns) section as a quick reference when building your own workflows **New to workflows?** Start with core concepts, then follow the example. The EC2 workflow demonstrates all key patterns in a real-world scenario. @@ -134,7 +134,7 @@ Understand these fundamentals before you build: - Mandatory field for loop functions to define iteration count + Required parameter for loop functions to define iteration count @@ -183,7 +183,7 @@ For detailed error handling patterns, see [Best practices](/docs/workflow-automa Build your first workflow in five steps: 1. Navigate to **[one.newrelic.com](https://one.newrelic.com) > All Capabilities > Workflow Automation** and select **[Create Your Own](https://onenr.io/0OQM47KgxjG)** -2. Define parameters for credentials (from secrets manager: `${{ :secrets:keyName }}`), configuration (regions, instance types), and runtime data (account IDs, alert IDs) +2. Define parameters for credentials (from [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager): `${{ :secrets:keyName }}`), configuration (regions, instance types), and runtime data (account IDs, alert IDs) 3. Drag actions from the [catalog](/docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog), connect them with `${{ .steps.stepName.outputs.field }}` syntax to pass data 4. Insert switches for conditional branching, loops for processing lists or polling, approval gates for human decisions 5. Run after each section to catch errors early, then [start or schedule](/docs/workflow-automation/create-a-workflow-automation/start-schedule) your workflow @@ -242,7 +242,7 @@ Four essential patterns handle most automation scenarios. Each pattern is demons ### Approval gates and waiting -**Use approval gates when:** Human judgment needed before destructive operations or compliance sign-off required +**Use approval gates when:** Human judgment is needed before destructive operations or compliance sign-off is required **Key syntax:** ```yaml @@ -314,7 +314,7 @@ Before building this workflow, ensure you have: - **AWS**: Credentials with EC2 and Systems Manager permissions - **Slack**: Bot token and channel for notifications - **New Relic**: Alert condition monitoring EC2 CPU -- **Secrets manager**: Configured (see [secrets management](/docs/infrastructure/host-integrations/installation/secrets-management/)) +- **Secrets manager**: Configured (see [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager)) ### Workflow overview [#workflow-overview] @@ -332,10 +332,10 @@ This example demonstrates key patterns you'll use in custom workflows: querying **Skip if you're reading for concepts.** This table details the 12 parameters this workflow uses. You can reference it when building, but it's not essential for understanding the flow. -This workflow requires credentials, configuration, and runtime context as inputs. Sensitive values come from secrets manager using `${{ :secrets:keyName }}` syntax. +This workflow requires credentials, configuration, and runtime context as inputs. Sensitive values come from [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) using `${{ :secrets:keyName }}` syntax. **Input categories:** -- **Authentication**: AWS and Slack credentials from secrets manager +- **Authentication**: AWS and Slack credentials from [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) - **Alert context**: Account ID and issue ID from New Relic - **Configuration**: Region, instance type, timezone, Slack channel @@ -370,7 +370,7 @@ This workflow requires credentials, configuration, and runtime context as inputs `${{ :secrets:awsAccessKeyId }}` - AWS Access Key ID retrieved from secrets manager for authenticating with AWS services. + AWS Access Key ID retrieved from [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) for authenticating with AWS services. @@ -384,7 +384,7 @@ This workflow requires credentials, configuration, and runtime context as inputs `${{ :secrets:awsSecretAccessKey }}` - AWS Secret Access Key retrieved from secrets manager. Pairs with the access key ID. + AWS Secret Access Key retrieved from [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). Pairs with the access key ID. @@ -606,7 +606,7 @@ Now let's build each part of the workflow. Each step includes the specific actio The workflow resizes the instance through AWS Systems Manager (SSM): * **`createSsmDocument`**: Creates an SSM Automation document that stops the instance, modifies type, and restarts it. - * **`generateIdempotencyToken`**: Creates a unique UUID. Prevents duplicate resizes if the workflow runs twice. + * **`generateIdempotencyToken`**: Creates a unique UUID to prevent duplicate resizes if the workflow runs twice. * **`startResizing`**: Executes the SSM document with instance ID and new type. * **`progressLoop` (Loop)**: Posts Slack updates every 10 seconds (5 times total). * **`waitForCompletion`**: Polls SSM status with 2-minute timeout. diff --git a/src/content/docs/workflow-automation/create-a-workflow-automation/start-schedule.mdx b/src/content/docs/workflow-automation/create-a-workflow-automation/start-schedule.mdx index 07857751112..1e96a9b19f2 100644 --- a/src/content/docs/workflow-automation/create-a-workflow-automation/start-schedule.mdx +++ b/src/content/docs/workflow-automation/create-a-workflow-automation/start-schedule.mdx @@ -38,7 +38,7 @@ Before triggering workflows, ensure you have: - **Account ID**: Your New Relic account ID (found in [Account settings](/docs/accounts/accounts-billing/account-structure/account-id)). - **Workflow name**: The exact name from your workflow definition. - **Required inputs**: Values for any parameters your workflow expects. -- **Secrets configured**: AWS credentials, Slack tokens, or other secrets stored in [secrets manager](/docs/infrastructure/host-integrations/installation/secrets-management/). +- **Secrets configured**: AWS credentials, Slack tokens, or other secrets stored in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). **New to workflows?** Create your first workflow before trying to trigger it. Start with [Use a template](/docs/workflow-automation/create-a-workflow-automation/use-a-template) for pre-built workflows. @@ -95,9 +95,9 @@ The following workflow definition invokes an AWS Lambda function and logs the ou - message: 'The lambda function message output is:${{ .steps.invoke1.outputs.payload.body }}' ``` -To start this workflow, use the following NerdGraph mutation. Before running this mutation, ensure you've stored your AWS credentials using the `secretsManagementCreateSecret` mutation. For more information, see [Introduction to secrets management](/docs/apis/nerdgraph/examples/nerdgraph-secrets-management). +To start this workflow, use the following NerdGraph mutation. Before running this mutation, ensure you've stored your AWS credentials using the `secretsManagementCreateSecret` mutation. For more information, see [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). -```graphql +```yaml mutation { workflowAutomationStartWorkflowRun( # Specify the account where the workflow is defined @@ -165,7 +165,7 @@ Schedules use cron expressions to define when workflows run. Format: `minute hou The following example schedules the `lambda1` workflow to run every day at 9 AM Eastern Time: -```graphql +```yaml mutation { workflowAutomationCreateSchedule( # Specify the account where the workflow is defined diff --git a/src/content/docs/workflow-automation/limitations-and-faq/workflow-best-practices.mdx b/src/content/docs/workflow-automation/limitations-and-faq/workflow-best-practices.mdx index 6cbb08c9955..e7946614bb4 100644 --- a/src/content/docs/workflow-automation/limitations-and-faq/workflow-best-practices.mdx +++ b/src/content/docs/workflow-automation/limitations-and-faq/workflow-best-practices.mdx @@ -107,7 +107,7 @@ Store all sensitive values in New Relic's secrets manager. Never hardcode creden Store AWS credentials, API tokens, and passwords: -```graphql +```yaml mutation { secretsManagementCreateSecret( scope: {type: ACCOUNT id: "YOUR_NR_ACCOUNT_ID"} diff --git a/src/content/docs/workflow-automation/limitations-and-faq/workflow-limits.mdx b/src/content/docs/workflow-automation/limitations-and-faq/workflow-limits.mdx index 493ed518548..d5b06e166b3 100644 --- a/src/content/docs/workflow-automation/limitations-and-faq/workflow-limits.mdx +++ b/src/content/docs/workflow-automation/limitations-and-faq/workflow-limits.mdx @@ -40,12 +40,22 @@ freshnessValidatedDate: never 50KB - No of Workflow definitions (Including all versions) + No of Workflow definitions at account level(excluding versions count) 1000 - No of Workflow definitions at org level (including all versions) + No of Workflow definitions at org level (excluding versions count) + + 1000 + + + No of versions per workflow definition at account level + + 1000 + + + No of versions per workflow definition at org level 1000 @@ -67,7 +77,7 @@ freshnessValidatedDate: never Length of a workflow input value - 1000 characters + 1000 Characters Workflow concurrent runs (per account) diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog.mdx index 0d0ea809374..cf80c587b84 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog.mdx @@ -5,7 +5,7 @@ tags: - workflow - workflow automation actions - actions catalog -metaDescription: "List of available actions catalog for workflow definition" +metaDescription: "List of available action catalogs for workflow definitions" freshnessValidatedDate: never --- @@ -15,18 +15,290 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -New Relic actions catalog provides actions that can be performed against your infrastructure and integrations. You can orchestrate and automate your end-to-end processes by linking together actions that perform tasks in your cloud providers, and New Relic accounts. +The New Relic actions catalog provides actions that can be performed against your infrastructure and integrations. You can orchestrate and automate your end-to-end processes by linking together actions that perform tasks in your cloud providers and New Relic accounts. -## Available action catalogs [#available-catalogs] +The actions follow a hierarchical naming convention: `company.product.action`, making it easy to find and use the right action for your workflow. -The following action catalogs are available for workflow automation: +## How to use this catalog -- [AWS actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws) - Integrate with AWS services including Lambda, EC2, and Systems Manager -- [Communication actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/communication) - Send notifications and messages through various communication channels -- [HTTP actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/http) - Make HTTP requests to external APIs and services -- [New Relic actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic) - Interact with New Relic platform features and data -- [PagerDuty actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty) - Manage PagerDuty incidents and integrations -- [Utility actions](/docs/workflow-automation/setup-and-configuration/actions-catalog/others) - Perform common data transformation and utility operations +This catalog is organized by provider and product hierarchy. You can: +- Browse the complete list of actions in the table below +- Use your browser's search function (Ctrl+F or Cmd+F) to quickly find specific actions +- Navigate to detailed documentation pages for each product category +- Use the left navigation to drill down into specific action categories + +## Complete actions catalog + +The table below lists all available actions. Click on any action name to view its detailed documentation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Action NameCategoryDescription
[Get log events from CloudWatch Logs](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch#aws.cloudWatch.getLogEvents)AWS CloudWatchGet log events from CloudWatch Logs
[Put log events to CloudWatch Logs](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch#aws.cloudWatch.putLogEvents)AWS CloudWatchPut log events to CloudWatch Logs
[Delete an EBS snapshot](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2#awsec2deletesnapshot)AWS EC2Delete an EBS snapshot
[Reboot EC2 instances](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2#awsec2rebootinstances)AWS EC2Reboot EC2 instances
[Launch new EC2 instances](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2#aws.ec2.runInstances)AWS EC2Launch new EC2 instances
[Start stopped EC2 instances](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2#awsec2startinstances)AWS EC2Start stopped EC2 instances
[Terminate EC2 instances](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2#awsec2terminateinstances)AWS EC2Terminate EC2 instances
[Execute any AWS API operation](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api#aws.execute.api)AWS Execute APIExecute any AWS API operation
[Get Lambda function configuration](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda#aws.lambda.getFunction)AWS LambdaGet Lambda function configuration
[Invoke a Lambda function](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda#aws.lambda.invoke)AWS LambdaInvoke a Lambda function
[List Lambda function aliases](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda#aws.lambda.listAliases)AWS LambdaList Lambda function aliases
[Update Lambda function configuration](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda#aws.lambda.updateFunctionConfiguration)AWS LambdaUpdate Lambda function configuration
[Delete an object from S3 bucket](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3#aws.s3.deleteObject)AWS S3Delete an object from S3 bucket
[Get an object from S3 bucket](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3#aws.s3.getObject)AWS S3Get an object from S3 bucket
[List objects in an S3 bucket](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3#aws.s3.listObjectsV2)AWS S3List objects in an S3 bucket
[Add an object to S3 bucket](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3#aws.s3.putObject)AWS S3Add an object to S3 bucket
[Publish a message to SNS topic](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns#aws.sns.publish)AWS SNSPublish a message to SNS topic
[Receive a message from SQS queue](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs#aws.sqs.receiveMessage)AWS SQSReceive a message from SQS queue
[Send a message to SQS queue](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs#aws.sqs.sendMessage)AWS SQSSend a message to SQS queue
[Delete a Systems Manager document](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager#aws.systemsManager.deleteDocument)AWS Systems ManagerDelete a Systems Manager document
[Start a Systems Manager automation](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager#awssystemsmanagerstartautomation)AWS Systems ManagerStart a Systems Manager automation
[Wait for automation execution status](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager#awssystemsmanagerwaitforautomationstatus)AWS Systems ManagerWait for automation execution status
[Create or update a Systems Manager document](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager#awssystemsmanagerwritedocument)AWS Systems ManagerCreate or update a Systems Manager document
[Perform HTTP DELETE request](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete#httpdelete)HTTPPerform HTTP DELETE request
[Perform HTTP GET request](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get#httpget)HTTPPerform HTTP GET request
[Perform HTTP POST request](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post#httppost)HTTPPerform HTTP POST request
[Perform HTTP PUT request](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put#httpput)HTTPPerform HTTP PUT request
[Send custom events to New Relic](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest#newrelic.ingest.sendEvents)New Relic IngestSend custom events to New Relic
[Send logs to New Relic](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest#newrelic.ingest.sendLogs)New Relic IngestSend logs to New Relic
[Execute NerdGraph query or mutation](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph#newrelic.nerdgraph.execute)New Relic NerdGraphExecute NerdGraph query or mutation
[Send notification to New Relic destination](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification#newrelic.notification.send)New Relic NotificationSend notification to New Relic destination
[Send email notification](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification#newrelic.notification.sendEmail)New Relic NotificationSend email notification
[Send Microsoft Teams notification](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification#newrelic.notification.sendMicrosoftTeams)New Relic NotificationSend Microsoft Teams notification
[Execute NRQL query](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb#newrelic.nrdb.query)New Relic NRDBExecute NRQL query
[Create a PagerDuty incident](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident#pagerDuty.incident.create)PagerDuty IncidentCreate a PagerDuty incident
[Get PagerDuty incident details](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident#pagerDuty.incident.get)PagerDuty IncidentGet PagerDuty incident details
[List PagerDuty incidents](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident#pagerDuty.incident.list)PagerDuty IncidentList PagerDuty incidents
[Resolve a PagerDuty incident](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident#pagerDuty.incident.resolve)PagerDuty IncidentResolve a PagerDuty incident
[Update a PagerDuty incident](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident#pagerDuty.incident.update)PagerDuty IncidentUpdate a PagerDuty incident
[Get reactions from Slack message](/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat#slack.chat.getReactions)Slack ChatGet reactions from Slack message
[Post a message to Slack channel](/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat#slack.chat.postMessage)Slack ChatPost a message to Slack channel
[Convert epoch timestamp to datetime](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime#utils.datetime.fromEpoch)Utilities - DateTimeConvert epoch timestamp to datetime
[Transform data to CSV format](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform#utils.transform.toCSV)Utilities - TransformTransform data to CSV format
[Generate a UUID](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid#utils.uuid.generate)Utilities - UUIDGenerate a UUID
+ +## Actions by category + +Browse actions organized by provider and product: + +### AWS Actions +- [AWS CloudWatch](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch) - CloudWatch Logs operations +- [AWS EC2](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2) - EC2 instance and snapshot management +- [AWS Execute API](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api) - Execute any AWS API operation +- [AWS Lambda](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda) - Lambda function operations +- [AWS S3](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3) - S3 bucket and object operations +- [AWS SNS](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns) - SNS topic operations +- [AWS SQS](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs) - SQS queue operations +- [AWS Systems Manager](/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager) - Systems Manager automation and documents + +### HTTP Actions +- [HTTP DELETE](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete) - DELETE request operations +- [HTTP GET](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get) - GET request operations +- [HTTP POST](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post) - POST request operations +- [HTTP PUT](/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put) - PUT request operations + +### New Relic Actions +- [New Relic Ingest](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest) - Send events and logs to New Relic +- [New Relic NerdGraph](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph) - Execute NerdGraph queries and mutations +- [New Relic NRDB](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb) - Query New Relic database +- [New Relic Notification](/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification) - Send notifications through New Relic + +### Communication Actions +- [Slack Chat](/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat) - Slack messaging operations + +### Incident Management Actions +- [PagerDuty Incident](/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident) - PagerDuty incident management + +### Utility Actions +- [Utilities - DateTime](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime) - Date and time utilities +- [Utilities - Transform](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform) - Data transformation utilities +- [Utilities - UUID](/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid) - UUID generation utilities ## What's next diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/auth/auth-jwt-create.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/auth/auth-jwt-create.mdx new file mode 100644 index 00000000000..167e641908e --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/auth/auth-jwt-create.mdx @@ -0,0 +1,204 @@ +--- +title: "Auth JWT actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - Auth actions + - Auth JWT actions +metaDescription: "A list of available auth jwt actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for authentication actions available in the workflow automation actions catalog. These actions enable you to create and manage JSON Web Tokens (JWT) for secure authentication in your workflows. + +## Authentication actions + + + + Create a JSON Web Token + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldTypeDescriptionExample
**algorithm**StringAlgorithm used to sign the token. + RS256 +

Supported algorithms: RS256 ,ES256

+
**privateKey**String + The private key for signing a JWT. + - RS256 supports private key in PKCS#8 & PKCS#1 format. ES256 supports private key in PKCS#8 (.p8) format. + - Private Key must be provided as a secret expression. + - PrivateKey must be stored as single line string in Secrets. + `${{ :secrets:namespace:privateKey }}`
**headers**Map + Headers provides metadata for JWT +

+ **UnSupported headers**: nested objects, arrays, null are not supported +

+ 		`{"kid": "key-2025-09"}`
**claims**Map + Claims are statements about an entity (typically, the user) and additional data +

+ **Unsupported Claim Types**: null, Nested objects / arbitrary maps, Lists containing non-strings or mixed types. +

+ 		`{"role": "admin", "scope": "read:all"}`
**expirationTimeMinutes**Int + Expiration time in minutes +

+ Expiration time should be greater than 0 and less than 30days. +

+ 		10
**includeIssuedAt**Boolean + Issued At timestamp +

+ Default: true +

+ 		true
**selectors**List + ```yaml + [name: token, + + expression: .jwt + + ] +``` +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription
**success**Boolean`true/false`
**jwt**String"`xxxxx.yyyyy.zzzzz`“
**errorMessage**String`“Unsupported algorithm for creating jwt token"`
+ + + + + + + + + + + + + + +
Workflow definition
+ ```yaml + name: create-json-web-token + description: "" + steps: + - name: auth_jwt_create_1 + type: action + action: auth.jwt.create + version: "1" + inputs: + algorithm: RS256 + privateKey: ${{ :secrets:namespace:privatekey}} + headers: + header1: value1 + claims: + claim1: value1 + expirationTimeMinutes: 10 + next: end + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws.mdx deleted file mode 100644 index 8e75f93182b..00000000000 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws.mdx +++ /dev/null @@ -1,4935 +0,0 @@ ---- -title: "AWS actions" -tags: - - workflow automation - - workflow - - workflow automation actions - - AWS actions -metaDescription: "A list of available actions in the actions catalog for workflow definitions" -freshnessValidatedDate: never ---- - - - We're still working on this feature, but we'd love for you to try it out! - - This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -This page provides a comprehensive reference for AWS actions available in the workflow automation actions catalog. These actions enable you to integrate AWS services into your workflow definitions, including Lambda functions, Systems Manager automation, EC2 instance management, and general API execution. - -## Prerequisites - -Before using AWS actions in workflow automation, ensure you have: - - * An AWS account with appropriate permissions. - * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). - * The necessary IAM permissions for the specific AWS services you plan to use. - -See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. - -## Lambda actions - - - - Invokes a Lambda function synchronously or asynchronously with an optional payload. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`my-lambda-function`
**invocationType**OptionalString`Event'|'RequestResponse'|'DryRun'`
**payload**OptionalString`'{"key": "value"}'`
**parameters**OptionalMap - ```yaml - { - "Qualifier": "1", - "ClientContext":"encoded value" - }, - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - - **Action Timeout**: This action has a maximum 1-minute(60-second) timeout for synchronous invocations - - **Long-Running Functions**: For functions that may run longer than 1 minute, you must use the Event InvocationType. This invokes the function asynchronously. You can then use other actions (like aws.cloudwatch.getLogEvents or checking an SQS/SNS callback) to get the result. - - `InvocationType` is critical: - - `RequestResponse` (default): Invokes the function synchronously. The action waits for the function to complete and returns the response. - - `Event`: Invokes the function asynchronously. The action returns a success status immediately without waiting for the code to finish. - - `ClientContext` is for advanced use cases and the provided String must be Base64-encoded - - Any additional API parameters not listed above can be passed in the `parameters` map. To support a wide range of inputs, the `parameters` map accepts any optional argument available in the official boto3 API documentation. This allows you to dynamically construct requests by adding multiple fields. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - [{"success":true,"response":{"StatusCode":200,"ExecutedVersion":"$LATEST","Payload":{"statusCode":200,"body":"\"Hello userName\""}}}] - ``` -

- Response syntax can be referred to [invoke - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/invoke.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "ValidationException: 1 validation error detected"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: lambda-invoke-function-test - description: 'Invokes a Lambda function with a payload' - workflowInputs: - arnRole: - type: String - steps: - - name: aws_lambda_invoke_1 - type: action - action: aws.lambda.invoke - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-east-1 - functionName: my-lambda-processor - payload: '{"orderId": "12345", "amount": 99.99}' - next: end - ``` -
- - - - - - - - Modifies the configuration of a specific AWS Lambda function. Provide only the parameters you want to change. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`"my-lambda-function-to-update"`
**role**OptionalString`arn:aws:iam::123456789012:role/new-lambda-role`
**handler**OptionalString`“main.new_handler"`
**description**OptionalString`Updated function description`
**parameters**OptionalMap - ```yaml - { - "Timeout": "60", - "MemorySize": 123, - }, - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - [{"success":true,"response":{"FunctionName":"hello-you","FunctionArn":"arn:aws:lambda:us-east-2:----:function:hello-you","Runtime":"nodejs20.x","Role":"arn:aws:iam::----:role/TF-hello-you-role","Handler":"hello-you.handler","CodeSize":334,"Description":"This is hello you description from action","Timeout":30,"MemorySize":128,"LastModified":"2025-09-23T13:57:03.000+0000","CodeSha256":"CU03aDDg+34=","Version":"$LATEST","TracingConfig":{"Mode":"PassThrough"},"RevisionId":"0f1e4d9b-c45a-4896-a32d-7cd78e77a273","State":"Active","LastUpdateStatus":"InProgress","LastUpdateStatusReason":"The function is being created.","LastUpdateStatusReasonCode":"Creating","PackageType":"Zip","Architectures":["x86_64"],"EphemeralStorage":{"Size":512},"SnapStart":{"ApplyOn":"None","OptimizationStatus":"Off"},"RuntimeVersionConfig":{"RuntimeVersionArn":"arn:aws:lambda:us-east-2::runtime:01eab27397bfdbdc243d363698d4bc355e3c8176d34a51cd47dfe58cf977f508"},"LoggingConfig":{"LogFormat":"Text","LogGroup":"/aws/lambda/hello-you"}}}] - ``` -

- Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/update_function_configuration.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`[ { "errorMessage": "An error occurred (ResourceNotFoundException) when calling the UpdateFunctionConfiguration operation: Function not found: arn:aws:lambda:us-east-2:661945836867:function:my-lambda-function-to-update", "success": false, "response": null } ]`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: lambda-update-config-test - description: 'Updates the timeout and memory of a Lambda function' - workflowInputs: - arnRole: - type: String - steps: - - name: aws_lambda_update_function_configuration_1 - type: action - action: aws.lambda.updateFunctionConfiguration - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-west-2 - functionName: my-lambda-function-to-update - parameters: - Timeout:60 - MemorySize:123 - - next: end - ``` -
- - - - - - - - Retrieves the configuration details, code location, and other metadata for a specific AWS Lambda function. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`"my-lambda-function"`
**parameters**OptionalMap - ```yaml - { - "Qualifier": "1" - }, - ``` -
**selectors**OptionalList`[[{"name": "response", "expression": ".response"}]`
- - - To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - {"response": } - ``` -

- Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/get_function.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "ResourceNotFoundException: Function not found"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: lambda-get-function-test - description: 'Retrieves the configuration of a specific Lambda function' - workflowInputs: - arnRole: - type: String - steps: - - name: aws_lambda_getFunction_1 - type: action - action: aws.lambda.getFunction - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-east-1 - FunctionName: hello-you - parameters: - Qualifier: 1 - next: end - ``` -
- - - - - - - Returns a list of aliases for a specific AWS Lambda function. Aliases are pointers to function versions. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`“my-lambda-function“`
**marker**OptionalString - Pass the `NextMarker` token from a previous response for pagination. -

- e.g., `“abcd....."` -

-
**maxItems**OptionalInt - Limit the number of aliases returned -

- e.g., `123` -

-
**parameters**OptionalMap - For additional optional API parameters. -

- e.g., `{"AnotherOptionalParam": "value"}` -

-
**selectors**OptionalList`[{"name": "response", "expression": ".response"}]`
- - - - **Pagination**: Use the Marker and MaxItems inputs to paginate through a large number of aliases. - - To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - {"response": } - ``` -

- Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/list_aliases.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "ResourceNotFoundException: Function not found"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: lambda-list-aliases-test - description: 'Lists all aliases for a Lambda function' - workflowInputs: - arnRole: - type: String - steps: - - name: aws_lambda_list_aliases_1 - type: action - action: aws.lambda.listAliases - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-east-1 - functionName: hello-you - parameters: - FunctionVersion: 1 - next: end - ``` -
- - - - - - -## EC2 actions - - - - - This action deletes an Amazon EC2 snapshot. You cannot delete a snapshot of the root device of an EBS volume used by a registered AMI. You must first deregister the AMI before you can delete the snapshot. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**snapshotId**RequiredString`“snapshot-id-1"`
**selectors**OptionalString`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**Object - No Response in case of success : true -

- Response syntax can be referred [delete_snapshot - Boto3 1.40.55 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/delete_snapshot.html). -

-
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Failed to delete snapshot"`
- - - - - - - - - - - - - - -
Workflow Example
- ```yaml - name: ec2-deleteSnapshot-test - description: '' - workflowInputs: - arnRole: - type: String - region: - type: String - defaultValue: us-west-2 - snapshotId: - type: List - defaultValue: snapshot-id-1 - steps: - - name: aws_ec2_deleteSnapshot_1 - type: action - action: aws.ec2.deleteSnapshot - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: ${{ .workflowInputs.region }} - snapshotId: ${{ .workflowInputs.snapshotId }} - next: end - ``` -
- - - - - - - - Requests a reboot of the specified instances. This operation is asynchronous; it only queues a request to reboot the specified instances. The operation succeeds if the instances are valid and belong to you. Requests to reboot terminated instances are ignored. - - If an instance does not cleanly shut down within a few minutes, Amazon EC2 performs a hard reboot. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**Object[reboot_instances - Boto3 1.40.56 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/reboot_instances.html)
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: ""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: reboot-ec2-test - description: '' - workflowInputs: - arnRole: - type: String - region: - type: String - defaultValue: us-west-2 - instanceIds: - type: List - defaultValue: ["i-123456789abcdef0"] - steps: - - name: aws_ec2_rebootInstances_1 - type: action - action: aws.ec2.rebootInstances - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: ${{ .workflowInputs.region }} - instanceIds: ${{ .workflowInputs.instanceIds }} - next: end - ``` -
- - - - - - - - Starts an Amazon EBS-backed instance that you previously stopped. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**Object - ```yaml - {"response":{ - 'StartingInstances': [ - { - 'InstanceId': 'String', - 'CurrentState': { - 'Code': 123, - 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' - }, - 'PreviousState': { - 'Code': 123, - 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' - } - }, - ] - } - - } - - } - ``` -

- Response syntax can be referred [start_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/start_instances.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "The parameter instancesSet cannot be used with the parameter maxResults"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: ab-ec2-startInstance-test - description: '' - workflowInputs: - arnRole: - type: String - region: - type: String - defaultValue: us-west-2 - instanceIds: - type: list - defaultValue: ["i-123456789abcdef0"] - steps: - - name: aws_ec2_startInstances_1 - type: action - action: aws.ec2.startInstances - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: ${{ .workflowInputs.region }} - instanceIds: ${{ .workflowInputs.instanceIds }} - next: end - ``` -
- - - - - - - - Terminates the specified instances. This operation is [idempotent](https://docs.aws.amazon.com/ec2/latest/devguide/ec2-api-idempotency.html); if you terminate an instance more than once, each call succeeds. - - If you specify multiple instances and the request fails (for example, because of a single incorrect instance ID), none of the instances are terminated. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - { - 'TerminatingInstances': [ - { - 'InstanceId': 'String', - 'CurrentState': { - 'Code': 123, - 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' - }, - 'PreviousState': { - 'Code': 123, - 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' - } - }, - ] - } - ``` -

- Response syntax can be referred [terminate_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/terminate_instances.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (`InvalidInstanceID.Malformed`) when calling the TerminateInstances operation: The instance ID 'i-012345678' is malformed"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: ec2-terminate-test - description: '' - workflowInputs: - arnRole: - type: String - region: - type: String - defaultValue: us-west-2 - instanceIds: - type: list - defaultValue: ["i-123456789abcdef0"] - steps: - - name: aws_ec2_terminateInstances_1 - type: action - action: aws.ec2.terminateInstances - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: ${{ .workflowInputs.region }} - instanceIds: ${{ .workflowInputs.instanceIds }} - next: end - ``` -
- - - - - - - - Launches the specified number of instances using an AMI for which you have permissions. - - You can specify a number of options, or leave the default options. The following rules apply: - - If you don’t specify a subnet ID, we choose a default subnet from your default VPC for you. If you don’t have a default VPC, you must specify a subnet ID in the request. - - If any of the AMIs have a product code attached for which the user has not subscribed, the request fails. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**imageId**RequiredString`“ami-0ca4d5db4872d0c28”`
**instanceType**RequiredString`“t2.micro”`
**minCount**RequiredInt`1`
**maxCount**RequiredInt`10`
**parameters**OptionalMap - ```yaml - { - "EbsOptimized": false, - "TagSpecifications": [ - { - "ResourceType": "instance", - "Tags": [ - { - "Key": "Name", - "Value": "My-Web-Server" - } - ] - } - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object -

- Response syntax can be referred: [run_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/run_instances.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: ""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: ec2_run_instance - workflowInputs: - arnRole: - type: String - required: true - steps: - - name: RunInstance - type: action - action: aws.ec2.runInstances - version: '1' - inputs: - awsRoleArn: ${{.workflowInputs.arnRole}} - region: us-east-2 - imageId: ami-0ca4d5db4872d0c28 - instanceType: t2.micro - minCount: 1 - maxCount: 1 - parameters: - EbsOptimized: false - TagSpecifications: - - ResourceType: instance - Tags: - - Key: Name - Value: My-Test-Instance - selectors: - - name: instanceId - expression: .response.Instances[0].InstanceId - ``` -
- - - - - - - -## Systems Manager actions - - - - Writes a document to the AWS account based on the AWS credentials passed in the action input. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/?id=docs_gateway) - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsAccessKeyId**RequiredString`${{ :secrets: }}`
**awsSecretAccessKey**RequiredString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
**documentType**OptionalString`documentType: "Command"`
**documentFormat**OptionalString`documentFormat: "YAML"`
**documentContent**RequiredString
**override**OptionalBoolean - `override: true (default)`. When `true`, always write the document with the provided name even if one already exist. When `false`, if a document with the provided `documentName` already exist, the action returns `success: false` and `errorMessage:Document already exists`. Please enable override if you want to update the existing document. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**documentName**String`documentName: "my-ssm-document"`
**documentVersion**String`documentVersion: 1`
**documentType**String`documentType: "Command"`
**documentStatus**String`documentStatus: "Active"`.
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
- - - - - - - - - - - - - - - - - - -
Workflow definitionInputsOutputs
- ```yaml - schemaVersion: '0.3' - description: List all Lambda function names. - mainSteps: - - name: ExecuteAwsApi - action: aws:executeAwsApi - isEnd: true - ``` - - ```yaml - inputs: - Service: lambda - Api: ListFunctions - ``` - - ```yaml - outputs: - - Name: resultFunctionName - Selector: $..FunctionName - Type: StringList - outputs: - - ExecuteAwsApi.resultFunctionName - ``` -
- - - - - - - Deletes an AWS document in the AWS account based on the credentials passed in the action input. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/documents.html) - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsAccessKeyId**RequiredString`${{ :secrets: }}`
**awsSecretAccessKey**RequiredString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**documentName**StringdocumentName: "my-ssm-document"
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
- - - - - - - - - - - - - - - - - - -
Workflow definitionInputsOutputs
- ```yaml - schemaVersion: '0.3' - description: List all Lambda function names. - mainSteps: - - name: ExecuteAwsApi - action: aws:executeAwsApi - isEnd: true - ``` - - ```yaml - inputs: - Service: lambda - Api: ListFunctions - ``` - - ```yaml - outputs: - - Name: resultFunctionName - Selector: $..FunctionName - Type: StringList - outputs: - - ExecuteAwsApi.resultFunctionName - ``` -
- - - - - - - Starts an automation using an AWS document. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_StartAutomationExecution.html) - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsAccessKeyId**RequiredString`${{ :secrets: }}`
**awsSecretAccessKey**RequiredString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
**parameters**OptionalMap`parameters: myKey: myValue`
**idempotencyToken**OptionalUUID`idempotencyToken: "any token"`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**automationExecutionId**String`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
- - - - - - - - - - - - - - - - - - -
Workflow definitionInputsOutputs
- ```yaml - schemaVersion: '0.3' - description: List all Lambda function names. - mainSteps: - - name: ExecuteAwsApi - action: aws:executeAwsApi - isEnd: true - ``` - - ```yaml - Service: lambda - Api: ListFunctions - ``` - - ```yaml - - Name: resultFunctionName - Selector: $..FunctionName - Type: StringList - outputs: - - ExecuteAwsApi.resultFunctionName - ``` -
- - - - - - - Waits for an automation using an AWS document. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/?id=docs_gateway) for more information. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**automationExecutionId**RequiredString`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`. The automation executionID for which we need to wait for its completion.
**automationExecutionStatuses**OptionalListList of automation execution statuses from [AutomationExecution](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_AutomationExecution.html#AutomationExecutionStatus) that can stop the waiting, `Default: ["Success", "Failed"]`
**timeout**Optionalint`timeout: 600`. The duration in seconds can wait for automation status to be one of the expected `automationExecutionStatuses`. Post this timeout duration, the action return value with timeout error.
**selectors**OptionalList`[{\"name\": \"automationExecutionStatus\", \"expression\": \".automationExecutionStatus\"}, {\"name\": \"scriptOutput\", \"expression\": \".automationExecutionOutputs.pythonStep.scriptOutput | tojson\"}]`.
- - - 1. In the action input, only `awsAccessKeyId` and `awsSecretAccessKey` can be provided, but they should be static credentials of an IAM user. - 2. If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to the action input. - 3. Refer to the instructions to set up [AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials). - 4. Use selectors to get only the specified parameters as output. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**automationExecutionId**String`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`
**automationExecutionStatus**String`automationExecutionStatus: "Success"`. If action is successful, It will either of the values passed in `automationExecutionStatuses` input field. Else, this will be null.
**automationExecutionOutputs**Map - ```yaml - "automationExecutionOutputs": { - "ExecuteGetApiResources": { - "resultResourceId": [ - "pky3cb" - ] - }, - "ExecuteListVersionsByFunction": { - "resultLambdaVersionArn": [ - "arn:aws:lambda:us-east-2:123456789012:function:ApiGwTestFn:1" - ] - } - } - ``` -

- The output will be a map of output values from the document. Any output in the document can be collected using this output field and can be used in subsequent steps of the workflow automation definition. -

-
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
- - - - - - - - - - - - - - - - - - -
Workflow definitionInputsOutputs
- ```yaml - schemaVersion: '0.3' - description: List all Lambda function names. - mainSteps: - - name: ExecuteAwsApi - action: aws:executeAwsApi - isEnd: true - ``` - - ```yaml - Service: lambda - Api: ListFunctions - ``` - - ```yaml - - Name: resultFunctionName - Selector: $..FunctionName - Type: StringList - outputs: - - ExecuteAwsApi.resultFunctionName - ``` -
- - - - - - - -## General AWS actions - - - - - This action allows you to execute any AWS API operation for a specified service. It supports providing AWS credentials, region, service name, API name, and optional parameters. The action can return outputs such as success status, response data, and error messages, making it versatile for interacting with AWS services programmatically. - - ### Security and IAM configuration - - To use this action, you must configure AWS credentials. See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for detailed instructions on creating an IAM role or IAM user. - - - **Security best practice:** When defining IAM policies for this action, always use least-privilege access. Grant only the specific AWS API actions your workflow requires, and restrict permissions to specific resources rather than using wildcards. - - - ### Required IAM permissions - - The permissions you need depend on which AWS services and APIs your workflow calls. Use the examples below as templates for creating least-privilege policies. - - **Example: Allow sending messages to a specific SQS queue** - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "sqs:SendMessage", - "Resource": "arn:aws:sqs:us-west-2::" - } - ] - } - ``` - - **Example: Allow querying a specific DynamoDB table** - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "dynamodb:Query", - "Resource": "arn:aws:dynamodb:us-west-2::table/" - } - ] - } - ``` - - **Example: Multiple services with specific permissions** - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "sqs:SendMessage", - "Resource": "arn:aws:sqs:us-west-2::" - }, - { - "Effect": "Allow", - "Action": "dynamodb:Query", - "Resource": "arn:aws:dynamodb:us-west-2::table/" - } - ] - } - ``` - - - - Replace ``, ``, and `` with your actual values - - Find available AWS service APIs in the [Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html) - - For more complex IAM policy patterns, see the [AWS IAM documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) - - - For more information on how this action works, see the [AWS Systems Manager executeAwsApi documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-action-executeAwsApi.html). - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**service**RequiredString`service: "sqs"`.[AWS available services](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html)
**api**RequiredStringapi: "create_queue"
**parameters**RequiredMap - ```yaml - parameters: { - "QueueName": "dks-testing-queue", - "Attributes": { - "DelaySeconds": "0", - "MessageRetentionPeriod": "86400" - } - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - - In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. - - In the action input, if `awsAccessKeyId` and `awsSecretAccessKey` are to be provided, make sure they are static credentials of an IAM user. - - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to the action input. - - Refer to [AWS credentials](/docs/workflow-automation/set-up-aws-credentials/) for instructions. - - Use selectors to get only the specified parameters as output. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object`{"response":` - }} each service and api have different response for example https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/client/query.html.
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "User does not have permission to query DynamoDB"`
- - - - - ### Example 1: Send a message to an SQS queue - - This example demonstrates how to send a message to an Amazon SQS queue using the `aws.execute.api` action with IAM role authentication. - - ```yaml - name: sqs_send_message_example - - workflowInputs: - awsRoleArn: - type: String - description: "ARN of the IAM role to assume (e.g., arn:aws:iam::123456789012:role/workflow-sqs-role)" - awsRegion: - type: String - defaultValue: us-east-2 - awsQueueUrl: - type: String - defaultValue: "https://sqs.us-east-2.amazonaws.com//" - - steps: - - name: sendSqsMessage - type: action - action: aws.execute.api - version: 1 - inputs: - awsRoleArn: ${{ .workflowInputs.awsRoleArn }} - region: ${{ .workflowInputs.awsRegion }} - service: sqs - api: send_message - parameters: - QueueUrl: ${{ .workflowInputs.awsQueueUrl }} - MessageBody: | - { - "message": "deployment is bad", - "status": "not good" - } - selectors: - - name: success - expression: '.success' - - name: messageId - expression: '.response.MessageId' - - name: errorMessage - expression: '.errorMessage' - - - name: logResult - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - message: 'SQS message sent. Success: ${{ .steps.sendSqsMessage.outputs.success }}, MessageId: ${{ .steps.sendSqsMessage.outputs.messageId }}' - licenseKey: '${{ :secrets:NEW_RELIC_LICENSE_KEY }}' - ``` - - **Required IAM policy for this example:** - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "sqs:SendMessage", - "Resource": "arn:aws:sqs:us-east-2::" - } - ] - } - ``` - - **Expected outputs:** - - `success`: Boolean indicating whether the message was sent successfully - - `messageId`: The unique ID assigned by SQS to the sent message - - `errorMessage`: Error message if the operation failed - - ### Example 2: Query a DynamoDB table - - This example demonstrates how to query a DynamoDB table using the `aws.execute.api` action with session credentials. - - ```yaml - name: dynamodb_query_example - - workflowInputs: - awsAccessKeyId: - type: String - defaultValue: "${{ :secrets:AWS_ACCESS_KEY_ID }}" - awsSecretAccessKey: - type: String - defaultValue: "${{ :secrets:AWS_SECRET_ACCESS_KEY }}" - awsSessionToken: - type: String - defaultValue: "${{ :secrets:AWS_SESSION_TOKEN }}" - awsRegion: - type: String - defaultValue: us-east-2 - tableName: - type: String - defaultValue: workflow-definitions-prod - scopedName: - type: String - description: "The scoped name to query" - version: - type: String - defaultValue: "1" - - steps: - - name: queryDynamoDB - type: action - action: aws.execute.api - version: 1 - inputs: - awsAccessKeyId: ${{ .workflowInputs.awsAccessKeyId }} - awsSecretAccessKey: ${{ .workflowInputs.awsSecretAccessKey }} - awsSessionToken: ${{ .workflowInputs.awsSessionToken }} - region: ${{ .workflowInputs.awsRegion }} - service: dynamodb - api: query - parameters: - TableName: ${{ .workflowInputs.tableName }} - KeyConditionExpression: "ScopedName = :scopedNameValue AND Version = :versionValue" - ExpressionAttributeValues: - ":scopedNameValue": - S: ${{ .workflowInputs.scopedName }} - ":versionValue": - N: ${{ .workflowInputs.version }} - selectors: - - name: success - expression: '.success' - - name: response - expression: '.response' - - name: errorMessage - expression: '.errorMessage' - - - name: logResult - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - message: 'DynamoDB query result: ${{ .steps.queryDynamoDB.outputs.response.Items }}' - licenseKey: '${{ :secrets:NEW_RELIC_LICENSE_KEY }}' - ``` - - **Required IAM policy for this example:** - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "dynamodb:Query", - "Resource": "arn:aws:dynamodb:us-east-2::table/workflow-definitions-prod" - } - ] - } - ``` - - **Expected outputs:** - - `success`: Boolean indicating whether the query was successful - - `response`: The DynamoDB query response containing the matching items - - `errorMessage`: Error message if the operation failed - - - - - - -## CloudWatch actions - - - - - This action retrieves a batch of log events from a specified log stream in AWS CloudWatch Logs. It's essential for monitoring, auditing, and troubleshooting applications by programmatically fetching log data. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**logStreamName**RequiredString`"2023/10/27/[$LATEST]abcdef123456"`
**logGroupName**OptionalString`"/aws/lambda/my-function"`
**logGroupIdentifier**OptionalString`“arn:partition:service:region:account-id:resource”`
**startTime**OptionalInt`1759296000000`
**endTime**OptionalInt`1759296000000`
**limit**OptionalInt`50`
**startFromHead**OptionalBoolean`true`
**unmask**OptionalBoolean`false`
**nextToken**OptionalString`“f/39218833627378687642013305455131706539523449361490509828/s”`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - { - 'events': [ - { - 'timestamp': 123, - 'message': 'string', - 'ingestionTime': 123 - }, - ], - 'nextForwardToken': 'string', - 'nextBackwardToken': 'string' -} - ``` -
**success**Boolean`success: true | false`
**errorMessage**String`“An error occurred (ExpiredTokenException) when calling the GetLogEvents operation: The security token included in the request is expired”`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: get-lambda-logs - description: 'Retrieve log events from an AWS Lambda function' - workflowInputs: - region: - type: String - defaultValue: us-east-2 - logGroupName: - type: String - defaultValue: /aws/lambda/my-function - logStreamName: - type: String - defaultValue: 2023/10/27/[$LATEST]abcdef123456 - steps: - name: get_events_step - type: action - action: aws.cloudwatch.get_log_events - version: '1' - inputs: - region: ${{ .workflowInputs.region }} - logGroupName: ${{ .workflowInputs.logGroupName }} - logStreamName: ${{ .workflowInputs.logStreamName }} - limit: 100 - ``` -
- - - - - - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**logGroupName**RequiredString`"/aws/lambda/hello-you"`
**logStreamName**RequiredString`"2025/09/24/[$LATEST]09f7ca9e9ab044f389419ce60305f594"`
**logEvents**RequiredList - ```yaml - [ - -{ "timestamp": 1698384000000, "message": "Workflow task started." }, - - { "timestamp": 1698384000015, "message": "Data validated successfully." } ] - ``` -
**entity**OptionalDict`{ "entity": { "keyAttributes": { "ResourceType": "AWS::ElasticLoadBalancingV2::LoadBalancer", "Identifier": "app/my-web-lb/12345", "Environment": "Production" }, "attributes": { "MonitoringTier": "Gold", "OwnerTeam": "Networking", "MaintenanceWindow": "Sat: 0200-0400" } } }`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - ```yaml - { - 'events': [ - { - 'timestamp': 123, - 'message': 'string', - 'ingestionTime': 123 - }, - ], - 'nextForwardToken': 'string', - 'nextBackwardToken': 'string' - } -``` -
**success**Boolean`success: true | false`
**errorMessage**String`“An error occurred (ExpiredTokenException) when calling the GetLogEvents operation: The security token included in the request is expired”`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: get-lambda-logs - description: 'Retrieve log events from an AWS Lambda function' - workflowInputs: - region: - type: String - defaultValue: us-east-2 - logGroupName: - type: String - defaultValue: /aws/lambda/my-function - logStreamName: - type: String - defaultValue: 2023/10/27/[$LATEST]abcdef123456 - steps: - name: get_events_step - type: action - action: aws.cloudwatch.get_log_events - version: '1' - inputs: - region: ${{ .workflowInputs.region }} - logGroupName: ${{ .workflowInputs.logGroupName }} - logStreamName: ${{ .workflowInputs.logStreamName }} - limit: 100 - ``` -
- - - - - - -## S3 actions - - - - - The `listObjectsV2` method returns some or all (up to 1,000) of the objects in a bucket. It is a more modern and recommended version of `list_objects`. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**prefix**OptionalString"`path/to/folder/`"
**maxKeys**OptionalInteger`100`
**continuationToken**OptionalString`some-token`
**parameters**OptionalMap - ```graphql - { - "Delimiter": "/" - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldType
EncodingTypeString
FetchOwnerBoolean
StartAfterString
RequestPayerString
ExpectedBucketOwnerString
OptionalObjectAttributesList
DelimiterString
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - - - ```yaml - { - 'IsTruncated': True|False, - 'Contents': [ - { - 'Key': 'string', - 'LastModified': datetime(2015, 1, 1), - 'ETag': 'string', - 'ChecksumAlgorithm': [ - 'CRC32'|'CRC32C'|'SHA1'|'SHA256'|'CRC64NVME', - ], - 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', - 'Size': 123, - 'StorageClass': 'STANDARD'|'REDUCED_REDUNDANCY'|'GLACIER'|'STANDARD_IA'|'ONEZONE_IA'|'INTELLIGENT_TIERING'|'DEEP_ARCHIVE'|'OUTPOSTS'|'GLACIER_IR'|'SNOW'|'EXPRESS_ONEZONE'|'FSX_OPENZFS', - 'Owner': { - 'DisplayName': 'string', - 'ID': 'string' - }, - 'RestoreStatus': { - 'IsRestoreInProgress': True|False, - 'RestoreExpiryDate': datetime(2015, 1, 1) - } - }, - ], - 'Name': 'string', - 'Prefix': 'string', - 'Delimiter': 'string', - 'MaxKeys': 123, - 'CommonPrefixes': [ - { - 'Prefix': 'string' - }, - ], - 'EncodingType': 'url', - 'KeyCount': 123, - 'ContinuationToken': 'string', - 'NextContinuationToken': 'string', - 'StartAfter': 'string', - 'RequestCharged': 'requester' - } - ``` -

- Response syntax can be referred to in the [list_objects_v2 - Boto3 1.40.52 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/list_objects_v2.html) -

- - -
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Parameter validation failed:\nInvalid bucket name \"s3-activity-test \": Bucket name must match the regex \"^[a-zA-Z0-9.\\-_]{1,255}$\" or be an ARN matching the regex \"^arn:(aws).:(s3|s3-object-lambda):[a-z\\-0-9]:[0-9]{12}:accesspoint[/:][a-zA-Z0-9\\-.]{1,63}$|^arn:(aws).*:s3-outposts:[a-z\\-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9\\-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9\\-]{1,63}$\""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: aws-s3-list-objects-v2 - description: 'List Objects in an AWS S3 Bucket' - - steps: - - name: aws_s3_listObjectsV2_1 - type: action - action: aws.s3.listObjectsV2 - version: '1' - inputs: - awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" - region: "us-east-2" - bucket: "examplebucket" - prefix: "path/to/folder/" - maxKeys: 100 - continuationToken: "some-token" - next: end - ``` -
- - - - - - - - The `deleteObject` method permanently removes a single object from a bucket. For versioned buckets, this operation inserts a **delete marker**, which hides the object without permanently deleting it unless a `VersionId` is specified. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**parameters**OptionalMap - ```yaml - { - "RequestPayer": "test", - "BypassGovernanceRetention": false - "VersionId":"testVersion", - "MFA":"Test" - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldType
RequestPayerString
BypassGovernanceRetentionBoolean
ExpectedBucketOwnerString
IfMatchString
IfMatchLastModifiedTimeMap
IfMatchSizeInt
VersionIdString
MFAString
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - - - ```yaml - { - 'DeleteMarker': True|False, - 'VersionId': 'string', - 'RequestCharged': 'requester' - } - ``` -

- Response syntax can be referred [delete_object - Boto3 1.40.55 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/delete_object.html) -

- - -
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Parameter validation failed:\nInvalid bucket name \"s3-activity-test \": Bucket name must match the regex \"^[a-zA-Z0-9.\\-_]{1,255}$\" or be an ARN matching the regex \"^arn:(aws).:(s3|s3-object-lambda):[a-z\\-0-9]:[0-9]{12}:accesspoint[/:][a-zA-Z0-9\\-.]{1,63}$|^arn:(aws).*:s3-outposts:[a-z\\-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9\\-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9\\-]{1,63}$\""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: aws-s3-delete-object - description: 'Delete an AWS S3 Object' - - steps: - - name: aws_s3_deleteObject_1 - type: action - action: aws.s3.deleteObject - version: '1' - inputs: - awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" - region: "us-west-2" - bucket: "my-bucket" - key: "path/to/object.txt" - next: end - ``` -
- - - - - - - - Adds an object to a bucket. Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**body**RequiredString`file content`
**contentType**RequiredString"`plain/text`"
**tagging**OptionalString`“key1=value1"`
**parameters**OptionalMap - ```yaml - { - "ServerSideEncryption": "AES256", - "Metadata": { - 'metadata1': 'value1', - 'metadata2': 'value2', - } - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldType
RequestPayerString
ACLString
CacheControlString
ContentDispositionString
ContentEncodingString
ContentLanguageString
ContentLengthInt
ContentMD5String
ChecksumAlgorithmString
ChecksumCRC32String
ChecksumCRC32CString
ChecksumCRC64NVMEString
ChecksumSHA1String
ChecksumSHA256String
ExpiresMap
IfMatchString
IfNoneMatchString
GrantFullControlString
GrantReadString
GrantReadACPString
GrantWriteACPString
WriteOffsetBytesInt
ServerSideEncryptionString
StorageClassString
WebsiteRedirectLocationString
SSECustomerAlgorithmString
SSECustomerKeyString
SSEKMSKeyIdString
SSEKMSEncryptionContextString
BucketKeyEnabledBoolean
RequestPayerString
ObjectLockModeString
ObjectLockRetainUntilDateMap
ObjectLockLegalHoldStatusString
ExpectedBucketOwnerString
MetadataMap
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - - - ```yaml - { - 'Expiration': 'string', - 'ETag': 'string', - 'ChecksumCRC32': 'string', - 'ChecksumCRC32C': 'string', - 'ChecksumCRC64NVME': 'string', - 'ChecksumSHA1': 'string', - 'ChecksumSHA256': 'string', - 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', - 'ServerSideEncryption': 'AES256'|'aws:fsx'|'aws:kms'|'aws:kms:dsse', - 'VersionId': 'string', - 'SSECustomerAlgorithm': 'string', - 'SSECustomerKeyMD5': 'string', - 'SSEKMSKeyId': 'string', - 'SSEKMSEncryptionContext': 'string', - 'BucketKeyEnabled': True|False, - 'Size': 123, - 'RequestCharged': 'requester' - } - ``` -

- Response syntax can be referred [put_object - Boto3 1.40.59 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/put_object.html) -

- - -
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: s3-put-object - description: 'Put an AWS S3 Object' - - steps: - - name: aws_s3_putObject_1 - type: action - action: aws.s3.putObject - version: '1' - inputs: - awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" - region: "us-east-2" - bucket: "examplebucket" - key: "path/to/object.txt" - body: "Hello world" - contentType: "plain/text" - tagging: "key1=value1" - next: end - ``` -
- - - - - - - - In the `GetObject` request, specify the full key name for the object. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**versionId**OptionalString`"some-version-id"`
**range**OptionalString`bytes=0-99`
**parameters**OptionalMap - ```yaml - { - "ChecksumMode": "ENABLED", - "ExpectedBucketOwner": "test-user" - } - ``` -
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
- - - The action will fail if the object is more than 100kb. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldType
IfMatchString
IfModifiedSinceMap
IfNoneMatchString
IfUnmodifiedSinceMap
ResponseCacheControlString
ResponseContentDispositionString
ResponseContentEncodingString
ResponseContentLanguageString
ResponseContentTypeString
ResponseExpiresMap
SSECustomerAlgorithmString
SSECustomerKeyString
RequestPayerString
PartNumberInt
ExpectedBucketOwnerString
ChecksumModeString
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - - - ```yaml - { - 'Body': StreamingBody(), - 'DeleteMarker': True|False, - 'AcceptRanges': 'string', - 'Expiration': 'string', - 'Restore': 'string', - 'LastModified': datetime(2015, 1, 1), - 'ContentLength': 123, - 'ETag': 'string', - 'ChecksumCRC32': 'string', - 'ChecksumCRC32C': 'string', - 'ChecksumCRC64NVME': 'string', - 'ChecksumSHA1': 'string', - 'ChecksumSHA256': 'string', - 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', - 'MissingMeta': 123, - 'VersionId': 'string', - 'CacheControl': 'string', - 'ContentDisposition': 'string', - 'ContentEncoding': 'string', - 'ContentLanguage': 'string', - 'ContentRange': 'string', - 'ContentType': 'string', - 'Expires': datetime(2015, 1, 1), - 'ExpiresString': 'string', - 'WebsiteRedirectLocation': 'string', - 'ServerSideEncryption': 'AES256'|'aws:fsx'|'aws:kms'|'aws:kms:dsse', - 'Metadata': { - 'string': 'string' - }, - 'SSECustomerAlgorithm': 'string', - 'SSECustomerKeyMD5': 'string', - 'SSEKMSKeyId': 'string', - 'BucketKeyEnabled': True|False, - 'StorageClass': 'STANDARD'|'REDUCED_REDUNDANCY'|'STANDARD_IA'|'ONEZONE_IA'|'INTELLIGENT_TIERING'|'GLACIER'|'DEEP_ARCHIVE'|'OUTPOSTS'|'GLACIER_IR'|'SNOW'|'EXPRESS_ONEZONE'|'FSX_OPENZFS', - 'RequestCharged': 'requester', - 'ReplicationStatus': 'COMPLETE'|'PENDING'|'FAILED'|'REPLICA'|'COMPLETED', - 'PartsCount': 123, - 'TagCount': 123, - 'ObjectLockMode': 'GOVERNANCE'|'COMPLIANCE', - 'ObjectLockRetainUntilDate': datetime(2015, 1, 1), - 'ObjectLockLegalHoldStatus': 'ON'|'OFF' - } - ``` -

- Response syntax can be referred to in the [get_object - Boto3 1.40.59 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/get_object.html) -

- - -
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (InvalidArgument) when calling the GetObject operation: Invalid version id specified"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: s3-get-object - description: 'Get an AWS S3 Object' - - steps: - - name: aws_s3_getObject_1 - type: action - action: aws.s3.getObject - version: '1' - inputs: - awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" - region: "us-east-2" - bucket: "examplebucket" - key: "path/to/object.txt" - next: end - ``` -
- - - - - - -## SNS actions - - - - - Sends a message to an Amazon SNS topic. All subscribers to the topic will receive the message. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**message**RequiredString - Messages must be UTF-8 encoded strings and at most 256 KB in size -

- `'Workflow failed at step 3'` -

-
**topicArn**OptionalString - If you don’t specify a value for the topicArn parameter, Must specify a value for the targetArn parameters. -

- `“arn:aws:sns:us-east-2:123456789012:my-topic”` -

-
**targetArn**OptionalString - If you don’t specify a value for the topicArn parameter, Must specify a value for the targetArn parameters. -

- `"arn:aws:sns:us-east-2:123456789012:MySNSTopic"` -

-
**subject**OptionalString`"Workflow Update"`
**MessageStructure**OptionalString`MessageStructure`
**messageAttributes**OptionalMap - ```json - { - 'string': { - 'DataType': 'string', - 'StringValue': 'string', - 'BinaryValue': b'bytes' - } - }, - ``` -
**messageDeduplicationId**OptionalString`“abc123deduplicationId5678”`
**messageGroupId**OptionalString`“order-processing-group-2023_A”`
- - - - - - - - - - - - - - - - - - -
Input FieldTypeExample
PhoneNumberStringWe do not include PhoneNumber as it is considered Personally Identifiable Information (PII).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - `[{"success":true,"response":{"MessageId":"2333ededwedwed-52f5-a716-e10355e3e2ff"}}]` -

- Response syntax can be referred to sns-publish- Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sns/client/publish.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`[{"errorMessage":"An error occurred (InvalidParameter) when calling the Publish operation: Invalid parameter: TopicArn or TargetArn Reason: no value for required parameter","success":false,"response":null}]`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: sns-publish-test - description: Publishes a notification to an SNS topic - workflowInputs: - arnRole: - type: String - steps: - - name: aws_sns_publish_1 - type: action - action: aws.sns.publish - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-east-1 - topicArn: arn:aws:sns:us-east-1:123456789012:workflow-test-topic - subject: "Workflow Update" - message: "The data processing workflow has completed successfully." - next: end - ``` -
- - - - - - -## SQS actions - - - - - Sends a message to a specified Amazon SQS queue. - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**queueUrl**RequiredString"`https://sqs.us-east-2.amazonaws.com/123456789012/my-queue`"
**messageBody**RequiredString`“This is a test message”`
**messageDeduplicationId**OptionalString`“abc123deduplicationId5678”`
**messageGroupId**OptionalString`“group1”`
**messageAttributes**OptionalMap -

- `{ "my_attribute_name_1": { "DataType": "String", "StringValue":"my_attribute_value_1"},` -

- -

- `"my_attribute_name_2": { "DataType": "String", "StringValue":"my_attribute_value_2"}}` -

-
**delaySeconds**OptionalInt`123`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - `{"statusCode":200, "payload":{"status":"success","data":{"MessageId":"e9b73a52-d018-4a73-9fcd-8efb682fba43","MD5OfMessageBody":"fae535c7f7c5687a1c3d8bc52288e33a","MD5OfMessageAttributes":"3ae3c4f59958e031d0d53af2d157e834", }, "message":"Message sent successfully to the SQS queue." }}` -

- Response syntax can be referred to [SQS send_message - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/send_message.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "SQS.Client.exceptions.QueueDoesNotExist: "The specified queue does not exist.""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: sqs-send-message-test - description: Sends a message to an SQS queue - workflowInputs: - arnRole: - type: String - steps: - - name: aws_sqs_sendMessage_1 - type: action - action: aws.sqs.sendMessage - version: '1' - inputs: - awsRoleArn: ${{ .workflowInputs.arnRole }} - region: us-east-2 - queueUrl: https://sqs.us-east-2.amazonaws.com/123456789012/workflow-test-queue - messageBody: "This is a test message" - messageAttributes: - my_attribute_name_1: - DataType: "String" - StringValue: "my_attribute_value_1" - my_attribute_name_2: - DataType: "String" - StringValue: "my_attribute_value_2" - next: end - ``` -
- - - - - - - - - - Retrieves one or more messages, from the specified queue - - - - - Inputs - - - Outputs - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**queueUrl**RequiredString"`https://sqs.us-east-2.amazonaws.com/123456789012/my-queue`"
**maxNumberOfMessages**OptionalInt`10`
**waitTimeSeconds**OptionalInt`5`
**VisibilityTimeout**OptionalInt`123`
**AttributeNames**OptionalList - ```yaml - [ - 'All'|'Policy'|'VisibilityTimeout'|'MaximumMessageSize'|'MessageRetentionPeriod'|'ApproximateNumberOfMessages'|'ApproximateNumberOfMessagesNotVisible'|'CreatedTimestamp'|'LastModifiedTimestamp'|'QueueArn'|'ApproximateNumberOfMessagesDelayed'|'DelaySeconds'|'ReceiveMessageWaitTimeSeconds'|'RedrivePolicy'|'FifoQueue'|'ContentBasedDeduplication'|'KmsMasterKeyId'|'KmsDataKeyReusePeriodSeconds'|'DeduplicationScope'|'FifoThroughputLimit'|'RedriveAllowPolicy'|'SqsManagedSseEnabled', - ] - ``` -
**messageAttributeNames**OptionalList - ```yaml - [ - 'message_attribute_name', - ], - ``` -
**messageSystemAttributeNames**OptionalList`['SenderId', 'SentTimestamp']`
**receiveRequestAttemptId**OptionalString`“req-1234abcd”`
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**response**object - `{"response": }
` -

- Response syntax can be referred to receive_message - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/receive_message.html) -

-
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "SQS.Client.exceptions.QueueDoesNotExist: "The specified queue does not exist.""`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: sqs-receive-message-test - description: 'Receives a message from an SQS queue' - steps: - - name: aws_sqs_receiveMessage_1 - type: action - action: aws.sqs.receiveMessage - version: '1' - inputs: - awsRoleArn: ${{ :secrets:awsRoleArn }} - region: us-east-1 - queueUrl: https://sqs.us-east-1.amazonaws.com/123456789012/workflow-test-queue - waitTimeSeconds: 5 - maxNumberOfMessages: 10 - messageAttributeNames: ['message_attribute_name'], - ``` -
- - - - - \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch.mdx new file mode 100644 index 00000000000..fc04b7d4b67 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch.mdx @@ -0,0 +1,419 @@ +--- +title: "AWS CloudWatch actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS CloudWatch actions +metaDescription: "A list of available aws cloudwatch actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws cloudwatch actions available in the workflow automation actions catalog. These actions enable you to cloudwatch logs operations. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + + This action retrieves a batch of log events from a specified log stream in AWS CloudWatch Logs. It's essential for monitoring, auditing, and troubleshooting applications by programmatically fetching log data. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**logStreamName**RequiredString`"2023/10/27/[$LATEST]abcdef123456"`
**logGroupName**OptionalString`"/aws/lambda/my-function"`
**logGroupIdentifier**OptionalString`“arn:partition:service:region:account-id:resource”`
**startTime**OptionalInt`1759296000000`
**endTime**OptionalInt`1759296000000`
**limit**OptionalInt`50`
**startFromHead**OptionalBoolean`true`
**unmask**OptionalBoolean`false`
**nextToken**OptionalString`“f/39218833627378687642013305455131706539523449361490509828/s”`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + { + 'events': [ + { + 'timestamp': 123, + 'message': 'string', + 'ingestionTime': 123 + }, + ], + 'nextForwardToken': 'string', + 'nextBackwardToken': 'string' +} + ``` +
**success**Boolean`success: true | false`
**errorMessage**String`“An error occurred (ExpiredTokenException) when calling the GetLogEvents operation: The security token included in the request is expired”`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: get-lambda-logs + description: 'Retrieve log events from an AWS Lambda function' + workflowInputs: + region: + type: String + defaultValue: us-east-2 + logGroupName: + type: String + defaultValue: /aws/lambda/my-function + logStreamName: + type: String + defaultValue: 2023/10/27/[$LATEST]abcdef123456 + steps: + name: get_events_step + type: action + action: aws.cloudwatch.get_log_events + version: '1' + inputs: + region: ${{ .workflowInputs.region }} + logGroupName: ${{ .workflowInputs.logGroupName }} + logStreamName: ${{ .workflowInputs.logStreamName }} + limit: 100 + ``` +
+ + + + + + + + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**logGroupName**RequiredString`"/aws/lambda/hello-you"`
**logStreamName**RequiredString`"2025/09/24/[$LATEST]09f7ca9e9ab044f389419ce60305f594"`
**logEvents**RequiredList + ```yaml + [ + +{ "timestamp": 1698384000000, "message": "Workflow task started." }, + + { "timestamp": 1698384000015, "message": "Data validated successfully." } ] + ``` +
**entity**OptionalDict`{ "entity": { "keyAttributes": { "ResourceType": "AWS::ElasticLoadBalancingV2::LoadBalancer", "Identifier": "app/my-web-lb/12345", "Environment": "Production" }, "attributes": { "MonitoringTier": "Gold", "OwnerTeam": "Networking", "MaintenanceWindow": "Sat: 0200-0400" } } }`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + ```yaml + { + 'events': [ + { + 'timestamp': 123, + 'message': 'string', + 'ingestionTime': 123 + }, + ], + 'nextForwardToken': 'string', + 'nextBackwardToken': 'string' + } +``` +
**success**Boolean`success: true | false`
**errorMessage**String`“An error occurred (ExpiredTokenException) when calling the GetLogEvents operation: The security token included in the request is expired”`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: get-lambda-logs + description: 'Retrieve log events from an AWS Lambda function' + workflowInputs: + region: + type: String + defaultValue: us-east-2 + logGroupName: + type: String + defaultValue: /aws/lambda/my-function + logStreamName: + type: String + defaultValue: 2023/10/27/[$LATEST]abcdef123456 + steps: + name: get_events_step + type: action + action: aws.cloudwatch.get_log_events + version: '1' + inputs: + region: ${{ .workflowInputs.region }} + logGroupName: ${{ .workflowInputs.logGroupName }} + logStreamName: ${{ .workflowInputs.logStreamName }} + limit: 100 + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2.mdx new file mode 100644 index 00000000000..69c55e0f43b --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2.mdx @@ -0,0 +1,1461 @@ +--- +title: "AWS EC2 actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS EC2 actions +metaDescription: "A list of available aws ec2 actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws ec2 actions available in the workflow automation actions catalog. These actions enable you to ec2 instance and snapshot management. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + + + Launches the specified number of instances using an AMI for which you have permissions. + + You can specify a number of options, or leave the default options. The following rules apply: + - If you don't specify a subnet ID, we choose a default subnet from your default VPC for you. If you don't have a default VPC, you must specify a subnet ID in the request. + - If any of the AMIs have a product code attached for which the user has not subscribed, the request fails. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**imageId**RequiredString`"ami-0ca4d5db4872d0c28"`
**instanceType**RequiredString`"t2.micro"`
**minCount**RequiredInt`1`
**maxCount**RequiredInt`10`
**parameters**OptionalMap + ```yaml + { + "EbsOptimized": false, + "TagSpecifications": [ + { + "ResourceType": "instance", + "Tags": [ + { + "Key": "Name", + "Value": "My-Web-Server" + } + ] + } + } + ``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object +

+ Response syntax can be referred: [run_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/run_instances.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: ""`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: ec2_run_instance + workflowInputs: + arnRole: + type: String + required: true + steps: + - name: RunInstance + type: action + action: aws.ec2.runInstances + version: '1' + inputs: + awsRoleArn: ${{.workflowInputs.arnRole}} + region: us-east-2 + imageId: ami-0ca4d5db4872d0c28 + instanceType: t2.micro + minCount: 1 + maxCount: 1 + parameters: + EbsOptimized: false + TagSpecifications: + - ResourceType: instance + Tags: + - Key: Name + Value: My-Test-Instance + selectors: + - name: instanceId + expression: .response.Instances[0].InstanceId + ``` +
+ + + + + + + + Describes the specified instances or all instances. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**OptionalList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**filters**OptionalList`"[{\"Name\": \"instance-state-name\", \"Values\": [\"running\"]}]"`
**nextToken**OptionalString`“abcdefgh“`
**maxResults**OptionalInt100
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + In action input at least one of the AWS credentials (short, long, role) should be provided, where role take precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + {"response": + + }} + ``` +

+ Response syntax can be referred [describe_instances](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/describe_instances.html). +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "The parameter instancesSet cannot be used with the parameter maxResults"`
+ + + - If you specify instance IDs, the output includes information for only the specified instances. + - If you specify filters, the output includes information for only those instances that meet the filter criteria. + - If you do not specify instance IDs or filters, the output includes information for all instances. + - The parameter `instanceIds` cannot be used with `maxResults`. + + + + + + + + + + + + + + + +
Workflow Example
+ ```yaml + name: ab-ec2-describe-test + description: '' + workflowInputs: + arnRole: + type: String + steps: + - name: aws_ec2_describeInstances_1 + type: action + action: aws.ec2.describeInstances + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-east-2 + instanceIds: + - i-123456789abcdef0 + next: end + ``` +
+ + + + + + + + Starts an Amazon EBS-backed instance that you previously stopped. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + {"response":{ + 'StartingInstances': [ + { + 'InstanceId': 'String', + 'CurrentState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + }, + 'PreviousState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + } + }, + ] + } + + } + + } + ``` +

+ Response syntax can be referred [start_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/start_instances.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "The parameter instancesSet cannot be used with the parameter maxResults"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: ab-ec2-startInstance-test + description: '' + workflowInputs: + arnRole: + type: String + region: + type: String + defaultValue: us-west-2 + instanceIds: + type: list + defaultValue: ["i-123456789abcdef0"] + steps: + - name: aws_ec2_startInstances_1 + type: action + action: aws.ec2.startInstances + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: ${{ .workflowInputs.region }} + instanceIds: ${{ .workflowInputs.instanceIds }} + next: end + ``` +
+ + + + + + + + Stops an Amazon EBS-backed instance + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**hibernate**OptionalBooleantrue or false (Default: `false`)
**force**OptionalBooleantrue or false (Default: `false`)
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + { + 'StoppingInstances': [ + { + 'InstanceId': 'string', + 'CurrentState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + }, + 'PreviousState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + } + }, + ] + } + ``` +

+ Response syntax can be referred [stop_instances](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/stop_instances.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (InvalidInstanceID.Malformed) when calling the StopInstances operation: The instance ID 'i-123456789' is malformed"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: ec2_stop_instance + description: '' + workflowInputs: + arnRole: + type: String + region: + type: String + defaultValue: us-west-2 + instanceIds: + type: list + defaultValue: ["i-123456789abcdef0"] + steps: + - name: aws_stop_instances_1 + type: action + action: aws.ec2.stopInstances + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: ${{ .workflowInputs.region }} + instanceIds: ${{ .workflowInputs.instanceIds }} + next: end + ``` +
+ + + + + + + + Requests a reboot of the specified instances. This operation is asynchronous; it only queues a request to reboot the specified instances. The operation succeeds if the instances are valid and belong to you. Requests to reboot terminated instances are ignored. + + If an instance does not cleanly shut down within a few minutes, Amazon EC2 performs a hard reboot. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object[reboot_instances - Boto3 1.40.56 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/reboot_instances.html)
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: ""`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: reboot-ec2-test + description: '' + workflowInputs: + arnRole: + type: String + region: + type: String + defaultValue: us-west-2 + instanceIds: + type: List + defaultValue: ["i-123456789abcdef0"] + steps: + - name: aws_ec2_rebootInstances_1 + type: action + action: aws.ec2.rebootInstances + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: ${{ .workflowInputs.region }} + instanceIds: ${{ .workflowInputs.instanceIds }} + next: end + ``` +
+ + + + + + + + Terminates the specified instances. This operation is [idempotent](https://docs.aws.amazon.com/ec2/latest/devguide/ec2-api-idempotency.html); if you terminate an instance more than once, each call succeeds. + + If you specify multiple instances and the request fails (for example, because of a single incorrect instance ID), none of the instances are terminated. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**instanceIds**RequiredList`"[\"i-0123456789abcdef0\", \"i-0fedcba9876543210\"]"`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + In the action input, at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + { + 'TerminatingInstances': [ + { + 'InstanceId': 'String', + 'CurrentState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + }, + 'PreviousState': { + 'Code': 123, + 'Name': 'pending'|'running'|'shutting-down'|'terminated'|'stopping'|'stopped' + } + }, + ] + } + ``` +

+ Response syntax can be referred [terminate_instances - Boto3 1.40.50 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/terminate_instances.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (`InvalidInstanceID.Malformed`) when calling the TerminateInstances operation: The instance ID 'i-012345678' is malformed"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: ec2-terminate-test + description: '' + workflowInputs: + arnRole: + type: String + region: + type: String + defaultValue: us-west-2 + instanceIds: + type: list + defaultValue: ["i-123456789abcdef0"] + steps: + - name: aws_ec2_terminateInstances_1 + type: action + action: aws.ec2.terminateInstances + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: ${{ .workflowInputs.region }} + instanceIds: ${{ .workflowInputs.instanceIds }} + next: end + ``` +
+ + + + + + + + Creates a snapshot of an EBS volume and stores it in Amazon S3. You can use snapshots for backups, to make copies of EBS volumes, and save data before shutting down an instance. + + The location of the source EBS volume determines where you can create the snapshot. + + + + + Inputs + + + + Outputs + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**description**OptionalString"This is a test snapshot"
**outpostArn**OptionalString`“arn:aws:ec2:us-east-1:123456789012:outpost/op-1a2b3c4d5e6f7g8h9”`
**volumeId**RequiredString“`vol-0123456789abcdef0`“
**tagSpecifications**OptionalList`[{"ResourceType":"snapshot","Tags":[{"Key":"testKey","Value":"testValue"}]}]`
**location**OptionalString`“regional”`
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + Input at least one of the AWS credentials (short, long, role) should be provided, where role take precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + ```yaml + { + 'OwnerAlias': 'string', + 'OutpostArn': 'string', + 'Tags': [ + { + 'Key': 'string', + 'Value': 'string' + }, + ], + 'StorageTier': 'archive'|'standard', + 'RestoreExpiryTime': datetime(2015, 1, 1), + 'SseType': 'sse-ebs'|'sse-kms'|'none', + 'AvailabilityZone': 'string', + 'TransferType': 'time-based'|'standard', + 'CompletionDurationMinutes': 123, + 'CompletionTime': datetime(2015, 1, 1), + 'FullSnapshotSizeInBytes': 123, + 'SnapshotId': 'string', + 'VolumeId': 'string', + 'State': 'pending'|'completed'|'error'|'recoverable'|'recovering', + 'StateMessage': 'string', + 'StartTime': datetime(2015, 1, 1), + 'Progress': 'string', + 'OwnerId': 'string', + 'Description': 'string', + 'VolumeSize': 123, + 'Encrypted': True|False, + 'KmsKeyId': 'string', + 'DataEncryptionKeyId': 'string' + } + ``` +

+ Response syntax can be referred [create_snapshot](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/create_snapshot.html). +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "The parameter instancesSet cannot be used with the parameter maxResults"`
+ + + + + + + + Deletes an Amazon EC2 snapshot. + + You cannot delete a snapshot of the root device of an EBS volume used by a registered AMI. You must first deregister the AMI before you can delete the snapshot. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**snapshotId**RequiredString`“snapshot-id-1"`
**selectors**OptionalString`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + Input at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object + No Response in case of `success : true` +

+ Response syntax can be referred [delete_snapshot - Boto3 1.40.55 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2/client/delete_snapshot.html). +

+
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Failed to delete snapshot"`
+ + + + + + + + + + + + + + +
Workflow Example
+ ```yaml + name: ec2-deleteSnapshot-test + description: '' + workflowInputs: + arnRole: + type: String + region: + type: String + defaultValue: us-west-2 + snapshotId: + type: List + defaultValue: snapshot-id-1 + steps: + - name: aws_ec2_deleteSnapshot_1 + type: action + action: aws.ec2.deleteSnapshot + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: ${{ .workflowInputs.region }} + snapshotId: ${{ .workflowInputs.snapshotId }} + next: end + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api.mdx new file mode 100644 index 00000000000..8eaa417a171 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api.mdx @@ -0,0 +1,327 @@ +--- +title: "AWS Execute API" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS Execute API +metaDescription: "A list of available aws execute api in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws execute api available in the workflow automation actions catalog. These actions enable you to execute any aws api operation. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + +## Security and IAM configuration + + To use this action, you must configure AWS credentials. See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for detailed instructions on creating an IAM role or IAM user. + + + **Security best practice:** When defining IAM policies for this action, always use least-privilege access. Grant only the specific AWS API actions your workflow requires, and restrict permissions to specific resources rather than using wildcards. + + +## Required IAM permissions + + The permissions you need depend on which AWS services and APIs your workflow calls. Use the examples below as templates for creating least-privilege policies. + + **Example 1: Send messages to a specific SQS queue** + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": "sqs:SendMessage", + "Resource": "arn:aws:sqs:us-west-2::" + } + ] + } + ``` + + **Examples 2: Query a specific DynamoDB table** + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": "dynamodb:Query", + "Resource": "arn:aws:dynamodb:us-west-2::table/" + } + ] + } + ``` + + **Example 3: Multiple services with specific permissions** + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": "sqs:SendMessage", + "Resource": "arn:aws:sqs:us-west-2::" + }, + { + "Effect": "Allow", + "Action": "dynamodb:Query", + "Resource": "arn:aws:dynamodb:us-west-2::table/" + } + ] + } + ``` + + + - Replace ``, ``, and `` with your actual values + - Find available AWS service APIs in the [Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html) + - For more complex IAM policy patterns, see the [AWS IAM documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) + + + For more information on how this action works, see the [AWS Systems Manager executeAwsApi documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-action-executeAwsApi.html). + +## Call an AWS API [#aws-execute-api] + + Execute any AWS API operation for a specified service. It supports providing AWS credentials, region, service name, API name, and optional parameters. The action can return outputs such as success status, response data, and error messages, making it versatile for interacting with AWS services programmatically. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**service**RequiredString`service: "sqs"`.[AWS available services](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html)
**api**RequiredString`api: "create_queue"`
**parameters**RequiredMap +

+ ```yaml + parameters: { + "QueueName": "dks-testing-queue", + "Attributes": { + "DelaySeconds": "0", + "MessageRetentionPeriod": "86400" + } +} + ``` +

+
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**Object`{"response":}` - each service and api have different response, for example see the [DynamoDB Query response](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/client/query.html).
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "User does not have permission to query DynamoDB"`
+ + + - Input at least one of the AWS credentials (short, long, role) should be provided, where the role takes precedence over the others. + - In the action input, if `awsAccessKeyId` and `awsSecretAccessKey` are to be provided, make sure they are static credentials of an IAM user. + - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to the action input. + - Refer to [AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for instructions. + - Use selectors to get only the specified parameters as output. + + + + + + ### Example: Query a DynamoDB table + + This example demonstrates how to query a DynamoDB table using the `aws.execute.api` action with session credentials. + + ```yaml + name: aws_execute_api_dynamoDB_dks + + workflowInputs: + key: + type: String + defaultValue: "${{ :secrets: }}" + access: + type: String + defaultValue: "${{ :secrets: }}" + region: + type: String + defaultValue: us-east-2 + tableName: + type: String + defaultValue: workflow-definitions-dev + scopedName: + type: String + version: + type: String + defaultValue: "1" + + steps: + - name: executeApi + type: action + action: aws.execute.api + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + service: dynamodb + api: query + parameters: + TableName: ${{ .workflowInputs.tableName }} + KeyConditionExpression: "ScopedName = :scopedNameValue AND Version = :VersionValue" + ExpressionAttributeValues: + ":scopedNameValue": + S: ${{ .workflowInputs.scopedName }} + ":VersionValue": + N: ${{ .workflowInputs.version }} + selectors: + - name: response + expression: '.response' + - name: errorMessage + expression: '.errorMessage' + - name: success + expression: '.success' + + + - name: wait + type: wait + seconds: 2 + + - name: logOutput + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: 'The execute API message output is:${{ .steps.executeApi.outputs.response.Item }}' + licenseKey: '${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }}' + - name: logOutput1 + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: 'does execute API have any error :${{ .steps.executeApi.outputs.errorMessage }}' + licenseKey: '${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }}' + - name: logOutput2 + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: 'is execute successful :${{ .steps.executeApi.outputs.success }}' + licenseKey: '${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }}' + ``` + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda.mdx new file mode 100644 index 00000000000..36ff17b2ad5 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda.mdx @@ -0,0 +1,841 @@ +--- +title: "AWS Lambda actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS Lambda actions +metaDescription: "A list of available AWS Lambda actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for AWS Lambda actions available in the workflow automation actions catalog. These actions enable you to manage and invoke Lambda functions as part of your workflow definitions. + +## Prerequisites + +Before using AWS Lambda actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for Lambda operations. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + +## Lambda actions + + + + Invokes a Lambda function synchronously or asynchronously with an optional payload. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`functionName: "hello-you"`
**payload**OptionalMap + `payload: user: R2-D2` +
**selectors**OptionalList`[{\"name\": \"payload\", \"expression\": \".payload\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**payload**Map + ```yaml + { + statusCode=200.0, + body=\"Hello R2-D2!\" + } + ``` +
**statusCode**Int`statusCode: 200`
**executedVersion**String`executedVersion: "$LATEST"`
**functionError**String`functionError: "Unhandled::Error occurred"`
**success**Boolean`Status of the request`
**errorMessage**String`Failure reason as message`
+ + + - In action input at least one of the AWS Credentials (short, long, role) should be provided, where role take precedence over the others. + - In action input, if `awsAccessKeyId` and `awsSecretAccessKey` are to be provided make sure they are static credentials of an IAM user. + - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to action input. + - The credential owner must have the `lambda:InvokeFunction` IAM permission to invoke the lambda function passed in the action input. + - The selectors to get the only specified parameters as output. + + + + + + + + + + + + + + + + + + + + + +
Workflow definitionInputsOutputsOutputs when selectors are provided
+ ```yaml + name: LambdaTest + + workflowInputs: + region: + type: String + functionName: + type: String + payload: + type: Map + defaultValue: {} + + steps: + - name: awsLambda + type: action + action: aws.lambda.invoke + version: 1 + inputs: + region: ${{ .workflowInputs.region }} + functionName: ${{ .workflowInputs.functionName }} + awsAccessKeyId: ${{ :secrets:awsAccessKeyId }} + awsSecretAccessKey: ${{ :secrets:awsSecretAccessKey }} + awsSessionToken: ${{ :secrets:awsSessionToken }} + payload: ${{ .workflowInputs.payload }} + selectors: ${{ .workflowInputs.selectors }} + + - name: logOutput + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: 'The lambda function message output is:${{ .steps.awsLambda.outputs.payload.body }}' + licenseKey: '${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }}' + ``` + + ```yaml + { + "inputs": [ + { + "key": "region" + "value": "\"us-east-2\"" + }, + { + "key": "functionName" + "value": "\"hello-you\"" + }, + { + "key": "payload" + "value": "{\"user\":\"R2-D2\"}" + }, + { + "key": "selectors" + "value": "[{\"name\": \"payload\", \"expression\": \".payload\"}]" + } + ] + } + ``` + + ```yaml + Success case: + { + success: true + executedVersion=$LATEST, + statusCode=200, + payload={ + statusCode=200.0, + body=\"Hello R2-D2\" + } + } + + Failure case: + { + "errorMessage": "Invalid format", + "success": false + } + ``` + + ```yaml + { + payload={ + statusCode=200.0, + body=\"Hello R2-D2\" + } + } + ``` +
+ + + + + + + + Modifies the configuration of a specific AWS Lambda function. Provide only the parameters you want to change. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`"my-lambda-function-to-update"`
**role**OptionalString`arn:aws:iam::123456789012:role/new-lambda-role`
**handler**OptionalString`"main.new_handler"`
**description**OptionalString`Updated function description`
**parameters**OptionalMap + ```yaml + { + "Timeout": "60", + "MemorySize": 123, + }, + ``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + ```yaml + [{"success":true,"response":{"FunctionName":"hello-you","FunctionArn":"arn:aws:lambda:us-east-2:----:function:hello-you","Runtime":"nodejs20.x","Role":"arn:aws:iam::----:role/TF-hello-you-role","Handler":"hello-you.handler","CodeSize":334,"Description":"This is hello you description from action","Timeout":30,"MemorySize":128,"LastModified":"2025-09-23T13:57:03.000+0000","CodeSha256":"CU03aDDg+34=","Version":"$LATEST","TracingConfig":{"Mode":"PassThrough"},"RevisionId":"0f1e4d9b-c45a-4896-a32d-7cd78e77a273","State":"Active","LastUpdateStatus":"InProgress","LastUpdateStatusReason":"The function is being created.","LastUpdateStatusReasonCode":"Creating","PackageType":"Zip","Architectures":["x86_64"],"EphemeralStorage":{"Size":512},"SnapStart":{"ApplyOn":"None","OptimizationStatus":"Off"},"RuntimeVersionConfig":{"RuntimeVersionArn":"arn:aws:lambda:us-east-2::runtime:01eab27397bfdbdc243d363698d4bc355e3c8176d34a51cd47dfe58cf977f508"},"LoggingConfig":{"LogFormat":"Text","LogGroup":"/aws/lambda/hello-you"}}}] + ``` +

+ Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/update_function_configuration.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`[ { "errorMessage": "An error occurred (ResourceNotFoundException) when calling the UpdateFunctionConfiguration operation: Function not found: arn:aws:lambda:us-east-2:661945836867:function:my-lambda-function-to-update", "success": false, "response": null } ]`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: lambda-update-config-test + description: 'Updates the timeout and memory of a Lambda function' + workflowInputs: + arnRole: + type: String + steps: + - name: aws_lambda_update_function_configuration_1 + type: action + action: aws.lambda.updateFunctionConfiguration + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-west-2 + functionName: my-lambda-function-to-update + parameters: + Timeout:60 + MemorySize:123 + + next: end + ``` +
+ + + + + + + + Retrieves the configuration details, code location, and other metadata for a specific AWS Lambda function. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`"my-lambda-function"`
**parameters**OptionalMap + ```yaml + { + "Qualifier": "1" + }, + ``` +
**selectors**OptionalList`[[{"name": "response", "expression": ".response"}]`
+ + + To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + ```yaml + {"response": } + ``` +

+ Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/get_function.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "ResourceNotFoundException: Function not found"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: lambda-get-function-test + description: 'Retrieves the configuration of a specific Lambda function' + workflowInputs: + arnRole: + type: String + steps: + - name: aws_lambda_getFunction_1 + type: action + action: aws.lambda.getFunction + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-east-1 + FunctionName: hello-you + parameters: + Qualifier: 1 + next: end + ``` +
+ + + + + + + Returns a list of aliases for a specific AWS Lambda function. Aliases are pointers to function versions. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**functionName**RequiredString`"my-lambda-function"`
**marker**OptionalString + Pass the `NextMarker` token from a previous response for pagination. +

+ e.g., `"abcd....."` +

+
**maxItems**OptionalInt + Limit the number of aliases returned +

+ e.g., `123` +

+
**parameters**OptionalMap + For additional optional API parameters. +

+ e.g., `{"AnotherOptionalParam": "value"}` +

+
**selectors**OptionalList`[{"name": "response", "expression": ".response"}]`
+ + + - **Pagination**: Use the `Marker` and `MaxItems` inputs to paginate through a large number of aliases. + - To support a wide range of inputs, the `parameters` map accepts any optional argument available. This allows you to dynamically construct requests by adding multiple fields. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + ```yaml + {"response": } + ``` +

+ Response syntax can be referred to [update_function_configuration - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/list_aliases.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "ResourceNotFoundException: Function not found"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: lambda-list-aliases-test + description: 'Lists all aliases for a Lambda function' + workflowInputs: + arnRole: + type: String + steps: + - name: aws_lambda_list_aliases_1 + type: action + action: aws.lambda.listAliases + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-east-1 + functionName: hello-you + parameters: + FunctionVersion: 1 + next: end + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3.mdx new file mode 100644 index 00000000000..8ce3685ab11 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3.mdx @@ -0,0 +1,1227 @@ +--- +title: "AWS S3 actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS S3 actions +metaDescription: "A list of available aws s3 actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws s3 actions available in the workflow automation actions catalog. These actions enable you to s3 bucket and object operations. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + + The `listObjectsV2` method returns some or all (up to 1,000) of the objects in a bucket. It is a more modern and recommended version of `list_objects`. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**prefix**OptionalString"`path/to/folder/`"
**maxKeys**OptionalInteger`100`
**continuationToken**OptionalString`some-token`
**parameters**OptionalMap + ```graphql + { + "Delimiter": "/" + } + ``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldType
EncodingTypeString
FetchOwnerBoolean
StartAfterString
RequestPayerString
ExpectedBucketOwnerString
OptionalObjectAttributesList
DelimiterString
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + + + ```yaml + { + 'IsTruncated': True|False, + 'Contents': [ + { + 'Key': 'string', + 'LastModified': datetime(2015, 1, 1), + 'ETag': 'string', + 'ChecksumAlgorithm': [ + 'CRC32'|'CRC32C'|'SHA1'|'SHA256'|'CRC64NVME', + ], + 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', + 'Size': 123, + 'StorageClass': 'STANDARD'|'REDUCED_REDUNDANCY'|'GLACIER'|'STANDARD_IA'|'ONEZONE_IA'|'INTELLIGENT_TIERING'|'DEEP_ARCHIVE'|'OUTPOSTS'|'GLACIER_IR'|'SNOW'|'EXPRESS_ONEZONE'|'FSX_OPENZFS', + 'Owner': { + 'DisplayName': 'string', + 'ID': 'string' + }, + 'RestoreStatus': { + 'IsRestoreInProgress': True|False, + 'RestoreExpiryDate': datetime(2015, 1, 1) + } + }, + ], + 'Name': 'string', + 'Prefix': 'string', + 'Delimiter': 'string', + 'MaxKeys': 123, + 'CommonPrefixes': [ + { + 'Prefix': 'string' + }, + ], + 'EncodingType': 'url', + 'KeyCount': 123, + 'ContinuationToken': 'string', + 'NextContinuationToken': 'string', + 'StartAfter': 'string', + 'RequestCharged': 'requester' + } + ``` +

+ Response syntax can be referred to in the [list_objects_v2 - Boto3 1.40.52 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/list_objects_v2.html) +

+ + +
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Parameter validation failed:\nInvalid bucket name \"s3-activity-test \": Bucket name must match the regex \"^[a-zA-Z0-9.\\-_]{1,255}$\" or be an ARN matching the regex \"^arn:(aws).:(s3|s3-object-lambda):[a-z\\-0-9]:[0-9]{12}:accesspoint[/:][a-zA-Z0-9\\-.]{1,63}$|^arn:(aws).*:s3-outposts:[a-z\\-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9\\-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9\\-]{1,63}$\""`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: aws-s3-list-objects-v2 + description: 'List Objects in an AWS S3 Bucket' + + steps: + - name: aws_s3_listObjectsV2_1 + type: action + action: aws.s3.listObjectsV2 + version: '1' + inputs: + awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" + region: "us-east-2" + bucket: "examplebucket" + prefix: "path/to/folder/" + maxKeys: 100 + continuationToken: "some-token" + next: end + ``` +
+ + + + + + + + The `deleteObject` method permanently removes a single object from a bucket. For versioned buckets, this operation inserts a **delete marker**, which hides the object without permanently deleting it unless a `VersionId` is specified. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**parameters**OptionalMap + ```yaml + { + "RequestPayer": "test", + "BypassGovernanceRetention": false + "VersionId":"testVersion", + "MFA":"Test" + } + ``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldType
RequestPayerString
BypassGovernanceRetentionBoolean
ExpectedBucketOwnerString
IfMatchString
IfMatchLastModifiedTimeMap
IfMatchSizeInt
VersionIdString
MFAString
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + + + ```yaml + { + 'DeleteMarker': True|False, + 'VersionId': 'string', + 'RequestCharged': 'requester' + } + ``` +

+ Response syntax can be referred [delete_object - Boto3 1.40.55 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/delete_object.html) +

+ + +
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "Parameter validation failed:\nInvalid bucket name \"s3-activity-test \": Bucket name must match the regex \"^[a-zA-Z0-9.\\-_]{1,255}$\" or be an ARN matching the regex \"^arn:(aws).:(s3|s3-object-lambda):[a-z\\-0-9]:[0-9]{12}:accesspoint[/:][a-zA-Z0-9\\-.]{1,63}$|^arn:(aws).*:s3-outposts:[a-z\\-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9\\-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9\\-]{1,63}$\""`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: aws-s3-delete-object + description: 'Delete an AWS S3 Object' + + steps: + - name: aws_s3_deleteObject_1 + type: action + action: aws.s3.deleteObject + version: '1' + inputs: + awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" + region: "us-west-2" + bucket: "my-bucket" + key: "path/to/object.txt" + next: end + ``` +
+ + + + + + + + Adds an object to a bucket. Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**body**RequiredString`file content`
**contentType**RequiredString"`plain/text`"
**tagging**OptionalString`“key1=value1"`
**parameters**OptionalMap + ```yaml + { + "ServerSideEncryption": "AES256", + "Metadata": { + 'metadata1': 'value1', + 'metadata2': 'value2', + } + } + ``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldType
RequestPayerString
ACLString
CacheControlString
ContentDispositionString
ContentEncodingString
ContentLanguageString
ContentLengthInt
ContentMD5String
ChecksumAlgorithmString
ChecksumCRC32String
ChecksumCRC32CString
ChecksumCRC64NVMEString
ChecksumSHA1String
ChecksumSHA256String
ExpiresMap
IfMatchString
IfNoneMatchString
GrantFullControlString
GrantReadString
GrantReadACPString
GrantWriteACPString
WriteOffsetBytesInt
ServerSideEncryptionString
StorageClassString
WebsiteRedirectLocationString
SSECustomerAlgorithmString
SSECustomerKeyString
SSEKMSKeyIdString
SSEKMSEncryptionContextString
BucketKeyEnabledBoolean
RequestPayerString
ObjectLockModeString
ObjectLockRetainUntilDateMap
ObjectLockLegalHoldStatusString
ExpectedBucketOwnerString
MetadataMap
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + + + ```yaml + { + 'Expiration': 'string', + 'ETag': 'string', + 'ChecksumCRC32': 'string', + 'ChecksumCRC32C': 'string', + 'ChecksumCRC64NVME': 'string', + 'ChecksumSHA1': 'string', + 'ChecksumSHA256': 'string', + 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', + 'ServerSideEncryption': 'AES256'|'aws:fsx'|'aws:kms'|'aws:kms:dsse', + 'VersionId': 'string', + 'SSECustomerAlgorithm': 'string', + 'SSECustomerKeyMD5': 'string', + 'SSEKMSKeyId': 'string', + 'SSEKMSEncryptionContext': 'string', + 'BucketKeyEnabled': True|False, + 'Size': 123, + 'RequestCharged': 'requester' + } + ``` +

+ Response syntax can be referred [put_object - Boto3 1.40.59 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/put_object.html) +

+ + +
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: s3-put-object + description: 'Put an AWS S3 Object' + + steps: + - name: aws_s3_putObject_1 + type: action + action: aws.s3.putObject + version: '1' + inputs: + awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" + region: "us-east-2" + bucket: "examplebucket" + key: "path/to/object.txt" + body: "Hello world" + contentType: "plain/text" + tagging: "key1=value1" + next: end + ``` +
+ + + + + + + + In the `GetObject` request, specify the full key name for the object. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**bucket**RequiredString"`examplebucket`"
**key**RequiredString"`path/to/object.txt`"
**versionId**OptionalString`"some-version-id"`
**range**OptionalString`bytes=0-99`
**parameters**OptionalMap +```yaml + { + "ChecksumMode": "ENABLED", + "ExpectedBucketOwner": "test-user" + } +``` +
**selectors**OptionalList`[{\"name\": \"response\", \"expression\": \".response\"}, {\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"errorMessage\", \"expression\": \".errorMessage\"}]`
+ + + The action will fail if the object is more than 100kb. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldType
IfMatchString
IfModifiedSinceMap
IfNoneMatchString
IfUnmodifiedSinceMap
ResponseCacheControlString
ResponseContentDispositionString
ResponseContentEncodingString
ResponseContentLanguageString
ResponseContentTypeString
ResponseExpiresMap
SSECustomerAlgorithmString
SSECustomerKeyString
RequestPayerString
PartNumberInt
ExpectedBucketOwnerString
ChecksumModeString
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + + + ```yaml + { + 'Body': StreamingBody(), + 'DeleteMarker': True|False, + 'AcceptRanges': 'string', + 'Expiration': 'string', + 'Restore': 'string', + 'LastModified': datetime(2015, 1, 1), + 'ContentLength': 123, + 'ETag': 'string', + 'ChecksumCRC32': 'string', + 'ChecksumCRC32C': 'string', + 'ChecksumCRC64NVME': 'string', + 'ChecksumSHA1': 'string', + 'ChecksumSHA256': 'string', + 'ChecksumType': 'COMPOSITE'|'FULL_OBJECT', + 'MissingMeta': 123, + 'VersionId': 'string', + 'CacheControl': 'string', + 'ContentDisposition': 'string', + 'ContentEncoding': 'string', + 'ContentLanguage': 'string', + 'ContentRange': 'string', + 'ContentType': 'string', + 'Expires': datetime(2015, 1, 1), + 'ExpiresString': 'string', + 'WebsiteRedirectLocation': 'string', + 'ServerSideEncryption': 'AES256'|'aws:fsx'|'aws:kms'|'aws:kms:dsse', + 'Metadata': { + 'string': 'string' + }, + 'SSECustomerAlgorithm': 'string', + 'SSECustomerKeyMD5': 'string', + 'SSEKMSKeyId': 'string', + 'BucketKeyEnabled': True|False, + 'StorageClass': 'STANDARD'|'REDUCED_REDUNDANCY'|'STANDARD_IA'|'ONEZONE_IA'|'INTELLIGENT_TIERING'|'GLACIER'|'DEEP_ARCHIVE'|'OUTPOSTS'|'GLACIER_IR'|'SNOW'|'EXPRESS_ONEZONE'|'FSX_OPENZFS', + 'RequestCharged': 'requester', + 'ReplicationStatus': 'COMPLETE'|'PENDING'|'FAILED'|'REPLICA'|'COMPLETED', + 'PartsCount': 123, + 'TagCount': 123, + 'ObjectLockMode': 'GOVERNANCE'|'COMPLIANCE', + 'ObjectLockRetainUntilDate': datetime(2015, 1, 1), + 'ObjectLockLegalHoldStatus': 'ON'|'OFF' + } + ``` +

+ Response syntax can be referred to in the [get_object - Boto3 1.40.59 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/get_object.html) +

+ + +
**success**Boolean`success: true | false`
**errorMessage**String`errorMessage: "An error occurred (InvalidArgument) when calling the GetObject operation: Invalid version id specified"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: s3-get-object + description: 'Get an AWS S3 Object' + + steps: + - name: aws_s3_getObject_1 + type: action + action: aws.s3.getObject + version: '1' + inputs: + awsRoleArn: "arn:aws:iam::123456789012:role/my-workflow-role" + region: "us-east-2" + bucket: "examplebucket" + key: "path/to/object.txt" + next: end + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns.mdx new file mode 100644 index 00000000000..a58ded5ba15 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns.mdx @@ -0,0 +1,267 @@ +--- +title: "AWS SNS actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS SNS actions +metaDescription: "A list of available aws sns actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws sns actions available in the workflow automation actions catalog. These actions enable you to sns topic operations. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + + Sends a message to an Amazon SNS topic. All subscribers to the topic will receive the message. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**message**RequiredString + Messages must be UTF-8 encoded strings and at most 256 KB in size +

+ `'Workflow failed at step 3'` +

+
**topicArn**OptionalString + If you don’t specify a value for the topicArn parameter, Must specify a value for the targetArn parameters. +

+ `“arn:aws:sns:us-east-2:123456789012:my-topic”` +

+
**targetArn**OptionalString + If you don’t specify a value for the topicArn parameter, Must specify a value for the targetArn parameters. +

+ `"arn:aws:sns:us-east-2:123456789012:MySNSTopic"` +

+
**subject**OptionalString`"Workflow Update"`
**MessageStructure**OptionalString`MessageStructure`
**messageAttributes**OptionalMap + ```json + { + 'string': { + 'DataType': 'string', + 'StringValue': 'string', + 'BinaryValue': b'bytes' + } + }, + ``` +
**messageDeduplicationId**OptionalString`“abc123deduplicationId5678”`
**messageGroupId**OptionalString`“order-processing-group-2023_A”`
+ + + + + + + + + + + + + + + + + + +
Input FieldTypeExample
PhoneNumberStringWe do not include PhoneNumber as it is considered Personally Identifiable Information (PII).
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + `[{"success":true,"response":{"MessageId":"2333ededwedwed-52f5-a716-e10355e3e2ff"}}]` +

+ Response syntax can be referred to sns-publish- Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sns/client/publish.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`[{"errorMessage":"An error occurred (InvalidParameter) when calling the Publish operation: Invalid parameter: TopicArn or TargetArn Reason: no value for required parameter","success":false,"response":null}]`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: sns-publish-test + description: Publishes a notification to an SNS topic + workflowInputs: + arnRole: + type: String + steps: + - name: aws_sns_publish_1 + type: action + action: aws.sns.publish + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-east-1 + topicArn: arn:aws:sns:us-east-1:123456789012:workflow-test-topic + subject: "Workflow Update" + message: "The data processing workflow has completed successfully." + next: end + ``` +
+ + + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs.mdx new file mode 100644 index 00000000000..7f0a7b7c9f4 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs.mdx @@ -0,0 +1,416 @@ +--- +title: "AWS SQS actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS SQS actions +metaDescription: "A list of available aws sqs actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws sqs actions available in the workflow automation actions catalog. These actions enable you to sqs queue operations. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + + Sends a message to a specified Amazon SQS queue. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**queueUrl**RequiredString"`https://sqs.us-east-2.amazonaws.com/123456789012/my-queue`"
**messageBody**RequiredString`“This is a test message”`
**messageDeduplicationId**OptionalString`“abc123deduplicationId5678”`
**messageGroupId**OptionalString`“group1”`
**messageAttributes**OptionalMap +

+ `{ "my_attribute_name_1": { "DataType": "String", "StringValue":"my_attribute_value_1"},` +

+ +

+ `"my_attribute_name_2": { "DataType": "String", "StringValue":"my_attribute_value_2"}}` +

+
**delaySeconds**OptionalInt`123`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + `{"statusCode":200, "payload":{"status":"success","data":{"MessageId":"e9b73a52-d018-4a73-9fcd-8efb682fba43","MD5OfMessageBody":"fae535c7f7c5687a1c3d8bc52288e33a","MD5OfMessageAttributes":"3ae3c4f59958e031d0d53af2d157e834", }, "message":"Message sent successfully to the SQS queue." }}` +

+ Response syntax can be referred to [SQS send_message - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/send_message.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "SQS.Client.exceptions.QueueDoesNotExist: "The specified queue does not exist.""`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: sqs-send-message-test + description: Sends a message to an SQS queue + workflowInputs: + arnRole: + type: String + steps: + - name: aws_sqs_sendMessage_1 + type: action + action: aws.sqs.sendMessage + version: '1' + inputs: + awsRoleArn: ${{ .workflowInputs.arnRole }} + region: us-east-2 + queueUrl: https://sqs.us-east-2.amazonaws.com/123456789012/workflow-test-queue + messageBody: "This is a test message" + messageAttributes: + my_attribute_name_1: + DataType: "String" + StringValue: "my_attribute_value_1" + my_attribute_name_2: + DataType: "String" + StringValue: "my_attribute_value_2" + next: end + ``` +
+ + + + + + + + + + Retrieves one or more messages, from the specified queue + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`"us-east-2"`
**queueUrl**RequiredString"`https://sqs.us-east-2.amazonaws.com/123456789012/my-queue`"
**maxNumberOfMessages**OptionalInt`10`
**waitTimeSeconds**OptionalInt`5`
**VisibilityTimeout**OptionalInt`123`
**AttributeNames**OptionalList + ```yaml + [ + 'All'|'Policy'|'VisibilityTimeout'|'MaximumMessageSize'|'MessageRetentionPeriod'|'ApproximateNumberOfMessages'|'ApproximateNumberOfMessagesNotVisible'|'CreatedTimestamp'|'LastModifiedTimestamp'|'QueueArn'|'ApproximateNumberOfMessagesDelayed'|'DelaySeconds'|'ReceiveMessageWaitTimeSeconds'|'RedrivePolicy'|'FifoQueue'|'ContentBasedDeduplication'|'KmsMasterKeyId'|'KmsDataKeyReusePeriodSeconds'|'DeduplicationScope'|'FifoThroughputLimit'|'RedriveAllowPolicy'|'SqsManagedSseEnabled', + ] + ``` +
**messageAttributeNames**OptionalList + ```yaml + [ + 'message_attribute_name', + ], + ``` +
**messageSystemAttributeNames**OptionalList`['SenderId', 'SentTimestamp']`
**receiveRequestAttemptId**OptionalString`“req-1234abcd”`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**response**object + `{"response": }
` +

+ Response syntax can be referred to receive_message - Boto3 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/receive_message.html) +

+
**success**Boolean`success: true | false`
**errorMessage**String`"errorMessage": "SQS.Client.exceptions.QueueDoesNotExist: "The specified queue does not exist.""`
+ + + + + + + + + + + + + + +
Workflow example
+```yaml + name: sqs-receive-message-test + description: 'Receives a message from an SQS queue' + steps: + - name: aws_sqs_receiveMessage_1 + type: action + action: aws.sqs.receiveMessage + version: '1' + inputs: + awsRoleArn: ${{ :secrets:awsRoleArn }} + region: us-east-1 + queueUrl: https://sqs.us-east-1.amazonaws.com/123456789012/workflow-test-queue + waitTimeSeconds: 5 + maxNumberOfMessages: 10 + messageAttributeNames: ['message_attribute_name'], +``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager.mdx new file mode 100644 index 00000000000..8b3cff75308 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager.mdx @@ -0,0 +1,1320 @@ +--- +title: "AWS Systems Manager actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - AWS actions + - AWS Systems Manager actions +metaDescription: "A list of available aws systems manager actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for aws systems manager actions available in the workflow automation actions catalog. These actions enable you to systems manager automation and document operations. + +## Prerequisites + +Before using AWS actions in workflow automation, ensure you have: + + * An AWS account with appropriate permissions. + * AWS credentials configured (IAM user credentials, IAM role ARN, or session credentials). + * The necessary IAM permissions for the specific AWS services you plan to use. + +See [Set up AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials/) for information on how to create IAM users and IAM roles, and set up static and session AWS credentials for integration with workflow automation AWS actions. + + + + Write an SSM document to the AWS account based on the aws credentials passed in the action input. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/?id=docs_gateway) + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
**documentType**OptionalString + `documentType: "Command"` +

Check valid values from [here](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DocumentDescription.html#systemsmanager-Type-DocumentDescription-Status:text=Required%3A%20No-,Status,-The%20status%20of).

+
**documentFormat**OptionalString + `documentFormat: "YAML"` +

Check valid values from [here](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DocumentDescription.html#systemsmanager-Type-DocumentDescription-Status:text=Required%3A%20No-,Status,-The%20status%20of).

+
**documentContent**RequiredStringCheck example
**override**OptionalBoolean + `override: true (default)`. + +

When `true`, always write the document with the provided name even if one already exist.

+ +

When `false`, if a document with the provided `documentName` already exist, the action returns `success: false` and `errorMessage: Document already exists. Please enable override if you want to update the existing document.`

+
**selectors**Optionallist`[{\"name\": \"documentName\", \"expression\": \".documentName\"}, {\"name\": \"documentType\", \"expression\": \".documentType\"}, {\"name\": \"documentStatus\", \"expression\": \".documentStatus\"}, {\"name\": \"success\", \"expression\": \".success\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription and example
**documentName**String`documentName: "my-ssm-document"`
**documentVersion**String`documentVersion: 1`
**documentType**String`documentType: "Command"`
**documentStatus**String + `documentStatus: "Active"` + +

The value will be one of the statuses from [here](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DocumentDescription.html#systemsmanager-Type-DocumentDescription-Status:text=Required%3A%20No-,Status,-The%20status%20of).

+
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
+ + + - In action input, only `awsAccessKeyId` and `awsSecretAccessKey` can be provided but they should be static credentials of an IAM user. + - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to action input. + - The selectors to get the only specified parameters as output. + - Refer to [AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials) for instructions. + + + + + + **Example 1**: A simple SSM document to list all lambda function + + ```yaml + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + inputs: + Service: lambda + Api: ListFunctions + outputs: + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + ``` + + **Complete autoflows definition with SSM listing lambda functions** + + ```yaml + name: aws-api + + workflowInputs: + key: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_ACCESS_KEY_ID }}" + access: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SECRET_ACCESS_KEY }}" + token: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SESSION_TOKEN }}" + region: + type: String + defaultValue: us-east-2 + + steps: + - name: createSsmDocument + type: action + action: aws.systemsManager.writeDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + selectors: + - name: documentName + expression: '.documentName' + - name: documentType + expression: '.documentType' + - name: documentStatus + expression: '.documentStatus' + - name: success + expression: '.success' + documentName: "LambdaListFunctionNames" + documentContent: | + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + inputs: + Service: lambda + Api: ListFunctions + outputs: + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + + - name: generateIdempotencyToken + type: action + action: utils.uuid.generate + version: 1 + + - name: start1 + type: action + action: aws.systemsManager.startAutomation + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: "${{ .steps.createSsmDocument.outputs.documentName }}" + idempotencyToken: ${{ .steps.generateIdempotencyToken.outputs.uuid }} + + - name: waitForCompletion + type: action + action: aws.systemsManager.waitForAutomationStatus + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + automationExecutionId: ${{ .steps.start1.outputs.automationExecutionId }} + # Optional, default is Success and Failed + automationExecutionStatuses: + - "Success" + - "Failed" + timeout: 60 + + - name: hasCompleted + type: switch + switch: + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Failed" }} + next: displayError + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Success" }} + next: displaySuccess + next: displayUnexpected + + - name: displayUnexpected + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Unexpected status ${{ .steps.waitForCompletion.outputs.automationExecutionStatus | tojson }}" + next: cleanupSsmDocument + + - name: displaySuccess + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "This is all the lambda function names on the region ${{ .workflowInputs.region }}:${{ .steps.waitForCompletion.outputs.automationExecutionOutputs.ExecuteAwsApi.resultFunctionName | join(\",\") }}" + next: cleanupSsmDocument + + - name: displayError + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Error while executing document ${{ .steps.createSsmDocument.outputs.documentName }}, detail: ${{ .steps.waitForCompletion.outputs.errorMessage }}" + next: cleanupSsmDocument + + - name: cleanupSsmDocument + type: action + action: aws.systemsManager.deleteDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: ${{ .steps.createSsmDocument.outputs.documentName }} + ``` + + **Example 2: Execute a Python script** + + + Using the AWS `SystemsManager` automation and document action, we can define a workflow definition that execute a python script. + + Here is a short example illustrating with a simple Hello World application. + + + ```yaml + schemaVersion: '0.3' + description: "Run a Python script that says 'Hello' to the username passed as input and capture the output." + parameters: + Username: + type: String + description: "The username to greet." + default: "User" + mainSteps: + - action: aws:executeScript + name: pythonStep + inputs: + Runtime: python3.8 + Handler: script_handler + Script: | + def script_handler(event, context): + username = event['username'] + return f'Hello {username}' + InputPayload: + username: "{{ Username }}" + outputs: + - Name: scriptOutput + Type: String + Selector: $.Payload + outputs: + - pythonStep.scriptOutput + ``` + This can then be used in the workflow below: + + + ```yaml + name: aws-python-script + + workflowInputs: + key: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_ACCESS_KEY_ID }}" + access: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SECRET_ACCESS_KEY }}" + token: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SESSION_TOKEN }}" + region: + type: String + defaultValue: us-west-2 + name: + type: String + defaultValue: ExecuteHelloPythonScript + username: + type: String + defaultValue: World! + + steps: + - name: generateIdempotencyToken + type: action + action: utils.uuid.generate + version: 1 + + - name: createSsmDocument + type: action + action: aws.systemsManager.writeDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: ${{ .workflowInputs.name }} + documentContent: | + schemaVersion: '0.3' + description: "Run a Python script that says 'Hello' to the username passed as input and capture the output." + parameters: + Username: + type: String + description: "The username to greet." + default: "User" + mainSteps: + - action: aws:executeScript + name: pythonStep + inputs: + Runtime: python3.8 + Handler: script_handler + Script: | + def script_handler(event, context): + username = event['username'] + return f'Hello {username}' + InputPayload: + username: "{{ Username }}" + outputs: + - Name: scriptOutput + Type: String + Selector: $.Payload + outputs: + - pythonStep.scriptOutput + + - name: start1 + type: action + action: aws.systemsManager.startAutomation + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: "${{ .steps.createSsmDocument.outputs.documentName }}" + idempotencyToken: ${{ .steps.generateIdempotencyToken.outputs.uuid }} + parameters: + Username: ${{ .workflowInputs.username }} + + - name: waitForCompletion + type: action + action: aws.systemsManager.waitForAutomationStatus + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + automationExecutionId: ${{ .steps.start1.outputs.automationExecutionId }} + # Optional, default is Success and Failed + automationExecutionStatuses: + - "Success" + - "Failed" + timeout: 300 + + - name: hasCompleted + type: switch + switch: + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Failed" }} + next: displayError + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Success" }} + next: displaySuccess + next: displayUnexpected + + - name: displayUnexpected + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Unexpected status ${{ .steps.waitForCompletion.outputs.automationExecutionStatus | tojson }}" + next: cleanupSsmDocument + + - name: displaySuccess + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "This is the results of the automation that was run on the region ${{ .workflowInputs.region }}:${{ .steps.waitForCompletion.outputs.automationExecutionOutputs.pythonStep.scriptOutput | tojson }}" + next: cleanupSsmDocument + + - name: displayError + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Error while executing document ${{ .steps.createSsmDocument.outputs.documentName }}, detail: ${{ .steps.waitForCompletion.outputs | tojson }}" + next: cleanupSsmDocument + + - name: cleanupSsmDocument + type: action + action: aws.systemsManager.deleteDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: ${{ .steps.createSsmDocument.outputs.documentName }} + ``` + This can be started with the following NerdGraph mutation, assuming the AWS temporary secrets have been previously stored with the `secretsManagementCreateSecretNerdGraph` mutations. + + ```yaml + mutation { + autoflowsStartWorkflowRun(accountId: 11933347, + definition: { + name: "aws-python-script", + }, workflowInputs: [ + {key: "key" value: "${{ :secrets:testUser123_AWS_ACCESS_KEY_ID }}"} + {key: "access" value: "${{ :secrets:testUser123_AWS_SECRET_ACCESS_KEY }}"} + {key: "token" value: "${{ :secrets:testUser123_AWS_SESSION_TOKEN }}"} + {key: "region" value:"us-west-2"} + {key: "username" value: "Julien"} + ]) + { runId } + } + ``` + + Executing the mutation above, returns a runId, for example `207e8c23-2c89-4af2-a74f-3c9ea2ffd543`. This runId can then be used to query the Logs and see the following output: + + Image of a python script execution output + + + + + **Example 3: A more complex SSM document** + + 1. Get the list of API gateway rest APIs. Filter my api (`Test API`) and get the rest API id. + 2. Get the list of all resources inside my api (`Test API`). Filter my specific resource based on pathPart(`/test`) and get the resourceID + 3. Get the list of versions for my lambda function (`ApiGwTestFn`). Filter the specific version that I want to rollback to (version: 1) and get the functionArn of that version. + 4. Update the API gateway integration with the lambda functionArn acquired in the above step. + 5. Create a new deployment for my rest API (`Test API`). + + + ```yaml + schemaVersion: '0.3' + description: Test SSM for API gateway rollback + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + nextStep: ExecuteGetApiResources + inputs: + Service: apigateway + Api: GetRestApis + outputs: + - Name: resultApiId + Selector: $.items[?(@.name=='Test API')].id + Type: String + - name: ExecuteGetApiResources + action: aws:executeAwsApi + nextStep: ExecuteListVersionsByFunction + inputs: + Service: apigateway + Api: GetResources + restApiId: '{{ ExecuteAwsApi.resultApiId }}' + outputs: + - Name: resultResourceId + Selector: $.items[?(@.pathPart=='test')].id + Type: String + - name: ExecuteListVersionsByFunction + action: aws:executeAwsApi + nextStep: ExecuteApiGwUpdateIntg + inputs: + Service: lambda + Api: ListVersionsByFunction + FunctionName: ApiGwTestFn + outputs: + - Name: resultLambdaVersionArn + Selector: $.Versions[?(@.Version=='1')].FunctionArn + Type: String + - name: ExecuteApiGwUpdateIntg + action: aws:executeAwsApi + nextStep: ExecuteApiGwCreateDeployment + inputs: + Service: apigateway + Api: UpdateIntegration + restApiId: '{{ ExecuteAwsApi.resultApiId }}' + resourceId: '{{ ExecuteGetApiResources.resultResourceId }}' + httpMethod: GET + patchOperations: + - op: replace + path: /uri + value: arn:aws:apigateway:us-east-2:lambda:path/2015-03-31/functions/{{ ExecuteListVersionsByFunction.resultLambdaVersionArn }}/invocations + - name: ExecuteApiGwCreateDeployment + action: aws:executeAwsApi + inputs: + Service: apigateway + Api: CreateDeployment + restApiId: '{{ ExecuteAwsApi.resultApiId }}' + outputs: + - ExecuteGetApiResources.resultResourceId + - ExecuteListVersionsByFunction.resultLambdaVersionArn + ``` + + + The sample SSM outputs `ExecuteGetApiResources.resultResourceId` and `ExecuteListVersionsByFunction.resultLambdaVersionArn`. These outputs can be used in further steps in the workflow definition. + + + + + + + + + This action is to delete an AWS SSM document in the AWS account based on the credentials passed in the action input. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/documents.html) + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**RequiredString`${{ :secrets: }}`
**awsSecretAccessKey**RequiredString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
**selectors**OptionalList`[{\"name\": \"success\", \"expression\": \".success\"}, {\"name\": \"documentName\", \"expression\": \".documentName\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**documentName**String`documentName: "my-ssm-document"`
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
+ + + - In action input, only `awsAccessKeyId` and `awsSecretAccessKey` can be provided but they should be static credentials of an IAM user. + - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to action input. + - The selectors to get the only specified parameters as output. + + + + + + A simple SSM document to list all lambda function + + ```yaml + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + inputs: + Service: lambda + Api: ListFunctions + outputs: + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + ``` + + **The complete workflow definition with SSM**: + + ```yaml + name: aws-api + + workflowInputs: + key: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_ACCESS_KEY_ID }}" + access: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SECRET_ACCESS_KEY }}" + token: + type: String + defaultValue: "${{ :secrets:11933347:USERNAME_AWS_SESSION_TOKEN }}" + region: + type: String + defaultValue: us-east-2 + + steps: + - name: createSsmDocument + type: action + action: aws.systemsManager.writeDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + selectors: + - name: documentName + expression: '.documentName' + - name: documentType + expression: '.documentType' + - name: documentStatus + expression: '.documentStatus' + - name: success + expression: '.success' + documentName: "LambdaListFunctionNames" + documentContent: | + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + inputs: + Service: lambda + Api: ListFunctions + outputs: + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + + - name: generateIdempotencyToken + type: action + action: utils.uuid.generate + version: 1 + + - name: start1 + type: action + action: aws.systemsManager.startAutomation + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: "${{ .steps.createSsmDocument.outputs.documentName }}" + idempotencyToken: ${{ .steps.generateIdempotencyToken.outputs.uuid }} + + - name: waitForCompletion + type: action + action: aws.systemsManager.waitForAutomationStatus + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + automationExecutionId: ${{ .steps.start1.outputs.automationExecutionId }} + # Optional, default is Success and Failed + automationExecutionStatuses: + - "Success" + - "Failed" + timeout: 60 + + - name: hasCompleted + type: switch + switch: + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Failed" }} + next: displayError + - condition: ${{ .steps.waitForCompletion.outputs.automationExecutionStatus == "Success" }} + next: displaySuccess + next: displayUnexpected + + - name: displayUnexpected + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Unexpected status ${{ .steps.waitForCompletion.outputs.automationExecutionStatus | tojson }}" + next: cleanupSsmDocument + + - name: displaySuccess + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "This is all the lambda function names on the region ${{ .workflowInputs.region }}:${{ .steps.waitForCompletion.outputs.automationExecutionOutputs.ExecuteAwsApi.resultFunctionName | join(\",\") }}" + next: cleanupSsmDocument + + - name: displayError + type: action + action: newrelic.instrumentation.log + version: 1 + inputs: + message: "Error while executing document ${{ .steps.createSsmDocument.outputs.documentName }}, detail: ${{ .steps.waitForCompletion.outputs.errorMessage }}" + next: cleanupSsmDocument + + - name: cleanupSsmDocument + type: action + action: aws.systemsManager.deleteDocument + version: 1 + inputs: + awsAccessKeyId: ${{ .workflowInputs.key }} + awsSecretAccessKey: ${{ .workflowInputs.access }} + awsSessionToken: ${{ .workflowInputs.token }} + region: ${{ .workflowInputs.region }} + documentName: ${{ .steps.createSsmDocument.outputs.documentName }} + ``` + + + + + + + + + Starts an automation using an AWS SSM document. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_StartAutomationExecution.html) + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**documentName**RequiredString`documentName: "my-ssm-document"`
**parameters**OptionalMap`parameters: myKey: myValue`
**idempotencyToken**OptionalUUID + `idempotencyToken: "any token"` +

This will be passed as client token for idempotency to start aws ssm automation.

+
**selectors**OptionalList`[{\"name\": \"automationExecutionId\", \"expression\": \".automationExecutionId\"}, {\"name\": \"success\", \"expression\": \".success\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**automationExecutionId**String`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
+ + + - In the action input, if `awsAccessKeyId` and `awsSecretAccessKey` are to be provided, make sure they are static credentials of an IAM user. + - If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to the action input. + - Refer to [AWS credentials](/docs/workflow-automation/set-up-aws-credentials/) for instructions. + - Use selectors to get only the specified parameters as output. + + + + + + + + + + + + + + + + + + + +
Workflow definitionInputsOutputs
+ ```yaml + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + ``` + + ```yaml + Service: lambda + Api: ListFunctions + ``` + + ```yaml + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + ``` +
+ + + + + + + + + Waits for an automation using an AWS document. See [AWS Systems Manager Documentation](https://docs.aws.amazon.com/systems-manager/?id=docs_gateway) for more information. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**awsRoleArn**OptionalString`arn:aws:iam::123456789012:role/my-workflow-role`
**awsAccessKeyId**OptionalString`${{ :secrets: }}`
**awsSecretAccessKey**OptionalString`${{ :secrets: }}`
**awsSessionToken**OptionalString`${{ :secrets: }}`
**region**RequiredString`region: "us-east-2"`
**automationExecutionId**RequiredString`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`. The automation `executionId` for which we need to wait for its completion.
**automationExecutionStatuses**OptionalList + `automationExecutionStatuses: ["status1", "status2"]` +

List of automation execution statuses from [AutomationExecution](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_AutomationExecution.html#AutomationExecutionStatus) that can stop the waiting.

`Default: ["Success", "Failed"]`

+
**timeout**Optionalint + `timeout: 180`(default), maximum 600. + +

The duration in seconds we can wait for automation status to be one of the expected `automationExecutionStatuses`.

+ +

If timeout occurred, the output contains `success: false` and `errorMessag: Timeout waiting for automation status`.

+
**selectors**OptionalList`[{\"name\": \"automationExecutionStatus\", \"expression\": \".automationExecutionStatus\"}, {\"name\": \"scriptOutput\", \"expression\": \".automationExecutionOutputs.pythonStep.scriptOutput | tojson\"}]`.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**automationExecutionId**String`automationExecutionId: "3143a28d-241c-4abd-a3ca-9c0ff3890241"`
**automationExecutionStatus**String + `automationExecutionStatus: "Success"` + +

If action is successful, It will either of the values passed in `automationExecutionStatuses` input field.

+ +

Else, this will be null.

+
**automationExecutionOutputs**Map + ```yaml + "automationExecutionOutputs": { + "ExecuteGetApiResources": { + "resultResourceId": [ + "pky3cb" + ] + }, + "ExecuteListVersionsByFunction": { + "resultLambdaVersionArn": [ + "arn:aws:lambda:us-east-2:661945836867:function:ApiGwTestFn:1" + ] + } + } + ``` +

+ The output will be a map of output values from the document. Any output in the document can be collected using this output field and can be used in subsequent steps of the workflow automation definition. +

+
**success**Boolean`success: true`
**errorMessage**String`errorMessage: "Some error message from ssm"`
+ + + 1. In the action input, only `awsAccessKeyId` and `awsSecretAccessKey` can be provided, but they should be static credentials of an IAM user. + 2. If session credentials are to be used, `awsAccessKeyId`, `awsSecretAccessKey` and `awsSessionToken` must be passed to the action input. + 3. Refer to the instructions to set up [AWS credentials](/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials). + 4. Use selectors to get only the specified parameters as output. + + + + + + + + + + + + + + + + + + + +
Workflow definitionInputsOutputs
+ ```yaml + schemaVersion: '0.3' + description: List all Lambda function names. + mainSteps: + - name: ExecuteAwsApi + action: aws:executeAwsApi + isEnd: true + ``` + + ```yaml + Service: lambda + Api: ListFunctions + ``` + + ```yaml + - Name: resultFunctionName + Selector: $..FunctionName + Type: StringList + outputs: + - ExecuteAwsApi.resultFunctionName + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index edfc92f7285..00000000000 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,664 +0,0 @@ ---- -title: "HTTP actions" -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: "A list of available HTTP actions in the actions catalog for workflow definitions" -freshnessValidatedDate: never ---- - - - We're still working on this feature, but we'd love for you to try it out! - - This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -This page provides a comprehensive reference for HTTP actions available in the workflow automation actions catalog. These actions enable you to make HTTP requests (GET, POST, PUT, DELETE) to external APIs and services as part of your workflow definitions. - -## Prerequisites - -Before using HTTP actions in workflow automation, ensure you have: - - * Target API endpoint URLs. - * Any required authentication credentials (API keys, tokens, etc.). - * Understanding of the API request/response formats. - - - HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See [secrets management](/docs/infrastructure/host-integrations/installation/secrets-management/) for more information. - - -## HTTP actions - - - - -Perform an HTTP GET call to retrieve data from an API endpoint. - - - This supports secret syntax for any header value. - - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The scheme must be included: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
- - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntegerThe HTTP status code of the response.
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **Example inputs:** - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **Example outputs:** - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - -Performs an HTTP POST call to send data to an API endpoint. - - - This supports secret syntax for any header value. - - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The scheme must be included: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**body**OptionalStringThe request body.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
- - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntegerThe HTTP status code of the response.
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **Example inputs:** - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **Example outputs:** - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - -Performs an HTTP PUT request to update data at an API endpoint. - - - If you need to pass sensitive data to an input, for example an `Api-Key` header, you can use values stored via the [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph mutation. - - Example: - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The URL must include the scheme (for example, https:// or http://). Example: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**body**OptionalStringThe request body.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
- - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntegerThe HTTP status code of the response.
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Example inputs:** - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Example outputs:** - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - -Performs an HTTP DELETE request to remove data at an API endpoint. - - - If you need to pass sensitive data to an input, for example an `Api-Key` header, you can use values stored via the [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph mutation. - - Example: - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The URL must include the scheme (for example, https:// or http://). Example: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
- - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntegerThe HTTP status code of the response.
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Example inputs:** - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Example outputs:** - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete.mdx new file mode 100644 index 00000000000..ea9d8c127c2 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete.mdx @@ -0,0 +1,213 @@ +--- +title: "HTTP Delete" +tags: + - workflow automation + - workflow + - workflow automation actions + - HTTP actions + - HTTP DELETE +metaDescription: "A list of available http delete in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for http delete available in the workflow automation actions catalog. These actions enable you to http delete request operations. + +## Prerequisites + +Before using HTTP actions in workflow automation, ensure you have: + + * Target API endpoint URLs. + * Any required authentication credentials (API keys, tokens, etc.). + * Understanding of the API request/response formats. + + + HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See [secrets management](/docs/infrastructure/host-integrations/installation/secrets-management/) for more information. + + +## Delete web data [#http-delete] + +Performs an HTTP DELETE request to remove data at an API endpoint. + + + If you need to pass sensitive data to an input, for example an `Api-Key` header, you can use values stored via the [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph mutation. + + Example: + ```json + { + "inputs": [ + { + "key": "headers", + "value": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" + } + ] + } + ``` + + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The URL must include the scheme (for example, https:// or http://). Example: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntThe status code of the response.
**success**BooleanStatus of the request.
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + + + + + +
Workflow definitionInputOutput
+ ```yaml + name: httpDeleteTest + steps: + - name: query + type: action + action: http.delete + version: 1 + inputs: + url: ${{ .workflowInputs.url }} + urlParams: ${{ .workflowInputs.urlParams }} + headers: ${{ .workflowInputs.headers }} + selectors: ${{ .workflowInputs.selectors }} + ``` + + ```yaml + { + "inputs": [ + { + "key": "url", + "value": "https://example.com" + }, + { + "key": "urlParams", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "headers", + "value": "{\"baz\": \"bat\"}" + }, + { + "key": "selectors", + "value": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" + } + ] + } + ``` + + ```yaml + Success case: + { + "success": true + "responseBody": "\n...\n", + "statusCode": 200 + } + + Failure case: + { + "errorMessage": "An unexpected error failed to call http delete endpoint.", + "success": false + } + ``` +
+ + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get.mdx new file mode 100644 index 00000000000..48aeab5883b --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get.mdx @@ -0,0 +1,214 @@ +--- +title: "HTTP Get" +tags: + - workflow automation + - workflow + - workflow automation actions + - HTTP actions + - HTTP GET +metaDescription: "A list of available http get in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for HTTP Get available in the workflow automation actions catalog. These actions enable you to perform HTTP GET request operations. + +## Prerequisites + +Before using HTTP actions in workflow automation, ensure you have: + + * Target API endpoint URLs. + * Any required authentication credentials (API keys, tokens, etc.). + * Understanding of the API request/response formats. + + + HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) for more information. + + +## Request web data [#http-get] + + Perform an HTTP GET call to retrieve data from an API endpoint. + + + If you need to pass sensitive data to an input, for example an `Api-Key` header, you can use values stored via the [secretsManagementCreateSecret](https://onenr.io/0KQXX6BmdQa) NerdGraph mutation. + + **Example** + + ```yaml + { + "inputs": [ + { + "key": "headers", + "value": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" + } + ] + } +``` + + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The scheme must be included: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntThe status code of the response.
**success**BooleanStatus of the request.
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + + + + + +
Workflow definitionInputOutput
+ ```yaml + name: httpGetTest + steps: + - name: query + type: action + action: http.get + version: 1 + inputs: + url: ${{ .workflowInputs.url }} + urlParams: ${{ .workflowInputs.urlParams }} + headers: ${{ .workflowInputs.headers }} + selectors: ${{ .workflowInputs.selectors }} + ``` + + ```yaml + { + "inputs": [ + { + "key": "url", + "value": "https://example.com" + }, + { + "key": "urlParams", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "headers", + "value": "{\"baz\": \"bat\"}" + }, + { + "key": "selectors", + "value": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" + } + ] + } + ``` + + ```yaml + Success case: + { + "responseBody": "\n...\n", + "statusCode": 200 + "success": true + } + + Failure case: + { + "errorMessage": "An unexpected error failed to call http get endpoint.", + "success": false + } + ``` +
+ + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post.mdx new file mode 100644 index 00000000000..52e608992d4 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post.mdx @@ -0,0 +1,226 @@ +--- +title: "HTTP Post" +tags: + - workflow automation + - workflow + - workflow automation actions + - HTTP actions + - HTTP POST +metaDescription: "A list of available http post in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for http post available in the workflow automation actions catalog. These actions enable you to http post request operations. + +## Prerequisites + +Before using HTTP actions in workflow automation, ensure you have: + + * Target API endpoint URLs. + * Any required authentication credentials (API keys, tokens, etc.). + * Understanding of the API request/response formats. + + + HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See [secrets management](/docs/infrastructure/host-integrations/installation/secrets-management/) for more information. + + +## Send data to a server [#http-post] + +Performs an HTTP POST call to send data to an API endpoint. + + + If you need to pass sensitive data to an input, for example an Api-Key header, you can use values stored via the [secretsManagementCreateSecret](https://onenr.io/0KQXX6BmdQa) NerdGraph mutation. + + **Example** + + ```yaml + { + "inputs": [ + { + "key": "headers", + "value": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" + } + ] + } +``` + + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The scheme must be included: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**body**OptionalStringThe request body.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntThe status code of the response.
**success**BooleanStatus of the request.
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + + + + + +
Workflow definitionInputOutput
+ ```yaml + name: httpPostTest + + steps: + - name: query + type: action + action: http.post + version: 1 + inputs: + url: ${{ .workflowInputs.url }} + urlParams: ${{ .workflowInputs.urlParams }} + headers: ${{ .workflowInputs.headers }} + body: ${{ .workflowInputs.body }} + selectors: ${{ .workflowInputs.selectors }} + ``` + + ```yaml + { + "inputs": [ + { + "key": "url", + "value": "https://example.com" + }, + { + "key": "headers", + "value": "{\"Content-Type\":\"application/json\"}" + }, + { + "key": "urlParams", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "body", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "selectors", + "value": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" + } + ] + } + ``` + + ```yaml + Success case: + { + "success": true + "responseBody": "", + "statusCode": 200 + } + + Failure case: + { + "errorMessage": "An unexpected error failed to call http post endpoint.", + "success": false + } + ``` +
+ + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put.mdx new file mode 100644 index 00000000000..c96f813e363 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put.mdx @@ -0,0 +1,225 @@ +--- +title: "HTTP Put" +tags: + - workflow automation + - workflow + - workflow automation actions + - HTTP actions + - HTTP PUT +metaDescription: "A list of available http put in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for http put available in the workflow automation actions catalog. These actions enable you to http put request operations. + +## Prerequisites + +Before using HTTP actions in workflow automation, ensure you have: + + * Target API endpoint URLs. + * Any required authentication credentials (API keys, tokens, etc.). + * Understanding of the API request/response formats. + + + HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See [secrets management](/docs/infrastructure/host-integrations/installation/secrets-management/) for more information. + + +## Create resource at URI [#http-put] + +Performs an HTTP PUT request to update data at an API endpoint. + + + If you need to pass sensitive data to an input, for example an `Api-Key` header, you can use values stored via the [secretsManagementCreateSecret](https://onenr.io/0KQXX6BmdQa) NerdGraph mutation. + + Example: + ```json + { + "inputs": [ + { + "key": "headers", + "value": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" + } + ] + } + ``` + + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeDescription
**url**RequiredStringThe target URL for the request. The scheme must be included: `https://example.com`
**urlParams**OptionalMapThe query parameters to append to the URL. Takes a stringified JSON object.
**headers**OptionalMapThe headers to add to the request. Takes a stringified JSON object.
**body**OptionalStringThe request body.
**selectors**OptionalListThe selectors to get only the specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeDescription
**responseBody**StringThe body of the response.
**statusCode**IntThe HTTP status code of the response.
**success**BooleanStatus of the request.
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + + + + + +
Workflow definitionInputsOutputs
+ ```yaml + name: httpPutTest + + steps: + - name: query + type: action + action: http.put + version: 1 + inputs: + url: ${{ .workflowInputs.url }} + urlParams: ${{ .workflowInputs.urlParams }} + headers: ${{ .workflowInputs.headers }} + body: ${{ .workflowInputs.body }} + selectors: ${{ .workflowInputs.selectors }} + ``` + + ```yaml + { + "inputs": [ + { + "key": "url", + "value": "https://example.com" + }, + { + "key": "headers", + "value": "{\"Content-Type\":\"application/json\"}" + }, + { + "key": "urlParams", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "body", + "value": "{\"foo\": \"bar\"}" + }, + { + "key": "selectors", + "value": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" + } + ] + } + ``` + + ```yaml + Success case: + { + "responseBody": "", + "statusCode": 200 + "success": true + } + + Failure case: + { + "errorMessage": "An unexpected error failed to call http post endpoint.", + "success": false + } + ``` +
+ + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest.mdx new file mode 100644 index 00000000000..16951e949f7 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest.mdx @@ -0,0 +1,355 @@ +--- +title: "New Relic Ingest actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - New Relic actions + - New Relic Ingest actions +metaDescription: "A list of available new relic ingest actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for new relic ingest actions available in the workflow automation actions catalog. These actions enable you to send events and logs to new relic. + +## Prerequisites + +Before using New Relic actions in workflow automation, ensure you have: + + * A New Relic account with appropriate permissions. + * A New Relic license key (if sending data to a different account). + * The necessary permissions for the specific New Relic services you plan to use. + +See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for information on how to create and manage your New Relic Account License Key. + +## Data ingest actions + + + + Reports a custom event to New Relic. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**attributes**OptionalMap`"{\"page\": \"1\", \"limit\": \"10\"}"`
**events**Requiredlist`"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"`
**licenseKey**Optionalstring`"{{ .secrets.secretName }}"`, where `secretName` is the key under which the license key is stored.
**selectors**Optionallist`[{\"name\": \"success\", \"expression\": \".success\"}]`
+ + + - **attributes**: Common attributes which are part of all the events when provided. Merging for each event item when needed event item overrides common definition. + - **events**: The list of event data. Note that events requires the use of an `eventType` field that represents the custom event type and the maximum events allowed per request is **100**. + - **licenseKey**: The **New Relic Account License Key** is a required input that specifies the target account where events are sent. If this value is not provided as an input, a default license key is assumed based on the account executing the workflow. In other words, you need to specify the **New Relic Account License Key** where you want to send your events. If you don't provide one, the system will use a default license key associated with the account running the workflow. Refer to [xyz](/docs/apis/intro-apis/new-relic-api-keys/#license-key) on how to create and manage your New Relic Account License Key. + - **selectors**: The selectors to get only the specified parameters as output. + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**success**Boolean`true`
**errorMessage**string`"Error message if operation failed"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: heartbeat_newrelicIngestSendEvents + + workflowInputs: + cellName: + type: String + + steps: + - name: runAction + type: action + action: newrelic.ingest.sendEvents + version: 1 + inputs: + attributes: + colour: red + id: 1234 + events: + - eventType: HeartBeat + test: "OK" + attributes: + foo: bar + - eventType: HeartBeat1234 + test: "OK1234" + attributes: + foo: bar + - eventType: HeartBeat12345 + test: "OK12345" + attributes: + foo: bar + colour: yellow + - eventType: HeartBeat12345678 + test: "OK12345678" + selectors: + - name: success + expression: ".success" + ``` + + **Expected output:** + ```yaml + { + "success": true + } + ``` + + **Retrieve events:** + + After successfully executing a workflow, you can retrieve the associated event by running a query under the account that executed the workflow: + + ```sql + SELECT * FROM HeartBeat + ``` +
+ + + + + + + + + +Send logs to New Relic + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeExample
**attributes**Optionalmap`"{\"page\": \"1\", \"limit\": \"10\"}"`
**logs**Requiredlist`"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"`
**licenseKey**Optionalstring`"{{ .secrets.secretName }}"`
**selectors**Optionallist`[{\"name\": \"success\", \"expression\": \".success\"}]`
+ + + - **attributes**: Common attributes included in all logs when provided. If a log item specifies the same attribute, it overrides the common definition. + - **logs**: The list of log data. Note that the maximum logs allowed per request is 100. + - **licenseKey**: The New Relic Account License Key that specifies the target account where logs are sent. If not provided, a default license key is assumed based on the account executing the workflow. See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for more information. + - **selectors**: The selectors to get only the specified parameters as output. + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**success**Boolean`true`
**errorMessage**string`"Error message if operation failed"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: heartbeat_newrelicIngestSendLogs + + workflowInputs: + cellName: + type: String + + steps: + - name: runAction + type: action + action: newrelic.ingest.sendLogs + version: 1 + inputs: + attributes: + colour: red + id: 1234 + logs: + - message: 'Heartbeat sendLogs Action Test Message' + attributes: + foo: bar + - message: 'HeartBeat1234' + attributes: + foo: bar + - message: 'HeartBeat12345' + attributes: + foo: bar + colour: yellow + - message: 'HeartBeat12345678' + selectors: + - name: success + expression: ".success" + ``` + + **Expected output:** + ```yaml + { + "success": true + } + ``` + + **Retrieve logs:** + + After successfully executing a workflow, you can retrieve the associated log by running a query under the account that executed the workflow: + ```sql + SELECT * FROM Log + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph.mdx new file mode 100644 index 00000000000..c889cb49b32 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph.mdx @@ -0,0 +1,197 @@ +--- +title: "New Relic NerdGraph actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - New Relic actions + - New Relic NerdGraph actions +metaDescription: "A list of available new relic nerdgraph actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for new relic nerdgraph actions available in the workflow automation actions catalog. These actions enable you to execute nerdgraph queries and mutations. + +## Prerequisites + +Before using New Relic actions in workflow automation, ensure you have: + + * A New Relic account with appropriate permissions. + * A New Relic license key (if sending data to a different account). + * The necessary permissions for the specific New Relic services you plan to use. + +See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for information on how to create and manage your New Relic Account License Key. + + +## NerdGraph actions + + + + +Executes a Graphql command against newrelic NerdGraph API. The command can either be a query or a mutation. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
InputOptionalityTypeDescriptionExample
**graphql**RequiredstringA GraphQL syntax. You should use GraphiQL to build and test your command
**variables**Requiredmap[string]anyAny key/value pair variables to use with the GraphQL statement.
**selectors**OptionalListThe selectors to get the only specified parameters as output. + ```yaml + steps: + - name: findingVar + type: action + action: newrelic.nerdgraph.execute + version: 1 + inputs: + graphql: | + query GetEntity($entityGuid: EntityGuid!) { + actor { + entity(guid: $entityGuid) { + alertSeverity + } + } + } + variables: + entityGuid: ${{ .workflowInputs.entityGuid }} + - name: findingInline + type: action + action: newrelic.nerdgraph.execute + version: 1 + inputs: + graphql: | + { + actor { + entity(guid: "${{ .workflowInputs.entityGuid }}") { + alertSeverity + } + } + } + selectors: + - name: entities + expression: '.data' + ``` +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
OutputTypeDescription
**data**map[string]anyContents of the `data` property of a NerdGraph response.
**success**BooleanStatus of the request.s
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + +
Example
+ ```yaml + steps: + - name: currentUserId + type: action + action: newrelic.nerdgraph.execute + version: 1 + inputs: + graphql: | + query userId { + currentUser { + id + } + } + - name: sayHello + type: action + action: example.messaging.sayHello + version: 1 + inputs: + name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification.mdx similarity index 53% rename from src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx rename to src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification.mdx index 4c2acb0fd97..86c2efc815e 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification.mdx @@ -1,11 +1,12 @@ --- -title: "New Relic actions" +title: "New Relic Notification actions" tags: - workflow automation - workflow - workflow automation actions - - New relic actions -metaDescription: "A list of available actions in the actions catalog for workflow definitions" + - New Relic actions + - New Relic Notification actions +metaDescription: "A list of available new relic notification actions in the actions catalog for workflow definitions" freshnessValidatedDate: never --- @@ -15,7 +16,7 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -This page provides a comprehensive reference for New Relic actions available in the workflow automation actions catalog. These actions enable you to integrate New Relic platform capabilities into your workflow definitions, including sending custom events and logs, executing NerdGraph queries, running NRQL queries, and sending notifications. +This page provides a comprehensive reference for new relic notification actions available in the workflow automation actions catalog. These actions enable you to send notifications through new relic. ## Prerequisites @@ -27,604 +28,6 @@ Before using New Relic actions in workflow automation, ensure you have: See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for information on how to create and manage your New Relic Account License Key. -## Data ingest actions - - - - Sends a custom events to New Relic - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**attributes**OptionalMap`"{\"page\": \"1\", \"limit\": \"10\"}"`
**events**Requiredlist`"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]`
**licenseKey**Optionalstring`"{{ .secrets.secretName }}"`
**selectors**Optionallist`[{\"name\": \"success\", \"expression\": \".success\"}]`
- - - - **attributes**: Common attributes which are part of all the events when provided. Merging for each event item when needed event item overrides common definition. - - **events**: The list of event data. Note that events requires the use of an `eventType` field that represents the custom event type and the maximum events allowed per request is 100. - - **licenseKey**: The New Relic Account License Key that specifies the target account where events are sent. If this value is not provided, a default license key is assumed based on the account executing the workflow. - - **selectors**: The selectors to get only the specified parameters as output. - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**success**Boolean`true`
**errorMessage**string`"Error message if operation failed"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **Expected output:** - ```yaml - { - "success": true - } - ``` - - **Retrieve events:** - - After successfully executing a workflow, you can retrieve the associated event by running a query under the account that executed the workflow: - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - -Send logs to New Relic - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Input FieldOptionalityTypeExample
**attributes**Optionalmap`"{\"page\": \"1\", \"limit\": \"10\"}"`
**logs**Requiredlist`"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"`
**licenseKey**Optionalstring`"{{ .secrets.secretName }}"`
**selectors**Optionallist`[{\"name\": \"success\", \"expression\": \".success\"}]`
- - - - **attributes**: Common attributes included in all logs when provided. If a log item specifies the same attribute, it overrides the common definition. - - **logs**: The list of log data. Note that the maximum logs allowed per request is 100. - - **licenseKey**: The New Relic Account License Key that specifies the target account where logs are sent. If not provided, a default license key is assumed based on the account executing the workflow. See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for more information. - - **selectors**: The selectors to get only the specified parameters as output. - - - - - - - - - - - - - - - - - - - - - - - - -
Output FieldTypeExample
**success**Boolean`true`
**errorMessage**string`"Error message if operation failed"`
- - - - - - - - - - - - - - -
Workflow example
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **Expected output:** - ```yaml - { - "success": true - } - ``` - - **Retrieve logs:** - - After successfully executing a workflow, you can retrieve the associated log by running a query under the account that executed the workflow: - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## NerdGraph actions - - - - -Executes a Graphql command against newrelic NerdGraph API. The command can either be a query or a mutation. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
InputOptionalityTypeDescriptionExample
**graphql**RequiredstringA GraphQL syntax. You should use GraphiQL to build and test your command
**variables**Requiredmap[string]anyAny key/value pair variables to use with the GraphQL statement.
**selectors**OptionalListThe selectors to get the only specified parameters as output. - ```yaml - steps: - - name: findingVar - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query GetEntity($entityGuid: EntityGuid!) { - actor { - entity(guid: $entityGuid) { - alertSeverity - } - } - } - variables: - entityGuid: ${{ .workflowInputs.entityGuid }} - - name: findingInline - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - { - actor { - entity(guid: "${{ .workflowInputs.entityGuid }}") { - alertSeverity - } - } - } - selectors: - - name: entities - expression: '.data' - ``` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OutputTypeDescription
**data**map[string]anyContents of the `data` property of a NerdGraph response.
**success**BooleanStatus of the request.s
**errorMessage**StringFailure reason as message.
- - - - - - - - - - - - - - -
Example
- ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - -## Query actions - - - - -Executes a cross-accounts NRQL query through the NerdGraph API. - - - - - Inputs - - - - Outputs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
InputOptionalityTypeDescriptionExample
**query**RequiredstringThe NRQL query statement.
**accountIds**Optionallist of intThe **New Relic Account ID** input is a list of target IDs that allows you to specify the target accounts where the query is executed against. If this value is not provided as an input, the query will automatically be executed against the account associated with the workflow's execution account.
**selectors**OptionallistThe selectors to get the only specified parameters as output. - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - -
OutputTypeExample
**results**: An array of objects containing the results of the query. - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - ## Notifications actions @@ -766,24 +169,26 @@ Executes a cross-accounts NRQL query through the NerdGraph API. id="nerdgraph-query-get-destinationId" title="NerdGraph Query to get destinationId" > - ```sh - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { - entities { - createdAt - id - name - active - } - } + +```yaml +{ + actor { + account(id: 12345678) { + aiNotifications { + destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { + entities { + createdAt + id + name + active } } } } - ``` + } +} +``` + @@ -862,7 +267,7 @@ Executes a cross-accounts NRQL query through the NerdGraph API. ```yaml - name: msTeam_notification_workflow + name: msTeam_notification_workflow description: This is a test workflow to test MSTeam notification send action steps: - name: SendMessageUsingMSTeam @@ -931,30 +336,32 @@ Executes a cross-accounts NRQL query through the NerdGraph API.

Refer [Destinations](/docs/alerts/get-notified/destinations/) to know more about destinations.

- + - ```yaml - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: EMAIL, active: true}) { - entities { - createdAt - id - name - active - } + +```yaml +{ + actor { + account(id: 12345678) { + aiNotifications { + destinations(filters: {type: EMAIL, active: true}) { + entities { + createdAt + id + name + active } } } } } - ``` +} +``` + @@ -1086,7 +493,7 @@ Executes a cross-accounts NRQL query through the NerdGraph API. ```yaml - name: email_testing_with_attachment + name: email_testing_with_attachment description: Workflow to test sending an email notification via NewRelic with log step workflowInputs: destinationId: @@ -1130,3 +537,327 @@ Executes a cross-accounts NRQL query through the NerdGraph API. + + + + + Sends a slack message to a channel, integrated with destinations . + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityDatatypeDescriptionExample
**destinationId**RequiredString + DestinationId associated with the newrelic destination. +

+ Refer [NerdGraph tutorial: Alerts destinations](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations/) for steps on how to configure a new destination and listing destination Id. +

+

+ Refer [Destinations](/docs/alerts/get-notified/destinations/) to know more about destinations. +

+ + + + +```yaml +{ + actor { + account(id: 12345678) { + aiNotifications { + destinations(filters: {type: SLACK, active: true}) { + entities { + createdAt + id + name + active + } + } + } + } + } +} +``` + + + + 		`123e4567-e89b-12d3-a456-426614174000`
**text**RequiredStringText message which need to be sent Hello ! this message from Workflow
**channel**RequiredStringChannel name where message will be senthelp-nomad
**selectors**OptionalListThe selectors to get the only specified parameters as output.`[{\"name\": \"success\", \"expression\": \".success\"}]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**success**Boolean`true/false`
**sessionId**String`"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"`
**errorMessage**String`Channel is a required field in the notification send"`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + name: slack_notification_workflow + description: This is a test workflow to test slack notification send action + steps: + - name: SendMessageUsingSlackChannel + type: action + action: newrelic.notification.sendSlack + version: 1 + inputs: + destinationId: ccd0d926-ed6f-4ddd-bc7d-b7ea9822908d + text: Hi , Testing notifcation api using slack channel name + channel: test-channel-workflow + ``` +
+ + + + + + + + + + Runs a workflow through the NerdGraph API. + + + + + Inputs + + + Outputs + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityDatatypeDescription
**definitionName**RequiredStringName of the workflow definition.
**definitionScopeType**OptionalStringScope type of the workflow definition. Scope type must be either `ACCOUNT` or `ORGANIZATION`.
**definitionVersion**OptionalIntVersion of the workflow definition
**idempotencyKey**OptionalStringUnique identifier to ensure idempotency of the request. It should be a UUID.
**workflowInputs**OptionalListVersion of the workflow definition
**runScopeType**RequiredStringScope type of the workflow. Scope type must be `ACCOUNT`. We'll support starting a workflow at the organization level in the future
**runScopeId**RequiredStringScope id of the workflow. Scope type must be accountId for now.
**selectors**OptionalListThe selectors to get the only specified parameters as output.
+ + ### Example + + ```yaml + steps: + - name: startHealthyHeartbeat + type: action + action: newrelic.workflowAutomation.startWorkflowRun + version: 1 + inputs: + definitionName: "heartbeat_newrelicIngestSendEvents_10062025" + definitionVersion: 1 + scopeType: "ACCOUNT" + definitionScopeType: "d34568b7-ee0b-4191-b663-7b2925b0de5b" + workflowInputs: + - key: "cellName" + value: "stg-joint-effort" + runScopeType: "ACCOUNT" + runScopeId: "11544325" + ``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldTypeExample
**runId**Unique identifier for the workflow run
**success**Boolean`Status of the request.`
**errorMessage**String`Failure reason as message.`
+ + + + + + + + + + + + + + +
Workflow example
+ ```yaml + { + "success": true + "runId": "00dc031f-c1cc-4d26-a3fb-6153c553c66b" + } + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb.mdx new file mode 100644 index 00000000000..e8a789c65b1 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb.mdx @@ -0,0 +1,135 @@ +--- +title: "New Relic NRDB actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - New Relic actions + - New Relic NRDB actions +metaDescription: "A list of available new relic nrdb actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for new relic nrdb actions available in the workflow automation actions catalog. These actions enable you to query new relic database. + +## Prerequisites + +Before using New Relic actions in workflow automation, ensure you have: + + * A New Relic account with appropriate permissions. + * A New Relic license key (if sending data to a different account). + * The necessary permissions for the specific New Relic services you plan to use. + +See [License Key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) for information on how to create and manage your New Relic Account License Key. + +## Query actions + + + + +Executes a cross-accounts NRQL query through the NerdGraph API. + + + + + Inputs + + + + Outputs + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
InputOptionalityTypeDescriptionExample
**query**RequiredstringThe NRQL query statement.
**accountIds**Optionallist of intThe **New Relic Account ID** input is a list of target IDs that allows you to specify the target accounts where the query is executed against. If this value is not provided as an input, the query will automatically be executed against the account associated with the workflow's execution account.
**selectors**OptionallistThe selectors to get the only specified parameters as output. + ```json + steps: + - name: queryForLog + type: action + action: newrelic.nrdb.query + version: 1 + inputs: + accountIds: [12345] + query: FROM Log SELECT * WHERE message LIKE 'DEMO%' + selectors: + - name: resultsAsString + expression: '.results | tostring' + ``` +
+ + + + + + + + + + + + + + + + + + +
OutputTypeExample
**results**: An array of objects containing the results of the query. + ```yaml + { + results=[ + { message=[INFO] - Workflow: test has ended, messageId=39af98 }, + { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, + ... + ] + } + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index c7f948557b7..00000000000 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,419 +0,0 @@ ---- -title: "Utility actions" -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: "A list of available utility actions in the actions catalog for workflow definitions" -freshnessValidatedDate: never ---- - -This page provides a reference for utility actions available in the workflow automation actions catalog. These actions enable you to perform common data transformation and utility operations in your workflow definitions. - -## Utility actions - - - - This action is used to transform from epoch timestamp to date/time. Possible references: - -* https://en.wikipedia.org/wiki/List_of_tz_database_time_zones -* https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS - -Refer [fromEpoch](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) for more information. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
InputOptionalityTypeDescription
**timestamp**RequiredintAn integer representing epoch timestamp. Note that, UNIX epochs are the number of seconds after 1st Jan 1970, midnight UTC (00:00)
**timestampUnit**OptionalstringA string representing unit of provided timestamp. Acceptable values: SECONDS, MILLISECONDS(DEFAULT)
**timezoneId**OptionalstringA string representing timezone for desired date/time, default: UTC
**pattern**OptionalstringA string representing pattern for desired datetime, default: ISO-8601
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldOptionalityDatatypeDescription
**date**RequiredstringA string representation of date.
**time**RequiredstringA string representation of time.
**datetime**RequiredstringA string representation of datetime.
**timezone**RequiredmapA map representation of timezoneId and abbreviation.
- - - - - - - - - - - - - - - - - - -
ExampleWorkflow InputOutputs
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - This action is used to transform various type of input (JSON, map) to a CSV format. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - - -
InputOptionalityTypeDescription
**data**RequiredanyA string representing a data to transform into CSV, typically a JSON string or a map.
- - - - - - - - - - - - - - - - - - - - -
FieldOptionalityDatatypeDescription
**csv**RequiredstringA CSV representation of the data received.
- - - - - - - - - - - - - - - - - - -
ExampleWorkflow InputOutputs
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` -
- - - - - - - - - Generate an RFC-compliant V4 uuid. - - - - - Inputs - - - - Outputs - - - - Example - - - - - - - - - - - - - - - - - - - - - -
InputOptionalityDatatypeDescription
- - - - - - - - - - - - - - - - - - -
FieldDatatypeDescription
**uuid**string
- - - - - - - - - - - - - - - - - - -
ExampleWorkflow InputOutputs
- name: generateUUID

- steps: - - name: generateUUID - type: action - action: utils.uuid.generate - version: 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident.mdx similarity index 96% rename from src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty.mdx rename to src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident.mdx index a7c9f773de2..a6003687a14 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident.mdx @@ -1,15 +1,22 @@ --- -title: "PagerDuty actions" +title: "PagerDuty Incident actions" tags: - workflow automation - workflow - workflow automation actions - - pagerduty actions -metaDescription: "A list of available actions in the actions catalog for workflow definitions" + - PagerDuty actions + - PagerDuty Incident actions +metaDescription: "A list of available pagerduty incident actions in the actions catalog for workflow definitions" freshnessValidatedDate: never --- -This page provides a comprehensive reference for PagerDuty actions available in the workflow automation actions catalog. These actions enable you to integrate PagerDuty incident management into your workflow definitions, including creating, updating, resolving, listing, and retrieving incidents. + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for pagerduty incident actions available in the workflow automation actions catalog. These actions enable you to pagerduty incident management. ## Prerequisites @@ -152,7 +159,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: ```yaml - name: resolve-pagerduty-incident + name: resolve-pagerduty-incident description: '' steps: - name: pagerduty_incident_resolve_1 @@ -301,7 +308,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: ```yaml - name: list-pagerduty-incidents + name: list-pagerduty-incidents description: '' steps: - name: pagerduty_incident_list_1 @@ -330,7 +337,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: id="pagerDuty.incident.get" title="Get a PagerDuty incident" > - Retrieves detailed information about a specific PagerDuty incident by its ID. + Ge a pagerduty incident. @@ -451,7 +458,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: ```yaml - name: get-pagerduty-incident + name: get-pagerduty-incident description: '' steps: - name: pagerduty_incident_get_1 @@ -713,7 +720,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: ```yaml - name: create-pagerduty-incident + name: create-pagerduty-incident description: '' steps: - name: create @@ -983,7 +990,7 @@ Before using PagerDuty actions in workflow automation, ensure you have: ```yaml - name: update-pagerduty-incident + name: update-pagerduty-incident description: '' steps: - name: pagerduty_incident_update_1 diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat.mdx similarity index 60% rename from src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx rename to src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat.mdx index a8a5f871cfc..9bc88cfe008 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat.mdx @@ -1,13 +1,13 @@ --- -title: "Communication actions" +title: "Slack Chat actions" tags: - workflow automation - workflow - workflow automation actions + - Slack actions - communication actions - - slack actions - - ms teams actions -metaDescription: "A list of available actions in the actions catalog for workflow definitions" + - Slack Chat actions +metaDescription: "A list of available slack chat actions in the actions catalog for workflow definitions" freshnessValidatedDate: never --- @@ -17,7 +17,7 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -This page provides a comprehensive reference for communication actions available in the workflow automation actions catalog. These actions enable you to integrate communication platforms into your workflow definitions, including sending messages to Slack channels, retrieving reactions, and more. +This page provides a comprehensive reference for slack chat actions available in the workflow automation actions catalog. These actions enable you to slack messaging operations. ## Prerequisites @@ -62,6 +62,7 @@ Sends a message to a slack channel, with an optional file attachment. Input Field Optionality Type + Description Example @@ -69,57 +70,61 @@ Sends a message to a slack channel, with an optional file attachment. **token** Required - secret + Secret + The Slack bot token to use. This should be passed as a secret syntax. Refer to [Add Slack configuration](/docs/alerts/get-notified/notification-integrations/) for instructions on setting up a token. `${{ :secrets:slackToken }}` **channel** Required - string + String + The name of the channel, or a channelID, to send the message. See [Slack API](https://docs.slack.dev/reference/methods/chat.postMessage/#arg_channel) for more information. `my-slack-channel` **text** Required - string + String + The message to be posted to Slack in the specified `channel`. `Hello World!` **threadTs** Optional - string + String + Timestamp belonging to parent message, used to create a message reply in a thread. `.` **attachment** Optional - map + Map + Allows attaching a file with a message onto the specified `channel`. **attachment.filename** Required - string + String + Specify the filename for the uploaded file in Slack. `file.txt` **attachment.content** Required - string + String + The content of the file to upload as UTF8. `Hello\nWorld!` + + **selectors** + Optional + List + The selectors to get the only specified parameters as output. + `[{\"name\": \"threadTs\", \"expression\": \".threadTs\"}, {\"name\": \"channelID\", \"expression\": \".channelID\")\"}]` + - - - - **token**: The Slack bot token to use. This should be passed as a secret syntax. Refer to [Add Slack configuration](/docs/autoflow/overview#add-the-slack-integration) for instructions on setting up a token. - - **channel**: The name of the channel, or a channelID, to send the message. See [Slack API](https://api.slack.com/methods/chat.postMessage#arg_channel/) for more information. - - **text**: The message to be posted to Slack in the specified `channel`. - - **threadTs**: Timestamp belonging to parent message, used to create a message reply in a thread. - - **attachment**: Allow attaching a file with a message onto the specified `channel`. - - **attachment.filename**: Specify the filename for the uploaded file in Slack. - - **attachment.content**: The content of the file to upload as UTF8. - @@ -128,27 +133,37 @@ Sends a message to a slack channel, with an optional file attachment. Output Field Type + Description Example **threadTs** - string + String + Timestamp of the message thread. May be used in future `postMessage` calls to post a reply in a thread. `.` **channelID** - string + String + Id of the channel where message is posted. + `` + + + **success** + Boolean + Status of the request + `true / false` + + + **errorMessage** + String + Failure reason as message `` - - - - **threadTs**: Timestamp of message. May be used in future postMessage calls to post a reply in a thread. - - **channelID**: Id of the channel where message is posted. - @@ -170,12 +185,17 @@ name: SendMessage steps: - name: send_slack_message type: action - action: slack.chat.postMessage + action: slack.chat.postMessage version: 1 inputs: - token: ${{ :secrets:slackToken }} + token: ${{ :secrets:dn_staging_slack_token }} channel: ${{ .workflowInputs.channel }} text: ${{ .workflowInputs.text }} + selectors: + - name: threadTs + expression: ".threadTs" + - name: channelID + expression: ".channelID" ``` **Expected inputs:** @@ -185,7 +205,7 @@ steps: "inputs": [ { "key" : "channel", - "value" : "my-channel" + "value" : "test-channel-workflow" }, { "key" : "text", @@ -202,6 +222,7 @@ steps: { "threadTs": "1718897637.400609", "channelID": "C063JK1RHN1" + "success": true } ] ``` @@ -225,13 +246,14 @@ steps: name: SendFileMessage steps: + - name: postCsv type: action action: slack.chat.postMessage version: 1 inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel + token: ${{ :secrets:dn_staging_slack_token }} + channel: test-channel-workflow text: "Please find the attached file:" attachment: filename: 'file.txt' @@ -245,6 +267,7 @@ steps: { "threadTs": "1718897637.400609", "channelID": "C063JK1RHN1" + "success": true } ] ``` @@ -289,6 +312,7 @@ Get a reaction of a message from Slack channel. Input Field Optionality Type + Description Example @@ -296,43 +320,40 @@ Get a reaction of a message from Slack channel. **token** Required - secret + Secret + The Slack bot token to use. This should be passed as a secret syntax. Refer to [Add Slack configuration](/docs/alerts/get-notified/notification-integrations/) for instructions on setting up a token. `${{ :secrets:slackToken }}` **channelID** Required - string + String + The channelID, to get the message reactions. See [`reactions.get` method](https://docs.slack.dev/reference/methods/reactions.get/#arg_channel) `C063JK1RHN1` **timeout** Optional - int + Int + The time in seconds for how long to wait for any reaction. Default is 60s, maximum allowed is 600s (10min). 60 **threadTs** Required - string + String + Timestamp belonging to message, used to get reaction of that message. `.` **selectors** Optional - list + List + The selectors to get the only specified parameters as output. `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` - - - - **token**: The Slack bot token to use. This should be passed as a secret syntax. Refer to [Add Slack configuration](/docs/autoflow/overview#add-the-slack-integration) for instructions on setting up a token. - - **channelID**: The channelID to get the message reactions. - - **timeout**: The time in seconds for how long to wait for any reaction. Default is 60s, maximum allowed is 600s (10min). - - **threadTs**: Timestamp belonging to message, used to get reaction of that message. - - **selectors**: The selectors to get the only specified parameters as output. - @@ -341,21 +362,31 @@ Get a reaction of a message from Slack channel. Output Field Type + Description Example - **reactions** - list - `` - + **reactions** + List + List of elements with all the reactions captured or an empty list if timeout occurred. + `` + + + **success** + Boolean + Status of the request + `true / false` + + + **errorMessage** + String + Failure reason as message + `Invalid slack token` + - - - - **reactions**: List of elements with all the reactions captured or an empty list if timeout occurred. - @@ -375,12 +406,12 @@ Get a reaction of a message from Slack channel. name: GetReactions steps: - - name: getReactions + - name: getReactions type: action action: slack.chat.getReactions version: 1 inputs: - token: ${{ :secrets:slackToken }} + token: ${{ :secrets:dn_staging_slack_token }} channelID: ${{ .steps.promptUser.outputs.channelID }} threadTs: ${{ .steps.promptUser.outputs.threadTs }} timeout: ${{ .workflowInputs.timeout }} @@ -412,26 +443,23 @@ steps: ```json [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } -] -``` - -Or if it is timed out: - -```json + { + "name": "grinning", + "users": [ + "W222222" + ], + "count": 1 + }, + { + "name": "question", + "users": [ + "W333333" + ], + "count": 1 + } + ] + +or if it is timed out, [] ``` diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/script-run.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/script-run.mdx new file mode 100644 index 00000000000..675f3050907 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/script-run.mdx @@ -0,0 +1,218 @@ +--- +title: "Auth JWT actions" +tags: + - workflow automation + - workflow + - workflow automation actions + - Auth actions + - Auth JWT actions +metaDescription: "A list of available auth jwt actions in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for authentication actions available in the workflow automation actions catalog. These actions enable you to create and manage JSON Web Tokens (JWT) for secure authentication in your workflows. + + + + Execute a python script and returns the response to a workflow. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input FieldOptionalityTypeDescriptionExample
**script**RequiredStringAny data transformation script + script: | + print("Hello, World!") +
**runtime**RequiredEnumRun time version of script`PYTHON_3_13`
**parameters**OptionalListlist of parameters to be used in script`parameters: ["--a", "10", "--b", "5"]`
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Output FieldDatatypeExamples
**success**Boolean`true/false`
**payload**Object`"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"`
**errorMessage**String`parsing error at line 9"`
+ + + + + + + + + + + + + + +
Example
+ ```yaml + name: script-workflow + + steps: + - name: runScript + type: action + action: script.run + version: 1 + inputs: + script: | + import json + import argparse + + p = argparse.ArgumentParser() + p.add_argument("--a", type=int, required=True) + p.add_argument("--b", type=int, required=True) + args = p.parse_args() + # Data transformation: output original, squared, and sum + result = { + "original": {"a": args.a, "b": args.b}, + "transformed": {"a_squared": args.a ** 2, "b_squared": args.b ** 2}, + "sum": args.a + args.b + } + print(json.dumps(result)) + parameters: ["--a", "10", "--b", "5"] + runtime: PYTHON_3_13 + - name: logOutput + type: action + action: newrelic.ingest.sendLogs + version: 1 + inputs: + logs: + - message: "Hello from script testing : ${{ .steps.runScript.outputs.payload }}" + ``` +
+ + + + + + +## What script.run can do + +### Supported python version + +- PYTHON_3_13 runtime with full language features + +### Allowed imports + +```yaml + "python-dateutil", + "simplejson", + "re", + "math", + "decimal", + "json", + "datetime", + "collections", + "itertools", + "functools", + "operator", + "string", + "argparse" +``` + +### Data handling + +- Parse and transform JSON data structures +- Process complex strings and perform text manipulation +- Format output as tables, markdown, or structured data + +### Parameter Ppssing + +- Pass simple values via command-line arguments with argparse + +## What script.run cannot do + +### Restricted imports + +- `base64` - Not allowed for security reasons +- `sys` - Not allowed for security reasons +- `os` - System operations restricted +- Most third-party libraries not included in Python 3.13 stdlib + +### Parameter limitations + +- Cannot pass complex JSON as command-line parameters (causes "Unsafe script argument" error) +- Cannot pass strings with special characters via parameters + +### Network/External access + +- No network calls or external API access +- No file system access outside script execution \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime.mdx new file mode 100644 index 00000000000..0d6954f45ff --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime.mdx @@ -0,0 +1,246 @@ +--- +title: "Utilities - DateTime" +tags: + - workflow automation + - workflow + - workflow automation actions + - utility actions + - Utilities - DateTime +metaDescription: "A list of available utilities - datetime in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for utilities - datetime available in the workflow automation actions catalog. These actions enable you to date and time utilities. + +## Utility actions + + + + This action is used to transform from epoch timestamp to date/time. Possible references: + + * https://en.wikipedia.org/wiki/List_of_tz_database_time_zones + * https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS + +Refer [fromEpoch](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) for more information. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
InputOptionalityTypeDescription
**timestamp**RequiredIntAn integer representing epoch timestamp. **Note**: *UNIX epochs are the number of seconds after 1st Jan 1970, midnight UTC (00:00)*
**timestampUnit**OptionalstringA string representing unit of provided timestamp. Acceptable values: SECONDS, MILLISECONDS(DEFAULT)
**timezoneId**OptionalString + A string representing timezone for desired date/time, default: UTC + +

+ For more information on supported zoneIds refer: [ZoneId (Java Platform SE 8 )](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html) +

+
**pattern**OptionalString + A string representing pattern for desired datetime, + +

default: `ISO-8601`

+ +

+ For more information on supported patterns refer: [DateTimeFormatter (Java Platform SE 8 )](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) +

+
**selectors**OptionalListThe selectors to get the only specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldOptionalityDatatypeDescription
**date**RequiredStringA string representation of date.
**time**RequiredStringA string representation of time.
**datetime**RequiredStringA string representation of datetime.
**timezone**RequiredMapA map representation of timezoneId and abbreviation.
**success**BooleanStatus of the request
**errorMessage**StringFailure reason as message
+ + + + + + + + + + + + + + + + + + +
ExampleWorkflow InputOutputs
+ ```yaml + name: from_epoch + + workflowInputs: + timestamp: + type: Int + timestampUnit: + type: String + timezoneId: + type: String + pattern: + type: String + + steps: + - name: epochTime + type: action + action: utils.datetime.fromEpoch + version: 1 + inputs: + timestamp: ${{ .workflowInputs.timestamp }} + timezoneId: ${{ .workflowInputs.timezoneId }} + pattern: ${{ .workflowInputs.pattern }} + timestampUnit: ${{ .workflowInputs.timestampUnit }} + selectors: + - name: date + expression: ".date" + - name: time + expression: ".time" + - name: datetime + expression: ".datetime" + - name: timezone + expression: ".timezone" + ``` + + ```yaml + mutation { + autoflowsStartWorkflowRun( + accountId: 11933347 + definition: { name: "from_epoch" } + workflowInputs: [ + {key: "timestamp", value: "1738236424003"} + {key: "timestampUnit", value: "MILLISECONDS"} + {key: "pattern", value: "yyyy-mm-dd HH:SS"} + {key: "timezoneId", value: "Asia/Kolkata"} + ] + ) { + runId + } + } + ``` + + ```yaml + { + "success": true + "date": "2025-01-30", + "time": "16:57:04.003" + "datetime": "2025-57-30 16:00", + "timezone": { + "abbreviation": "IST", + "id": "Asia/Kolkata" + } + } + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform.mdx new file mode 100644 index 00000000000..a62a77d605e --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform.mdx @@ -0,0 +1,218 @@ +--- +title: "Utilities - Transform" +tags: + - workflow automation + - workflow + - workflow automation actions + - utility actions + - Utilities - Transform +metaDescription: "A list of available utilities - transform in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for utilities - transform available in the workflow automation actions catalog. These actions enable you to data transformation utilities. + + + + This action is used to transform various type of input (JSON, map) to a CSV format. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
InputOptionalityTypeDescription
**data**RequiredanyA string representing a data to transform into CSV, typically a JSON string or a map.
**selectors**OptionalListThe selectors to get the only specified parameters as output.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldOptionalityDatatypeDescription
**csv**RequiredstringA CSV representation of the data received.
**success**BooleanStatus of the request
****StringFailure reason as message
+ + + + + + + + + + + + + + + + + + +
ExampleWorkflow InputOutputs
+ ```yaml + name: nrqltocsv + + steps: + - name: queryForLog + type: action + action: newrelic.nrql.query + version: 1 + inputs: + accountIds: ['${{ .workflowInputs.accountId }}'] + query: ${{ .workflowInputs.nrql }} + + - name: csv1 + type: action + action: utils.transform.toCSV + version: 1 + inputs: + data: ${{ .steps.queryForLog.outputs.results | tostring }} + selectors: + - name: csv + expression: ".csv" + ``` + + ```yaml + mutation { + startWorkflowRun( + accountId: 11933347 + definition: { + name: "nrqltocsv", + } + workflowInputs: [ + {key: "accountId" value: "11933347"} + {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'temporal-workflow-worker%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} + ] + ) + { runId } + } + ``` + + ```yaml + error.class,error.message,query,request.uri,timestamp,transactionName + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561445470,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561445470,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561445470,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561445470,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561445470,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561445470,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561445470,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561445470,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439931,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439931,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439931,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439931,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439930,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439930,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439930,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439930,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439770,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439770,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439770,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439770,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561439769,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439560,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439560,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439559,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439559,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439559,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561439473,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421659,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421659,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421659,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421659,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421659,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421659,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421659,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421659,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421648,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421648,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421648,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421648,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561421648,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421648,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421648,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561421648,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561412587,Unknown + "java.lang.RuntimeException","java.net.UnknownHostException: temporal-frontend.temporal.svc.cluster.local: Name or service not known",,,1720561412587,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561412587,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561412587,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561412587,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561412587,Unknown + "io.grpc.StatusRuntimeException","UNAVAILABLE: Unable to resolve host temporal-frontend.temporal.svc.cluster.local",,,1720561412587,Unknown + ``` +
+ + + + + \ No newline at end of file diff --git a/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid.mdx b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid.mdx new file mode 100644 index 00000000000..2f38b3dd294 --- /dev/null +++ b/src/content/docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid.mdx @@ -0,0 +1,138 @@ +--- +title: "Utilities - UUID" +tags: + - workflow automation + - workflow + - workflow automation actions + - utility actions + - Utilities - UUID +metaDescription: "A list of available utilities - uuid in the actions catalog for workflow definitions" +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +This page provides a comprehensive reference for utilities - uuid available in the workflow automation actions catalog. These actions enable you to uuid generation utilities. + + + + + Generate an RFC-compliant V4 uuid. Uses Temporal workflow's deterministic PRNG making it safe for use within a workflow. Refer to [Namespace: workflow | Temporal TypeScript SDK API Reference](https://typescript.temporal.io/api/namespaces/workflow?&_ga=2.223881945.39829224.1686648936-167080156.1680123165#uuid4) for more information. + + + + + Inputs + + + + Outputs + + + + Example + + + + + + + + + + + + + + + + + + + + + +
InputOptionalityDatatypeDescription
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldDatatypeDescription
**uuid**string
**selectors**ListThe selectors to get the only specified parameters as output.
**success**BooleanStatus of the request.
**errorMessage**StringFailure reason as message.
+ + + + + + + + + + + + + + + + +
Workflow DefinitionOutputs
+ ```yaml + name: generateUUID + steps: + - name: generateUUID + type: action + action: utils.uuid.generate + version: 1 + inputs: + selectors: + - name: uuid + expression: ".uuid" + ``` + + ```yaml + { + "uuid": "-------------------------------", + "success": true + } + ``` +
+ + + + + diff --git a/src/content/docs/workflow-automation/setup-and-configuration/create-destinations.mdx b/src/content/docs/workflow-automation/setup-and-configuration/create-destinations.mdx index 4b3a760e1e1..07a5c8a8c64 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/create-destinations.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/create-destinations.mdx @@ -105,7 +105,7 @@ Before configuring notifications, ensure you have: - A workflow created in your account (from [template](/docs/workflow-automation/create-a-workflow-automation/use-a-template) or [custom-built](/docs/workflow-automation/create-a-workflow-automation/create-your-own)). - Credentials for your notification channel (Slack bot token, PagerDuty API key, etc.). - - Credentials stored in [secrets manager](/docs/infrastructure/host-integrations/installation/secrets-management/). + - Credentials stored in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). ## Setup a destination [#set-the-destination] diff --git a/src/content/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials.mdx b/src/content/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials.mdx index 4f82f75ad8a..9130d4b0b87 100644 --- a/src/content/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials.mdx +++ b/src/content/docs/workflow-automation/setup-and-configuration/set-up-aws-credentials.mdx @@ -180,7 +180,7 @@ Choose the method that matches your use case from the table above: 4. Save this ARN securely—you'll paste it directly into workflow configurations - **Important:** Role ARNs go directly in workflow inputs—don't store them in secrets manager. They're not sensitive credentials; they're resource identifiers. + **Important:** Role ARNs go directly in workflow inputs—don't store them in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). They're not sensitive credentials; they're resource identifiers. The role is now configured. Use the ARN in workflow configurations that require AWS access. @@ -228,12 +228,12 @@ Choose the method that matches your use case from the table above: ### Store credentials securely - Never hardcode AWS credentials in workflows. Store them in New Relic's [secrets manager](/docs/infrastructure/host-integrations/installation/secrets-management/) instead. + Never hardcode AWS credentials in workflows. Store them in New Relic's [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) instead. 1. Open the [NerdGraph GraphiQL explorer](https://one.newrelic.com/nerdgraph-graphiql) 2. Run this mutation to store your Access Key ID (replace the placeholder values): - ```graphql + ```yaml mutation { secretsManagementCreateSecret( scope: {type: ACCOUNT id: "YOUR_NR_ACCOUNT_ID"} @@ -249,7 +249,7 @@ Choose the method that matches your use case from the table above: 3. Run another mutation for your Secret Access Key: - ```graphql + ```yaml mutation { secretsManagementCreateSecret( scope: {type: ACCOUNT id: "YOUR_NR_ACCOUNT_ID"} @@ -313,7 +313,7 @@ Choose the method that matches your use case from the table above: } ``` - 3. Store all three credentials in secrets manager: + 3. Store all three credentials in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager): - `AccessKeyId` store as `awsAccessKeyId` - `SecretAccessKey` store as `awsSecretAccessKey` - `SessionToken` store as `awsSessionToken` @@ -331,19 +331,19 @@ Choose the method that matches your use case from the table above: ### IAM role (recommended) - Paste the role ARN directly into workflow inputs—no secrets manager needed: + Paste the role ARN directly into workflow inputs—no [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) needed: ```yaml awsRoleArn: arn:aws:iam::123456789012:role/NewRelicWorkflowAutomationRole ``` - + Role ARNs are resource identifiers, not sensitive credentials. Don't store them in secrets manager—paste them directly into workflow configurations. ### IAM user or session tokens - Reference secrets manager for access keys: + Reference [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) for access keys: ```yaml awsAccessKeyId: ${{ :secrets:awsAccessKeyId }} diff --git a/src/content/docs/workflow-automation/troubleshooting.mdx b/src/content/docs/workflow-automation/troubleshooting.mdx index f89a4b510f6..07df7e7161f 100644 --- a/src/content/docs/workflow-automation/troubleshooting.mdx +++ b/src/content/docs/workflow-automation/troubleshooting.mdx @@ -50,7 +50,7 @@ This page provides solutions to common issues you might encounter when using Wor --role-arn "arn:aws:iam::YOUR_ACCOUNT:role/YOUR_ROLE" \ --role-session-name "WorkflowAutomationSession" ``` -2. **For access keys:** Verify both the Access Key ID and Secret Access Key are correctly stored in secrets manager. Re-check the values in [NerdGraph GraphiQL explorer](https://one.newrelic.com/nerdgraph-graphiql). +2. **For access keys:** Verify both the Access Key ID and Secret Access Key are correctly stored in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager). Re-check the values in [NerdGraph GraphiQL explorer](https://one.newrelic.com/nerdgraph-graphiql). 3. **Check secrets syntax:** Ensure you're using `${{ :secrets:keyName }}` format, not `${{ secrets.keyName }}`. The colon prefix (`:secrets:`) is required. ### Can't find my role ARN @@ -196,7 +196,7 @@ For detailed instructions on viewing logs and execution history, see [Monitor wo 3. **Verify bot is in channel**: Add the bot to the target channel: - Type `/invite @YourBotName` in the channel - Confirm the bot appears in the member list -4. **Check token in secrets**: Verify the Slack token stored in secrets manager is correct and hasn't expired. +4. **Check token in secrets**: Verify the Slack token stored in [secrets manager](/docs/workflow-automation/limitations-and-faq/workflow-best-practices/#use-secrets-manager) is correct and hasn't expired. ### AWS Systems Manager operations fail diff --git a/src/content/docs/workflow-automation/workflow-automation-apis/create-workflow-definition.mdx b/src/content/docs/workflow-automation/workflow-automation-apis/create-workflow-definition.mdx index 061dd4779d8..8476a99e307 100644 --- a/src/content/docs/workflow-automation/workflow-automation-apis/create-workflow-definition.mdx +++ b/src/content/docs/workflow-automation/workflow-automation-apis/create-workflow-definition.mdx @@ -15,7 +15,7 @@ This API is used to create a workflow definition. It returns an error if the wor Use the [Query Builder](https://one.newrelic.com/nerdgraph-graphiql?state=c8579e50-f154-fec6-22b8-f9fdcfc1990a) to create and edit a workflow. See [NerdGraph API explorer](/docs/apis/nerdgraph/get-started/nerdgraph-explorer). -```graphiql +```yaml mutation { workflowAutomationCreateWorkflowDefinition( scope: { diff --git a/src/content/docs/workflow-automation/workflow-automation-apis/definition-schema.mdx b/src/content/docs/workflow-automation/workflow-automation-apis/definition-schema.mdx index 1e9dabe889f..f2e23534476 100644 --- a/src/content/docs/workflow-automation/workflow-automation-apis/definition-schema.mdx +++ b/src/content/docs/workflow-automation/workflow-automation-apis/definition-schema.mdx @@ -2,7 +2,7 @@ title: Workflow definition schema tags: - workflow automation - - workflow schems + - workflow schemas - workflow automation API metaDescription: "Workflow definitions are written in YAML. Keys use a camelCase naming convention." freshnessValidatedDate: never @@ -109,19 +109,19 @@ Workflow definitions are written in YAML. Keys use a `camelCase` naming conventi - **Type**: Map of values (includes [expressions]()) - **Description**: - The inputs to pass to the action function. The specific inputs accepted are defined by each action. - - Inputs can use expressions. See the [Expressions Strings]() section for details. + - Inputs can use expressions. See the [Expression Strings]() section for details. No sensitive data (no API keys or secrets, no PII, PHI or any personally identifiable data) should be passed-in as arguments. - **`steps[*].inputs.selectors`** (Optional) - - **Type**: list of map in the form of `name` with `expression`. + - **Type**: list of maps in the form of `name` with `expression`. - **Description**: - - The `selectors` input allows to redefine the output to only return the specified elements. - - Expression can be used. See the [Expressions Strings]() section for details. + - The `selectors` input allows you to redefine the output to only return the specified elements. + - Expressions can be used. See the [Expression Strings]() section for details. - **Example** - - In the given example we are getting the `pageUrl` and `statusDescription` as response of http.get action. + - In the given example we are getting the `pageUrl` and `statusDescription` as the response from the http.get action. ```yaml name: status @@ -196,9 +196,9 @@ For more details see below: - `element` and `index` are automatically assigned as part of the loop. - - `Index` is a zero-based. + - `Index` is zero-based. - The `element` can be a complex type if you have a collection of complex elements. - - All loop variables and outputs from steps within the loop have loop-level scope. These variables are cleared after exiting the loop and accessing them outside of the loop will result in null value. Loop can access variables that are outside of the loop if it’s previously defined. + - All loop variables and outputs from steps within the loop have loop-level scope. These variables are cleared after exiting the loop and accessing them outside of the loop will result in a null value. A loop can access variables that are outside of the loop if they are previously defined. **Simple for loop on integers** @@ -341,7 +341,7 @@ For more details see below: - name: loopStep type: loop for: - in: "${{ [range(1; 5)] }}"" + in: "${{ [range(1; 5)] }}" steps: - name: step1 type: action @@ -382,7 +382,7 @@ For more details see below: ### wait - A step that causes the workflow run to wait a certain number of seconds before continuing. It can also listen for one or more signals. If no signal is received during the wait, it will proceed as normal. The signals are defined in a list. Each signal must have a corresponding next step defined. The first signal to be received is the one that will be processed. The value received for the signal will be stored in the step output for the wait step and can be used for logic our processing in later steps. + A step that causes the workflow run to wait a certain number of seconds before continuing. It can also listen for one or more signals. If no signal is received during the wait, it will proceed as normal. The signals are defined in a list. Each signal must have a corresponding next step defined. The first signal to be received is the one that will be processed. The value received for the signal will be stored in the step output for the wait step and can be used for logic or processing in later steps. - Example: @@ -436,7 +436,7 @@ Several properties accept string values with embedded expressions that are evalu jq provides the ability to access and operate on values in many ways. For example, the length of a workflow input string could be achieved with the following: `${{ .workflowInputs.myString | length }}` -To build and [test JQ](https://play.jqlang.org/) expression this tool can be used. +To validate and test your JQ expressions, use the [JQ Playground](https://play.jqlang.org/). ### Expression properties @@ -500,12 +500,12 @@ For the following examples, assume myArray has a value of [1, 2, 3]. -### Expression-Safe Pattern [#expression-safe-pattern] +### Expression-safe pattern [#expression-safe-pattern] Properties that can be used in expressions must conform to the following regex: `^[A-Za-z_][A-Za-z0-9_]*$` -### Secret References +### Secret references Secret values can be used in actions via reference strings that specify the name of a secret to look up in the Secrets Service. To reference a secret in a workflow definition, use the syntax: - `${{ :secrets: }}` for a secret not in a `namespace` @@ -513,7 +513,7 @@ Secret values can be used in actions via reference strings that specify the name An expression string can contain a mix of secret references and JQ expressions and/or multiple secret references. -Examples: +### Examples: ```yaml steps: @@ -525,8 +525,6 @@ Examples: Authorization: Bearer ${{ :secrets: }} ``` -## Examples - - Hello World ```yaml diff --git a/src/content/docs/workflow-automation/workflow-examples.mdx b/src/content/docs/workflow-automation/workflow-examples.mdx index bffd5bcea34..74913ae2b8c 100644 --- a/src/content/docs/workflow-automation/workflow-examples.mdx +++ b/src/content/docs/workflow-automation/workflow-examples.mdx @@ -11,9 +11,7 @@ freshnessValidatedDate: never This page shows common automation scenarios you can build with Workflow Automation. Use these examples as starting points for your own workflows, or explore the [template library](/docs/workflow-automation/create-a-workflow-automation/use-a-template) for ready-to-deploy solutions. -## Incident response and remediation - -### API gateway rollback +## API gateway rollback Revert API gateway configs to a previous state so you can fix errors and misconfigurations. @@ -33,7 +31,7 @@ Revert API gateway configs to a previous state so you can fix errors and misconf **Key actions**: `newrelic.nerdgraph.execute`, `slack.chat.postMessage`, `slack.chat.getReactions`, `aws.systemsManager.writeDocument`, `aws.systemsManager.startAutomation`, `aws.systemsManager.waitForAutomationStatus`, `aws.systemsManager.deleteDocument` -### EC2 instance management +## EC2 instance management Automate provisioning, scaling, and termination of EC2 instances for optimal performance and cost. @@ -54,7 +52,7 @@ Automate provisioning, scaling, and termination of EC2 instances for optimal per **Key actions**: `newrelic.nerdgraph.execute`, `newrelic.nrdb.query`, `slack.chat.postMessage`, `slack.chat.getReactions`, `aws.systemsManager.writeDocument`, `aws.systemsManager.startAutomation`, `aws.systemsManager.waitForAutomationStatus`, `aws.systemsManager.deleteDocument`, `utils.datetime.fromEpoch`, `utils.uuid.generate` -### Deployment rollback +## Deployment rollback Rollback deployment if entity becomes unhealthy and notify with either AWS SQS or HTTP. @@ -74,9 +72,7 @@ Rollback deployment if entity becomes unhealthy and notify with either AWS SQS o **Key actions**: `newrelic.nerdgraph.execute`, `newrelic.ingest.sendLogs`, `aws.execute.api` (sqs.send_message), `http.post` -## Data processing and reporting - -### Send a report to Slack +## Send a report to Slack Send a NRQL query output as a CSV file on Slack. @@ -91,7 +87,7 @@ Send a NRQL query output as a CSV file on Slack. **Key actions**: `newrelic.nrdb.query`, `utils.transform.toCSV`, `slack.chat.postMessage` -### JSON Parsing +## JSON Parsing Parses the New Relic public status API JSON (HTTP) and optionally logs operational and non-operational components. @@ -108,6 +104,153 @@ Parses the New Relic public status API JSON (HTTP) and optionally logs operation **Key actions**: `http.get`, `newrelic.ingest.sendLogs` +## REST API polling and logging + +Poll a REST API endpoint, loop through results, and log data to New Relic. + + +**Key Point:** You don't need to use selectors if you want the full payload. Most workflow tools let you reference the complete response object directly. + + +### Simple GET and Log + +For a basic use case of polling an API and logging the full response: + +**What this workflow does:** +- Trigger: Schedule (e.g., every 5 minutes) or you can use Run for manual +- HTTP Request Step: + - Method: GET + - URL: https://pokeapi.co/api/v2/pokemon + - Save full response body to a variable (e.g., `{{.http_response}}`) +- Log/Create Event Step: + - Send the entire `{{.http_response.body}}` as the payload + - No selectors needed - just pass through the raw JSON + +### REST API with loops and selectors + +This example collects all results from an API, loops through them, makes individual HTTP calls, and logs extracted data. + +**What this workflow does:** +- Fetches all results from a REST API endpoint +- Loops through each result in the response +- Makes individual API calls for each item using data from the loop +- Extracts specific fields from each response using selectors +- Logs the extracted data to New Relic with custom attributes + +**Requirements:** +- Access to a REST API endpoint +- Permissions to send logs via newrelic.ingest.sendLogs + +**Key actions**: `http.get`, `newrelic.ingest.sendLogs` + +```yaml +name: pokemon_workflow +description: '' +steps: + - name: get_all_pokemons + type: action + action: http.get + version: '1' + inputs: + url: https://pokeapi.co/api/v2/pokemon + selectors: + - name: pokemons + expression: .responseBody | fromjson.results + - name: pokemon_loop + type: loop + for: + in: ${{ .steps.get_all_pokemons.outputs.pokemons }} + steps: + - name: get_individual_pokemon + type: action + action: http.get + version: '1' + inputs: + url: ${{ .steps.pokemon_loop.loop.element.url }} + selectors: + - name: pokemon_name + expression: .responseBody | fromjson.name + - name: pokemon_id + expression: .responseBody | fromjson.id + - name: pokemon_stats + expression: .responseBody | fromjson.stats + - name: log_pokemon_info + type: action + action: newrelic.ingest.sendLogs + version: '1' + inputs: + logs: + - message: >- + Pokemon name is: ${{ + .steps.get_individual_pokemon.outputs.pokemon_name}}, Id: ${{ + .steps.get_individual_pokemon.outputs.pokemon_id}} + attributes: + pokemon_stats: ${{ .steps.get_individual_pokemon.outputs.pokemon_stats}} + next: continue + next: end +``` + +### REST API to CSV conversion + +This example illustrates using the full response without selectors, converting API data to CSV, and sharing it via Slack. + +**What this workflow does:** +- Fetches current time data from World Time API based on timezone input +- Converts the full JSON response to CSV format +- Logs the CSV data to New Relic +- Posts the CSV file to a Slack channel + +**Requirements:** +- Access to a REST API endpoint +- Permissions to send logs via newrelic.ingest.sendLogs +- A configured Slack app with a token and target channel + +**Key actions**: `http.get`, `utils.transform.toCSV`, `newrelic.ingest.sendLogs`, `slack.chat.postMessage` + +```yaml +name: jsontocsv + +workflowInputs: + timezone: + type: String + defaultValue: 'America/Los_Angeles' + +steps: + - name: getCurrentTime + type: action + action: http.get + version: 1 + inputs: + url: 'https://worldtimeapi.org/api/timezone/${{ .workflowInputs.timezone }}' + + - name: csv1 + type: action + action: utils.transform.toCSV + version: 1 + inputs: + json: ${{ .steps.getCurrentTime.outputs.responseBody }} + + - name: logOutput + type: action + action: newrelic.ingest.sendLogs + version: 1 + inputs: + logs: + - message: 'CSV: ${{ .steps.csv1.outputs.csv }}' + + - name: postCsv + type: action + action: slack.chat.postMessage + version: 1 + inputs: + channel: test-channel-workflow + text: "Current Date details" + attachment: + filename: 'file.csv' + content: ${{ .steps.csv1.outputs.csv }} + token: ${{ :secrets:dn_staging_slack_token }} +``` + ## Available template workflows The templates listed above are available directly in the New Relic Workflow Automation UI. To access them: diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx deleted file mode 100644 index 92c77337bb4..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-10-02' -version: 'Sep 26 - Oct 02, 2025' -translationType: machine ---- - -### Cambios importantes - -* [Documentación de control de flota](/docs/new-relic-control/fleet-control/overview) actualizada con revisiones integrales para Kubernetes GA y la vista previa pública de Hosts, incluidas nuevas capacidades de administración de flotas, funciones de seguridad mejoradas y procedimientos de configuración actualizados. -* [Documentación de control del agente](/docs/new-relic-control/agent-control/overview) actualizada con revisiones exhaustivas para la vista previa pública, incluidas opciones de configuración mejoradas, capacidades de monitoreo y orientación para la resolución de problemas. -* [Documentación de marcas y medidas](/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures/) reestructurada para disponibilidad general con detalles completos de características y orientación de implementación. -* [Flujo de alerta de trabajo](/docs/alerts/admin/rules-limits-alerts) mejorado con nuevos pasos de validación de email y límites de destino. -* Se actualizó el [nombre del modelo de precios](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management/) de "New Relic Compute Public Preview o planes Core calcula" a "Planes Advanced o Core calcula". - -### Cambios menores - -* Instrucciones [de integración completa de WordPress](/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration) actualizadas para un proceso de configuración mejorado. -* Documentación [de variables de plantilla de dashboard](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables) mejorada con captura de pantalla actualizada y ejemplos mejorados. -* [Consulta de uso actualizada y alertas](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) con capacidades mejoradas de monitoreo de uso de cálculo. -* [Documentación UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-ui) mejorada con función integral de gestión de cálculos. -* Se corrigió una referencia de ancla duplicada en [la configuración del agente .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration). -* [Integración de notificaciones](/docs/alerts/get-notified/notification-integrations) actualizada con gestión mejorada de destinos de email. -* Documentación [de AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink) actualizada con mayor claridad del lenguaje para las regiones admitidas y los requisitos de configuración de VPC. -* Identificador de publicaciones de novedades actualizado para la gestión de contenidos. - -### Notas de la versión - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Agente deNode.js v13.4.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0): - - * Se actualizó amqplib y cassandra-driver instrumentación para suscribir al evento emitido. - * Reporte de compatibilidad del agente Node.js actualizado con las últimas versiones de paquetes compatibles. - * Se agregaron optimizaciones WASM para rastrear ganchos. - * Requisitos JSDoc mejorados para una mejor documentación del código. - - * [Agente dePython v11.0.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000): - - * Se eliminó la compatibilidad con Python 3.7 y se dejaron obsoletas varias API legacy. - * Se agregó nueva instrumentación para AutoGen y Pyzeebe framework. - * Se introdujeron los intervalos con nombre MCP (Protocolo de contexto de modelo) para el monitoreo de IA. - * Se corrigió el fallo en psycopg y se cercioró que los intervalos de MCP solo se registren cuando el monitoreo de IA está habilitado. - - * [agente de infraestructura v1.69.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690): - - * Se actualizó el SDK de AWS de V1 a V2 y la biblioteca de API de Docker de v26 a v28. - * Se solucionó el monitoreo de CPU Windows fijo para instancias con múltiples grupos de CPU (más de 64 núcleos). - * Manejo mejorado del formato de log con soporte de nivel de log predeterminado. - - * [Integración Kubernetes v3.45.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3): - - * Incluido en las versiones de gráficos newrelic-infrastructure-3.50.3 y nri-bundle-6.0.15. - - * [NRDOT v1.5.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-25): - - * Se agregó metricsgenerationprocessor a nrdot-recolector-k8s para una recopilación de métricas mejorada. - - * [Agente .NET v10.45.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0): - - * Se agregó un nuevo muestreador basado en la relación TraceId para el rastreo distribuido basado en la implementación de OpenTelemetry. - * Se corrigieron excepciones en el análisis de cadenas de conexión MSSQL que podían deshabilitar el almacenamiento de datos instrumentación. - * Se resolvieron los problemas de instrumentación "Consumir" de Kafka para una mejor compatibilidad con la instrumentación personalizada. - - * [Aplicación móvil New Relic para Android v5.30.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5308): - - * Corrección de errores y mejoras para mejorar el rendimiento de la aplicación móvil. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx deleted file mode 100644 index 4c1115257dd..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-11' -version: 'version: October 4-10, 2024' -translationType: machine ---- - -### Nuevos documentos - -* [No aparecen datos de fallas en la versión de lanzamiento (Android)](/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears) le indica qué hacer si no ve datos relacionados con una falla de la aplicación en la UI New Relic. -* [¿Cómo puedo usar WSL y CodeStream?](/docs/codestream/troubleshooting/using-wsl) proporciona instrucciones paso a paso sobre el uso del Subsistema de Windows para Linux (WSL) con CodeStream. -* [`UserAction`](/docs/browser/browser-monitoring/browser-pro-features/user-actions) es un nuevo tipo de evento en el monitoreo de navegador que lo ayuda a comprender el comportamiento del usuario con su aplicación sitio web. -* [WithLlmCustomAttributes (API Python del agente)](/docs/apm/agents/python-agent/python-agent-api/withllmcustomattributes-python-agent-api) describe la nueva API del administrador de contexto, incluidos sus requisitos, parámetros, valores de retorno y un ejemplo de uso. - -### Cambios menores - -* Se agregó un centro de datos extremo de EE. UU. y la UE para el agente APM en [el extremo de telemetríaNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). - -* Instrucciones actualizadas sobre cómo encontrar logs del lado del cliente de CodeStream al usar [Visual Studio](/docs/codestream/troubleshooting/client-logs/#visual-studio). - -* Se reformularon [las opciones de notificación para silenciar las reglas](/docs/alerts/get-notified/muting-rules-suppress-notifications/#notify) para lograr mayor claridad. - -* Se actualizó la información de compatibilidad para los siguientes paquetes en [los módulos instrumentado](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrumented-modules): - - * `@aws-sdk/client-bedrock-runtime` - * `@aws-sdk/client-dynamodb` - * `@aws-sdk/client-sns` - * `@aws-sdk/client-sqs` - * `@aws-sdk/lib-dynamodb` - * `@grpc/grpc-js` - * `@langchain/core` - * `@smithy/smithy-client` - * `next` - * `openai` - -* Se corrigió el segundo centro de datos extremo de la UE a `212.32.0.0/20` en [bloques de IP de ingesta de datos](https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#ingest-blocks). - -* Se especifica que el servicio de alertas de New Relic se ejecuta en los Estados Unidos, independientemente de si sus datos están almacenados en [el centro de datos de New Relic en la UE o en los EE. UU](/docs/alerts/overview/#eu-datacenter). - -* Se modificó información sobre cómo establecer un [atributo personalizado](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes). Además, se actualizaron los ejemplos. - -* Se actualizaron los pasos para [dejar de reconocer y cerrar un problema](/docs/alerts/get-notified/acknowledge-alert-incidents/#unacknowledge-issue). - -* Se agregó información sobre [cómo reconocer y cerrar múltiples problemas](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#bulk-actions). - -* Se amplió la introducción de [las frecuencias de actualización de gráficos](/docs/query-your-data/explore-query-data/use-charts/chart-refresh-rates) para indicar que la frecuencia de actualización solo se puede configurar si tiene el plan de precios de consumo de New Relic Compute. - -* Se corrigió la información de la versión de Seguridad de la capa de transporte (TLS) requerida en [el cifrado TLS](/docs/new-relic-solutions/get-started/networks/#tls). - -* Se actualizó el paso 6 en el procedimiento [de instalación de integraciónKubernetes ](/install/kubernetes)para que coincida con la UI actual New Relic. - -* Se destacó la importancia del evento no facturable, `InternalK8sCompositeSample`, en [la consulta de datos Kubernetes ](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#view-data), luego de la tabla. - -* Se reescribieron las instrucciones para [ver y gestionar la clave de API](/docs/apis/intro-apis/new-relic-api-keys/#keys-ui) para mayor precisión y claridad. - -* Instrucciones actualizadas sobre cómo usar el explorador de API en [Usar el explorador de API](/docs/apis/rest-api-v2/api-explorer-v2/use-api-explorer) y [enumerar el ID de la aplicación, el ID del host y el ID de la instancia](/docs/apis/rest-api-v2/get-started/list-application-id-host-id-instance-id) para que coincidan con el explorador de API actual. - -* Se agregó nuevamente el ejemplo para [correlacionar la infraestructura con OpenTelementry APM](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/#infrastructure-correlation). - -* Se señaló cómo evitar nombres de métricas duplicados al [migrar al monitoreo de integración de Azure ](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#migrate). - -### Notas de la versión - -Consulta nuestras publicaciones de Novedades para conocer nuevas características y lanzamientos: - -* [New Relic Pathpoint conecta la telemetría con los KPI empresariales](/whats-new/2024/10/whats-new-10-10-pathpoint) - -Mantener actualizado sobre nuestros lanzamientos más recientes: - -* [Bandeja de entrada de errores para Android v5.25.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-52501) - * Le permite iterar a través de errores, inspeccionar atributos perfilados y mucho más. - -* [Agente Flutter v1.1.4](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-114) - * Actualiza el agente de iOS a 7.5.2 - -* [Integración Kubernetes v3.29.6](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6) - - * Actualizaciones Ir a v1.23.2 - * Actualiza la biblioteca común para Prometheus a v0.60.0 - -* [Agente Python v10.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100) - - * Compatible con Python 3.13 - * Proporciona una nueva API de administrador de contexto - * Admite reportes de ID de Docker de Amazon ECS Fargate - * Incluye instrumentación para `SQLiteVec` - -* [Agente de Unity v1.4.1](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141) - - * Actualiza el agente nativo Android e iOS - * Contiene correcciones de errores \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx deleted file mode 100644 index 00181148419..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-18' -version: 'version: October 11-17, 2024' -translationType: machine ---- - -### Nuevos documentos - -* [Forward Kong Gateway logs](/docs/logs/forward-logs/kong-gateway/) describe cómo instalar y usar este nuevo complemento de reenvío de registros a través de la integración Kubernetes. -* [El monitoreo deAzure App Service](/docs/apm/agents/manage-apm-agents/azure/monitoring-azure-app-service/) describe cómo integrar este servicio Azure con New Relic y proporciona enlaces a instrucciones sobre cómo configurarlo para nuestro agente APM Java, .NET, Node.js y Python. -* [Introducción al explorador de datos](/docs/query-your-data/explore-query-data/query-builder/introduction-new-data-explorer/) describe cómo emplear nuestra nueva UI del explorador de datos para consultar sus datos y obtener información más profunda y valiosa sobre cómo la plataforma New Relic puede ayudarlo y resolver sus problemas. -* [Monitorear los entornos de Amazon ECS con el agente de lenguaje APM El agente de lenguaje APM](/docs/infrastructure/elastic-container-service-integration/monitor-ecs-with-apm-agents/) lo ayuda a instalar nuestro agente APM en su entorno de Amazon ECS. -* [Migrar a NRQL](/docs/apis/rest-api-v2/migrate-to-nrql/) describe cómo migrar su API REST v2 consulta a NRQL consulta. - -### Cambios importantes - -* Hemos migrado contenido de nuestro sitio de código abierto a nuestro sitio de documentación. -* Se aclaró cómo gestionar secretos con el [operador del agente de Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/). - -### Cambios menores - -* En [OpenTelemetry métrica en New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics/#otlp-summary), aclaramos que las métricas de resumen OpenTelemetry no son compatibles. -* Se actualizó una captura de pantalla en [la política de alertas recomendada y dashboards](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies/#add-recommended-alert-policy) para aclarar dónde encontrar los mosaicos Kubernetes y Google Kubernetes Engine. -* Se eliminaron los documentos de Stackato y WebFaction relacionados con el agente APM de Python, porque ya no son relevantes. -* Se agregó un nuevo monitoreo de navegador extremo a nuestro documento [de Redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Se solucionaron problemas menores en nuestros documentos de monitoreo de resolución de problemas del navegador. -* En [la sección de solución de problemas de errores de actualización en tiempo de ejecución](/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting/#scripted-api-form) se describe cómo resolver problemas al emplear tiempos de ejecución de Node más antiguos con objetos `$http`. -* En [la API del agente .NET](/docs/apm/agents/net-agent/net-agent-api/net-agent-api), agregamos `NewRelic.Api.Agent.NewRelic` a la llamada API `ITransaction` y agregamos la nueva llamada API `RecordDatastoreSegment`. - -### Notas de la versión - -Mantener actualizado sobre nuestros lanzamientos más recientes: - -* [Agente Android v7.6.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-761/) - - * Agrega soporte para el complemento Gradle Android 8.7 - * Corrige el problema de que los archivos de mapeo de ProGuard/DexGuard no se cargan correctamente - * Otras correcciones de errores - -* [Agente del browser v1.269.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0/) - - * Permite que el cargador de MicroAgent en NPM emplee API logging para capturar manualmente datos de registro - * Agrega metadatos de instrumentación a la carga de logging - * Corrige errores relacionados con el rastreo de sesión y errores de la política de seguridad de reproducción de sesión. - -* [Go agente v3.35.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0/) - - * Agrega soporte para reportes seguros de eventos de cookies - * Emplea el valor `error.Error()` para el atributo log - * Mejora la compatibilidad de URL para conexiones de servidor AMQP - * Varias correcciones de errores - -* [Extensión Lambda v2.3.14](/docs/release-notes/lambda-extension-release-notes/lambda-extension-2.3.14/) - - * Agrega una función para ignorar las comprobaciones de inicio de la extensión - * Actualiza el archivo README con información sobre cómo emplear la variable de entorno `NR_TAGS` - * Agrega soporte para la variable de entorno booleana `NEW_RELIC_ENABLED` - -* [Agente .NET v10.32.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0/) - - * Desaprobó las variables de entorno prefijadas `NEWRELIC_` - * Implementa un esquema de nombres consistente para todas las variables de entorno - * Actualiza la instrumentación de CosmosDB para admitir la última versión - -* [Tiempo de ejecución de ping v1.47.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.47.0/) - * Corrige un problema relacionado con las licencias de usuario para el script de control de tiempo de ejecución de ping para usuarios no root. - -* [Agente Python v10.2.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200/) - * Agrega el indicador de operador Azure init contenedor para admitir esa opción para monitorear aplicaciones de Azure contenedor \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx deleted file mode 100644 index 5919f7dd9cc..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-07' -version: 'November 2 - November 7, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregaron [ejemplos de control de acceso a datos de NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-data-access-control) para proporcionar ejemplos prácticos de gestión del control de acceso a datos a través de la API de NerdGraph. -* Se agregó [detección de valor atípico](/docs/alerts/create-alert/set-thresholds/outlier-detection) para brindar orientación para configurar la condición de alerta de detección de valor atípico. -* Se agregó [un catálogo de infraestructuras](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog/) para proporcionar una documentación mejorada con los requisitos previos para la configuración del monitoreo de infraestructuras. -* Se agregaron [mapas de servicios de transmisión multimedia](/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps/) para proporcionar orientación sobre la comprensión de las relaciones entre la transmisión multimedia y las entidades de navegador/móvil. -* Se agregó [una bandeja de entrada de errores para la transmisión de contenido multimedia](/docs/errors-inbox/media-streaming-group-error/) con el fin de proporcionar instrucciones para agrupar y gestionar los errores de transmisión de contenido multimedia. - -### Cambios importantes - -* Se actualizó [la configuración de control del agente](/docs/new-relic-control/agent-control/configuration) con ejemplos YAML revisados para mayor claridad y nombres de campo actualizados. -* Se actualizó [la configuración del control del agente](/docs/new-relic-control/agent-control/setup) con ejemplos de configuración YAML mejorados. -* [Reinstrumentación actualizada del control del agente](/docs/new-relic-control/agent-control/reinstrumentation) con ejemplos YAML actualizados para una mayor precisión. -* [Agente control resolución de problemas](/docs/new-relic-control/agent-control/troubleshooting) actualizado con ejemplos de configuración refinados. - -### Cambios menores - -* Se agregó información sobre la compatibilidad con MariaDB a la documentación [de requisitos de integración de MySQL](/install/mysql/). -* Se agregó [control de acceso a datos](/docs/accounts/accounts-billing/new-relic-one-user-management/data-access-control) para proporcionar una guía completa sobre cómo controlar el acceso a telemetry data mediante políticas de datos. -* Documentación actualizada [de integración de GitHub en la nube](/docs/service-architecture-intelligence/github-integration/) con los últimos detalles de configuración. -* [Documentación CLI de diagnóstico](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-360) actualizada para la versión 3.60. -* Documentación actualizada de configuración [de puertos de Vizier](/docs/ebpf/k8s-installation/) para Kubernetes. - -### Notas de la versión - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Agente Python v11.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100): - - * Se agregó compatibilidad con Python 3.14. - * Se agregaron variables de entorno para la configuración del filtro de atributos. - * Se agregó soporte para generadores asíncronos en los decoradores de errores. - * Se agregó compatibilidad con modelos adicionales en la instrumentación de AWS Bedrock, incluidos los modelos Claude Sonnet 3+ y los modelos sensibles a la región. - * Se agregó instrumentación para los nuevos métodos de AWS Kinesis, incluidos describe\_account\_settings, update\_account\_settings, update\_max\_record\_size y update\_stream\_warm\_throughput. - * Se corrigió el error RecursionError en aiomysql al usar ConnectionPool. - * Se corrigió un error por el cual las propiedades no se pasaban correctamente en el productor de kombu. - * Se corrigió un error que ocurría cuando se llamaba a shutdown\_agent desde dentro del hilo de recolección. - - * [Agente iOS v7.6.0](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760): - - * Se agregó la funcionalidad de vista previa pública Session Replay celulares. - * Se actualizó la versión de iOS requerida a iOS 16. - * Se solucionó un problema con las excepciones controladas que podía ocurrir al logging. - * Se corrigió la advertencia sobre nombres de parámetros incorrectos. - - * [Agente Android v7.6.12](/docs/release-notes/mobile-release-notes/android-release-notes/android-7612): - - * Se agregó la funcionalidad de reproducción de sesión para Jetpack Compose. - * Se publicó la versión de vista previa pública oficial de Session Replay. - * Se corrigieron varios errores de reproducción de sesiones. - - * [Integración Kubernetes v3.49.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0): - - * Consulte los cambios detallados en las notas de la versión de GitHub. - * Incluido en las versiones de gráficos newrelic-infrastructure-3.54.0 y nri-bundle-6.0.20. - - * [Logs v251104](/docs/release-notes/logs-release-notes/logs-25-11-04): - - * Se agregó compatibilidad con formatos de carga útil de log específicos de .NET. - * Se introdujo la variable de entorno NEW\_RELIC\_FORMAT\_LOGS para el procesamiento de formatos de registro específicos de .NET. - - * [Node browser runtime rc1.2](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.2): - - * Actualicé el navegador Chrome a la versión 141. - * Se corrigieron las vulnerabilidades CVE-2025-5889 para la expansión de llaves. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx deleted file mode 100644 index 68d22b14024..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-14' -version: 'November 08 - November 14, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó [el modo de consentimiento de Browser ](/docs/browser/new-relic-browser/configuration/consent-mode)para documentar la implementación de la gestión del consentimiento y así monitorear el cumplimiento de las normativas de privacidad por parte del navegador. -* Se agregaron [extensiones de Java en la conexión automática de Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach) para brindar orientación sobre la configuración para la instrumentación de Java APM en entornos de Kubernetes. -* Se agregó [Traiga su propia configuración de caché](/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache) para documentar las opciones de configuración de caché de OpenTelemetry para el rastreo distribuido. - -### Cambios importantes - -* [Inteligencia artificial de respuesta](/docs/alerts/incident-management/response-intelligence-ai) mejorada con capacidades de resumen de logs de IA para analizar alertas basadas en logs. -* Se renombró y reestructuró la documentación de Gestión de Calcular a [Gestión de Consumo](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management). -* [Configuración del agente de Java ](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file)actualizada con opciones de nomenclatura de transacciones Spring y configuración del analizador SQL. -* [Roles personalizados de integración de GCP](/docs/infrastructure/google-cloud-platform-integrations/get-started/integrations-custom-roles) actualizados con licencias revisadas para 4 servicios de Google en la nube. -* Documentación mejorada [para la resolución de problemas del MCP](/docs/agentic-ai/mcp/troubleshoot) con escenarios y soluciones de configuración del Protocolo de Contexto del Modelo. -* [Configuración mejorada del agenteRuby ](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration)con nuevas opciones de configuración de error de reintento de Sidekiq. -* Se actualizó [la instalación del agente PHP](/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian) con soporte para Debian Trixie. - -### Cambios menores - -* Se agregó compatibilidad con Java 25 a [los requisitos de compatibilidad del agente Java](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent). -* Se agregó compatibilidad con .NET 10 a [los requisitos de compatibilidad del agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). -* [Administración actualizada a nivel de servicio alertas](/docs/service-level-management/alerts-slm). -* Se actualizó [la compatibilidad del agente PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) con la información de versión de Drupal y Laravel. -* [Compatibilidad de integración de Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements) actualizada. -* [Requisitos de compatibilidad del agente Java](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent) actualizados con soporte de framework. - -### Notas de la versión - -Consulta las publicaciones de novedades para: - -* [Lanzamiento del nuevo servidor MCP New Relic en versión preliminar pública](/whats-new/2025/11/whats-new-11-05-mcp-server) - -* [New Relic valor atípico Detection en vista previa pública](/whats-new/2025/11/whats-new-11-05-outlier-detection) - -* [Resumen de alertas del log de IA (Vista previa)](/whats-new/2025/11/whats-new-11-13-AI-Log-Alert-Summarization) - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Agente Node.js v13.6.4](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4): - - * Se corrigió MessageConsumerSubscriber para finalizar correctamente las transacciones de consumo de mensajes. - * Se corrigió MessageProducerSubscriber para establecer correctamente el indicador de ejemplificación en traceparent. - * Se corrigió la prioridad de registro del middleware de Bedrock para una correcta deserialización de la carga útil. - - * [Agente Node.js v13.6.3](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3): - - * Se corrigió el manejo de la transmisión de instrumentación de OpenAI con stream\_options.include\_usage. - * Se corrigió la asignación del recuento de token de @google/GenAI a LlmCompletionSummary. - * Se corrigió la asignación de recuento token de instrumentación AWS Bedrock. - - * [agente de Java v8.25.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250): - - * Se agregó compatibilidad con Java 25. - * Se agregó compatibilidad con Logback-1.5.20. - * Se introdujo la opción de configuración de nomenclatura de transacciones de Spring Controller. - * Se agregó compatibilidad con Kotlin Coroutines v1.4+. - * Se corrigió la lógica de análisis de nombres de clases con errores. - * Se solucionó un posible problema de memoria en el logging de errores con stack de rastreo grande. - - * [Agente Ruby v9.23.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0): - - * Se agregó sidekiq.ignore\_retry\_errors Opción de configuración para controlar la captura de errores de reintento. - * Grabación de despliegue de Capistrano obsoleta (eliminación en la versión 10.0.0). - * Aplicación de configuración de ejemplificación remota para padres mejorada para una distribución de rastreo más consistente. - - * [Agente .NET v10.46.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1): - - * Se eliminó el intervalo de consumo de las transacciones en modo procesador de Azure Service Bus para mejorar la precisión. - * Se actualizó la serialización del enum ReportedConfiguration para una mayor claridad UI. - - * [Integración Kubernetes v3.50.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0): - - * Se actualizó la versión del gráfico KSM e2e a la versión 2.16. - * Se agregó compatibilidad con la métrica kube\_endpoint\_address. - * Se corrigió un problema de plantillas de priorityClassName con la compatibilidad con Windows habilitada. - - * [Sintéticos Job Manager versión 486](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-486): - - * Se corrigieron vulnerabilidades de Ubuntu y Java, incluidas CVE-2024-6763 y CVE-2025-11226. - - * [Sintéticos Ping Runtime v1.58.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.0): - - * Se corrigieron vulnerabilidades de Ubuntu y Java, incluidas CVE-2025-5115 y CVE-2025-11226. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx deleted file mode 100644 index 2ad9501aee7..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-21' -version: 'November 17 - November 21, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregaron [reglas de eliminación de migración a las reglas cloud de canalización](/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules/) para brindar una guía completa para migrar las reglas de eliminación existentes al nuevo sistema de reglas cloud de canalización. -* Se agregó [incompatibilidadPHPUnit ](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility)para brindar orientación sobre resolución de problemas para errores de falta de memoria PHPUnit versión 11+ con el agente PHP New Relic. - -### Cambios importantes - -* Se eliminó la documentación del análisis de datos de prueba de PHPUnit luego de que el agente PHP dejó de brindar soporte para PHPUnit. Reemplazado con la documentación de resolución de problemas para problemas de incompatibilidad PHPUnit. -* Se reestructuró [la búsqueda y filtrado de entidades](/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) para una mejor organización y se agregó una nueva característica de filtrado de catálogo. -* [Instalación actualizada de New Relic eBPF en entornos Kubernetes ](/docs/ebpf/k8s-installation)con opciones de configuración de desacoplamiento para la monitorización del rendimiento de la red. - -### Cambios menores - -* Se agregó información de retención de transmisión de datos de medios a la documentación [Gestionar retención de datos](/docs/data-apis/manage-data/manage-data-retention). -* Se eliminó PHPUnit de la tabla de [compatibilidad de requisitos y compatibilidad del agente PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) luego del final del soporte. -* Se corrigió el ejemplo de consulta NRQL para [consulta de uso y alertas](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). -* Se actualizó [la página de configuración de la aplicaciónBrowser ](/docs/browser/new-relic-browser/configuration/browser-app-settings-page/)con información de configuración de almacenamiento local. -* Se agregó el modo de consentimiento a la navegación de la documentación del browser. -* Se actualizaron [las configuraciones](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings) para el SDK móvil. -* Documentación [de tipos de gráficos](/docs/query-your-data/explore-query-data/use-charts/chart-types) mejorada con información adicional sobre tipos de gráficos. -* [Descripción general](/docs/agentic-ai/mcp/overview) actualizada y [solución de problemas](/docs/agentic-ai/mcp/troubleshoot) para MCP con aclaración de roles RBAC. - -### Notas de la versión - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Go agente v3.42.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0): - - * Se agregaron nuevas opciones de configuración de muestras máximas para transacciones, Insights personalizada, errores y logs. - * Se agregó soporte para MultiValueHeaders en nrlambda. - * Se eliminaron las variables no empleadas en nrpxg5. - * Se corrigió un error donde el evento de error no marcaba correctamente el error esperado. - - * [Agente .NET v10.47.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0): - - * Se agregó un mecanismo de almacenamiento de transacciones opcional para permitir que las transacciones fluyan con ExecutionContext para aplicaciones sitio web ASP.NET. - * Se solucionó la excepción de referencia nula de instrumentación de Azure Service Bus. - * Se corrigió la instrumentación de OpenAI para manejar las finalizaciones de chat cuando el parámetro de mensajes no es una matriz. - - * [AgenteNode.js v13.6.5](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5): - - * Se actualizó la instrumentación expresa para omitir el error cuando el siguiente controlador pasa por la ruta o el enrutador. - * Se actualizó MessageConsumerSubscriber para esperar a que finalice la devolución de llamada del consumidor cuando es una promesa. - - * [Agente Node.js v13.6.6](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6): - - * Se actualizó la instrumentación Express de app.use o router.use para encapsular adecuadamente todo el middleware definido. - * Se agregó configuración para distributed\_tracing.samplers.partial\_granularity y distributed\_tracing.samplers.full\_granularity. - - * [Agente PHP v12.2.0.27](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27): - - * Se agregó soporte para Laravel 12. - * Se agregó compatibilidad con Laravel Horizon en Laravel 10.x+ y PHP 8.1+. - * Se solucionó el manejo de excepciones de trabajos en cola de Laravel. - * Se actualizó la versión de golang a 1.25.3. - - * [Integración Kubernetes v3.50.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1): - - * Actualizado a la versión 3.50.1 con correcciones de errores y mejoras. - - * [Agente de infraestructura v1.71.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711): - - * Se actualizó la dependencia newrelic/nri-docker a v2.6.3. - * Se actualizó la dependencia newrelic/nri-flex a v1.17.1. - * Versión de go actualizada a 1.25.4. - * Se actualizó la dependencia newrelic/nri-prometheus a v2.27.3. - - * [Logs 25-11-20](/docs/release-notes/logs-release-notes/logs-25-11-20): - - * Se corrigió CVE-2025-53643 en lambda de AWS-log-ingestion. - * Biblioteca aiohttp actualizada a 3.13.2 y versión poética a 1.8.3. - - * [Tiempo de ejecución del browser de nodo rc1.3](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.3): - - * Actualicé el navegador Chrome a la versión 142. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx deleted file mode 100644 index ecff7051eac..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-05-24' -version: 'version: May 17-23, 2024' -translationType: machine ---- - -### Nuevos documentos - -* Nuestra nueva [integraciónApache Mesos](/docs/infrastructure/host-integrations/host-integrations-list/apache-mesos-integration) lo ayuda a monitorear el rendimiento del kernel de sus sistemas distribuidos. -* Nuestra nueva [integración Temporal en la nube](/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration) lo ayuda a monitorear y diagnosticar problemas de flujo de trabajo, namespace y aplicaciones escalables en su Temporal Cloud. -* ¿Tiene una [aplicación .NET en AWS Elastic Beanstalk](/docs/apm/agents/net-agent/install-guides/install-net-agent-on-aws-elastic-beanstalk)? Este nuevo documento de instalación muestra una ruta clara para ingerir esos datos en nuestra plataforma. - -### Cambios importantes - -* Se agregaron y actualizaron ejemplos de código de monitor con secuencias de comandos de navegador y Sintético para [el monitoreo sintético de mejores prácticas](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide) y [la referencia del navegador con secuencias de comandos de Sintético](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100). Los ejemplos de código son una de las cosas que más piden los lectores, por eso siempre nos alegra ver más. - -* En nuestros documentos de monitoreo del rendimiento de la red, muchas pequeñas actualizaciones llevaron a un cambio importante: se actualizaron los entornos compatibles con Podman en 17 documentos. - -* Se aclaró cómo funcionan [los logs live archives](/docs/logs/get-started/live-archives) y cuándo [están disponibles esos datos de registro](/docs/logs/get-started/live-archives-billing). - -* Se agregó un diagrama y variables de entorno al [instrumento de monitoreo Lambda de su capa de imagen en contenedor](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images/). - -* La API REST v1 de New Relic llegó a su fin por completo y eliminamos varios documentos relacionados con ella. - -* Un análisis masivo de nuestros documentos de monitoreo de infraestructura para: - - * Alineelo con nuestra guía de estilo. - * Eliminar contenido innecesario. - * Haga que el documento de instalación sea más visible en el panel de navegación izquierdo. - * Mejorar el flujo del documento de instalación. - -* Continúa nuestra migración del sitio de desarrolladores a documentos, con más de 30 documentos migrados esta semana. - -* A partir del 23 de mayo de 2024, el monitoreo de IA admite Java. Actualizamos varios documentos de monitoreo de IA para reflejar esta importante actualización. - -### Cambios menores - -* [Controles de seguridad de almacenamiento de datos en la nube actualizados para garantizar la privacidad](/docs/security/security-privacy/data-privacy/security-controls-privacy/#cloud-data-storage) con un reporte de cumplimiento de enlaces. -* Simplificamos nuestros pasos [de instalación de yum .NET](/install/dotnet/installation/linuxInstall2/#yum). -* Se actualizó la documentación [de compatibilidad de Python](/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent/#basic) para mostrar que ahora admitimos Python 3.12. -* Se actualizó [la compatibilidad con .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) para agregar que admitimos la versión `Elastic.Clients.Elasticsearch` 8.13.12 de almacenamiento de datos. -* Se actualizó la tabla de módulos instrumentados [de compatibilidad del agente APM Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) -* Se actualizaron las regiones y zonas compatibles con [AWS Privatelink](/docs/data-apis/custom-data/aws-privatelink) extremo. -* El agente de infraestructura ahora es compatible con Ubuntu 24.04 (Noble Numbat), pero aún no admitimos infraestructura más logs en esta versión de Ubuntu. -* Si usa [CyberARK y Microsoft SQL Server](/docs/infrastructure/host-integrations/installation/secrets-management/#cyberark-api) con autenticación de Windows, aclaramos que debe preceder su nombre de usuario con su dominio. -* En nuestra [configuración del agente APM .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration/#error-ignoreErrors), agregamos variables de entorno para los códigos de estado ignorados y esperados. -* Al [emplear sus gráficos](/docs/query-your-data/explore-query-data/use-charts/use-your-charts), aclaró lo que queremos decir con KB, MB, GB y TB. (Empleamos el Sistema Internacional de Unidades, que emplea potencias de 10 para los cálculos). -* En [la configuración de email](/docs/accounts/accounts/account-maintenance/account-email-settings), aclaramos los caracteres permitidos y los límites en las direcciones de email de los usuarios New Relic. -* Se agregó la URL del servicio validador IAST extremo a la tabla de telemetría extremo New Relic de nuestras [redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Se agregó una sugerencia sobre cómo monitorear múltiples versiones de trampas SNMP en un host en [el monitoreo de rendimiento de SNMP](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring). -* Si desea ampliar su [instrumentación de Node.js para incluir Apollo Server](/docs/apm/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs/#extend-instrumentation), agregamos enlaces a archivos README de GitHub útiles. -* Se agregó información de compatibilidad .NET a [los requisitos y compatibilidad del monitoreo de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#compatibility). - -### Notas de la versión y publicaciones de novedades - -* [Agente del browser v1.260.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1) -* [Agente de infraestructura v1.52.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523) -* [Agente de Java v8.12.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120) -* [Administrador de trabajos v370](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-370) -* [Integración Kubernetes v3.28.7](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7) -* [Aplicación móvil para Android v5.18.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5180) -* [Agente .NET v10.25.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0) -* [Tiempo de ejecución de la API de Node v1.2.1](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.1) -* [Tiempo de ejecución de la API de Node v1.2.58](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.58) -* [Tiempo de ejecución de la API de Node v1.2.67](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.67) -* [Tiempo de ejecución de la API de Node v1.2.72](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.72) -* [Tiempo de ejecución de la API de Node v1.2.75](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.75) -* [Tiempo de ejecución de la API de Node v1.2.8](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.8) -* [Agente Node.js v11.17.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0) -* [Agente PHP v10.21.0.11](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11) \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx deleted file mode 100644 index 605c828833c..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-06-28' -version: 'version: June 21-27, 2024' -translationType: machine ---- - -### Nuevos documentos - -* La característica de [aplicación que no responde](/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding) de monitoreo de celulares lo ayuda a rastrear y analizar cuándo y por qué su aplicación Android está bloqueada durante más de cinco segundos. -* Los nuevos documentos API de monitoreo de navegador [`log()`](/docs/browser/new-relic-browser/browser-apis/log) y [`wrapLogger()`](/docs/browser/new-relic-browser/browser-apis/wraplogger) definen la sintaxis, los requisitos, los parámetros y los ejemplos sobre cómo usar estos nuevos extremos. - -### Cambios importantes - -* Eliminamos nuestra categoría de nivel superior `Other capabilities` y hemos migrado todo lo que estaba allí a categorías más apropiadas. Con todo en su lugar, te resultará más fácil encontrar lo que buscas. -* Se trasladaron los ejemplos del recolector OpenTelemetry de nuestro sitio de documentación a nuestro `newrelic-opentelemetry-examples`]\([https://github.com/newrelic/newrelic-opentelemetry-examples](https://github.com/newrelic/newrelic-opentelemetry-examples)) Repositorio GitHub para facilitar el mantenimiento y mejorar la visibilidad de su código abierto. -* Nuestro monitoreo de IA es compatible con [los modelos NVIDIA NIM](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#deploy-at-scale) y no requiere ninguna configuración adicional fuera de nuestros flujos de instalación manuales o basados en UI. Lea más sobre ello en nuestro blog [de monitoreo de IA para NVIDIA NIM](https://newrelic.com/blog/how-to-relic/ai-monitoring-for-nvidia-nim). - -### Cambios menores - -* Se agregó IAST la URL del servicio de validación extremo a las [redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) [y extremos compatibles con](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#agents) FedRAMP. -* [Resolución de problemasIAST ](/docs/iast/troubleshooting/#see-my-application)actualizada con rangos de IP específicos a lista blanca si no ves tu aplicación. -* Se actualizó [la configuración del agente Ruby](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/#instrumentation-aws_sqs) con información de configuración de instrumentación automática `NEW_RELIC_INSTRUMENTATION_AWS_SQS`. -* Se eliminó la información de configuración de reportes `ApplicationExitInfo` de [la configuración de monitoreo de dispositivos móviles](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings), porque esto se puede hacer en la UI. -* [Los enriquecimientos del flujo de trabajo](/docs/alerts/get-notified/incident-workflows/#enrichments) admiten múltiples variables para que pueda personalizar sus datos de manera más específica según sus necesidades. -* Se agregó el atributo [MobileApplicationExit](/attribute-dictionary/?dataSource=Mobile&event=MobileApplicationExit) a nuestro diccionario de datos. Nuestro diccionario de datos no es solo un recurso de documentación, sino que también alimenta definiciones de atributos directamente a la UI, por ejemplo, cuando escribe una consulta NRQL en nuestro generador de consultas. -* Se eliminaron documentos relacionados con la API REST de alertas obsoletas. - -### Notas de la versión y publicaciones de novedades - -* Novedades de [New Relic : la monitorización de IA ahora se integra con los microservicios de inferencia NVIDIA NIM](/whats-new/2024/06/whats-new-06-24-nvidianim) - -* Novedades de [Actualización del nuevo tiempo de ejecución del monitor Sintético para evitar impactos en sus monitores Sintético](/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm) - -* [Agente Android v7.4.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-741) - * `ApplicationExitInfo` reportes habilitados de forma predeterminada - -* [Agente del browser v1.261.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0) - - * Logging de argumentos de API pasados como objetos para una mejor extensibilidad - * Varias otras características nuevas y correcciones de errores - -* [CLI de diagnóstico (nrdiag) v3.2.7](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-327) - -* [Integración Kubernetes v3.29.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0) - - * Se agregó soporte en 1.29 y 1.30, se eliminó el soporte en 1.24 y 1.25 - * Dependencia actualizada: paquetes Kubernetes v0.30.2 y Alpine v3.20.1 - -* [Aplicación móvil para iOS v6.5.0](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6050) - - * Ver todas las entidades que forman parte de una carga de trabajo - * Más opciones de personalización dashboard - * Varias otras mejoras - -* [Agente Node.js v11.20.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0) - - * Compatibilidad con APIde mensajes Anthropic's Claude - * Varias otras mejoras - -* [Agente Node.js v11.21.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0) - * Soporte para obtener ID de contenedores desde APIde metadatos de ECS - -* [Agente PHP v10.22.0.12](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12) - - * Soporte EOL para PHP 7.0 y 7.1 - * Varias correcciones de errores - -* [Agente Ruby v9.11.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0) - - * Nueva instrumentación para la gema `aws-sdk-sqs` - * Un par de correcciones de errores \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index ecb03f5a0ba..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó una nueva característica sobre [Cómo depurar problemas del agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), que incluye logging detallado, monitoreo de solicitudes de red e inspección de eventos para una resolución mejorada de problemas en las versiones del agente 1.285.0 y superiores. -* Se agregó compatibilidad con [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para la supervisión de funciones `python` y `.node.js`. -* Se agregó [un optimizador de cálculo](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) para obtener información práctica y mejorar la eficiencia del cálculo, con la capacidad de identificar ineficiencias, proporcionar recomendaciones de optimización y estimar los ahorros de CCU en la plataforma New Relic. -* Se agregó [Inteligencia para costos en la nube](/docs/cci/getting-started/overview), que ofrece herramientas para la visibilidad y la gestión de los costos cloud, incluidas características como desgloses completos de costos, asignación de costos Kubernetes, estimación de costos en tiempo real y recopilación de datos entre cuentas, y que actualmente solo admite los costos AWS cloud. -* Se agregó [la observabilidad OpenTelemetry para Kubernetes con la integración independiente del proveedor de la característica New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para un monitoreo continuo del clúster a través del diagrama Helm, mejorando las señales de telemetría para métricas, eventos y logs transmitidos a las herramientas y el tablero de New Relic. -* Se agregó [limitación y resolución de problemas para la integración Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) -* Se agregó la integración de AWS a través de [CloudFormation y CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), lo que admite el sondeo de API para servicios no compatibles. -* Se agregó [una etiqueta mejorada para la base de datos de entidad New Relic ](/docs/infrastructure/host-integrations/db-entity-tags/)para la base de datos de entidad monitoreada mediante integración en el host para MySQL y MS SQL Server, enriqueciendo metadatos, información valiosa y organización en New Relic sin afectar la facturación o la telemetría existente. - -### Cambios importantes - -* Se agregaron funciones no agregadoras a [las referenciasNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/). -* Se actualizaron los [requisitos del agenteRuby y el marco compatible](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/). -* Se agregaron logs como evento personalizado New Relic a los [logs OpenTelemetry en el documento New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events). -* Se actualizaron los tiempos de ejecución compatibles con Linux, Windows y funciones en contenedores en el documento [Compatibilidad y requisitos para funciones instrumentadas Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes). -* Se actualizaron los datos métricos de [Confluent integración en la nube](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics). -* Se eliminó GCP Cloud Run de [la configuración del agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) -* Se actualizó [la compatibilidad y los requisitos para el monitoreo de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) para incluir bibliotecas adicionales compatibles con el agente .NET. -* Se agregó New Relic telemetría dualstack extremo al [tráfico de red deNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Se agregó `GcpHttpExternalRegionalLoadBalancerSample` a la [integración de monitoreo de Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/). -* Se agregó el procedimiento de inicio de OpenShift sobre cómo [instalar el documento del administrador de trabajos Sintéticos](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install). -* Se actualizó la [versión 12 del agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) -* Se agregó una integración perfecta para [AWS con New Relic empleando CloudFormation y CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), incluido soporte para sondeo de API. - -### Cambios menores - -* Se agregó `Transaction` como periodo de retención para [la traza de la transacción](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/). -* Se agregó `Destination` como una nueva categoría a [Reglas y límites de alerta](/docs/alerts/admin/rules-limits-alerts/). -* Se agregó una llamada en [el documento Introducción al servicio New Relic nativo de Azure](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) para garantizar que las configuraciones de diagnóstico en los recursos de Azure estén configuradas correctamente o deshabilitar el reenvío a través del servicio New Relic nativo de Azure para evitar que los datos se envíen a la plataforma New Relic. -* Se actualizó la última biblioteca compatible con [el agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/). -* Se agregó una llamada en el documento [de notas de la versión del agente de iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) para anunciar que, a partir de la versión 7.5.4 del SDK de iOS, Un cambio ahora da como resultado el reporte de eventos de excepción manejados que anteriormente se suprimieron. -* Se actualizaron los requisitos para las relaciones servicio-contenedor para especificar el atributo de recurso para entornos Kubernetes y `container.id` para entornos que no son-Kubernetes, lo que garantiza una configuración de telemetría adecuada para [los recursos de OpenTelemetry en New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/). -* Se agregó compatibilidad CLI para la instalación de versiones [específicas del agente de infraestructura](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), lo que permite una implementación consistente y compatibilidad del sistema; especifique la versión usando `@X.XX.X` en el nombre de la receta. -* Se agregó un llamado para enfatizar los requisitos de acceso de roles para usar las funciones **Manage Account Cardinality**, **Manage Metric Cardinality** y **Create Pruning Rules** en la UI; cerciorar de que las licencias estén configuradas en [Administración de cardinalidad](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table). -* Se actualizó la [compatibilidad y los requisitos para el agente Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) a `v12.23.0`. -* Se agregaron las licencias mínimas requeridas para configurar un [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration). -* Se actualizó el uso máximo aceptable del atributo `FACET` de los límites de 5000 a 20000 valores para [la sintaxis de alerta NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). - -### Notas de la versión - -* Se anunció el 7 de enero de 2026 como la fecha de finalización de la vida útil de las [reglas de lanzamiento dirigidas a eventos de infraestructura en `SystemSample`, `ProcessSample`, `NetworkSample` y `StorageSample`](/eol/2025/05/drop-rule-filter/) - -* Con vigencia inmediata, el fin de la vida útil de [FACET en messageId y timestamp en condición de alerta](/eol/2025/07/deprecating-alert-conditions/). - -* Se anunció el 28 de octubre de 2025 como la fecha de finalización de la vida útil de [Atención requerida](/eol/2025/07/upcoming-eols/). - -* Consulta nuestras publicaciones de Novedades: - - * [Enviar notificación directamente a Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [¡New Relic Compute Optimizer ya está disponible de forma general!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [Logs de consultas de cuentas cruzadas en el Explorador de consultas unificado](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [¡El monitoreo de Kubernetes con OpenTelemetry ya está disponible de manera general!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [La monitorización de nodos Windows para Kubernetes ahora está en versión preliminar pública](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [Identificar problemas de rendimiento: filtrado avanzado para páginas vistas y Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [Ahora puedes ordenar por errores más recientes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [Tus datos del navegador, tus términos: Nuevas opciones de control](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [Análisis de consulta profunda para base de datos ahora disponible de forma general](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [Las predicciones NRQL y las alertas predictivas ya están disponibles de forma general](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [Convergencia APM + OpenTelemetry GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [La integración de Agentic para GitHub Copilot y ServiceNow ya está disponible de forma general](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Tiempo de ejecución de la API de Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * Se corrigieron problemas de vulnerabilidades. - - * [Tiempo de ejecución de ping v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * Se corrigieron las vulnerabilidades del núcleo logback durante el tiempo de ejecución de ping. - * Se corrigieron las vulnerabilidades del servidor Jetty durante el tiempo de ejecución de ping. - * Se corrigieron las vulnerabilidades de Ubuntu para el tiempo de ejecución de ping. - - * [Agente de Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * Actualizar la definición `BrowserInteraction` y `previousUrl`. - * Se agregó evento de inspección adicional. - * Valor fijo `finished` API `timeSinceLoad`. - - * [Integración Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * Se corrigieron los ajustes internos backend y relacionados con CI para compatibilidad futura con plataformas. - - * [Administrador de trabajos v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * Se solucionó un problema que impedía que ciertos clientes vieran resultados para algunos monitores con tiempos de ejecución más prolongados. - - * [Agente de Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * Se agregó soporte para `Azure Function Apps`. - * Se corrigieron los archivos `pb2` para habilitar el soporte `protobuf v6`. - - * [Agente Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * Rendimiento mejorado para resolver ANR al informar logs. - * Se solucionó un problema para continuar informando logs al finalizar la aplicación. - * Se resolvió un problema con la aplicación de monitoreo de estado y transmisión de datos. - * Se mejoraron algunas complicaciones al activar el modo estricto. - - * [Integración Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * Actualizado `golang.org/x/crypto` a `v0.39.0`. - * Actualizado `go` a `v1.24.4`. - - * [Agente .NET v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Se agregó soporte para Azure Service Bus. - * Se corrigieron errores de compilación del generador de perfiles con la última versión de VS. - - * [agente PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * Se agregó API de tiempo de ejecución de Composer para usarla de manera predeterminada para detectar paquetes empleados por la aplicación PHP. - * Se solucionó el comportamiento indefinido cuando se ejecuta la API de tiempo de ejecución de Composer. - - * [Tiempo de ejecución del navegador de nodos v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * Opciones de creación de Chrome actualizadas para Chrome 131. - - * [Aplicación móvil para iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * Se mejoró la función Ask AI con una conexión de socket más robusta y confiable, cerciorando una experiencia perfecta. - - * [Aplicación móvil para Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * Se mejoró la función Ask AI con una conexión de socket más robusta y confiable, cerciorando una experiencia perfecta. - - * [Agente de Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * Se agregó soporte para transmisión `openai` v5. - * Se agregó soporte para la API `openai.responses.create`. - * Se corrigió el log de error para el encabezado de estado de seguimiento no definido. - - * [agente de infraestructura v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * Dependencia actualizada `newrelic/nri-winservices` a `v1.2.0` - * Etiqueta de Docker Alpine actualizada a `v3.22` - - * [agente de infraestructura v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * actualizar la dependencia `newrelic/nri-flex` a `v1.16.6` - - * [Agente de Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * Se corrigió la precedencia de la condición de carrera del atributo personalizado. - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * Se elevó el núcleo beta de OTEL a `v0.128.0` - - * [Agente de medios para HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * Se introdujo un nuevo tipo de evento. - * El tipo de evento `PageAction` quedó obsoleto. - - * [Agente de medios para HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * Se habilitó la publicación npm para el paquete, lo que garantiza una fácil accesibilidad y distribución. - * Se agregaron las compilaciones `cjs`, `esm` y `umd` a la carpeta `dist`, lo que garantiza la compatibilidad con los formatos de módulos CommonJS, ES y UMD. - - * [Agente multimedia para Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * Se introdujo un nuevo tipo de evento. - * El tipo de evento `RokuVideo` quedó obsoleto. - * El tipo de evento `RokuSystem` quedó obsoleto. - - * [Agente multimedia para Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * El nombre `errorName` renombrado con `errorMessage` como `errorName` quedó obsoleto. - - * [Administrador de trabajos v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * Actualización de la imagen base fija de `ubuntu 22.04` a `ubuntu 24.4` - - * [Tiempo de ejecución de ping v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * Actualización de imagen base mejorada de `ubuntu 22.04` a `ubuntu 24.04` - - * [Integración Kubernetes v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * Se agregó soporte para la monitorización de nodos Windows en el clúster de Kubernetes. - - * [Aplicación móvil para Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * Se corrigió un error y se mejoró UI para una experiencia más fluida. - - * [Agente de Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * Se agregó la capacidad de informar solo sobre los tramos de entrada y salida. - * Se agregó compatibilidad con Node.js 24. - * Reporte de compatibilidad actualizado. - - * [Tiempo de ejecución de la API de Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * Se corrigieron las vulnerabilidades de `CVE-2024-39249` - - * [Aplicación móvil para iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * Se mejoró la característica Ask AI con símbolo dinámico. - - * [Agente de Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * Se agregó mensaje interno **de tareas largas**. - * Se solucionó el problema que impedía deshabilitar el rastreo distribuido. - - * [Tiempo de ejecución del navegador de nodos v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * Imagen base mejorada - - * [Agente de Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Metadatos vinculados para servicios de aplicaciones Azure. - * Se eliminó la instrumentación `MonoFlatMapMain`. - - * [Agente de Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Se implementó un límite de tamaño de valor de atributo configurable - * Reporte de compatibilidad actualizado. - - * [Integración Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * Actualizar la versión del gráfico kube-state-métrica de `5.12.1` a `5.30.1` - - * [Agente iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. - - * [Aplicación móvil para Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * Se mejoró la retroalimentación con representación de UI dinámica. - - * [Aplicación móvil para Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * Se corrigieron errores y se actualizaron las banderas de Teams GA para una mejor experiencia de usuario. - - * [Go agente v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * Utilización revertida. Vuelva a la versión v3.39.0 debido a un error de bloqueo. - * Se eliminaron las pruebas awssupport\_test.go que agregaron dependencia directa al módulo go - - * [Agente de Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * Se mejoró el agente nativo de Android actualizado a la versión 7.6.7 - * Se mejoró el agente nativo de iOS actualizado a la versión 7.5.6 - - * [Agente de Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Se eliminó el soporte para Node.js 18 - * Se actualizó la versión mínima compatible para `fastify` a 3.0.0. `pino` a 8.0.0 y `koa-router` a 12.0.0 - - * [Agente de Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * Reporte corregido: URL anterior vacía como indefinida - - * [agente de infraestructura v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * Se actualizó la dependencia `newrelic/nri-prometheus` a v2.26.2 - - * [Aplicación móvil para iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * Se mejoró la retroalimentación con representación de UI dinámica. - - * [Agente NDK Android v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * Se agregó soporte para tamaño de página de 16 KB - - * [agente de infraestructura v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Se modificó el identificador del proceso de Windows. - * Subió `nri-docker` a `v2.5.1`, `nri-prometheus` a `v2.26.1` - - * [Agente .NET v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Se agregó compatibilidad con temas para Azure Service Bus - - * [Agente de Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * Se corrigió el instrumento AWS Bedrock Converse API - - * [Agente de Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Se implementó un límite de tamaño de valor de atributo configurable - * Reporte de compatibilidad actualizado - - * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * Se resolvieron los errores relacionados con GLIBC, como `/lib64/libc.so.6: version 'GLIBC_2.34'` no encontrado. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx deleted file mode 100644 index 35bd55c1bc8..00000000000 --- a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-11-13' -version: 1.303.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Allow consent API to be invoked without localStorage access - - Allow nested registrations - - Additional validation to prepare agent for MFE registrations - - Add measure support to register API - - Add useConsentModel functionality - - Retry initial connect call - - Add custom event support to register API - - SMs for browser connect response -bugs: - - Obfuscate custom attributes for logs added after PVE - - memoize promise context propagation to avoid safari hangs -security: [] -translationType: machine ---- - -## v1.303.0 - -### Característica - -#### Permitir que se invoque la API de consentimiento sin acceso a localStorage - -Permite que la API de consentimiento funcione sin necesidad de acceso a localStorage, al mantener un estado común en el agente que controla las recopilaciones. La aplicación debe invocar la API en cada carga completa de la página cuando el acceso a localStorage esté bloqueado. - -#### Permitir registros anidados - -Para facilitar las relaciones inherentes padre-hijo con la API de registro planeada, permita que la entidad registrada exponga su propia API `.register()` para que los hijos de esa entidad se registren con ella. Las entidades que se registren con el agente contenedor estarán relacionadas con el contenedor. Las entidades que se registren bajo otra entidad registrada estarán relacionadas tanto con la entidad contenedora como con la entidad matriz. - -#### Validación adicional para preparar al agente para los registros MFE - -Agregar reglas de validación en el agente para evitar valores incorrectos para el objetivo MFE `id` y `name` en apoyo de los registros MFE/v2. - -#### Agregar soporte de medidas para registrar la API - -Agrega soporte para la API de medidas en el objeto de respuesta de registro. Esto respalda la futura oferta de microfrontends prevista. - -#### Agregar funcionalidad useConsentModel - -Agrega la propiedad de inicialización use\_consent\_mode y su funcionalidad. Agrega la llamada a la API consent(). El modelo de consentimiento, si está habilitado, impide la recolección de agentes a menos que se dé el consentimiento a través de la llamada API consent(). - -#### Reintentar la llamada de conexión inicial - -Para ayudar a prevenir la pérdida de datos, el agente ahora reintentará la llamada "RUM" original una vez más para los códigos de estado reintentables. - -#### Agregue soporte para eventos personalizados para registrar API - -Agrega métodos para capturar eventos personalizados a la API de registro, para ser empleados posteriormente cuando se establezca el soporte MFE. - -#### SM para la respuesta de conexión del navegador - -Agrega una métrica de soporte para las respuestas fallidas al inicializar el agregado page\_view\_event. - -### Corrección de errores - -#### Ofuscar atributo personalizado para registros agregados luego de PVE - -Extiende la ofuscación para cubrir el atributo personalizado en el evento de registro agregado luego de la recolección inicial RUM/PageViewEvent. - -#### Memorizando la propagación del contexto de la promesa para evitar que Safari se cuelgue. - -Memoriza la propagación del contexto de promesa para evitar posibles bloqueos de browser en Safari al evitar operaciones de contexto repetidas. - -## Declaración de apoyo - -New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. - -Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. - -De acuerdo con nuestra [política de soporte de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.303.0 del agente del navegador se construyó y probó con los siguientes navegadores y rangos de versiones: Chrome 131-141, Edge 131-141, Safari 17-26 y Firefox 134-144. Para dispositivos móviles, la versión 1.303.0 se compiló y probó para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx deleted file mode 100644 index 23a0a814a9b..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-11-17' -version: rc1.3 -translationType: machine ---- - -### Mejoras - -* Actualicé el navegador Chrome a la versión 142. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx deleted file mode 100644 index cd082a1a0ec..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-11-12' -version: 1.58.0 -translationType: machine ---- - -### Mejoras - -Se corrigieron vulnerabilidades relacionadas con Ubuntu y Java para solucionar problemas de seguridad en el entorno de ejecución de Ping; a continuación se muestran las CVE de Java corregidas. - -* CVE-2025-5115 -* CVE-2025-11226 \ No newline at end of file diff --git a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx deleted file mode 100644 index 89628a3908b..00000000000 --- a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ /dev/null @@ -1,652 +0,0 @@ ---- -title: acciones de comunicación -tags: - - workflow automation - - workflow - - workflow automation actions - - communication actions - - slack actions - - ms teams actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras! - - Esta característica se proporciona actualmente como parte de un programa de vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página proporciona una referencia completa de las acciones de comunicación disponibles en el catálogo de acciones de automatización del flujo de trabajo. Estas acciones te permiten integrar la plataforma de comunicación en tus definiciones de flujo de trabajo, incluyendo el envío de mensajes a canales de Slack, la recuperación de reacciones y más. - -## Requisitos previos - -Antes de emplear acciones de comunicación en la automatización del flujo de trabajo, cerciorar de tener: - -* Un espacio de trabajo de Slack con las licencias adecuadas. -* Un token de bot de Slack configurado como secreto en la automatización del flujo de trabajo. -* Acceso a los canales de Slack donde deseas enviar mensajes. - -Consulta [la sección "Agregar configuración de Slack"](/docs/autoflow/overview#add-the-slack-integration) para obtener información sobre cómo configurar la integración de Slack. - -## Acciones de Slack - - - - Envía un mensaje a un canal de Slack, con un archivo adjunto opcional. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Ejemplo -
- **token** - - Requerido - - secreto - - `${{ :secrets:slackToken }}` -
- **canal** - - Requerido - - cadena - - `my-slack-channel` -
- **texto** - - Requerido - - cadena - - `Hello World!` -
- **hilosTs** - - Opcional - - cadena - - `.` -
- **adjunto** - - Opcional - - mapa - -
- **archivo adjunto** - - Requerido - - cadena - - `file.txt` -
- **contenido del archivo adjunto** - - Requerido - - cadena - - `Hello\nWorld!` -
- - - * **token**: El token del bot de Slack que se va a emplear. Esto debe pasar como una sintaxis secreta. Consulte [la sección "Agregar configuración de Slack"](/docs/autoflow/overview#add-the-slack-integration) para obtener instrucciones sobre cómo configurar un token. - * **channel**: El nombre del canal, o un ID de canal, al que se enviará el mensaje. Consulta [la API de Slack](https://api.slack.com/methods/chat.postMessage#arg_channel/) para obtener más información. - * **text**: El mensaje que se publicará en Slack en el `channel` especificado. - * **threadTs**: marca de tiempo perteneciente al mensaje principal, empleada para crear una respuesta de mensaje en un hilo. - * **attachment**: Permite anexar un archivo con un mensaje al `channel` especificado. - * **attachment.filename**: Especifique el nombre del archivo cargado en Slack. - * **attachment.content**: El contenido del archivo a subir en formato UTF-8. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **hilosTs** - - cadena - - `.` -
- **ID de canal** - - cadena - - `` -
- - - * **threadTs**: marca de tiempo del mensaje. Puede emplear en futuras llamadas a postMessage para publicar una respuesta en un hilo. - * **channelID**: Identificador del canal donde se publica el mensaje. - - - - - **Ejemplo 1: Publicar un mensaje en un canal de Slack** - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: SendMessage - - steps: - - name: send_slack_message - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: ${{ .workflowInputs.channel }} - text: ${{ .workflowInputs.text }} - ``` - - **Entradas esperadas:** - - ```json - { - "inputs": [ - { - "key" : "channel", - "value" : "my-channel" - }, - { - "key" : "text", - "value" : "This is my message *with bold text* and `code backticks`" - } - ] - } - ``` - - **Resultado esperado:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - **Ejemplo 2: Anexar un archivo** - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: SendFileMessage - - steps: - - name: postCsv - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel - text: "Please find the attached file:" - attachment: - filename: 'file.txt' - content: "Hello\nWorld!" - ``` - - **Resultado esperado:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - - - - - - - - Obtén una reacción a un mensaje del canal de Slack. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Ejemplo -
- **token** - - Requerido - - secreto - - `${{ :secrets:slackToken }}` -
- **ID de canal** - - Requerido - - cadena - - `C063JK1RHN1` -
- **se acabó el tiempo** - - Opcional - - En t - - 60 -
- **hilosTs** - - Requerido - - cadena - - `.` -
- **selectores** - - Opcional - - lista - - `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` -
- - - * **token**: El token del bot de Slack que se va a emplear. Esto debe pasar como una sintaxis secreta. Consulte [la sección "Agregar configuración de Slack"](/docs/autoflow/overview#add-the-slack-integration) para obtener instrucciones sobre cómo configurar un token. - * **channelID**: El ID del canal para obtener las reacciones a los mensajes. - * **timeout**: El tiempo en segundos que se debe esperar para obtener alguna respuesta. El valor predeterminado es 60 segundos, el máximo permitido es 600 segundos (10 minutos). - * **threadTs**: marca de tiempo perteneciente al mensaje, empleada para obtener la reacción a ese mensaje. - * **selectors**: Los selectores para obtener como salida el único parámetro especificado. - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **reacciones** - - lista - - `` -
- - - * **reactions**: Lista de elementos con todas las reacciones capturadas o una lista vacía si se produjo un tiempo de espera agotado. - - - - - **Ejemplo 1: Slack obtiene reacciones** - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: GetReactions - - steps: - - name: getReactions - type: action - action: slack.chat.getReactions - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channelID: ${{ .steps.promptUser.outputs.channelID }} - threadTs: ${{ .steps.promptUser.outputs.threadTs }} - timeout: ${{ .workflowInputs.timeout }} - selectors: ${{ .workflowInputs.selectors }} - ``` - - **Entradas esperadas:** - - ```json - { - "inputs": [ - { - "key" : "channelID", - "value" : "C063JK1RHN1" - }, - { - "key" : "threadTs", - "value" : "1718897637.400609" - }, - { - "key" : "selectors", - "value" : "[{\"name\": \"reactions\", \"expression\": \".reactions \"}]" - } - ] - } - ``` - - **Resultado esperado:** - - ```json - [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } - ] - ``` - - O si se agota el tiempo de espera: - - ```json - [] - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index 0590bd77d78..00000000000 --- a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,1043 +0,0 @@ ---- -title: Acciones HTTP -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: A list of available HTTP actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras! - - Esta característica se proporciona actualmente como parte de un programa de vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página proporciona una referencia completa de las acciones HTTP disponibles en el catálogo de acciones de automatización de flujo de trabajo. Estas acciones te permiten realizar requests HTTP (GET, POST, PUT, DELETE) a API y servicios externos como parte de tus definiciones de flujo de trabajo. - -## Requisitos previos - -Antes de emplear acciones HTTP en la automatización de flujos de trabajo, cerciorar de tener: - -* Objetivo extremos de URL de API. -* Cualquier credencial de autenticación requerida (clave de API, token, etc.). -* Comprensión de los formatos de solicitud/respuesta de la API. - - - Las acciones HTTP admiten sintaxis secreta para cualquier valor de encabezado, lo que le permite pasar de forma segura datos confidenciales como la clave de API. Consulte [la sección de gestión de secretos](/docs/infrastructure/host-integrations/installation/secrets-management/) para obtener más información. - - -## Acciones HTTP - - - - Realizar una llamada HTTP GET para recuperar datos de un extremo de API. - - - Esto admite sintaxis secreta para cualquier valor de encabezado. - - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Descripción -
- **url** - - Requerido - - Cadena - - La URL de destino para la solicitud. El esquema debe estar incluido: - - `https://example.com` -
- **parámetros de URL** - - Opcional - - Mapa - - El parámetro consulta que se agregará a la URL. Toma un objeto JSON en formato de cadena. -
- **encabezados** - - Opcional - - Mapa - - Las cabeceras que se deben agregar a la solicitud. Toma un objeto JSON en formato de cadena. -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener únicamente el parámetro especificado como resultado. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Descripción -
- **cuerpo de respuesta** - - Cadena - - El cuerpo de la respuesta. -
- **código de estado** - - Entero - - El código de estado HTTP de la respuesta. -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **Ejemplos de entradas:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **Ejemplos de resultados:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - Realiza una llamada HTTP POST para enviar datos a un extremo de API. - - - Esto admite sintaxis secreta para cualquier valor de encabezado. - - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Descripción -
- **url** - - Requerido - - Cadena - - La URL de destino para la solicitud. El esquema debe estar incluido: - - `https://example.com` -
- **parámetros de URL** - - Opcional - - Mapa - - El parámetro consulta que se agregará a la URL. Toma un objeto JSON en formato de cadena. -
- **encabezados** - - Opcional - - Mapa - - Las cabeceras que se deben agregar a la solicitud. Toma un objeto JSON en formato de cadena. -
- **cuerpo** - - Opcional - - Cadena - - El cuerpo de la solicitud. -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener únicamente el parámetro especificado como resultado. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Descripción -
- **cuerpo de respuesta** - - Cadena - - El cuerpo de la respuesta. -
- **código de estado** - - Entero - - El código de estado HTTP de la respuesta. -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **Ejemplos de entradas:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **Ejemplos de resultados:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Realiza una solicitud HTTP PUT para actualizar datos en un extremo de API. - - - Si necesita pasar datos confidenciales a una entrada, por ejemplo un encabezado `Api-Key`, puede usar valores almacenados a través de la mutación [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) de NerdGraph. - - Ejemplo: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Descripción -
- **url** - - Requerido - - Cadena - - La URL de destino para la solicitud. La URL debe incluir el esquema (por ejemplo, https:// o http://). Ejemplo: - - `https://example.com` -
- **parámetros de URL** - - Opcional - - Mapa - - El parámetro consulta que se agregará a la URL. Toma un objeto JSON en formato de cadena. -
- **encabezados** - - Opcional - - Mapa - - Las cabeceras que se deben agregar a la solicitud. Toma un objeto JSON en formato de cadena. -
- **cuerpo** - - Opcional - - Cadena - - El cuerpo de la solicitud. -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener únicamente el parámetro especificado como resultado. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Descripción -
- **cuerpo de respuesta** - - Cadena - - El cuerpo de la respuesta. -
- **código de estado** - - Entero - - El código de estado HTTP de la respuesta. -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Ejemplos de entradas:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Ejemplos de resultados:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Realiza una solicitud HTTP DELETE para eliminar datos en un extremo de API. - - - Si necesita pasar datos confidenciales a una entrada, por ejemplo un encabezado `Api-Key`, puede usar valores almacenados a través de la mutación [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) de NerdGraph. - - Ejemplo: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Descripción -
- **url** - - Requerido - - Cadena - - La URL de destino para la solicitud. La URL debe incluir el esquema (por ejemplo, https:// o http://). Ejemplo: - - `https://example.com` -
- **parámetros de URL** - - Opcional - - Mapa - - El parámetro consulta que se agregará a la URL. Toma un objeto JSON en formato de cadena. -
- **encabezados** - - Opcional - - Mapa - - Las cabeceras que se deben agregar a la solicitud. Toma un objeto JSON en formato de cadena. -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener únicamente el parámetro especificado como resultado. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Descripción -
- **cuerpo de respuesta** - - Cadena - - El cuerpo de la respuesta. -
- **código de estado** - - Entero - - El código de estado HTTP de la respuesta. -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Ejemplos de entradas:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Ejemplos de resultados:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx deleted file mode 100644 index b04ff808757..00000000000 --- a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ /dev/null @@ -1,1910 +0,0 @@ ---- -title: Acciones de New Relic -tags: - - workflow automation - - workflow - - workflow automation actions - - New relic actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras! - - Esta característica se proporciona actualmente como parte de un programa de vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página proporciona una referencia completa de las acciones de New Relic disponibles en el catálogo de acciones de automatización de flujo de trabajo. Estas acciones te permiten integrar las capacidades de la plataforma New Relic en tus definiciones de flujo de trabajo, incluyendo el envío de eventos personalizados y logs, la ejecución de consultas NerdGraph, la ejecución de consultas NRQL y el envío de notificaciones. - -## Requisitos previos - -Antes de emplear las acciones New Relic en la automatización del flujo de trabajo, cerciorar de tener lo siguiente: - -* Una cuenta de New Relic con las licencias adecuadas. -* Una clave de licencia de New Relic (si se envían datos a una cuenta diferente). -* Las licencias necesarias para los servicios específicos de New Relic que planea emplear. - -Consulte [la clave de licencia](/docs/apis/intro-apis/new-relic-api-keys/#license-key) para obtener información sobre cómo crear y gestionar su clave de licencia de cuenta de New Relic. - -## acciones de ingesta de datos - - - - Envía un evento personalizado a New Relic - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Ejemplo -
- **Atributo** - - Opcional - - Mapa - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **evento** - - Requerido - - lista - - `"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]` -
- **clave de licencia** - - Opcional - - cadena - - `"{{ .secrets.secretName }}"` -
- **selectores** - - Opcional - - lista - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Atributo común que forma parte de todos los eventos cuando se proporciona. Se realiza la fusión para cada elemento del evento cuando sea necesario; el elemento del evento anula la definición común. - * **events**: La lista de datos del evento. Tenga en cuenta que el evento requiere el uso de un campo `eventType` que representa el tipo de evento personalizado y el máximo de eventos permitidos por solicitud es 100. - * **licenseKey**: La clave de licencia de New Relic Account que especifica la cuenta objetivo donde se envían los eventos. Si no se proporciona este valor, se asume una clave de licencia predeterminada basada en la cuenta que ejecuta el flujo de trabajo. - * **selectors**: Los selectores para obtener únicamente el parámetro especificado como salida. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **éxito** - - Booleano - - `true` -
- **mensaje de error** - - cadena - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **Resultado esperado:** - - ```yaml - { - "success": true - } - ``` - - **Recuperar evento:** - - Tras ejecutar correctamente un flujo de trabajo, puede recuperar el evento asociado ejecutando una consulta en la cuenta que ejecutó el flujo de trabajo: - - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - Enviar log a New Relic - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo - - Ejemplo -
- **Atributo** - - Opcional - - mapa - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **logs** - - Requerido - - lista - - `"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"` -
- **clave de licencia** - - Opcional - - cadena - - `"{{ .secrets.secretName }}"` -
- **selectores** - - Opcional - - lista - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Atributo común incluido en todos los logs cuando se proporciona. Si un elemento de log especifica el mismo atributo, anula la definición común. - * **logs**: La lista de datos de log. Tenga en cuenta que el número máximo de logs permitidos por solicitud es 100. - * **licenseKey**: La clave de licencia de New Relic Account que especifica la cuenta objetivo a la que se envían los logs. Si no se proporciona, se asume una clave de licencia predeterminada basada en la cuenta que ejecuta el flujo de trabajo. Consulte [la clave de licencia](/docs/apis/intro-apis/new-relic-api-keys/#license-key) para obtener más información. - * **selectors**: Los selectores para obtener únicamente el parámetro especificado como salida. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **éxito** - - Booleano - - `true` -
- **mensaje de error** - - cadena - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **Resultado esperado:** - - ```yaml - { - "success": true - } - ``` - - **Recuperar logs:** - - Tras ejecutar correctamente un flujo de trabajo, puede recuperar el log asociado ejecutando una consulta en la cuenta que ejecutó el flujo de trabajo: - - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## Acciones de NerdGraph - - - - Ejecuta un comando Graphql contra la API NerdGraph de New Relic. El comando puede ser una consulta o una mutación. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo - - Descripción - - Ejemplo -
- **Graphql** - - Requerido - - cadena - - Sintaxis GraphQL. Deberías usar GraphiQL para construir y probar tu comando. - -
- **variables** - - Requerido - - map[string]any - - Variables de pares principales de valor para usar con la declaración GraphQL. - -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener como resultado el único parámetro especificado. - - ```yaml - steps: - - name: findingVar - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query GetEntity($entityGuid: EntityGuid!) { - actor { - entity(guid: $entityGuid) { - alertSeverity - } - } - } - variables: - entityGuid: ${{ .workflowInputs.entityGuid }} - - name: findingInline - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - { - actor { - entity(guid: "${{ .workflowInputs.entityGuid }}") { - alertSeverity - } - } - } - selectors: - - name: entities - expression: '.data' - ``` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Producción - - Tipo - - Descripción -
- **datos** - - map[string]any - - Contenido de la propiedad - - `data` - - de una respuesta de NerdGraph. -
- **éxito** - - Booleano - - Status of the request.s -
- **mensaje de error** - - Cadena - - Mensaje de motivo del fallo. -
- - - - - - - - - - - - - - - -
- Ejemplo -
- ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - -## Acciones de consulta - - - - Ejecuta una consulta NRQL entre cuentas a través de la API de NerdGraph. - - - - - Entradas - - - - Salidas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo - - Descripción - - Ejemplo -
- **consulta** - - Requerido - - cadena - - La instrucción de consulta NRQL. - -
- **ID de cuenta** - - Opcional - - lista de int - - El campo - - **New Relic Account ID** - - es una lista de ID de objetivo que le permite especificar las cuentas objetivo contra las que se ejecuta la consulta. Si no se proporciona este valor como entrada, la consulta se ejecutará automáticamente en la cuenta asociada con la cuenta de ejecución del flujo de trabajo. - -
- **selectores** - - Opcional - - lista - - Los selectores para obtener como resultado el único parámetro especificado. - - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - - - - -
- Producción - - Tipo - - Ejemplo -
- **results** - - : Una matriz de objetos que contiene los resultados de la consulta. - - - - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - -## acciones de notificación - - - - Envía un mensaje a un canal, integrado con destinos como por ejemplo Slack. - - - - - Entradas - - - - Salidas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo - - Descripción - - Ejemplo -
- **tipo** - - Requerido - - cadena - - Tipo de destino de New Relic - - `slack` -
- **ID de destino** - - Requerido - - Cadena - - DestinationId asociado con el destino de New Relic. - - `123e4567-e89b-12d3-a456-426614174000` -
- **parámetro** - - Requerido - - mapa - - Campos obligatorios para enviar notificaciones al tipo de destino seleccionado. - - `{\"channel\": \"${{ YOUR_CHANNEL }}\", \"text\": \"Enter your text here\"}` -
- **selectores** - - Opcional - - lista - - Los selectores para obtener como resultado el único parámetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - -
- Producción - - Tipo - - Ejemplo -
- éxito - - booleano - - `true/false` -
- - - - - - - - - Envía un mensaje a un canal de equipo de MS, integrado con destinos. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo de datos - - Descripción - - Ejemplo -
- **ID de destino** - - Requerido - - Cadena - - DestinationId asociado con el destino de New Relic. - - Consulte [la integración de New Relic para Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) para obtener los pasos sobre cómo configurar un nuevo destino y listar el ID del destino. - - Consulta [la sección Destinos](/docs/alerts/get-notified/destinations/) para obtener más información sobre los destinos. - - - - ```sh - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **teamName** - - Requerido - - Cadena - - Nombre del equipo asociado al ID de destino dado - - `TEST_TEAM` -
- **channelName** - - Requerido - - Cadena - - Nombre del canal donde se debe enviar el mensaje - - `StagingTesting` -
- **mensaje** - - Requerido - - Cadena - - Mensaje de texto que debe enviar - - `Hello! this message from Workflow` -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener como resultado el único parámetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **éxito** - - Booleano - - `true/false` -
- **sessionId** - - Cadena - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **mensaje de error** - - Cadena - - `Message is a required field in the notification send"` -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: msTeam_notification_workflow - description: This is a test workflow to test MSTeam notification send action - steps: - - name: SendMessageUsingMSTeam - type: action - action: newrelic.notification.sendMicrosoftTeams - version: 1 - inputs: - destinationId: acc24dc2-d4fc-4eba-a7b4-b3ad0170f8aa - channel: DEV_TESTING - teamName: TEST_TEAM_DEV - message: Hello from Workflow - ``` -
- - - - - - - - - Envía un email a las direcciones de email de NewRelic con o sin archivos adjuntos. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidad - - Tipo de datos - - Descripción - - Ejemplo -
- **ID de destino** - - Requerido - - Cadena - - DestinationId asociado con el destino de New Relic. - - Consulte [la integración de New Relic para Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) para obtener los pasos sobre cómo configurar un nuevo destino y listar el ID del destino. - - Consulta [la sección Destinos](/docs/alerts/get-notified/destinations/) para obtener más información sobre los destinos. - - - - ```yaml - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: EMAIL, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **sujeto** - - Requerido - - Cadena - - Asunto del email - - `workflow-notification` -
- **mensaje** - - Requerido - - Cadena - - Mensaje que debe enviar por email - - `Hello! from Workflow Automation` -
- **archivos adjuntos** - - Opcional - - Lista - - Lista de archivos adjuntos opcionales - -
- **attachment.type** - - Requerido - - Enumeración - - Uno de los siguientes: - - `QUERY` - - , - - `RAW` - -
- **attachment.query** - - Opcional - - Cadena - - Para el tipo - - `QUERY` - - , esta es una declaración de consulta NRQL. - - `SELECT * FROM LOG` -
- *attachment.accountIds* - - \* - - Opcional - - Lista - - Para - - `QUERY` - - , los - - **New Relic Account IDs** - - para ejecutar la consulta. Si no se proporciona ninguna, se emplea la cuenta asociada a la ejecución del flujo de trabajo. - - `[12345567]` -
- **attachment.format** - - Opcional - - Enumeración - - Para - - `QUERY` - - , especifique el tipo de resultados; por defecto, se especifica el tipo predeterminado. - - `JSON` - - `JSON CSV` -
- **contenido del archivo adjunto** - - Opcional - - Cadena - - Para - - `RAW` - - , este es el contenido del archivo adjunto en UTF-8. - - `A,B,C\n1,2,3` -
- **archivo adjunto** - - Opcional - - Cadena - - Nombre del archivo adjunto - - `log_count.csv` -
- **selectores** - - Opcional - - Lista - - Los selectores para obtener como resultado el único parámetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"},{\"name\": \"attachments\", \"expression\": \".response.attachments\"},{\"name\": \"sessionId\", \"expression\": \".response.sessionId\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de salida - - Tipo - - Ejemplo -
- **éxito** - - Booleano - - `true/false` -
- **sessionId** - - Cadena - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **mensaje de error** - - Cadena - - `Channel is a required field in the notification send"` -
- **archivos adjuntos** - - Lista - - ```yaml - [{ - "blobId": "43werdtfgvhiu7y8t6r5e4398yutfgvh", - "rowCount": 100 - }] - ``` -
- - - - - - - - - - - - - - - -
- Ejemplo de flujo de trabajo -
- ```yaml - name: email_testing_with_attachment - description: Workflow to test sending an email notification via NewRelic with log step - workflowInputs: - destinationId: - type: String - steps: - - name: sendEmailNotification - type: action - action: newrelic.notification.sendEmail - version: '1' - inputs: - destinationId: ${{ .workflowInputs.destinationId }} - subject: "workflow notification" - message: "Workflow Email Notification Testing from local" - attachments: - - type: QUERY - query: "SELECT * FROM Log" - format: JSON - filename: "log_count.json" - selectors: - - name: success - expression: '.success' - - name: sessionId - expression: '.response.sessionId' - - name: attachments - expression: '.response.attachments' - - name: logOutput - type: action - action: newrelic.ingest.sendLogs - version: '1' - inputs: - logs: - - message: "Hello from cap check Testing staging server user2 : ${{ .steps.sendEmailNotification.outputs.result.attachments }}" - licenseKey: ${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }} - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index b8378fa33d5..00000000000 --- a/src/i18n/content/es/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,634 +0,0 @@ ---- -title: acciones de utilidad -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: A list of available utility actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - -Esta página proporciona una referencia para las acciones de utilidad disponibles en el catálogo de acciones de automatización de flujo de trabajo. Estas acciones le permiten realizar operaciones comunes de transformación de datos y utilidades en las definiciones de su flujo de trabajo. - -## acciones de utilidad - - - - Esta acción se emplea para transformar timestamp Unix a fecha/hora. Posibles referencias: - - * [https://en.wikipedia.org/wiki/list\_of\_tz\_database\_time\_zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - * [https://docs.oracle.com/javase/8/docs/api/java/time/zoneid.html#SHORT\_IDS](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS) - - Consulte [FromEpoch](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) para obtener más información. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo - - Descripción -
- **timestamp** - - Requerido - - En t - - Un número entero que representa timestamp de la época. Tenga en cuenta que las épocas UNIX son el número de segundos transcurridos desde el 1 de enero de 1970, medianoche UTC (00:00). -
- **marca de tiempoUnidad** - - Opcional - - cadena - - Una cadena que representa la unidad de timestamp proporcionada. Valores aceptables: SEGUNDOS, MILISEGUNDOS (PREDETERMINADO) -
- **ID de zona horaria** - - Opcional - - cadena - - Cadena de texto que representa la zona horaria para la fecha y hora deseadas; por defecto: UTC -
- **patrón** - - Opcional - - cadena - - Cadena que representa el patrón para la fecha y hora deseadas; por defecto: ISO-8601 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Opcionalidad - - Tipo de datos - - Descripción -
- **fecha** - - Requerido - - cadena - - Una representación en cadena de texto de una fecha. -
- **tiempo** - - Requerido - - cadena - - Una representación en cadena del tiempo. -
- **fecha y hora** - - Requerido - - cadena - - Una representación en cadena de texto de una fecha y hora. -
- **zona horaria** - - Requerido - - mapa - - Representación cartográfica del ID de zona horaria y su abreviatura. -
- - - - - - - - - - - - - - - - - - - - - - - -
- Ejemplo - - Entrada del flujo de trabajo - - Salidas -
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - Esta acción se emplea para transformar varios tipos de entrada (JSON, mapa) a formato CSV. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo - - Descripción -
- **datos** - - Requerido - - cualquier - - Una cadena que representa datos para transformar a CSV, normalmente una cadena JSON o un mapa. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Opcionalidad - - Tipo de datos - - Descripción -
- **csv** - - Requerido - - cadena - - Una representación CSV de los datos recibidos. -
- - - - - - - - - - - - - - - - - - - - - - -
- Ejemplo - - Entrada del flujo de trabajo - - Salidas -
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` - -
- - - - - - - - - Generar un UUID V4 compatible con RFC. - - - - - Entradas - - - - Salidas - - - - Ejemplo - - - - - - - - - - - - - - - - - - - - - - -
- Aporte - - Opcionalidad - - Tipo de datos - - Descripción -
- - - - -
- - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Tipo de datos - - Descripción -
- **uuid** - - cadena - -
- - - - - - - - - - - - - - - - - - - - - -
- Ejemplo - - Entrada del flujo de trabajo - - Salidas -
- - - nombre: generarUUID
pasos: - - * nombre: generarUUID tipo: acción acción: utils.uuid.generate versión: 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx deleted file mode 100644 index cf3b7234141..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-10-02' -version: 'Sep 26 - Oct 02, 2025' -translationType: machine ---- - -### Changements majeurs - -* [Documentation de contrôle de la flotte](/docs/new-relic-control/fleet-control/overview) mise à jour avec des révisions complètes pour Kubernetes GA et l'aperçu public Hôtes, y compris de nouvelles fonctionnalités de gestion de flotte, une fonctionnalité de sécurité améliorée et des procédures de configuration mises à jour. -* [Documentation de contrôle de l'agent](/docs/new-relic-control/agent-control/overview) mise à jour avec des révisions approfondies pour l'aperçu public, y compris des options configuration améliorées, des capacités monitoring et des conseils de dépannage. -* [Documentation des marques et mesures](/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures/) restructurée pour une disponibilité générale avec des détails complets sur les fonctionnalités et des conseils de mise en œuvre. -* [Flux de travail notification d'alerte](/docs/alerts/admin/rules-limits-alerts) amélioré avec de nouvelles étapes de validation des e-mails et des limites de destination. -* Le [nom du modèle de tarification](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management/) a été mis à jour : il est passé de « Plans New Relic Compute Public Preview ou Core Compute » à « Plans Advanced ou Core Compute ». - -### Modifications mineures - -* Instructions [d'intégration Fullstack WordPress](/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration) mises à jour pour un processus de configuration amélioré. -* Documentation améliorée [des variables du modèle de tableau de dashboard](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables) avec capture d'écran mise à jour et exemples améliorés. -* [Requête d'utilisation et alertes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) mises à jour avec des capacités améliorées monitoring de l'utilisation du calculateur. -* [Documentation améliorée de l'interface utilisateur d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-ui) avec une fonctionnalité complète de gestion des calculs. -* Correction de la référence d'ancrage en double dans [la configuration de l'agent .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration). -* [Intégration des notifications](/docs/alerts/get-notified/notification-integrations) mise à jour avec une gestion améliorée des destinations des e-mails. -* Documentation [AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink) mise à jour avec une clarté linguistique améliorée pour les régions prises en charge et les exigences de configuration VPC. -* Mise à jour de l'identifiant de publication Quoi de neuf pour la gestion de contenu. - -### Notes de version - -* Restez au courant de nos dernières sorties : - - * [Agent Node.js v13.4.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0): - - * Mise à jour de l'instrumentation amqplib et cassandra-driver pour s'abonner à l'événement émis. - * Rapport de compatibilité de l'agent Node.js mis à jour avec les dernières versions package prises en charge. - * Ajout d'optimisations WASM pour le traçage des hooks. - * Exigences JSDoc améliorées pour une meilleure documentation du code. - - * [Agent Python v11.0.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000): - - * Suppression de la prise en charge de Python 3.7 et dépréciation de diverses API legacy. - * Ajout d'une nouvelle instrumentation pour le framework AutoGen et Pyzeebe. - * Introduction des spans nommés MCP (Model Context Protocol) pour monitoring de l'IA. - * Correction d'un crash dans psycopg et garantie que MCP s'étend uniquement sur l'enregistrement lorsque monitoring de l'IA est activée. - - * [Agent d'infrastructure v1.69.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690): - - * Mise à niveau du SDK AWS de V1 à V2 et de la bibliothèque API Docker de v26 à v28. - * monitoring du processeur Windows fixe par exemple avec plusieurs groupes de processeurs (plus de 64 cœurs). - * Gestion améliorée du format log avec prise en charge du niveau de log par défaut. - - * [Intégration Kubernetes v3.45.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3): - - * Inclus dans les versions graphiques newrelic-infrastructure-3.50.3 et nri-bundle-6.0.15. - - * [NRDOT v1.5.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-25): - - * Ajout du processeur de génération de métriques à nrdot-collecteur-k8s pour une collecte de métriques améliorée. - - * [Agent .NET v10.45.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0): - - * Ajout d'un nouvel échantillonneur basé sur le ratio TraceId pour le traçage distribué basé sur l'implémentation OpenTelemetry. - * Correction des exceptions d'analyse de la chaîne de connexion MSSQL qui pouvaient désactiver l'instrumentation de la banque de données. - * Problèmes d'instrumentation « Consume » de Kafka résolus pour une meilleure compatibilité avec l'instrumentation personnalisée. - - * [Application mobile New Relic Android v5.30.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5308): - - * débogage et améliorations pour des performances accrues des applications mobiles. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx deleted file mode 100644 index d227f7337f8..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-11' -version: 'version: October 4-10, 2024' -translationType: machine ---- - -### Nouveaux documents - -* [Aucune donnée de plantage n'apparaît dans la version sortie (Android)](/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears) vous indique ce qu'il faut faire si vous ne voyez pas de données relatives à un plantage d'application sur l'interface utilisateur de New Relic. -* [Comment utiliser WSL et CodeStream ?](/docs/codestream/troubleshooting/using-wsl) Ce guide fournit des instructions étape par étape sur l’utilisation du sous-système Windows pour Linux (WSL) avec CodeStream. -* [`UserAction`](/docs/browser/browser-monitoring/browser-pro-features/user-actions) est un nouveau type d'événement dans monitoring des navigateurs qui vous aide à comprendre le comportement des utilisateurs avec votre application Web. -* [WithLlmCustomAttributes (agent de l'API Python)](/docs/apm/agents/python-agent/python-agent-api/withllmcustomattributes-python-agent-api) décrit la nouvelle API de gestion de contexte, y compris ses exigences, ses paramètres, ses valeurs de retour et un exemple d'utilisation. - -### Modifications mineures - -* Ajout du point de terminaison data center américains et européens pour l'agent APM dans [le point de terminaison New Relic télémétrie](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). - -* Instructions mises à jour sur la façon de trouver les logs côté client CodeStream lors de l'utilisation [de Visual Studio](/docs/codestream/troubleshooting/client-logs/#visual-studio). - -* [Options de notification reformulées pour les règles de mise en sourdine](/docs/alerts/get-notified/muting-rules-suppress-notifications/#notify) afin d'améliorer la clarté. - -* Mise à jour des informations de compatibilité pour le package suivant dans [les modules instrumenté](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrumented-modules): - - * `@aws-sdk/client-bedrock-runtime` - * `@aws-sdk/client-dynamodb` - * `@aws-sdk/client-sns` - * `@aws-sdk/client-sqs` - * `@aws-sdk/lib-dynamodb` - * `@grpc/grpc-js` - * `@langchain/core` - * `@smithy/smithy-client` - * `next` - * `openai` - -* Correction du deuxième point de terminaison data center de l'UE à `212.32.0.0/20` dans [les blocs IP d'ingestion de données](https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#ingest-blocks). - -* Il est précisé que le service d'alertes de New Relic est exécuté aux États-Unis, que vos données soient stockées dans [le data centereuropéen ou américain de New Relic](/docs/alerts/overview/#eu-datacenter). - -* Informations modifiées sur la façon de définir un [attribut personnalisé](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes). J'ai également mis à jour les exemples. - -* Mise à jour des étapes pour [annuler la prise en compte et clore un problème](/docs/alerts/get-notified/acknowledge-alert-incidents/#unacknowledge-issue). - -* Ajout d'informations sur [la prise en compte et la clôture de plusieurs problèmes](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#bulk-actions). - -* L'introduction [concernant les taux de rafraîchissement des graphiques](/docs/query-your-data/explore-query-data/use-charts/chart-refresh-rates) a été développée afin de préciser que le taux de rafraîchissement n'est configurable que si vous avez souscrit au plan tarifaire de consommation New Relic Compute. - -* Correction des informations de version TLS (Transport Layer Security) requises dans [le chiffrement TLS](/docs/new-relic-solutions/get-started/networks/#tls). - -* L'étape 6 de la procédure [d'installation de l'intégration Kubernetes ](/install/kubernetes)a été mise à jour pour correspondre à l'interface utilisateur actuelle de New Relic. - -* J'ai noté l'importance de l'événement non facturable, `InternalK8sCompositeSample`, dans [les données Kubernetes de requête](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#view-data), après le tableau. - -* J'ai réécrit les instructions pour [consulter et gérer l'API clé](/docs/apis/intro-apis/new-relic-api-keys/#keys-ui) afin d'en améliorer l'exactitude et la clarté. - -* Instructions mises à jour sur la façon d'utiliser l'explorateur d'API dans [Utiliser l'explorateur d'API](/docs/apis/rest-api-v2/api-explorer-v2/use-api-explorer) et [lister l'identifiant d'application, l'ID hôte, l'ID d' instance](/docs/apis/rest-api-v2/get-started/list-application-id-host-id-instance-id) pour correspondre à l'explorateur d'API actuel. - -* J'ai réintégré l'exemple de [corrélation de l'infrastructure avec OpenTelementry APM](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/#infrastructure-correlation). - -* J'ai noté comment éviter les noms de métriques en double lors de [la migration vers l'intégration Azure Monitor](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#migrate). - -### Notes de version - -Consultez nos articles What's New pour en savoir plus sur les nouvelles fonctionnalités et sorties : - -* [New Relic Pathpoint connecte la télémétrie aux indicateurs clés de performance (KPI) de l'entreprise.](/whats-new/2024/10/whats-new-10-10-pathpoint) - -Restez au courant de notre sortie la plus récente : - -* [Boîte de réception des erreurs pour Android v5.25.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-52501) - * Permet de parcourir les erreurs, d'inspecter les attributs profilés, et bien plus encore. - -* [Agent Flutter v1.1.4](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-114) - * Mise à jour de l'agent iOS vers la version 7.5.2 - -* [Intégration Kubernetes v3.29.6](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6) - - * Mises à jour : Passez à la version 1.23.2 - * Mise à jour de la bibliothèque commune pour Prometheus vers la version 0.60.0 - -* [Agent Python v10.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100) - - * Compatible avec Python 3.13 - * Fournit une nouvelle API de gestion du contexte - * Permet de générer des rapports sur les identifiants Docker Amazon ECS Fargate - * Comprend l'instrumentation pour `SQLiteVec` - -* [Agent Unity v1.4.1](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141) - - * Mises à jour des agents natifs Android et iOS - * Contient du débogage \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx deleted file mode 100644 index 5993cc88148..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-18' -version: 'version: October 11-17, 2024' -translationType: machine ---- - -### Nouveaux documents - -* [Le log de Forward Kong Gateway](/docs/logs/forward-logs/kong-gateway/) décrit comment installer et utiliser ce nouveau plugin de transfert de logvia l'intégration Kubernetes. -* [La documentation relative à le monitoring d'Azure App Service](/docs/apm/agents/manage-apm-agents/azure/monitoring-azure-app-service/) explique comment intégrer ce service Azure à New Relic et fournit des liens vers des instructions sur la configuration de nos agents APM Java, .NET, Node.js et Python. -* [L'introduction à l'explorateur de données](/docs/query-your-data/explore-query-data/query-builder/introduction-new-data-explorer/) explique comment utiliser notre nouvelle interface utilisateur pour interroger vos données et obtenir des informations plus détaillées sur la manière dont la plateforme New Relic peut vous aider et résoudre vos problèmes. -* [Le moniteur d'environnements Amazon ECS avec agents de langage APM](/docs/infrastructure/elastic-container-service-integration/monitor-ecs-with-apm-agents/) vous aide à installer nos agents APM sur votre environnement Amazon ECS. -* [La section « Migrer vers NRQL](/docs/apis/rest-api-v2/migrate-to-nrql/) explique comment migrer votre requête API REST v2 vers une requête NRQL. - -### Changements majeurs - -* Nous avons transféré le contenu de notre site open source vers notre site de documentation. -* Nous avons clarifié la manière de gérer les secrets avec l' [opérateur d'agent Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/). - -### Modifications mineures - -* Dans [les métriquesOpenTelemetry de New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics/#otlp-summary), nous avons précisé que les métriques récapitulatives OpenTelemetry ne sont pas prises en charge. -* Mise à jour d'une capture d'écran dans [la règle d'alerte recommandée et dashboards](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies/#add-recommended-alert-policy) pour préciser où trouver les vignettes Kubernetes et Google Kubernetes Engine. -* Suppression des documents Stackato et WebFaction relatifs à l'agent Python APM, car ils ne sont plus pertinents. -* Ajout d'un nouveau point de terminaison de monitoring des navigateurs à notre document [Réseaux](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Correction de problèmes mineurs dans nos documents de dépannage de monitoring des navigateurs. -* Dans [la section dépannage des erreurs de mise à niveau de l'environnement d'exécution,](/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting/#scripted-api-form) il est décrit comment résoudre les problèmes rencontrés lors de l'utilisation d'anciens environnements d'exécution Node avec des objets `$http`. -* Dans [.NET API d'agent](/docs/apm/agents/net-agent/net-agent-api/net-agent-api), nous avons ajouté `NewRelic.Api.Agent.NewRelic` à l'appel d'API `ITransaction` et ajouté le nouvel appel d'API `RecordDatastoreSegment`. - -### Notes de version - -Restez au courant de notre sortie la plus récente : - -* [Agent Android v7.6.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-761/) - - * Ajoute la prise en charge du plug-in Android Gradle 8.7 - * Correction d'un problème de chargement des fichiers de modélisation ProGuard/DexGuard. - * Autres débogages - -* [L'agent de browser v1.269.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0/) - - * Permet au chargeur MicroAgent sur NPM d'utiliser les API de logging pour capturer manuellement les données log. - * Ajoute des métadonnées d'instrumentation aux charges utiles de logging - * Correction de bugs liés aux erreurs de politique de sécurité de traçage de session et de relecture de session - -* [Agent Go v3.35.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0/) - - * Ajoute la prise en charge du rapport sécurisé sur les événements liés aux cookies - * Utilise la valeur `error.Error()` pour l'attribut log - * Améliore la prise en charge des URL pour les connexions au serveur AMQP - * Divers débogages - -* [Extension Lambda v2.3.14](/docs/release-notes/lambda-extension-release-notes/lambda-extension-2.3.14/) - - * Ajoute une fonctionnalité permettant d'ignorer les vérifications de démarrage des extensions. - * Met à jour le fichier README avec des informations sur l'utilisation de la variable d'environnement `NR_TAGS` - * Ajoute la prise en charge de la variable d'environnement booléenne `NEW_RELIC_ENABLED` - -* [Agent .NET v10.32.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0/) - - * Déprécie les variables d'environnement préfixées `NEWRELIC_` - * Met en œuvre une convention de nommage cohérente pour toutes les variables d'environnement. - * Mise à jour de l'instrumentation CosmosDB pour prendre en charge la dernière version - -* [Ping Runtime v1.47.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.47.0/) - * Corrige un problème lié aux permissions utilisateur pour le script de contrôle d'exécution ping pour les utilisateurs non root. - -* [Agent Python v10.2.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200/) - * Ajoute un indicateur d'opérateur de conteneur d'initialisation Azure pour prendre en charge cette option de monitoring des applications de conteneur Azure \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx deleted file mode 100644 index 54278a0ec47..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-07' -version: 'November 2 - November 7, 2025' -translationType: machine ---- - -### Nouveaux documents - -* Ajout [d'exemples de contrôle d'accès aux données NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-data-access-control) afin de fournir des exemples pratiques de gestion du contrôle d'accès aux données via l'API NerdGraph. -* Ajout [de la détection de valeur hors norme](/docs/alerts/create-alert/set-thresholds/outlier-detection) pour fournir des conseils pour la configuration de la condition d'alerte de détection de valeur hors norme. -* Ajout [d'un catalogue d'infrastructure](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog/) pour fournir une documentation améliorée avec les prérequis pour la configuration de infrastructure monitoring. -* Ajout [de cartes des services de streaming multimédia](/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps/) pour faciliter la compréhension des relations entre le streaming multimédia et les entités navigateur/mobile. -* Ajout [d'une boîte de réception des erreurs pour la diffusion multimédia](/docs/errors-inbox/media-streaming-group-error/) afin de fournir des instructions pour le regroupement et la gestion des erreurs de diffusion multimédia. - -### Changements majeurs - -* [Configuration du contrôle d'agent](/docs/new-relic-control/agent-control/configuration) mise à jour avec des exemples YAML révisés pour plus de clarté et des noms de champs mis à jour. -* [Configuration du contrôle des agents](/docs/new-relic-control/agent-control/setup) mise à jour avec des exemples de configuration YAML améliorés. -* [Réinstrumentation du contrôle des agents](/docs/new-relic-control/agent-control/reinstrumentation) mise à jour avec des exemples YAML actualisés pour une meilleure précision. -* [Dépannage du contrôle des agents](/docs/new-relic-control/agent-control/troubleshooting) mis à jour avec des exemples configuration améliorés. - -### Modifications mineures - -* Ajout d'informations sur la compatibilité avec MariaDB à la documentation [relative aux exigences d'intégration de MySQL](/install/mysql/). -* Ajout [du contrôle d'accès aux données](/docs/accounts/accounts-billing/new-relic-one-user-management/data-access-control) pour fournir des conseils complets pour contrôler l'accès aux données télémétriques à l'aide de politiques de données. -* Documentation [cloud d'intégration GitHub](/docs/service-architecture-intelligence/github-integration/) mise à jour avec les dernières informations configuration. -* [Documentation CLI de diagnostic](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-360) mise à jour pour la version 3.60. -* Documentation mise à jour de la configuration [des ports Vizier](/docs/ebpf/k8s-installation/) pour Kubernetes. - -### Notes de version - -* Restez au courant de nos dernières sorties : - - * [Agent Python v11.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100): - - * Ajout de la prise en charge de Python 3.14. - * Ajout de variables d'environnement pour les paramètres de filtrage des attributs. - * Ajout de la prise en charge des générateurs asynchrones dans les décorateurs transaction. - * Ajout de la prise en charge de modèles supplémentaires dans l'instrumentation AWS Bedrock, notamment les modèles Claude Sonnet 3+ et les modèles prenant en compte les régions. - * Ajout d'une instrumentation pour les nouvelles méthodes AWS Kinesis, notamment describe\_account\_settings, update\_account\_settings, update\_max\_record\_size et update\_stream\_warm\_throughput. - * Correction d'une erreur de récursion dans aiomysql lors de l'utilisation d'un pool de connexions. - * Correction d'un bug où les propriétés n'étaient pas correctement transmises au producteur Kombu. - * Correction d'une erreur survenant lors de l'appel à shutdown\_agent depuis le thread harvest. - - * [Agent iOS v7.6.0](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760): - - * Ajout d'une fonctionnalité de prévisualisation publique Session Replay mobiles. - * La version iOS requise a été mise à jour à iOS 16. - * Correction d'un problème lié à la gestion des exceptions pouvant survenir lors du logging. - * Correction d'un avertissement concernant un nom de paramètre incorrect. - - * [Agent Android v7.6.12](/docs/release-notes/mobile-release-notes/android-release-notes/android-7612): - - * Ajout de la fonctionnalité de relecture de session pour Jetpack Compose. - * Sortie officielle Session Replay version de prévisualisation publique. - * Correction de plusieurs bugs liés à la relecture des sessions. - - * [Intégration Kubernetes v3.49.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0): - - * Consultez les notes de sortie GitHub pour obtenir des informations détaillées sur les modifications. - * Inclus dans les versions graphiques newrelic-infrastructure-3.54.0 et nri-bundle-6.0.20. - - * [Logs v251104](/docs/release-notes/logs-release-notes/logs-25-11-04): - - * Ajout de la prise en charge des formats de frais log spécifiques à .NET. - * Introduction de la variable d'environnement NEW\_RELIC\_FORMAT\_LOGS pour le traitement des formats log spécifiques à .NET. - - * [Environnement d'exécution de Node browser rc1.2](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.2): - - * J'ai mis à jour mon navigateur Chrome vers la version 141. - * Correction des vulnérabilités CVE-2025-5889 pour l'extension du renfort. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx deleted file mode 100644 index 320567db62d..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-14' -version: 'November 08 - November 14, 2025' -translationType: machine ---- - -### Nouveaux documents - -* Ajout d' [un mode de consentement du Browser ](/docs/browser/new-relic-browser/configuration/consent-mode)pour documenter la mise en œuvre de la gestion du consentement afin monitoring la conformité des navigateurs aux réglementations en matière de protection de la vie privée. -* Ajout [d'extensions Java à la fonction d'attachement automatique de Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach) afin de fournir des conseils de configuration pour l'instrumentation Java APM dans les environnements Kubernetes. -* Ajout de la documentation [« Apportez votre propre configurationde cache »](/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache) pour les options configuration de cache OpenTelemetry pour le tracing distribué. - -### Changements majeurs - -* [Intelligence artificielle de réponse](/docs/alerts/incident-management/response-intelligence-ai) améliorée avec des capacités de synthèse log d'IA pour l'analyse des alertes basées sur log. -* Documentation de gestion des calculs renommée et restructurée en [Gestion de la consommation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management). -* [configurationde l'agentJava ](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file)mise à jour avec les options de nommage transaction Spring et configuration de l'analyseur SQL. -* Mise à jour [des rôles personnalisés d'intégration GCP](/docs/infrastructure/google-cloud-platform-integrations/get-started/integrations-custom-roles) avec des autorisations révisées pour 4 services cloud Google. -* Documentation [de dépannage MCP](/docs/agentic-ai/mcp/troubleshoot) améliorée avec des scénarios et des solutions de configuration du protocole de contexte de modèle. -* [Configuration améliorée de l'agent Ruby](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration) avec de nouvelles options de configuration des erreurs de nouvelle tentative Sidekiq. -* [Installation de l'agent PHP](/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian) mise à jour avec prise en charge de Debian Trixie. - -### Modifications mineures - -* Ajout de la compatibilité Java 25 aux [exigences de compatibilité de l'agentJava ](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent). -* Ajout de la prise en charge de .NET 10 aux [exigences de compatibilité d'agent .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). -* Mise à jour [des alertes de gestion des niveaux de service](/docs/service-level-management/alerts-slm). -* Mise à jour de [la compatibilité PHP de d'agent](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) avec les informations de version de Drupal et Laravel. -* [Compatibilité d'intégration Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements) mise à jour. -* Mise à jour [des exigences de compatibilitéJava de l'agent](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent) avec prise en charge framework. - -### Notes de version - -Consultez les publications « Nouveautés » pour : - -* [Lancement du serveur New Relic MCP en aperçu public](/whats-new/2025/11/whats-new-11-05-mcp-server) - -* [Détection de valeurs hors norme de New Relic en aperçu public](/whats-new/2025/11/whats-new-11-05-outlier-detection) - -* [Résumé des alertes des logs IA (Aperçu)](/whats-new/2025/11/whats-new-11-13-AI-Log-Alert-Summarization) - -* Restez au courant de nos dernières sorties : - - * [Agent Node.js v13.6.4](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4): - - * Correction du comportement de MessageConsumerSubscriber pour que les transactions de consommation de messages se terminent correctement. - * Correction de MessageProducerSubscriber pour définir correctement l'indicateur d'échantillonnage sur traceparent. - * Priorité d'enregistrement du middleware Bedrock corrigée pour une désérialisation correcte de la charge utile. - - * [Agent Node.js v13.6.3](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3): - - * Correction de la gestion du flux d'instrumentation OpenAI avec stream\_options.include\_usage. - * Correction de l'affectation du nombre de jetons @google/IA générative (GenAI) à LlmCompletionSummary. - * Correction de l'affectation du nombre de jetons pour l'instrumentation AWS Bedrock. - - * [Agent Java v8.25.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250): - - * Ajout de la prise en charge de Java 25. - * Ajout de la prise en charge de Logback-1.5.20. - * Introduction d'une option configuration de nommage transaction pour Spring Controller. - * Ajout de la prise en charge Kotlin Coroutines v1.4 et supérieures. - * Correction d'une erreur dans la logique d'analyse des noms de classes. - * Correction d'un problème potentiel de mémoire dans le logging des erreurs avec une trace d'appels importante. - - * [Agent Ruby v9.23.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0): - - * Ajout de sidekiq.ignore\_retry\_errors Option de configuration permettant de contrôler la capture des erreurs de nouvelle tentative. - * Enregistrement du déploiement Capistrano obsolète (suppression dans la v10.0.0). - * Application configuration d'échantillonnage parent distant améliorée pour un tracing distribué plus cohérent. - - * [Agent .NET v10.46.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1): - - * Suppression de l'étendue de consommation des transactions en mode Processeur d' Azure Service Bus pour une précision accrue. - * Mise à jour de la sérialisation de l'énumération ReportedConfiguration pour une meilleure clarté de l'interface utilisateur. - - * [Intégration Kubernetes v3.50.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0): - - * Mise à jour de la version du graphique KSM e2e vers la version 2.16. - * Ajout de la prise en charge de la métrique kube\_endpoint\_address. - * Correction d'un problème de modélisation de priorityClassName lorsque la prise en charge de Windows est activée. - - * [Gestionnaire de tâchesSynthetics sortie 486](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-486): - - * Correction de vulnérabilités Ubuntu et Java, notamment CVE-2024-6763 et CVE-2025-11226. - - * [Synthetics Ping Runtime v1.58.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.0): - - * Correction de vulnérabilités Ubuntu et Java, notamment CVE-2025-5115 et CVE-2025-11226. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx deleted file mode 100644 index ecd046fab79..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-21' -version: 'November 17 - November 21, 2025' -translationType: machine ---- - -### Nouveaux documents - -* Ajout [de la migration des règles de suppression vers les règles cloud du pipeline](/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules/) afin de fournir des instructions complètes pour la migration des règles de suppression existantes vers le nouveau système de règles cloud du pipeline. -* Ajout d'une [section sur l'incompatibilité avec PHPUnit](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) afin de fournir des conseils de dépannage pour les erreurs de mémoire insuffisante de PHPUnit version 11+ avec l'agent PHP New Relic. - -### Changements majeurs - -* La documentation relative à l'analyse des données de test PHPUnit a été supprimée suite à l'arrêt du support de PHPUnit par l'agent PHP. Remplacé par la documentation de dépannage pour les problèmes d'incompatibilité de PHPUnit. -* [Entité de recherche et de filtrage](/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) restructurée pour une meilleure organisation et ajout d'une nouvelle fonctionnalité de filtrage du catalogue. -* Mise à jour de [l'installation de New Relic eBPF sur les environnements Kubernetes ](/docs/ebpf/k8s-installation)avec des options configuration de découplage pour monitoring des performances réseau. - -### Modifications mineures - -* Ajout des informations sur la rétention des données multimédias de streaming à la documentation [Gérer la rétention des données](/docs/data-apis/manage-data/manage-data-retention). -* PHPUnit a été retiré du tableau [de compatibilité PHP et des exigences](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) de compatibilité suite à la fin du support. -* Correction d'un exemple de requête NRQL pour [les requêtes d'utilisation et les alertes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). -* [Page des paramètres de l'applicationBrowser ](/docs/browser/new-relic-browser/configuration/browser-app-settings-page/)mise à jour avec les informations configuration du stockage local. -* Ajout d'un mode de consentement à la navigation dans la documentation du browser. -* Mise à jour [des paramètres de configuration](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings) du SDK mobile. -* Documentation améliorée [sur les types de graphiques,](/docs/query-your-data/explore-query-data/use-charts/chart-types) avec des informations supplémentaires. -* [Présentation](/docs/agentic-ai/mcp/overview) et [dépannage](/docs/agentic-ai/mcp/troubleshoot) mis à jour pour MCP avec clarification des rôles RBAC. - -### Notes de version - -* Restez au courant de nos dernières sorties : - - * [Agent Go v3.42.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0): - - * Ajout de nouvelles options configuration du nombre maximal d'échantillons pour les transactions, Insights personnalisées, les erreurs et les logs. - * Ajout de la prise en charge des en-têtes MultiValue dans nrlambda. - * Suppression des variables inutilisées dans nrpxg5. - * Correction d'un bug où l'événement d'erreur ne signalait pas correctement l'erreur attendue. - - * [Agent .NET v10.47.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0): - - * Ajout d'un mécanisme de stockage transaction optionnel pour permettre aux transactions de suivre le flux d'exécution des applications web ASP.NET. - * Correction d'une exception de référence nulle liée à l'instrumentation d'Azure Service Bus. - * Correction de l'instrumentation OpenAI pour gérer les complétions de chat lorsque le paramètre messages n'est pas un éventail. - - * [Agent Node.js v13.6.5](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5): - - * Instrumentation Express mise à jour pour ignorer les erreurs lorsque le gestionnaire suivant passe par la route ou le routeur. - * Mise à jour de MessageConsumerSubscriber pour attendre la fin du rappel du consommateur lorsqu'il s'agit d'une promesse. - - * [Agent Node.js v13.6.6](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6): - - * Mise à jour de l'instrumentation Express de app.use ou router.use pour encapsuler correctement tous les intergiciels définis. - * Ajout d'une configuration pour distributed\_tracing.samplers.partial\_granularity et distributed\_tracing.samplers.full\_granularity. - - * [Agent PHP v12.2.0.27](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27): - - * Ajout de la prise en charge de Laravel 12. - * Ajout de la prise en charge de Laravel Horizon sur Laravel 10.x+ et PHP 8.1+. - * Correction de la gestion des exceptions des tâches en file d'attente dans Laravel. - * Version de golang mise à jour à 1.25.3. - - * [Intégration Kubernetes v3.50.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1): - - * Mise à jour vers la version 3.50.1 avec débogage et améliorations. - - * [Agent d'infrastructure v1.71.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711): - - * Dépendance newrelic/nri-Docker mise à jour vers la version 2.6.3. - * Dépendance newrelic/nri-flex mise à jour vers la version 1.17.1. - * Mise à jour de la version de Go vers la version 1.25.4. - * Dépendance newrelic/nri-Prometheus mise à jour vers la version 2.27.3. - - * [Logs du 25-11-20](/docs/release-notes/logs-release-notes/logs-25-11-20): - - * Correction de la vulnérabilité CVE-2025-53643 dans la fonction lambda aws-log-ingestion. - * Mise à jour de la bibliothèque aiohttp vers la version 3.13.2 et la version poésie pour la version 1.8.3. - - * [Environnement d'exécution du browser Node rc1.3](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.3): - - * J'ai mis à jour mon navigateur Chrome vers la version 142. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx deleted file mode 100644 index 3f26f245126..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-05-24' -version: 'version: May 17-23, 2024' -translationType: machine ---- - -### Nouveaux documents - -* Notre nouvelle [intégrationApache Mesos](/docs/infrastructure/host-integrations/host-integrations-list/apache-mesos-integration) vous aide à monitor les performances du noyau de vos systèmes distribués. -* Notre nouveau [cloudd'intégration Temporal](/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration) vous aide à monitor et à diagnostiquer les problèmes workflow, d'espace de nommage et d'applications évolutives dans votre cloud Temporal. -* Avez-vous une [application .NET sur AWS Elastic Beanstalk](/docs/apm/agents/net-agent/install-guides/install-net-agent-on-aws-elastic-beanstalk)? Ce nouveau document d'installation présente une méthode claire pour intégrer ces données à notre plateforme. - -### Changements majeurs - -* Ajout et mise à jour d'exemples de code de moniteur Synthétique et de script de navigateur pour [monitoring les bonnes pratiques de Synthétique](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide) et [la référence du navigateur de script Synthétique](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100). Les exemples de code font partie des choses que nos lecteurs demandent le plus, nous sommes donc toujours heureux d'en voir davantage. - -* Dans notre documentation monitoring des performances réseau, de nombreuses petites mises à jour ont conduit à un changement majeur : mise à jour des environnements pris en charge par Podman dans 17 documents. - -* Nous avons clarifié le fonctionnement [des logs live archives](/docs/logs/get-started/live-archives) et les conditions [de disponibilité de ceslog ](/docs/logs/get-started/live-archives-billing). - -* Ajout d'un diagramme et de variables d'environnement à [l'instrument de monitoring Lambda de votre couche d'image conteneurisée](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images/). - -* L'API REST v1 de New Relic n'est plus prise en charge et nous avons supprimé plusieurs documents s'y rapportant. - -* Une mise à jour massive de notre documentation sur infrastructure de monitoring : - - * Alignez-le sur notre guide de style. - * Supprimez le contenu inutile. - * Rendre le document d'installation plus visible dans le menu de navigation de gauche. - * Améliorer le flux du document d'installation. - -* La migration de notre site développeurs vers la documentation se poursuit, avec plus de 30 documents migrés cette semaine. - -* À compter du 23 mai 2024, monitoring de l'IA prend en charge Java. Nous avons mis à jour plusieurs documents monitoring de l'IA pour refléter cette importante mise à jour. - -### Modifications mineures - -* Mise à jour [des contrôles de sécurité du stockage des données dans le cloud pour une meilleure confidentialité,](/docs/security/security-privacy/data-privacy/security-controls-privacy/#cloud-data-storage) avec un rapport de conformité des liens. -* Nous avons simplifié les étapes [d'installation de .NET via yum](/install/dotnet/installation/linuxInstall2/#yum). -* Documentation [de compatibilité Python](/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent/#basic) mise à jour pour indiquer que nous prenons désormais en charge Python 3.12. -* [Compatibilité .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) mise à jour pour ajouter que nous prenons en charge la version `Elastic.Clients.Elasticsearch` 8.13.12 du datastore. -* Tableau des modules instrumentés [de compatibilité de l'agent APMNode.js ](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent)mis à jour. -* Mise à jour des régions et zones prises en charge [par AWS Privatelink](/docs/data-apis/custom-data/aws-privatelink). -* L'agent d'infrastructure prend désormais en charge Ubuntu 24.04 (Noble Numbar), mais nous ne prenons pas encore en charge infrastructure plus les logs sur cette version d'Ubuntu. -* Si vous utilisez [CyberARK et Microsoft SQL Server](/docs/infrastructure/host-integrations/installation/secrets-management/#cyberark-api) avec l'authentification Windows, nous avons précisé que vous devez faire précéder votre nom d'utilisateur de votre domaine. -* Dans [la configuration de notre agent .NET APM](/docs/apm/agents/net-agent/configuration/net-agent-configuration/#error-ignoreErrors), nous avons ajouté des variables d'environnement pour les codes d'état ignorés et attendus. -* Dans [vos graphiques](/docs/query-your-data/explore-query-data/use-charts/use-your-charts), nous avons clarifié ce que nous entendons par KB, MB, GB et TB. (Nous utilisons le Système international d'unités, qui utilise les puissances de 10 pour les calculs.) -* Dans [les paramètres de messagerie](/docs/accounts/accounts/account-maintenance/account-email-settings), nous avons précisé les caractères autorisés et les limites des adresses e-mail des utilisateurs de New Relic. -* Ajout du point de terminaison URL du service de validation IAST à la table de point de terminaison New Relic télémétrie de nos [réseaux](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Ajout d'une astuce sur la façon de monitor plusieurs versions de traps SNMP sur un hôte dans [monitoring des performances SNMP](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring). -* Si vous souhaitez étendre votre [instrumentation Node.js pour inclure Apollo Server](/docs/apm/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs/#extend-instrumentation), nous avons ajouté des liens vers des fichiers README utiles sur GitHub. -* Ajout d'informations de compatibilité .NET à [monitoring de la compatibilité et des exigences de l'IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#compatibility). - -### Notes de sortie et articles « Quoi de neuf » - -* [L'agent de browser v1.260.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1) -* [Agent d'infrastructure v1.52.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523) -* [Agent Java v8.12.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120) -* [Gestionnaire de tâches v370](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-370) -* [Intégration Kubernetes v3.28.7](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7) -* [Application mobile pour Android v5.18.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5180) -* [Agent .NET v10.25.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0) -* [Environnement d'exécution de l'API Node v1.2.1](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.1) -* [Environnement d'exécution de l'API Node v1.2.58](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.58) -* [Environnement d'exécution de l'API Node v1.2.67](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.67) -* [Environnement d'exécution de l'API Node v1.2.72](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.72) -* [Environnement d'exécution de l'API Node v1.2.75](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.75) -* [Environnement d'exécution de l'API Node v1.2.8](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.8) -* [Agent Node.js v11.17.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0) -* [Agent PHP v10.21.0.11](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11) \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx deleted file mode 100644 index e7f221a6c2e..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-06-28' -version: 'version: June 21-27, 2024' -translationType: machine ---- - -### Nouveaux documents - -* La fonctionnalité monitoring des applications mobiles [qui détecte les applications ne répondant pas](/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding) vous aide à suivre et à analyser quand et pourquoi votre application Android est bloquée pendant plus de cinq secondes. -* La nouvelle documentation de l'API monitoring des navigateurs [`log()`](/docs/browser/new-relic-browser/browser-apis/log) et [`wrapLogger()`](/docs/browser/new-relic-browser/browser-apis/wraplogger) définit la syntaxe, les exigences, les paramètres et des exemples sur la façon d'utiliser ces nouveaux points de terminaison. - -### Changements majeurs - -* Nous avons supprimé notre catégorie de niveau supérieur `Other capabilities` et migré tout son contenu vers des catégories plus appropriées. Avec chaque chose à sa place, il vous sera plus facile de trouver ce que vous cherchez. -* Nous avons déplacé les exemples de collecteur OpenTelemetry de notre site de documentation vers notre `newrelic-opentelemetry-examples`]\([https://github.com/newrelic/newrelic-opentelemetry-examples](https://github.com/newrelic/newrelic-opentelemetry-examples)) Un référentiel GitHub pour faciliter la maintenance et améliorer la visibilité de leur code source ouvert. -* Notre monitoring de l'IA prend en charge [les modèles NVIDIA NIM](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#deploy-at-scale) et ne nécessite aucune configuration supplémentaire en dehors de nos flux d'installation manuels ou basés sur une interface utilisateur. Pour en savoir plus, consultez notre blog [monitoring de l'IA pour NVIDIA NIM](https://newrelic.com/blog/how-to-relic/ai-monitoring-for-nvidia-nim). - -### Modifications mineures - -* Ajout du point de terminaison d'URL du service de validation IAST aux [points de terminaison](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#agents) et [aux réseaux](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) conformes à FedRAMP. -* Mise à jour [du dépannageIAST ](/docs/iast/troubleshooting/#see-my-application)avec des plages d'adresses IP spécifiques pour afficher une liste blanche si votre application n'apparaît pas. -* [Configuration de l'agentRuby ](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/#instrumentation-aws_sqs)mise à jour avec les informations configuration auto-instrumentation `NEW_RELIC_INSTRUMENTATION_AWS_SQS`. -* Les informations configuration de rapport `ApplicationExitInfo` ont été supprimées des [paramètres de configuration monitoring des applications mobiles](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings), car vous pouvez le faire dans l'interface utilisateur. -* [Les enrichissements de workflow](/docs/alerts/get-notified/incident-workflows/#enrichments) prennent en charge plusieurs variables, ce qui vous permet de personnaliser vos données plus précisément en fonction de vos besoins. -* Nous avons ajouté l'attribut [MobileApplicationExit](/attribute-dictionary/?dataSource=Mobile&event=MobileApplicationExit) à notre dictionnaire de données. Notre dictionnaire de données n'est pas seulement une ressource de documentation, mais il alimente également directement l'interface utilisateur en définitions d'attributs, par exemple lorsque vous écrivez une requête NRQL dans notre générateur de requêtes. -* Suppression de la documentation relative à l'API REST d'alertes obsolète. - -### Notes de sortie et articles « Quoi de neuf » - -* Nouveautés pour [monitoring New Relic : l’IA s’intègre désormais aux microservices d’inférence NVIDIA NIM.](/whats-new/2024/06/whats-new-06-24-nvidianim) - -* Nouveautés de [la mise à jour du nouveau moteur d'exécution du moniteur Synthétique pour éviter tout impact sur votre moniteur Synthétique](/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm) - -* [Agent Android v7.4.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-741) - * `ApplicationExitInfo` La génération de rapports est activée par défaut - -* [L'agent de browser v1.261.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0) - - * Les arguments de l'API de logging sont transmis sous forme d'objets pour une extensibilité accrue. - * Diverses autres nouveautés et débogage - -* [CLI de diagnostic (nrdiag) v3.2.7](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-327) - -* [Intégration Kubernetes v3.29.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0) - - * Ajout de la prise en charge des versions 1.29 et 1.30, suppression de la prise en charge des versions 1.24 et 1.25 - * Dépendance mise à jour : package Kubernetes v0.30.2 et Alpine v3.20.1 - -* [Application mobile pour iOS v6.5.0](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6050) - - * Afficher toutes les entités faisant partie d'une workload - * Plus d'options de personnalisation dashboard - * Diverses autres améliorations - -* [Agent Node.js v11.20.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0) - - * Prise en charge de l'API de messages Anthropic's Claude - * Diverses autres améliorations - -* [Agent Node.js v11.21.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0) - * Prise en charge de la récupération des ID de conteneur à partir de l'API de métadonnées ECS - -* [Agent PHP v10.22.0.12](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12) - - * Fin de vie du support pour PHP 7.0 et 7.1 - * Divers débogages - -* [Agent Ruby v9.11.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0) - - * Nouvelle instrumentation pour le gem `aws-sdk-sqs` - * Un couple de débogage \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index 8bc0d292535..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### Nouveaux documents - -* Ajout d'une nouvelle fonctionnalité sur [la façon de déboguer les problèmes de l'agent New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), y compris le logging détaillé, monitoring des demandes réseau et l'événement d'inspection pour un dépannage amélioré dans les versions d'agent 1.285.0 et supérieures. -* Ajout de la prise en charge [d’Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) pour le monitoring des fonctions `python` et `.node.js`. -* Ajout [d'un optimiseur de calcul](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) pour des informations détaillées exploitables pour améliorer l'efficacité du calcul, avec une fonctionnalité permettant d'identifier les inefficacités, de fournir des recommandations d'optimisation et d'estimer les économies de CCU dans la plateforme New Relic. -* Ajout [d'Intelligence Coûts du cloud](/docs/cci/getting-started/overview), offrant des outils de visibilité et de gestion des coûts cloud, y compris des fonctionnalités telles que la répartition complète des coûts, l'allocation des coûts Kubernetes, l'estimation des coûts en temps réel et la collecte de données inter-comptes, prenant actuellement en charge uniquement les coûts AWS cloud. -* Ajout [de l'observabilité OpenTelemetry pour Kubernetes avec l'intégration indépendante du fournisseur de fonctionnalités New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) pour monitoring transparente du cluster via le graphique Helm, améliorant les signaux de télémétrie pour les métriques, les événements et les logs transmis aux outils et au tableau de bord de New Relic. -* Ajout [de limitations et de dépannage pour l'intégration Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) -* Ajout de l'intégration AWS via [CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), prenant en charge l'API Polling pour les services non pris en charge. -* Ajout [d'une balise améliorée pour la base de données entité New Relic](/docs/infrastructure/host-integrations/db-entity-tags/) pour le moniteur de base de données entité via l'intégration sur hôte pour MySQL et MS SQL Server, enrichissant les métadonnées informations détaillées et l'organisation dans New Relic sans affecter la facturation ou la télémétrie existante. - -### Changements majeurs - -* Ajout de fonctions non-agrégateur aux [référencesNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/). -* Mise à jour des [exigences de l'agentRuby et du framework pris en charge](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/). -* Ajout des logs en tant qu'événements New Relic personnalisé (New Relic Custom Events) aux [logs OpenTelemetry dans le document New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events). -* Mise à jour des runtimes pris en charge pour les fonctions Linux, Windows et conteneurisées dans le document [Compatibilité et exigences pour les fonctions Azure instrumentées](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes). -* Mise à jour des données métriques pour [l'intégration cloudConfluent](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics). -* Suppression de GCP Cloud Run de [la configuration de l'agent Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) -* [Compatibilité et exigences mises à jour pour monitoring de l'IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) pour inclure une bibliothèque supplémentaire prise en charge par l'agent .NET. -* Ajout du point de terminaison New Relic télémétrie dualstack au [trafic réseau New Relic](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Ajout `GcpHttpExternalRegionalLoadBalancerSample` à l' [intégration de monitoring de Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/). -* Ajout de la procédure de démarrage OpenShift sur la façon d' [installer le document du gestionnaire de tâches Synthetics](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install). -* Mise à jour de la [version 12 de l'agent Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) -* Ajout d'une intégration transparente pour [AWS avec New Relic utilisant CloudFormation et le flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), y compris la prise en charge de l'interrogation API. - -### Modifications mineures - -* Ajout `Transaction` comme période de conservation pour [la trace de transaction](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/). -* Ajout `Destination` comme nouvelle catégorie aux [règles et limites d'alerte](/docs/alerts/admin/rules-limits-alerts/). -* Ajout d’une légende dans [le document Introduction au service Azure Native New Relic](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) pour garantir que les paramètres de diagnostic sur les ressources Azure sont correctement configurés ou désactiver le transfert via le service Azure Native New Relic pour empêcher l’envoi de données à la plateforme New Relic. -* Mise à jour de la dernière bibliothèque compatible pour [l'agent .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/). -* Ajout d'un appel dans le document [de notes de sortie de l'agent iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) pour annoncer qu'à partir de la version 7.5.4 du SDK iOS, un changement entraîne désormais le signalement d'un événement d'exception gérée précédemment supprimé. -* Exigences mises à jour pour les relations service-conteneur pour spécifier l'attribut de ressource pour les environnements Kubernetes et `container.id` pour les environnements non-Kubernetes, garantissant configuration de télémétrie appropriée pour [les ressources-OpenTelemetry dans New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/). -* Ajout de la prise en charge CLI pour l'installation d'une version [d'agent infrastructure spécifique](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), permettant un déploiement cohérent et une compatibilité système ; spécifiez la version à l'aide de `@X.XX.X` dans le nom de la recette. -* Ajout d'une légende pour souligner les exigences d'accès aux rôles pour l'utilisation des fonctionnalités **Manage Account Cardinality**, **Manage Metric Cardinality** et **Create Pruning Rules** dans l'interface utilisateur ; assurez-vous que les autorisations sont définies dans la [gestion de la cardinalité](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table). -* Mise à jour de la [compatibilité et des exigences pour l'agent Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) vers `v12.23.0`. -* Ajout des autorisations minimales requises pour la configuration d'un [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration). -* Mise à jour de l'attribut `FACET` utilisation maximale acceptable des limites de 5 000 à 20 000 valeurs pour [la syntaxe d'alerte NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). - -### Notes de version - -* Annoncé le 7 janvier 2026 comme date de fin de vie des [règles d'abandon ciblant l'événement infrastructure dans `SystemSample`, `ProcessSample`, `NetworkSample`, et `StorageSample`](/eol/2025/05/drop-rule-filter/) - -* À compter d'aujourd'hui, la fin de vie de [FACET sur messageId et horodatage en condition d'alerte](/eol/2025/07/deprecating-alert-conditions/). - -* Annoncé le 28 octobre 2025 comme date de fin de vie pour [Attention requise](/eol/2025/07/upcoming-eols/). - -* Consultez nos articles Quoi de neuf : - - * [Envoyer une notification directement à Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [New Relic Compute Optimizer est généralement disponible !](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [Logs Cross Account Query dans le Unified Query Explorer](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [Monitoring Kubernetes avec OpenTelemetry est généralement disponible !](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [Monitoring des nœuds Windows pour Kubernetes est désormais en version préliminaire publique](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [Identifier les problèmes de performances : filtrage avancé des pages vues et des Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [Vous pouvez désormais trier par erreurs les plus récentes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [Vos données de navigateur, vos termes : Nouvelles options de contrôle](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [Analyse approfondie des requêtes pour la base de données désormais généralement disponible](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [Les prévisions NRQL et les alertes prédictives sont désormais disponibles pour tous](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [APM + OpenTelemetry Convergence GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [L'intégration agentique pour GitHub Copilot et ServiceNow est désormais disponible](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* Restez au courant de nos dernières sorties : - - * [Exécution de l'API Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * Problèmes de vulnérabilité résolus. - - * [Ping Runtime v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * Correction des vulnérabilités de logback-core pour l'exécution du ping. - * Correction des vulnérabilités du serveur Jetty pour l'exécution du ping. - * Correction des vulnérabilités d'Ubuntu pour l'exécution du ping. - - * [Agent Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * Mettre à jour les définitions `BrowserInteraction` et `previousUrl`. - * Ajout d'un événement d'inspection supplémentaire. - * Valeur API `finished` fixe `timeSinceLoad`. - - * [Intégration Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * Correction des ajustements internes liés au backend et au CI pour la compatibilité future de la plateforme. - - * [Gestionnaire de tâches v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * Correction d'un problème qui empêchait certains clients de voir les résultats de certains moniteurs avec des temps d'exécution plus longs. - - * [Agent Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * Prise en charge ajoutée pour `Azure Function Apps`. - * Correction `pb2` fichiers pour activer la prise en charge `protobuf v6`. - - * [Agent Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * Amélioration des performances pour résoudre les ANR lors du reporting des logs. - * Correction d'un problème permettant de continuer à signaler les logs à la fin de l'application. - * Résolution d’un problème avec monitoring de l’état de l’application et la transmission des données. - * Amélioration de quelques violations lors de l'activation du mode strict. - - * [Intégration Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * Mis à jour `golang.org/x/crypto` à `v0.39.0`. - * Mis à jour `go` à `v1.24.4`. - - * [Agent .NET v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Prise en charge ajoutée pour Azure Service Bus. - * Correction des erreurs de construction du profileur avec la dernière version de VS. - - * [Agent PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * Ajout de l'API d'exécution Composer à utiliser par défaut pour détecter le package utilisé par les applications PHP. - * Comportement indéfini corrigé lors de l'exécution de l'API Composer. - - * [Exécution du navigateur de nœuds v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * Options de création de Chrome mises à jour pour Chrome 131. - - * [Application mobile pour iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * Amélioration de la fonctionnalité Ask AI avec une connexion socket plus robuste et plus fiable, garantissant une expérience transparente. - - * [Application mobile pour Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * Amélioration de la fonctionnalité Ask AI avec une connexion socket plus robuste et plus fiable, garantissant une expérience transparente. - - * [Agent Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * Ajout de la prise en charge du streaming `openai` v5. - * Prise en charge ajoutée pour l'API `openai.responses.create`. - * Logging des erreurs corrigée pour l'en-tête tracestate non défini. - - * [Agent d'infrastructure v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * Mise à jour de la dépendance `newrelic/nri-winservices` à `v1.2.0` - * Mise à jour tag docker alpine pour `v3.22` - - * [Agent d'infrastructure v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * mettre à jour la dépendance `newrelic/nri-flex` vers `v1.16.6` - - * [Agent Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * Correction de la priorité des conditions de course de l'attribut personnalisé. - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * Le noyau bêta d'OTEL a été augmenté à `v0.128.0` - - * [Agent multimédia pour HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * Introduction d'un nouveau type d'événement. - * Le type d'événement `PageAction` est obsolète. - - * [Agent multimédia pour HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * Activation de la publication npm pour le package, garantissant une accessibilité et une distribution faciles. - * Ajout des builds `cjs`, `esm` et `umd` au dossier `dist`, garantissant la compatibilité avec les formats de modules CommonJS, ES et UMD. - - * [Agent multimédia pour Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * Introduction d'un nouveau type d'événement. - * Le type d'événement `RokuVideo` est obsolète. - * Le type d'événement `RokuSystem` est obsolète. - - * [Agent multimédia pour Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * Renommer `errorName` avec `errorMessage` en `errorName` est obsolète. - - * [Gestionnaire de tâches v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * Mise à niveau de l'image de base fixe de `ubuntu 22.04` à `ubuntu 24.4` - - * [Ping Runtime v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * Mise à niveau de l'image de base améliorée de `ubuntu 22.04` à `ubuntu 24.04` - - * [Intégration Kubernetes v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * Ajout de la prise en charge de monitoring des nœuds Windows dans le cluster Kubernetes. - - * [Application mobile pour Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * Bug corrigé et interface utilisateur améliorée pour une expérience plus fluide. - - * [Agent Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * Ajout de la possibilité de générer des rapports uniquement sur les portées d'entrée et de sortie. - * Prise en charge de Node.js 24 ajoutée. - * Rapport de compatibilité mis à jour. - - * [Exécution de l'API Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * Correction des vulnérabilités pour `CVE-2024-39249` - - * [Application mobile pour iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * Amélioration de la fonctionnalité Ask AI avec une invite dynamique. - - * [Agent Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * Ajout d'un message interne **sur les tâches longues**. - * Problème résolu empêchant la désactivation des traces distribuées. - - * [Exécution du navigateur de nœuds v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * Image de base améliorée - - * [Agent Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Métadonnées liées pour les services Azure App. - * Suppression de l'instrumentation `MonoFlatMapMain`. - - * [Agent Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Limite de taille de valeur d'attribut configurable implémentée - * Rapport de compatibilité mis à jour. - - * [Intégration Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * Mettre à jour la version du graphique kube-state-métriques de `5.12.1` vers `5.30.1` - - * [Agent iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * Correction d'un problème qui pouvait entraîner le fait que le tracing distribué ne contienne pas toutes les informations de compte requises au démarrage d'une session. - - * [Application mobile pour Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * Amélioration des commentaires avec un rendu d'interface utilisateur dynamique. - - * [Application mobile pour Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * Correction de bugs et mise à jour des indicateurs Teams GA pour une expérience utilisateur améliorée. - - * [Agent Go v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * Utilisation annulée. Retour à la version 3.39.0 sortie en raison d'un bug de blocage - * Suppression des tests awssupport\_test.go qui ajoutaient une dépendance directe au module go - - * [Agent Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * Amélioration de l'agent Android natif mis à jour vers la version 7.6.7 - * Amélioration de l'agent iOS natif mis à jour vers la version 7.5.6 - - * [Agent Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Suppression du support pour Node.js 18 - * Version minimale prise en charge mise à jour pour `fastify` vers 3.0.0, `pino` à 8.0.0 et `koa-router` à 12.0.0 - - * [Agent Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * Rapport fixe vide previousUrl comme non défini - - * [Agent d'infrastructure v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * Mise à jour de la dépendance `newrelic/nri-prometheus` vers la version 2.26.2 - - * [Application mobile pour iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * Amélioration des commentaires avec un rendu d'interface utilisateur dynamique. - - * [Agent Android NDK v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * Ajout de la prise en charge de la taille de page de 16 Ko - - * [Agent d'infrastructure v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Modification du handle de processus Windows. - * Remonté `nri-docker` à `v2.5.1`, `nri-prometheus` à `v2.26.1` - - * [Agent .NET v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Ajout de la prise en charge des rubriques dans Azure Service Bus - - * [Agent Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * API AWS Bedrock Converse à instrument fixe - - * [Agent Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Limite de taille de valeur d'attribut configurable implémentée - * Rapport de compatibilité mis à jour - - * [CLI de diagnostic (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * Les erreurs liées à GLIBC fixes telles que `/lib64/libc.so.6: version 'GLIBC_2.34'` introuvable ont été résolues \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx deleted file mode 100644 index 094fc99f50c..00000000000 --- a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-11-13' -version: 1.303.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Allow consent API to be invoked without localStorage access - - Allow nested registrations - - Additional validation to prepare agent for MFE registrations - - Add measure support to register API - - Add useConsentModel functionality - - Retry initial connect call - - Add custom event support to register API - - SMs for browser connect response -bugs: - - Obfuscate custom attributes for logs added after PVE - - memoize promise context propagation to avoid safari hangs -security: [] -translationType: machine ---- - -## v1.303.0 - -### Caractéristiques - -#### Autoriser l'appel de l'API de consentement sans accès au stockage local - -Permet à l'API de consentement de fonctionner sans nécessiter d'accès à localStorage, en conservant un état commun dans l'agent qui contrôle les récoltes. Les applications doivent appeler l'API à chaque chargement de page lorsque l'accès à localStorage est bloqué. - -#### Autoriser les inscriptions imbriquées - -Pour faciliter les relations parent-enfant inhérentes avec l'API d'enregistrement prévue, permettre à l'entité enregistrée d'exposer sa propre API `.register()` pour que les enfants de cette entité puissent s'y enregistrer. Les entités qui s'enregistrent auprès de l'agent conteneur seront liées au conteneur. Une entité qui s'enregistre sous une autre entité enregistrée sera liée à la fois au conteneur et à l'entité parente. - -#### Validation supplémentaire pour préparer l'agent aux enregistrements MFE - -Ajout de règles de validation dans l'agent pour empêcher les mauvaises valeurs pour la cible MFE `id` et `name` en support des enregistrements MFE/v2. - -#### Ajouter la prise en charge des mesures pour enregistrer l'API - -Ajoute la prise en charge de l'API de mesure dans l'objet de réponse d'enregistrement. Ceci soutient la future offre de micro-frontend prévue. - -#### Ajouter la fonctionnalité useConsentModel - -Ajoute la propriété et la fonctionnalité d'initialisation use\_consent\_mode. Ajoute l'appel d'API consent(). Le modèle de consentement, s'il est activé, interdit la collecte d'agents à moins que le consentement ne soit donné via l'appel d'API consent(). - -#### Réessayer l'appel de connexion initial - -Pour éviter toute perte de données, l'agent va désormais réessayer l'appel « RUM » initial une fois de plus pour les codes d'état pouvant être réessayés. - -#### Ajouter le support des événements personnalisés pour enregistrer l'API - -Ajoute des méthodes de capture d'événements personnalisées à l'API d'enregistrement, qui seront utilisées ultérieurement lorsque la prise en charge MFE sera établie. - -#### Réponse SM pour la connexion au navigateur - -Ajoute des indicateurs de prise en charge pour les réponses ayant échoué lors de l'initialisation de l'agrégat page\_view\_event. - -### Débogage - -#### Obfuscation de l'attribut personnalisé pour le journal ajouté après le JcE - -Étend obfuscation pour couvrir l'attribut personnalisé lors de l'événement de journalisation ajouté après la récolte initiale RUM/PageViewEvent. - -#### Mémoriser la propagation du contexte de la promesse pour éviter les blocages de Safari - -Mémorise la propagation du contexte des promesses afin d'éviter les blocages potentiels de browser dans Safari en évitant les opérations de contexte répétées. - -## Déclaration de soutien - -New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. - -Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. - -Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.303.0 de l'agent Browser a été conçue et testée avec les navigateurs et plages de versions suivants : Chrome 131-141, Edge 131-141, Safari 17-26 et Firefox 134-144. Pour les appareils mobiles, la version 1.303.0 a été conçue et testée pour Android OS 16 et iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx deleted file mode 100644 index a13305a9259..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-11-17' -version: rc1.3 -translationType: machine ---- - -### Améliorations - -* J'ai mis à jour mon navigateur Chrome vers la version 142. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx deleted file mode 100644 index ebbb4fdd429..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-11-12' -version: 1.58.0 -translationType: machine ---- - -### Améliorations - -Correction de vulnérabilités liées à Ubuntu et à Java afin de résoudre des problèmes de sécurité dans l'environnement d'exécution de Ping ; vous trouverez ci-dessous la liste des CVE Java corrigées. - -* CVE-2025-5115 -* CVE-2025-11226 \ No newline at end of file diff --git a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx deleted file mode 100644 index a8c1ca7e136..00000000000 --- a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ /dev/null @@ -1,652 +0,0 @@ ---- -title: Actions de communication -tags: - - workflow automation - - workflow - - workflow automation actions - - communication actions - - slack actions - - ms teams actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l'essayiez ! - - Cette fonctionnalité est actuellement fournie dans le cadre d'un programme d'aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Cette page fournit une référence complète des actions de communication disponibles dans le catalogue des actions d'automatisation workflow. Ces actions vous permettent d'intégrer une plateforme de communication à vos définitions workflow, notamment en envoyant des messages aux canaux Slack, en récupérant les réactions, et bien plus encore. - -## Prérequis - -Avant d'utiliser des actions de communication dans l'automatisation workflow, assurez-vous de disposer de : - -* Un espace de travail Slack avec les autorisations appropriées. -* Un bot Slack configuré comme secret dans l'automatisation workflow. -* Accès aux canaux Slack dans lesquels vous souhaitez envoyer des messages. - -Consultez la section [« Ajouter une configuration Slack »](/docs/autoflow/overview#add-the-slack-integration) pour plus d'informations sur la configuration de l'intégration Slack. - -## Actions Slack - - - - Envoie un message vers un canal Slack, avec une pièce jointe facultative. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Exemple -
- **jeton** - - Requis - - secrète - - `${{ :secrets:slackToken }}` -
- **canal** - - Requis - - chaîne - - `my-slack-channel` -
- **texte** - - Requis - - chaîne - - `Hello World!` -
- **filTs** - - Facultatif - - chaîne - - `.` -
- **pièce jointe** - - Facultatif - - carte - -
- **pièce jointe.nom_de_fichier** - - Requis - - chaîne - - `file.txt` -
- **pièce jointe.contenu** - - Requis - - chaîne - - `Hello\nWorld!` -
- - - * **token**: Le bot Slack jeton à utiliser. Cela devrait être transmis comme une syntaxe secrète. Consultez la section [« Ajouter une configuration Slack »](/docs/autoflow/overview#add-the-slack-integration) pour obtenir des instructions sur la configuration d'un jeton. - * **channel**: Le nom du canal, ou un identifiant de canal, sur lequel envoyer le message. Consultez [l'API Slack](https://api.slack.com/methods/chat.postMessage#arg_channel/) pour plus d'informations. - * **text**: Le message à publier sur Slack dans le `channel` spécifié. - * **threadTs**: horodatage appartenant au message parent, utilisé pour créer une réponse à un message dans un fil de discussion. - * **attachment**: Autoriser la pièce jointe d'un fichier avec un message sur le `channel` spécifié. - * **attachment.filename**: Spécifiez le nom du fichier téléchargé dans Slack. - * **attachment.content**: Le contenu du fichier à télécharger au format UTF-8. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **filTs** - - chaîne - - `.` -
- **ID du canal** - - chaîne - - `` -
- - - * **threadTs**: horodatage du message. Peut être utilisé dans de futurs appels postMessage pour publier une réponse dans un fil de discussion. - * **channelID**: Identifiant du canal où le message est publié. - - - - - **Exemple 1 : Publier un message sur un canal Slack** - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: SendMessage - - steps: - - name: send_slack_message - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: ${{ .workflowInputs.channel }} - text: ${{ .workflowInputs.text }} - ``` - - **Entrées attendues :** - - ```json - { - "inputs": [ - { - "key" : "channel", - "value" : "my-channel" - }, - { - "key" : "text", - "value" : "This is my message *with bold text* and `code backticks`" - } - ] - } - ``` - - **Résultat attendu :** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - **Exemple 2 : Joindre un fichier** - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: SendFileMessage - - steps: - - name: postCsv - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel - text: "Please find the attached file:" - attachment: - filename: 'file.txt' - content: "Hello\nWorld!" - ``` - - **Résultat attendu :** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - - - - - - - - Obtenir une réaction à un message provenant d'un canal Slack. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Exemple -
- **jeton** - - Requis - - secrète - - `${{ :secrets:slackToken }}` -
- **ID du canal** - - Requis - - chaîne - - `C063JK1RHN1` -
- **temps mort** - - Facultatif - - int - - 60 -
- **filTs** - - Requis - - chaîne - - `.` -
- **sélecteurs** - - Facultatif - - liste - - `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` -
- - - * **token**: Le bot Slack jeton à utiliser. Cela devrait être transmis comme une syntaxe secrète. Consultez la section [« Ajouter une configuration Slack »](/docs/autoflow/overview#add-the-slack-integration) pour obtenir des instructions sur la configuration d'un jeton. - * **channelID**: L'identifiant du canal permettant d'obtenir les réactions aux messages. - * **timeout**: Durée en secondes pendant laquelle il faut attendre une réaction. La valeur par défaut est de 60 secondes, la valeur maximale autorisée est de 600 secondes (10 minutes). - * **threadTs**: horodatage associé au message, utilisé pour obtenir la réaction à ce message. - * **selectors**: Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **réactions** - - liste - - `` -
- - - * **reactions**: Liste des éléments contenant toutes les réactions capturées ou une liste vide en cas de dépassement de délai. - - - - - **Exemple 1 : Slack obtient des réactions** - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: GetReactions - - steps: - - name: getReactions - type: action - action: slack.chat.getReactions - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channelID: ${{ .steps.promptUser.outputs.channelID }} - threadTs: ${{ .steps.promptUser.outputs.threadTs }} - timeout: ${{ .workflowInputs.timeout }} - selectors: ${{ .workflowInputs.selectors }} - ``` - - **Entrées attendues :** - - ```json - { - "inputs": [ - { - "key" : "channelID", - "value" : "C063JK1RHN1" - }, - { - "key" : "threadTs", - "value" : "1718897637.400609" - }, - { - "key" : "selectors", - "value" : "[{\"name\": \"reactions\", \"expression\": \".reactions \"}]" - } - ] - } - ``` - - **Résultat attendu :** - - ```json - [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } - ] - ``` - - Ou si le délai est dépassé : - - ```json - [] - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index 5539127c7c3..00000000000 --- a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,1043 +0,0 @@ ---- -title: actions HTTP -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: A list of available HTTP actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l'essayiez ! - - Cette fonctionnalité est actuellement fournie dans le cadre d'un programme d'aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Cette page fournit une référence complète des actions HTTP disponibles dans le catalogue des actions d'automatisation workflow. Ces actions vous permettent d'effectuer requests HTTP (GET, POST, PUT, DELETE) vers des API et des services externes dans le cadre de vos définitions workflow. - -## Prérequis - -Avant d'utiliser les actions HTTP dans l'automatisation workflow, assurez-vous de disposer de : - -* cible points de terminaison d'API URLs. -* Toutes les informations d'identification d'authentification requises (clé API, jeton, etc.). -* Compréhension des formats de requête/réponse de l'API. - - - Les actions HTTP prennent en charge la syntaxe secrète pour toute valeur d'en-tête, vous permettant de transmettre en toute sécurité des données sensibles telles que l'API clé. Consultez [la section Gestion des secrets](/docs/infrastructure/host-integrations/installation/secrets-management/) pour plus d'informations. - - -## actions HTTP - - - - Effectuez un appel HTTP GET pour récupérer des données à partir d'un point de terminaison d'API. - - - Cela prend en charge la syntaxe secrète pour toute valeur d'en-tête. - - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Description -
- **url** - - Requis - - Chaîne - - L'URL cible de la requête. Le dispositif doit être inclus : - - `https://example.com` -
- **urlParams** - - Facultatif - - Carte - - Les paramètres de requête à ajouter à l'URL. Prend un objet JSON converti en chaîne de caractères. -
- **en-têtes** - - Facultatif - - Carte - - Les en-têtes à ajouter à la requête. Prend un objet JSON converti en chaîne de caractères. -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Description -
- **corps de réponse** - - Chaîne - - Le corps de la réponse. -
- **code d'état** - - Entier - - Le code d'état HTTP de la réponse. -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **Exemples d'entrées :** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **Exemples de résultats :** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - Effectue un appel HTTP POST pour envoyer des données à un point de terminaison d'API. - - - Cela prend en charge la syntaxe secrète pour toute valeur d'en-tête. - - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Description -
- **url** - - Requis - - Chaîne - - L'URL cible de la requête. Le dispositif doit être inclus : - - `https://example.com` -
- **urlParams** - - Facultatif - - Carte - - Les paramètres de requête à ajouter à l'URL. Prend un objet JSON converti en chaîne de caractères. -
- **en-têtes** - - Facultatif - - Carte - - Les en-têtes à ajouter à la requête. Prend un objet JSON converti en chaîne de caractères. -
- **corps** - - Facultatif - - Chaîne - - Le corps de la requête. -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Description -
- **corps de réponse** - - Chaîne - - Le corps de la réponse. -
- **code d'état** - - Entier - - Le code d'état HTTP de la réponse. -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **Exemples d'entrées :** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **Exemples de résultats :** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Effectue une requête HTTP PUT pour mettre à jour les données à un point de terminaison d'API. - - - Si vous devez transmettre des données sensibles à une entrée, par exemple un en-tête `Api-Key`, vous pouvez utiliser les valeurs stockées via la mutation NerdGraph [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql). - - Exemple: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Description -
- **url** - - Requis - - Chaîne - - L'URL cible de la requête. L'URL doit inclure le schéma (par exemple, https:// ou http://). Exemple: - - `https://example.com` -
- **urlParams** - - Facultatif - - Carte - - Les paramètres de requête à ajouter à l'URL. Prend un objet JSON converti en chaîne de caractères. -
- **en-têtes** - - Facultatif - - Carte - - Les en-têtes à ajouter à la requête. Prend un objet JSON converti en chaîne de caractères. -
- **corps** - - Facultatif - - Chaîne - - Le corps de la requête. -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Description -
- **corps de réponse** - - Chaîne - - Le corps de la réponse. -
- **code d'état** - - Entier - - Le code d'état HTTP de la réponse. -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Exemples d'entrées :** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Exemples de résultats :** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Effectue une requête HTTP DELETE pour supprimer des données à un point de terminaison d'API. - - - Si vous devez transmettre des données sensibles à une entrée, par exemple un en-tête `Api-Key`, vous pouvez utiliser les valeurs stockées via la mutation NerdGraph [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql). - - Exemple: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Description -
- **url** - - Requis - - Chaîne - - L'URL cible de la requête. L'URL doit inclure le schéma (par exemple, https:// ou http://). Exemple: - - `https://example.com` -
- **urlParams** - - Facultatif - - Carte - - Les paramètres de requête à ajouter à l'URL. Prend un objet JSON converti en chaîne de caractères. -
- **en-têtes** - - Facultatif - - Carte - - Les en-têtes à ajouter à la requête. Prend un objet JSON converti en chaîne de caractères. -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Description -
- **corps de réponse** - - Chaîne - - Le corps de la réponse. -
- **code d'état** - - Entier - - Le code d'état HTTP de la réponse. -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Exemples d'entrées :** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Exemples de résultats :** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx deleted file mode 100644 index 3587d22dd0e..00000000000 --- a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ /dev/null @@ -1,1910 +0,0 @@ ---- -title: Actions de New Relic -tags: - - workflow automation - - workflow - - workflow automation actions - - New relic actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l'essayiez ! - - Cette fonctionnalité est actuellement fournie dans le cadre d'un programme d'aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Cette page fournit une référence complète des actions New Relic disponibles dans le catalogue des actions d'automatisation workflow. Ces actions vous permettent d'intégrer les fonctionnalités de la plateforme New Relic dans vos définitions workflow, notamment l'envoi d'événements personnalisés et de logs, l'exécution de requêtes NerdGraph, l'exécution de requêtes NRQL et l'envoi de notifications. - -## Prérequis - -Avant d'utiliser les actions New Relic dans l'automatisation workflow, assurez-vous de disposer de : - -* Un compte New Relic disposant des autorisations appropriées. -* Une clé de licence New Relic (si vous envoyez des données vers un compte différent). -* Les autorisations nécessaires pour les services New Relic spécifiques que vous prévoyez d'utiliser. - -Consultez [la clé de licence](/docs/apis/intro-apis/new-relic-api-keys/#license-key) pour obtenir des informations sur la façon de créer et de gérer votre compte New Relic. - -## actions d'ingestion de données - - - - Envoie un événement personnalisé à New Relic - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Exemple -
- **attributes** - - Facultatif - - Carte - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **événement** - - Requis - - liste - - `"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]` -
- **clé de licence** - - Facultatif - - chaîne - - `"{{ .secrets.secretName }}"` -
- **sélecteurs** - - Facultatif - - liste - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Attribut commun qui fait partie de tous les événements lorsqu'il est fourni. Fusion pour chaque élément d'événement lorsque cela est nécessaire, l'élément d'événement remplace la définition commune. - * **events**: La liste des données d'événement. Notez que l'événement nécessite l'utilisation d'un champ `eventType` qui représente le type d'événement personnalisé et que le nombre maximal d'événements autorisés par requête est de 100. - * **licenseKey**: La clé de licence du compte New Relic qui spécifie le compte cible où les événements sont envoyés. Si cette valeur n’est pas fournie, une clé de licence par défaut est supposée en fonction du compte exécutant le workflow. - * **selectors**: Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **succès** - - Booléen - - `true` -
- **message d'erreur** - - chaîne - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **Résultat attendu :** - - ```yaml - { - "success": true - } - ``` - - **Récupérer l'événement :** - - Une fois un workflow exécuté avec succès, vous pouvez récupérer l'événement associé en exécutant une requête sous le compte qui a exécuté le workflow: - - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - Envoyer les logs à New Relic - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type - - Exemple -
- **attributes** - - Facultatif - - carte - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **logs** - - Requis - - liste - - `"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"` -
- **clé de licence** - - Facultatif - - chaîne - - `"{{ .secrets.secretName }}"` -
- **sélecteurs** - - Facultatif - - liste - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Attribut commun inclus dans tous les logs lorsqu'il est fourni. Si un élément log spécifie le même attribut, il remplace la définition commune. - * **logs**: La liste des données log. Notez que le nombre maximal des logs d'entrées autorisé par requête est de 100. - * **licenseKey**: La clé de licence du compte New Relic qui spécifie le compte cible où les logs sont envoyés. Si aucune clé de licence n’est fournie, une clé de licence par défaut est supposée en fonction du compte exécutant le workflow. Consultez [la clé de licence](/docs/apis/intro-apis/new-relic-api-keys/#license-key) pour plus d'informations. - * **selectors**: Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **succès** - - Booléen - - `true` -
- **message d'erreur** - - chaîne - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **Résultat attendu :** - - ```yaml - { - "success": true - } - ``` - - **Récupérer les logs :** - - Une fois un workflow exécuté avec succès, vous pouvez récupérer le log associé en exécutant une requête sous le compte qui a exécuté le workflow: - - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## Actions NerdGraph - - - - Exécute une commande Graphql sur l'API New Relic NerdGraph. La commande peut être soit une requête, soit une mutation. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type - - Description - - Exemple -
- **graphql** - - Requis - - chaîne - - Une syntaxe GraphQL. Vous devriez utiliser GraphiQL pour construire et tester votre commande - -
- **variables** - - Requis - - map[string]any - - Toutes les variables de type paire valeur-clé à utiliser avec l'instruction GraphQL. - -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - ```yaml - steps: - - name: findingVar - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query GetEntity($entityGuid: EntityGuid!) { - actor { - entity(guid: $entityGuid) { - alertSeverity - } - } - } - variables: - entityGuid: ${{ .workflowInputs.entityGuid }} - - name: findingInline - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - { - actor { - entity(guid: "${{ .workflowInputs.entityGuid }}") { - alertSeverity - } - } - } - selectors: - - name: entities - expression: '.data' - ``` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Sortir - - Type - - Description -
- **données** - - map[string]any - - Contenu de la propriété - - `data` - - d'une réponse NerdGraph. -
- **succès** - - Booléen - - État de la demande. -
- **message d'erreur** - - Chaîne - - Motif de l'échec : message. -
- - - - - - - - - - - - - - - -
- Exemple -
- ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - -## Actions de requête - - - - Exécute une requête NRQL inter-comptes via l'API NerdGraph. - - - - - Entrées - - - - Sorties - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type - - Description - - Exemple -
- **requête** - - Requis - - chaîne - - L'instruction de requête NRQL. - -
- **identifiants de compte** - - Facultatif - - liste d'entiers - - Le champ - - **New Relic Account ID** - - est une liste d’identifiants cibles qui vous permet de spécifier les comptes cibles sur lesquels la requête est exécutée. Si cette valeur n'est pas fournie en entrée, la requête sera automatiquement exécutée sur le compte associé au compte d'exécution du workflow. - -
- **sélecteurs** - - Facultatif - - liste - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - - - - -
- Sortir - - Type - - Exemple -
- **results** - - : Un éventail d'objets contenant les résultats de la requête. - - - - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - -## Actions de notification - - - - Envoie un message à un canal, intégré à des destinations comme Slack par exemple. - - - - - Entrées - - - - Sorties - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type - - Description - - Exemple -
- **type** - - Requis - - chaîne - - Type de destination New Relic - - `slack` -
- **destinationId** - - Requis - - Chaîne - - DestinationId associé à la destination New Relic. - - `123e4567-e89b-12d3-a456-426614174000` -
- **paramètres** - - Requis - - carte - - Champs requis pour envoyer une notification au type de destination choisi. - - `{\"channel\": \"${{ YOUR_CHANNEL }}\", \"text\": \"Enter your text here\"}` -
- **sélecteurs** - - Facultatif - - liste - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - -
- Sortir - - Type - - Exemple -
- succès - - booléen - - `true/false` -
- - - - - - - - - Envoie un message à un canal d'équipe Microsoft, intégré aux destinations. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type de données - - Description - - Exemple -
- **destinationId** - - Requis - - Chaîne - - DestinationId associé à la destination New Relic. - - Consultez la section relative [à l'intégration de New Relic pour Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) pour connaître les étapes à suivre pour configurer une nouvelle destination et afficher l'ID de destination. - - Consultez [la section Destinations](/docs/alerts/get-notified/destinations/) pour en savoir plus sur les destinations. - - - - ```sh - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **teamName** - - Requis - - Chaîne - - Nom de l'équipe associée à l'identifiant de destination donné - - `TEST_TEAM` -
- **channelName** - - Requis - - Chaîne - - Nom du canal où le message doit être envoyé - - `StagingTesting` -
- **message** - - Requis - - Chaîne - - Message texte à envoyer - - `Hello! this message from Workflow` -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **succès** - - Booléen - - `true/false` -
- **sessionId** - - Chaîne - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **message d'erreur** - - Chaîne - - `Message is a required field in the notification send"` -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: msTeam_notification_workflow - description: This is a test workflow to test MSTeam notification send action - steps: - - name: SendMessageUsingMSTeam - type: action - action: newrelic.notification.sendMicrosoftTeams - version: 1 - inputs: - destinationId: acc24dc2-d4fc-4eba-a7b4-b3ad0170f8aa - channel: DEV_TESTING - teamName: TEST_TEAM_DEV - message: Hello from Workflow - ``` -
- - - - - - - - - Envoie un courriel aux destinations de messagerie NewRelic avec ou sans pièces jointes - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de saisie - - optionnalité - - Type de données - - Description - - Exemple -
- **destinationId** - - Requis - - Chaîne - - DestinationId associé à la destination New Relic. - - Consultez la section relative [à l'intégration de New Relic pour Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) pour connaître les étapes à suivre pour configurer une nouvelle destination et afficher l'ID de destination. - - Consultez [la section Destinations](/docs/alerts/get-notified/destinations/) pour en savoir plus sur les destinations. - - - - ```yaml - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: EMAIL, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **sujet** - - Requis - - Chaîne - - Objet du courriel - - `workflow-notification` -
- **message** - - Requis - - Chaîne - - Messages à envoyer par courriel - - `Hello! from Workflow Automation` -
- **pièces jointes** - - Facultatif - - List - - Liste des accessoires optionnels - -
- **attachment.type** - - Requis - - Énumération - - L'un des suivants : - - `QUERY` - - , - - `RAW` - -
- **attachment.query** - - Facultatif - - Chaîne - - Pour le type - - `QUERY` - - , il s'agit d'une instruction de requête NRQL. - - `SELECT * FROM LOG` -
- *attachment.accountIds* - - \* - - Facultatif - - List - - Pour - - `QUERY` - - , les - - **New Relic Account IDs** - - pour exécuter la requête. Si aucun compte n'est fourni, c'est celui associé à l'exécution du workflow qui est utilisé. - - `[12345567]` -
- **attachment.format** - - Facultatif - - Énumération - - Pour - - `QUERY` - - , spécifiez le type des résultats, par défaut - - `JSON` - - `JSON CSV` -
- **pièce jointe.contenu** - - Facultatif - - Chaîne - - Pour - - `RAW` - - , voici le contenu de la pièce jointe en UTF-8. - - `A,B,C\n1,2,3` -
- **pièce jointe.nom_de_fichier** - - Facultatif - - Chaîne - - Nom du fichier joint - - `log_count.csv` -
- **sélecteurs** - - Facultatif - - List - - Les sélecteurs permettant d'obtenir uniquement les paramètres spécifiés en sortie. - - `[{\"name\": \"success\", \"expression\": \".success\"},{\"name\": \"attachments\", \"expression\": \".response.attachments\"},{\"name\": \"sessionId\", \"expression\": \".response.sessionId\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ de sortie - - Type - - Exemple -
- **succès** - - Booléen - - `true/false` -
- **sessionId** - - Chaîne - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **message d'erreur** - - Chaîne - - `Channel is a required field in the notification send"` -
- **pièces jointes** - - List - - ```yaml - [{ - "blobId": "43werdtfgvhiu7y8t6r5e4398yutfgvh", - "rowCount": 100 - }] - ``` -
- - - - - - - - - - - - - - - -
- Exemple de workflow -
- ```yaml - name: email_testing_with_attachment - description: Workflow to test sending an email notification via NewRelic with log step - workflowInputs: - destinationId: - type: String - steps: - - name: sendEmailNotification - type: action - action: newrelic.notification.sendEmail - version: '1' - inputs: - destinationId: ${{ .workflowInputs.destinationId }} - subject: "workflow notification" - message: "Workflow Email Notification Testing from local" - attachments: - - type: QUERY - query: "SELECT * FROM Log" - format: JSON - filename: "log_count.json" - selectors: - - name: success - expression: '.success' - - name: sessionId - expression: '.response.sessionId' - - name: attachments - expression: '.response.attachments' - - name: logOutput - type: action - action: newrelic.ingest.sendLogs - version: '1' - inputs: - logs: - - message: "Hello from cap check Testing staging server user2 : ${{ .steps.sendEmailNotification.outputs.result.attachments }}" - licenseKey: ${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }} - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index 0bc41561c11..00000000000 --- a/src/i18n/content/fr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,634 +0,0 @@ ---- -title: Actions utilitaires -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: A list of available utility actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - -Cette page fournit une référence pour les actions utilitaires disponibles dans le catalogue des actions d'automatisation workflow. Ces actions vous permettent d'effectuer des opérations courantes de transformation et d'utilisation des données dans vos définitions workflow. - -## Actions utilitaires - - - - Cette action permet de convertir un horodatage Unix en date/heure. Références possibles : - - * [https://en.wikipedia.org/wiki/List\_of\_tz\_database\_time\_zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - * [https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT\_IDS](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS) - - Consultez [fromEpoch](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) pour plus d'informations. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type - - Description -
- **horodatage** - - Requis - - int - - Un entier représentant l'horodatage de l'époque. Notez que les époques UNIX correspondent au nombre de secondes écoulées depuis le 1er janvier 1970 à minuit UTC (00:00). -
- **horodatageUnité** - - Facultatif - - chaîne - - Une chaîne de caractères représentant l'unité de l'horodatage fourni. Valeurs acceptables : SECONDES, MILLISECONDES (PAR DÉFAUT) -
- **fuseau horaireId** - - Facultatif - - chaîne - - Chaîne de caractères représentant le fuseau horaire de la date et de l'heure souhaitées (par défaut : UTC). -
- **modèle** - - Facultatif - - chaîne - - Chaîne de caractères représentant le format de date et d'heure souhaité, par défaut : ISO-8601 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ - - optionnalité - - Type de données - - Description -
- **date** - - Requis - - chaîne - - Représentation sous forme de chaîne de caractères de la date. -
- **temps** - - Requis - - chaîne - - Une représentation sous forme de chaîne de caractères du temps. -
- **date et heure** - - Requis - - chaîne - - Représentation sous forme de chaîne de caractères d'une date et heure. -
- **fuseau horaire** - - Requis - - carte - - Représentation cartographique de l'identifiant et de l'abréviation du fuseau horaire. -
- - - - - - - - - - - - - - - - - - - - - - - -
- Exemple - - Workflow Entrée - - Sorties -
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - Cette action permet de transformer différents types d'entrées (JSON, map) au format CSV. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type - - Description -
- **données** - - Requis - - n'importe lequel - - Une chaîne de caractères représentant des données à transformer en CSV, généralement une chaîne JSON ou une carte. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Champ - - optionnalité - - Type de données - - Description -
- **csv** - - Requis - - chaîne - - Une représentation CSV des données reçues. -
- - - - - - - - - - - - - - - - - - - - - - -
- Exemple - - Workflow Entrée - - Sorties -
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` - -
- - - - - - - - - Générer un UUID V4 conforme à la RFC. - - - - - Entrées - - - - Sorties - - - - Exemple - - - - - - - - - - - - - - - - - - - - - - -
- Saisir - - optionnalité - - Type de données - - Description -
- - - - -
- - - - - - - - - - - - - - - - - - - - - - -
- Champ - - Type de données - - Description -
- **uuid** - - chaîne - -
- - - - - - - - - - - - - - - - - - - - - -
- Exemple - - Workflow Entrée - - Sorties -
- - - nom : générerUUID
mesures: - - * nom : generateUUID type : action action : utils.uuid.generate version : 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx deleted file mode 100644 index 4207aa61627..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-10-02' -version: 'Sep 26 - Oct 02, 2025' -translationType: machine ---- - -### 主な変更点 - -* 新しいフリート管理機能、強化されたセキュリティ機能、更新されたセットアップ手順など、 Kubernetes GA およびホスト パブリック プレビューの包括的な改訂により、 [Fleet Controlドキュメント](/docs/new-relic-control/fleet-control/overview)が更新されました。 -* 強化された設定オプション、監視機能、トラブルシューティング ガイダンスなど、パブリック プレビュー向けに広範な改訂を加えて[エージェント コントロールのドキュメント](/docs/new-relic-control/agent-control/overview)を更新しました。 -* 包括的な機能の詳細と実装ガイダンスを含め[、マークとメジャーのドキュメントを](/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures/)一般公開に向けて再構成しました。 -* 新しい電子メール検証手順と宛先制限により[、一括通知ワークフローが](/docs/alerts/admin/rules-limits-alerts)強化されました。 -* [価格モデル名を](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management/)「 New Relicの計算パブリックプレビューまたはコア計算プラン」から「アドバンスまたはコア計算プラン」に更新しました。 - -### マイナーチェンジ - -* セットアッププロセスを改善するために、 [WordPress フルスタック統合](/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration)手順を更新しました。 -* [ダッシュボード テンプレート変数の](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables)ドキュメントが更新され、スクリーンショットと改善された例が追加されました。 -* [使用量計算とアラート](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts)を更新し、使用量計算監視機能を強化しました。 -* 包括的な計算管理機能を備えた強化された[使用法UIドキュメント](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-ui)。 -* [.NETエージェント設定](/docs/apm/agents/net-agent/configuration/net-agent-configuration)の重複したアンカー参照を修正しました。 -* [通知統合](/docs/alerts/get-notified/notification-integrations)が更新され、電子メール宛先管理が改善されました。 -* サポートされているリージョンと VPC セットアップ要件に関する言語の明確さを向上させた[AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink)ドキュメントを更新しました。 -* コンテンツ管理用の「新着情報」投稿識別子を更新しました。 - -### リリースノート - -* 弊社の最新リリース情報を常に把握してください: - - * [Node.jsエージェント v13.4.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0) : - - * 発行されたイベントをサブスクライブするために amqplib と cassandra-driver の計装を更新しました。 - * Node.jsエージェントの互換性レポートをサポートされている最新のパッケージバージョンで更新しました。 - * トレース フックの WASM 最適化を追加しました。 - * より優れたコードドキュメント化のために JSDoc 要件が強化されました。 - - * [Pythonエージェント v11.0.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000) : - - * Python 3.7 のサポートが削除され、さまざまなレガシー API が非推奨になりました。 - * AutoGen と Pyzeebe フレームワーク用の新しい計装を追加しました。 - * AIモニタリング用にMCP（Model Context Protocol）名前付きスパンを導入しました。 - * psycopg のクラッシュを修正し、AI モニタリングが有効な場合にのみ MCP スパンが記録されるようにしました。 - - * [インフラストラクチャエージェント v1.69.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690) : - - * AWS SDK を V1 から V2 に、Docker API ライブラリを v26 から v28 にアップグレードしました。 - * 複数の CPU グループ (64 コア以上) を持つインスタンスのWindows CPU 監視を修正しました。 - * デフォルトのログレベルのサポートにより、ログ形式の処理が改善されました。 - - * [Kubernetesインテグレーション v3.45.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3) : - - * newrelic-インフラストラクチャ-3.50.3 および nri-bundle-6.0.15 チャート バージョンに含まれています。 - - * [NRDOT v1.5.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-25) : - - * メトリクス収集を強化するために、メトリクス生成プロセッサを nrdot-collectors-k8s に追加しました。 - - * [.NET エージェント v10.45.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0): - - * OpenTelemetry実装に基づいたディストリビューティッド（分散）トレーシング用の新しい TraceId Ratio-Based Sampler を追加しました。 - * データストアの計装を無効にする可能性がある MSSQL 接続文字列解析例外を修正しました。 - * カスタムインストゥルメンテーションとの互換性を向上させるために、Kafka の「消費」計装の問題を解決しました。 - - * [New Relic Android モバイルアプリ v5.30.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5308) : - - * バグ修正と改善により、モバイル アプリのパフォーマンスが向上しました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx deleted file mode 100644 index 2b5c4671fd1..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-11' -version: 'version: October 4-10, 2024' -translationType: machine ---- - -### 新しいドキュメント - -* [リリース ビルド (Android) にクラッシュ データが表示されないという問題は、](/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears) New Relic UI にアプリケーション クラッシュに関連するデータが表示されない場合の対処法を示しています。 -* [WSL と CodeStream をどのように使用すればよいですか?](/docs/codestream/troubleshooting/using-wsl)では、CodeStream で Windows Subsystem for Linux (WSL) を使用する手順について説明します。 -* [`UserAction`](/docs/browser/browser-monitoring/browser-pro-features/user-actions)はブラウザ監視の新しいイベント タイプで、Web アプリケーションを使用したユーザーの行動を理解するのに役立ちます。 -* [WithLlmCustomAttributes (PythonエージェントAPI)](/docs/apm/agents/python-agent/python-agent-api/withllmcustomattributes-python-agent-api)では、新しいコンテキスト マネージャーAPIについて、その要件、問題、戻り値、使用例などを含めて説明します。 - -### マイナーチェンジ - -* [New Relicテレメトリー エンドポイント](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints)のAPMエージェントに米国および EU データセンター エンドポイントを追加しました。 - -* [Visual Studio](/docs/codestream/troubleshooting/client-logs/#visual-studio)を使用するときに CodeStream のクライアント側ログを見つける方法に関する手順を更新しました。 - -* [ミュートルールの通知オプションの](/docs/alerts/get-notified/muting-rules-suppress-notifications/#notify)表現を変更し、わかりやすくしました。 - -* [インストゥルメント化されたモジュール](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrumented-modules)内の次のパッケージの互換性情報を更新しました。 - - * `@aws-sdk/client-bedrock-runtime` - * `@aws-sdk/client-dynamodb` - * `@aws-sdk/client-sns` - * `@aws-sdk/client-sqs` - * `@aws-sdk/lib-dynamodb` - * `@grpc/grpc-js` - * `@langchain/core` - * `@smithy/smithy-client` - * `next` - * `openai` - -* [データ取り込み IP ブロック](https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#ingest-blocks)内の 2 番目の EU データセンター エンドポイントを`212.32.0.0/20`に修正しました。 - -* データが[New Relicの EU データセンターに保存されているか米国データセンター](/docs/alerts/overview/#eu-datacenter)に保存されているかに関係なく、 New Relicのアラート サービスが米国で実行されるように指定しました。 - -* [カスタムアトリビュートの](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes)設定方法に関する情報を修正しました。 また、例も更新しました。 - -* [問題を未承認にしてクローズする](/docs/alerts/get-notified/acknowledge-alert-incidents/#unacknowledge-issue)手順を更新しました。 - -* [複数の問題を認識して解決する方法](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#bulk-actions)に関する情報を追加しました。 - -* [チャート更新レートの](/docs/query-your-data/explore-query-data/use-charts/chart-refresh-rates)紹介を拡張し、 New Relicの消費価格プランを利用している場合にのみ更新レートを構成できることを明記しました。 - -* [TLS 暗号化](/docs/new-relic-solutions/get-started/networks/#tls)で必要なトランスポート層セキュリティ (TLS) バージョン情報を修正しました。 - -* 現在のNew Relic UIと一致するように[、 Kubernetes](/install/kubernetes)インテグレーションの手順 6 を更新しました。 - -* 表の後の[Kubernetes データのクエリ](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#view-data)で、課金対象外のイベント`InternalK8sCompositeSample`の重要性に留意しました。 - -* 正確さと明確さのために、 [API表示および管理する](/docs/apis/intro-apis/new-relic-api-keys/#keys-ui)ための手順を書き直しました。 - -* API[エクスプローラーの使用」でAPI](/docs/apis/rest-api-v2/api-explorer-v2/use-api-explorer)エクスプローラーの使用方法に関する手順を更新し、現在のAPIエクスプローラーと一致するように[アプリケーション ID、ホスト ID、インスタンス ID をリストします](/docs/apis/rest-api-v2/get-started/list-application-id-host-id-instance-id)。 - -* [インフラストラクチャを OpenTelementry APM と相関させる](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/#infrastructure-correlation)例を再度追加しました。 - -* [Azure Monitor インテグレーションに移行する](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#migrate)ときにメトリクス名の重複を避ける方法について説明しました。 - -### リリースノート - -新しい機能やリリースの詳細については、「新機能」の投稿をご覧ください。 - -* [New Relic Pathpoint はテレメトリーをビジネス KPI に接続します](/whats-new/2024/10/whats-new-10-10-pathpoint) - -弊社の最新リリースの最新情報を入手してください: - -* [Android用エラー受信トレイ v5.25.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-52501) - * エラーを反復処理したり、プロファイルされた属性を検査したり、その他多くのことができます - -* [Flutter v1.1.4](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-114) - * iOS エージェントを 7.5.2 に更新します。 - -* [Kubernetesインテグレーション v3.29.6](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6) - - * アップデート v1.23.2 へ - * Prometheusの共通ライブラリをv0.60.0に更新します - -* [Python v10.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100) - - * Python 3.13をサポート - * 新しいコンテキストマネージャAPIを提供します - * Amazon ECS Fargate Docker IDのレポートをサポート - * のための計装が含まれています `SQLiteVec` - -* [ユニティエージェント v1.4.1](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141) - - * ネイティブAndroidおよび iOS エージェントを更新します - * バグ修正が含まれています \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx deleted file mode 100644 index 9e551f58d91..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-18' -version: 'version: October 11-17, 2024' -translationType: machine ---- - -### 新しいドキュメント - -* [Forward Kong Gateway ログでは、](/docs/logs/forward-logs/kong-gateway/) Kubernetesインテグレーションを介してこの新しい転送ログ プラグインをインストールして使用する方法について説明します。 -* [Azure App Service 監視では、](/docs/apm/agents/manage-apm-agents/azure/monitoring-azure-app-service/)このAzureサービスをNew Relicと統合する方法について説明し、これをJava 、 .NET、 Node.js 、およびPython APM向けに設定する手順へのリンクを示しています。 -* [データ エクスプローラーの概要では、](/docs/query-your-data/explore-query-data/query-builder/introduction-new-data-explorer/)新しいデータ エクスプローラーUI使用してデータを書き込み、 New Relicプラットフォームがどのようにユーザーをサポートし、問題を解決できるかをサイト内でより深く理解する方法について説明します。 -* [APM言語エージェントを使用した Amazon ECS 環境の監視は、](/docs/infrastructure/elastic-container-service-integration/monitor-ecs-with-apm-agents/) AMazaon ECS 環境にAPMエージェントをインストールするのに役立ちます。 -* [「NRQL への移行」では、](/docs/apis/rest-api-v2/migrate-to-nrql/) REST API v2 クエリを NRQL クエリに移行する方法について説明します。 - -### 主な変更点 - -* オープンソース サイトのコンテンツをドキュメント サイトに移行しました。 -* [Kubernetes エージェント オペレーター](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/)を使用してシークレットを管理する方法を明確にしました。 - -### マイナーチェンジ - -* [New RelicのOpenTelemetryメトリクス](/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics/#otlp-summary)では、 OpenTelemetry概要メトリクスがサポートされていないことを明確にしました。 -* Kubernetesおよび Google Kubernetes Engine タイルの場所を明確にするために[、推奨されるアラート ポリシーとダッシュボード](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies/#add-recommended-alert-policy)のスクリーンショットを更新しました。 -* Python APMに関連するStackatoおよび WebFaction ドキュメントは、関連性がなくなったため削除されました。 -* [ネットワーク](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints)ドキュメントに新しいブラウザ監視エンドポイントを追加しました。 -* ブラウザ監視のトラブルシューティング ドキュメント全体にわたって、小さな問題を修正しました。 -* [ランタイム アップグレード エラーのトラブルシューティング](/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting/#scripted-api-form)では、 `$http`オブジェクトで古い Node ランタイムを使用するときに問題を解決する方法について説明しました。 -* [.NET エージェントAPI](/docs/apm/agents/net-agent/net-agent-api/net-agent-api)では、 `NewRelic.Api.Agent.NewRelic` `ITransaction` APIコールに追加し、新しい`RecordDatastoreSegment` APIコールを追加しました。 - -### リリースノート - -弊社の最新リリースの最新情報を入手してください: - -* [Android エージェント v7.6.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-761/) - - * Android Gradle プラグイン 8.7 のサポートを追加 - * ProGuard/DexGuard マッピングファイルが正しくアップロードされない問題を修正しました - * その他のバグ修正 - -* [Browser v1.269.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0/) - - * NPM 上の MicroAgent ローダーがログ API を使用して手動でログ データをキャプチャできるようにします。 - * ロギングペイロードに計装メタデータを追加 - * セッショントレースおよびセッションリプレイのセキュリティポリシーエラーに関連するバグを修正 - -* [Go エージェント v3.35.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0/) - - * 安全な Cookie イベントレポートのサポートを追加 - * ログ属性に`error.Error()`値を使用します - * AMQP サーバー接続の URL サポートを強化 - * さまざまなバグ修正 - -* [ラムダ拡張機能 v2.3.14](/docs/release-notes/lambda-extension-release-notes/lambda-extension-2.3.14/) - - * 拡張機能の起動チェックを無視する機能を追加 - * `NR_TAGS`環境変数の使用方法に関する情報をREADMEに更新します - * `NEW_RELIC_ENABLED`ブール環境変数のサポートを追加します - -* [.NET エージェント v10.32.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0/) - - * 環境変数のプレフィックスを廃止 `NEWRELIC_` - * すべての環境変数に一貫した命名規則を実装します - * 最新バージョンをサポートするために CosmosDB 計装を更新します - -* [Ping ランタイム v1.47.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.47.0/) - * 非 root ユーザー向けの ping ランタイム コントロール スクリプトのユーザー権限に関連する問題を修正します。 - -* [Python v10.2.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200/) - * Azureコンテナー アプリ監視のオプションをサポートするためにAzure init コンテナー オペレーター フラグを追加しました \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx deleted file mode 100644 index 782869cec2c..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-07' -version: 'November 2 - November 7, 2025' -translationType: machine ---- - -### 新しいドキュメント - -* NerdGraph API を介して[データ アクセス制御を管理するための実用的な例を提供するために、データ アクセス制御 NerdGraph の例](/docs/apis/nerdgraph/examples/nerdgraph-data-access-control)を追加しました。 -* [万が一値検出アラート条件を設定するためのガイダンスを提供するために、万が一値検出](/docs/alerts/create-alert/set-thresholds/outlier-detection)を追加しました。 -* [インフラストラクチャ カタログを](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog/)追加して、インフラストラクチャ モニタリングのセットアップの前提条件を含む改善されたドキュメントを提供します。 -* メディア ストリーミングとブラウザー/モバイル エンティティ間の関係を理解するためのガイダンスを提供するために、 [メディア ストリーミング サービス マップを](/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps/)追加しました。 -* [メディア ストリーミングのエラー受信トレイ](/docs/errors-inbox/media-streaming-group-error/)を追加し、メディア ストリーミング エラーをグループ化して管理するための手順を示しました。 - -### 主な変更点 - -* [エージェント コントロールの設定](/docs/new-relic-control/agent-control/configuration)を更新し、わかりやすくするために YAML の例を修正し、フィールド名を更新しました。 -* YAML 設定例が改善され、[エージェント コントロールのセットアップ](/docs/new-relic-control/agent-control/setup)が更新されました。 -* 精度向上のため、更新された YAML の例を使用して[エージェント制御の再インストルメンテーション](/docs/new-relic-control/agent-control/reinstrumentation)を更新しました。 -* 洗練された設定例を使用して[、エージェント制御トラブルシューティングを](/docs/new-relic-control/agent-control/troubleshooting)更新しました。 - -### マイナーチェンジ - -* MariaDB の互換性情報を[MySQL要件](/install/mysql/)ドキュメントに追加しました。 -* データ ポリシーを使用してテレメトリーデータへのアクセスを制御するための包括的なガイダンスを提供する[データ アクセス制御を](/docs/accounts/accounts-billing/new-relic-one-user-management/data-access-control)追加しました。 -* [GitHub クラウド インテグレーションの](/docs/service-architecture-intelligence/github-integration/)ドキュメントを最新の設定の詳細で更新しました。 -* バージョン 3.60 の[診断 CLI ドキュメント](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-360)を更新しました。 -* Kubernetesの[Vizier ポート](/docs/ebpf/k8s-installation/)設定ドキュメントを更新しました。 - -### リリースノート - -* 弊社の最新リリース情報を常に把握してください: - - * [Pythonエージェント v11.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100) : - - * Python 3.14 のサポートが追加されました。 - * 属性フィルター設定用の環境変数を追加しました。 - * トランザクション デコレータの非同期ジェネレータのサポートが追加されました。 - * Claude Sonnet 3+ モデルやリージョン対応モデルなど、 AWS Bedrock コンピューティングの追加モデルのサポートが追加されました。 - * describe\_account\_settings、update\_account\_settings、update\_max\_record\_size、update\_stream\_warm\_throughput などの新しいAWS Kinesis メソッドのスケジュールを追加しました。 - * ConnectionPool 使用時の aiomysql の RecursionError を修正しました。 - * kombu プロデューサーでプロパティが適切に渡されないバグを修正しました。 - * 収集スレッド内からshutdown\_agentが呼び出されたときのエラーを修正しました。 - - * [iOS エージェント v7.6.0](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760) : - - * モバイルセッションリプレイのパブリックプレビュー機能を追加しました。 - * 必要な iOS バージョンを iOS 16 に引き上げました。 - * ログ記録時に発生する可能性のある処理済み例外の問題を修正しました。 - * 間違った命名警告を修正しました。 - - * [Android エージェント v7.6.12](/docs/release-notes/mobile-release-notes/android-release-notes/android-7612) : - - * Jetpack Compose のセッションリプレイ機能を追加しました。 - * 公式セッションリプレイのパブリックプレビュー版をリリースしました。 - * 複数のセッションリプレイのバグを修正しました。 - - * [Kubernetesインテグレーション v3.49.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0) : - - * 詳細な変更については、GitHub リリース ノートをご覧ください。 - * newrelic-infrastructure-3.54.0 および nri-bundle-6.0.20 チャート バージョンに含まれています。 - - * [ログ v251104](/docs/release-notes/logs-release-notes/logs-25-11-04) : - - * .NET 固有のログ ペイロード形式のサポートが追加されました。 - * .NET 固有のログ形式を処理するための NEW\_RELIC\_FORMAT\_LOGS 環境変数を導入しました。 - - * [Node ブラウザ ランタイム rc1.2](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.2) : - - * Chromeブラウザをバージョン141にアップグレードしました。 - * 中括弧展開の脆弱性 CVE-2025-5889 を修正しました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx deleted file mode 100644 index 0a583848c8d..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-14' -version: 'November 08 - November 14, 2025' -translationType: machine ---- - -### 新しいドキュメント - -* ブラウザ監視のプライバシー規制への準拠のため、ドキュメント同意管理の実装に[Browser同意モード](/docs/browser/new-relic-browser/configuration/consent-mode)を追加しました。 -* Kubernetes環境でのJava APM計装の設定ガイダンスを提供するために、 [Kubernetes自動アタッチにJava拡張機能を](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach)追加しました。 -* ディストリビューティッド（分散）トレーシングのドキュメントOpenTelemetryキャッシュ設定オプションに、[独自のキャッシュ設定を追加し](/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache)ました。 - -### 主な変更点 - -* ログベースのアラートを分析するための AI ログ要約機能を備えた強化された[Response Intelligence AI](/docs/alerts/incident-management/response-intelligence-ai) 。 -* 計算管理ドキュメントの名前を[「消費管理」](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management)に変更し、再構築しました。 -* Spring 瞬間命名オプションと SQL パーサー設定を使用して[Javaエージェント設定を](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file)更新しました。 -* 4 つの Google クラウド サービスの権限が改訂された[GCP 統合カスタム ロール](/docs/infrastructure/google-cloud-platform-integrations/get-started/integrations-custom-roles)が更新されました。 -* モデル コンテキスト プロトコルのセットアップ シナリオとソリューションを含む、 [MCP トラブルシューティング](/docs/agentic-ai/mcp/troubleshoot)ドキュメントが強化されました。 -* 新しい Sidekiq 再試行エラー設定オプションを備えた[Rubyエージェント設定](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration)が強化されました。 -* Debian Trixie のサポートを含む[PHP エージェント インストレーション](/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian)を更新しました。 - -### マイナーチェンジ - -* [Java エージェントの互換性要件](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent)に Java 25 互換性を追加しました。 -* [.NET エージェントの互換性要件](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements)に .NET 10 サポートを追加しました。 -* [サービスレベル管理アラート](/docs/service-level-management/alerts-slm)を更新しました。 -* Drupal および Laravel のバージョン情報と[PHP エージェントの互換性](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements)が更新されました。 -* [Kubernetesインテグレーションの互換性](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements)を更新しました。 -* フレームワーク サポートによる[Java エージェントの互換性要件](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent)が更新されました。 - -### リリースノート - -以下の新着投稿をチェックしてください: - -* [New Relic MCP サーバーがパブリック プレビューにリリース](/whats-new/2025/11/whats-new-11-05-mcp-server) - -* [New Relicまさか値のパブリック プレビューでの検出](/whats-new/2025/11/whats-new-11-05-outlier-detection) - -* [AIログ集計（プレビュー）](/whats-new/2025/11/whats-new-11-13-AI-Log-Alert-Summarization) - -* 弊社の最新リリース情報を常に把握してください: - - * [Node.jsエージェント v13.6.4](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4) : - - * メッセージ消費のトランザクションを適切に終了するように MessageConsumerSubscriber を修正しました。 - * MessageProducerSubscriber を修正し、traceparent にサンプリング フラグを正しく設定しました。 - * 適切なペイロードの逆シリアル化のために、Bedrock ミドルウェアの登録優先順位を修正しました。 - - * [Node.jsエージェント v13.6.3](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3) : - - * stream\_options.include\_usage によるOpenAIストリーミング処理を修正しました。 - * @google/生成AI による LlmCompletionsummary へのカウントの割り当てを修正しました。 - * AWS Bedrock 計装時のカウント割り当てを修正しました。 - - * [Javaエージェント v8.25.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250) : - - * Java 25のサポートが追加されました。 - * Logback-1.5.20 のサポートを追加しました。 - * Spring Controllerのネーミング設定オプションを導入しました。 - * Kotlin Coroutines v1.4+ のサポートが追加されました。 - * エラークラス命名解析ロジックを修正しました。 - * 大規模なスタックトレースでのエラーログにおける潜在的なメモリの問題を修正しました。 - - * [Rubyエージェント v9.23.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0) : - - * sidekiq.ignore\_retry\_errors を追加しました再試行エラーキャプチャを制御するための設定オプション。 - * Capistrano デプロイメント記録は廃止されました (v10.0.0 で削除)。 - * より一貫したディストリビューティッド（分散）トレーシングのためのリモート親サンプリング設定アプリケーションが強化されました。 - - * [.NET エージェント v10.46.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1) : - - * 精度を向上させるために、Azure Service Bus プロセッサ モード トランザクションから消費スパンを削除しました。 - * UI の明瞭性を向上させるために ReportedConfiguration 列挙型のシリアル化を更新しました。 - - * [Kubernetesインテグレーション v3.50.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0) : - - * KSM e2e チャート バージョンを 2.16 に更新しました。 - * kube\_endpoint\_address メトリクスのサポートが追加されました。 - * Windows サポートが有効になっている場合の prioritizeClassName テンプレートの問題を修正しました。 - - * [外形監視 Job Manager リリース 486](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-486) : - - * CVE-2024-6763 および CVE-2025-11226 を含む Ubuntu および Java の脆弱性を修正しました。 - - * [外形監視 Ping ランタイム v1.58.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.0) : - - * CVE-2025-5115 および CVE-2025-11226 を含む Ubuntu および Java の脆弱性を修正しました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx deleted file mode 100644 index 18c3e96beca..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-21' -version: 'November 17 - November 21, 2025' -translationType: machine ---- - -### 新しいドキュメント - -* 既存の[ドロップ ルールを新しいパイプラインcloudルール システムに移行するための包括的なガイダンスを提供するために、「ドロップ ルールをパイプライン](/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules/)cloudルールに移行」を追加しました。 -* New Relic PHPエージェントでのPHPUnitバージョン 11 以降のメモリ不足エラーに対するトラブルシューティング ガイダンスを提供するために、 [PHPUnit非互換性](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility)を追加しました。 - -### 主な変更点 - -* PHPエージェントによるPHPUnitのサポート終了に伴い、 PHPUnitテスト データ分析ドキュメントを削除しました。 PHPUnit の非互換性の問題に関するトラブルシューティング ドキュメントに置き換えられました。 -* 組織の改善のために[検索およびフィルター エンティティ](/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities)を再構築し、新しいカタログ フィルター機能を追加しました。 -* ネットワーク パフォーマンス監視の分離設定オプションを備えた[Kubernetes環境へのNew Relic eBPF のインストールを](/docs/ebpf/k8s-installation)更新しました。 - -### マイナーチェンジ - -* [データ保持期間の管理](/docs/data-apis/manage-data/manage-data-retention)に関するドキュメントにメディア ストリーミング データ保持情報を追加しました。 -* サポート終了後、 [PHP エージェントの互換性および要件の](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements)互換性テーブルから PHPUnit を削除しました。 -* [使用法とアラート](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts)のNRQL書き込みの例を修正しました。 -* [Browserアプリの設定ページ](/docs/browser/new-relic-browser/configuration/browser-app-settings-page/)にローカル ストレージの設定情報を追加しました。 -* ブラウザのドキュメントナビゲーションに同意モードを追加しました。 -* モバイル SDK の[設定を](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings)更新しました。 -* 追加のチャート タイプ情報を含む[チャート タイプの](/docs/query-your-data/explore-query-data/use-charts/chart-types)ドキュメントが強化されました。 -* RBAC ロールの明確化に伴い、MCP の[概要](/docs/agentic-ai/mcp/overview)と[トラブルシューティング](/docs/agentic-ai/mcp/troubleshoot)を更新しました。 - -### リリースノート - -* 弊社の最新リリース情報を常に把握してください: - - * [Go エージェント v3.42.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0) : - - * トランザクション、カスタムInsights 、エラー、ログの新しい最大サンプル設定オプションを追加しました。 - * nrlambda に MultiValueHeaders のサポートが追加されました。 - * nrpxg5 内の未使用の変数を削除しました。 - * エラーイベントが予想されるエラーを正しくマークしなかったバグを修正しました。 - - * [.NET エージェント v10.47.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0) : - - * ASP.NET Web アプリの ExecutionContext を使用してトランザクションをフローできるようにするためのオプションのトランザクション ストレージ メカニズムを追加しました。 - * Azure Service Bus 計装の null 参照例外を修正しました。 - * メッセージが配列でない場合にチャットの完了を処理するようにOpenAI計装を修正しました。 - - * [Node.jsエージェント v13.6.5](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5) : - - * 次のハンドラーがルートまたはルーターを通過するときに、express 計装を無視されたエラーに更新しました。 - * Promise の場合、消費者のコールバックが終了するまで待機するように MessageConsumerSubscriber を更新しました。 - - * [Node.jsエージェント v13.6.6](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6) : - - * 定義されたすべてのミドルウェアを適切にラップするように、app.use または router.use Express 計装を更新しました。 - * distributed\_tracing.samplers.partial\_granularity の設定を追加しましたおよびdistributed\_tracing.samplers.full\_granularity。 - - * [PHPエージェント v12.2.0.27](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27) : - - * Laravel 12 のサポートが追加されました。 - * Laravel 10.x+ および PHP 8.1+ で Laravel Horizon サポートが追加されました。 - * Laravel キュージョブの例外処理を修正しました。 - * golang バージョンを 1.25.3 に上げました。 - - * [Kubernetesインテグレーション v3.50.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1) : - - * バグ修正と改善を加えてバージョン 3.50.1 に更新されました。 - - * [インフラストラクチャエージェント v1.71.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711) : - - * 依存関係 newrelic/nri-docker を v2.6.3 に更新しました。 - * 依存関係 newrelic/nri-flex を v1.17.1 に更新しました。 - * goバージョンを1.25.4にアップグレードしました。 - * 依存関係 newrelic/nri-prometheus を v2.27.3 に更新しました。 - - * [ログ 25-11-20](/docs/release-notes/logs-release-notes/logs-25-11-20) : - - * AWS-log-ingestion ラムダの CVE-2025-53643 を修正しました。 - * aiohttpライブラリを3.13.2に更新しました そして詩のバージョンを 1.8.3 にしました。 - - * [Node ブラウザ ランタイム rc1.3](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.3) : - - * Chromeブラウザを142にアップグレードしました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx deleted file mode 100644 index 622089999aa..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-05-24' -version: 'version: May 17-23, 2024' -translationType: machine ---- - -### 新しいドキュメント - -* 新しい[Apache Mesos 統合は、](/docs/infrastructure/host-integrations/host-integrations-list/apache-mesos-integration)分散システム カーネルのパフォーマンスを監視するのに役立ちます。 -* 新しい[Temporal クラウド インテグレーションは、Temporal クラウド内のワークフロー](/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration)、ネームスペース、およびスケーラブルなアプリケーションの問題を監視および診断するのに役立ちます。 -* [AWS Elastic Beanstalk に .NET アプリは](/docs/apm/agents/net-agent/install-guides/install-net-agent-on-aws-elastic-beanstalk)ありますか?この新しいインストール ドキュメントには、そのデータを当社のプラットフォームに取り込むための明確なパスが示されています。 - -### 主な変更点 - -* 合成およびブラウザ スクリプト モニタのコード例を[外形監視](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide)ベストプラクティスおよび[合成スクリプト ブラウザ リファレンス](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100)に追加および更新しました。 コード例は読者が最も求めるものの 1 つなので、コード例が増えると私たちはいつもうれしく思います。 - -* ネットワーク パフォーマンス監視ドキュメントでは、多くの小さな更新が大きな変更につながりました。17 のドキュメントにわたって Podman のサポート対象環境が更新されました。 - -* [ログ ライブ アーカイブの](/docs/logs/get-started/live-archives)仕組みと、その[ログ データがいつ利用できる](/docs/logs/get-started/live-archives-billing)かを明確にしました。 - -* [コンテナ化されたイメージレイヤーの](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images/)Lambda監視計に図と環境変数を追加しました。 - -* New Relic の REST API v1 は完全に EOL となり、関連するいくつかのドキュメントが削除されました。 - -* 当社のインフラストラクチャ監視ドキュメントの大規模な内容により、次のことが可能になります。 - - * スタイル ガイドに従ってください。 - * 不要なコンテンツを削除します。 - * 左側のナビゲーションでインストレーション ドキュメントを見やすくします。 - * インストレーション ドキュメントの流れを改善します。 - -* 開発者サイトからドキュメントサイトへの移行は継続しており、今週はさらに 30 件以上のドキュメントが移行されます。 - -* 2024年5月23日現在、AIモニタリングはJavaをサポートしています。この重要な更新を反映するために、いくつかの AI モニタリング ドキュメントを更新しました。 - -### マイナーチェンジ - -* リンク コンプライアンス レポートを使用して、 [プライバシーのためのクラウド データ ストレージ セキュリティ制御](/docs/security/security-privacy/data-privacy/security-controls-privacy/#cloud-data-storage)を更新しました。 -* [.NET yum のインストレーション](/install/dotnet/installation/linuxInstall2/#yum)手順を簡素化しました。 -* [Python 互換性](/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent/#basic)ドキュメントを更新し、現在 Python 3.12 をサポートしていることを示します。 -* [.NET 互換性](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/)を更新し、 `Elastic.Clients.Elasticsearch`バージョン 8.13.12 データストアをサポートしていることを追加しました。 -* [Node.js APMエージェント互換性](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent)インストゥルメントされたモジュールの表を更新しました。 -* [AWS Privatelink で](/docs/data-apis/custom-data/aws-privatelink)サポートされているリージョンとゾーンのエンドポイントを更新しました。 -* インフラストラクチャエージェントは現在 Ubuntu 24.04 (Noble Numbat) をサポートしていますが、このバージョンの Ubuntu ではインフラストラクチャ plus ログはまだサポートしていません。 -* Windows 認証で[CyberARK と Microsoft SQL Server を](/docs/infrastructure/host-integrations/installation/secrets-management/#cyberark-api)使用している場合は、ユーザー名の前にドメインを付ける必要があることを明確にしました。 -* [.NET APMエージェント設定](/docs/apm/agents/net-agent/configuration/net-agent-configuration/#error-ignoreErrors)では、無視されるステータス コードと予期されるステータス コードの環境変数を追加しました。 -* [チャートの使用](/docs/query-your-data/explore-query-data/use-charts/use-your-charts)において、KB、MB、GB、TB の意味を明確にしました。(計算には 10 の累乗を使用する国際単位系を使用します。) -* [電子メール設定](/docs/accounts/accounts/account-maintenance/account-email-settings)では、New Relic ユーザーの電子メール アドレスに使用できる文字と制限を明確にしました。 -* IASTバリデータ サービス URL エンドポイントを[ネットワーク](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints)New Relicテレメトリー エンドポイント テーブルに追加しました。 -* [SNMP パフォーマンス監視](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring)に 1 つのホスト上の複数の SNMP トラップ バージョンを監視する方法に関するヒントを追加しました。 -* [Node.jsシステムを拡張して Apollo Server を含める](/docs/apm/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs/#extend-instrumentation)場合は、便利な GitHub README へのリンクを追加しました。 -* .NET 互換性情報を[AI モニタリングの互換性と要件](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#compatibility)に追加しました。 - -### リリースノートと新機能の投稿 - -* [Browser v1.260.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1) -* [インフラストラクチャエージェント v1.52.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523) -* [Javaエージェント v8.12.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120) -* [ジョブマネージャー v370](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-370) -* [Kubernetesインテグレーション v3.28.7](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7) -* [Android 向けモバイルアプリ v5.18.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5180) -* [.NET エージェント v10.25.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0) -* [Node API ランタイム v1.2.1](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.1) -* [Node API ランタイム v1.2.58](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.58) -* [Node API ランタイム v1.2.67](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.67) -* [Node API ランタイム v1.2.72](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.72) -* [Node API ランタイム v1.2.75](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.75) -* [Node API ランタイム v1.2.8](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.8) -* [Node.jsエージェント v11.17.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0) -* [PHPエージェント v10.21.0.11](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11) \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx deleted file mode 100644 index 44a93fbe992..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-06-28' -version: 'version: June 21-27, 2024' -translationType: machine ---- - -### 新しいドキュメント - -* モバイル監視のアプリケーション[が応答しない](/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding)機能は、 Androidアプリケーションが 5 秒以上ブロックされた時期と理由を追跡し、分析するのに役立ちます。 -* 新しいブラウザ監視[`log()`](/docs/browser/new-relic-browser/browser-apis/log)および[`wrapLogger()`](/docs/browser/new-relic-browser/browser-apis/wraplogger) API ドキュメントでは、これらの新しいエンドポイントの使用方法に関する構文、要件、パラメーター、および例が定義されています。 - -### 主な変更点 - -* 最上位の`Other capabilities`カテゴリを削除し、そこにあったすべてのものをより適切なカテゴリに移行しました。すべてが適切な場所に配置されているため、探しているものを見つけやすくなります。 -* ドキュメント サイトの OpenTelemetry コレクターの例を`newrelic-opentelemetry-examples` ]\([https://github.com/newrelic/newrelic-opentelemetry-examples](https://github.com/newrelic/newrelic-opentelemetry-examples)) に移動しました。メンテナンスを容易にし、オープンソースの可視性を向上させるための GitHub リポジトリ。 -* 当社の AI モニタリングは[NVIDIA NIM モデルを](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#deploy-at-scale)サポートしており、手動またはUIベースの導入フロー以外に追加の設定は必要ありません。 詳細については、ブログ[「NVIDIA NIM の AI モニタリング」を](https://newrelic.com/blog/how-to-relic/ai-monitoring-for-nvidia-nim)参照してください。 - -### マイナーチェンジ - -* [FedRAMP 準拠のエンドポイント](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#agents)と[ネットワーク](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints)に IAST バリデータ サービス URL エンドポイントを追加しました。 -* アプリケーションが表示されない場合にホワイトリストに追加する特定の IP 範囲を使用して[IAST トラブルシューティング](/docs/iast/troubleshooting/#see-my-application)を更新しました。 -* [Rubyエージェント設定](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/#instrumentation-aws_sqs)を更新し、 `NEW_RELIC_INSTRUMENTATION_AWS_SQS`自動インストゥルメンテーション設定情報を追加しました。 -* UI で実行できるため、[モバイル監視設定の構成](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings)から`ApplicationExitInfo`レポート構成情報を削除しました。 -* [ワークフロー エンリッチメントで](/docs/alerts/get-notified/incident-workflows/#enrichments)は複数の変数がサポートされているため、ニーズに合わせてデータをより具体的にカスタマイズできます。 -* データ ディクショナリに[MobileApplicationExit](/attribute-dictionary/?dataSource=Mobile&event=MobileApplicationExit)属性を追加しました。データ ディクショナリは単なるドキュメント リソースではなく、たとえば、書き込みビルダーでNRQL書き込みを作成するときに、プロパティ定義をUIに直接フィードします。 -* 古くなったアラート REST API に関連するドキュメントを削除しました。 - -### リリースノートと新機能の投稿 - -* [New Relic AIモニタリングの新機能がNVIDIA NIM推論マイクロサービスと統合されました](/whats-new/2024/06/whats-new-06-24-nvidianim) - -* [合成モニターへの影響を防ぐための新しい合成モニター ランタイムの更新](/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm)の新機能 - -* [Android エージェント v7.4.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-741) - * `ApplicationExitInfo` レポートはデフォルトで有効になっています - -* [Browser v1.261.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0) - - * 拡張性を向上させるためにオブジェクトとして渡された API 引数をログに記録する - * その他さまざまな新機能とバグ修正 - -* [診断 CLI (nrdiag) v3.2.7](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-327) - -* [Kubernetesインテグレーション v3.29.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0) - - * 1.29と1.30のサポートを追加し、1.24と1.25のサポートを削除しました - * 依存関係の更新: Kubernetes パッケージ v0.30.2 および Alpine v3.20.1 - -* [iOS向けモバイルアプリv6.5.0](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6050) - - * ワークロードの一部であるすべてのエンティティを表示する - * ダッシュボードのカスタマイズオプションがさらに充実 - * その他のさまざまな改善 - -* [Node.jsエージェント v11.20.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0) - - * Anthropic's Claude 3 メッセージAPIのサポート - * その他のさまざまな改善 - -* [Node.jsエージェント v11.21.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0) - * ECS メタデータ API からコンテナ ID を取得するためのサポート - -* [PHPエージェント v10.22.0.12](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12) - - * PHP 7.0 および 7.1 のサポート終了 - * さまざまなバグ修正 - -* [Ruby v9.11.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0) - - * `aws-sdk-sqs` gemの新しい計装 - * いくつかのバグ修正 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index 2f86d7a18bc..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### 新しいドキュメント - -* [New Relic Browserエージェントの問題をデバッグする方法](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/)に関する新しい機能が追加されました。これには、バージョン 1.285.0 以降で強化されたトラブルシューティングのための詳細なログ記録、ネットワーク リクエストの監視、検査イベントが含まれます。 -* `python`および`.node.js`関数の監視に[Azure Functions の](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/)サポートが追加されました。 -* New Relicプラットフォームで非効率性を特定し、最適化の推奨事項を提供し、CCU 節約量を見積もる機能を備え、計算効率を向上させる実用的なインサイト用の[計算オプティマイザー](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/)を追加しました。 -* [Cloud Cost Intelligence](/docs/cci/getting-started/overview)を追加しました。 cloudコストの可視化と管理のためのツールを提供します。これには、包括的なコストの内訳、 Kubernetesコストの割り当て、手動コストの見積もり、クロスアカウント データ収集などの機能が含まれます。現在はAWSクラウド コストのみをサポートしています。 -* [KubernetesにOpenTelemetryオブザーバNew Relic](/docs/kubernetes-pixie/k8s-otel/intro/)を追加し、 Helmチャートを介してクラスタをシームレスに監視するための New Relic 機能プロバイダーに依存しない統合を使用して、 New Relicのツールとダッシュボードに送信されるメトリクス、イベント、ログのテレメトリー信号を強化しました。 -* [Windowsインテグレーションの制限とトラブルシューティング](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)を追加 -* [CloudFormation およびCloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)を介したAWSインテグレーションが追加され、サポートされていないサービスのAPIポーリングがサポートされました。 -* MySQL および MS SQL Server のオンホスト インテグレーションを介して[、 New Relicデータベース](/docs/infrastructure/host-integrations/db-entity-tags/)エンティティ for MySQLや既存のテレメトリーに影響を与えることなく、 New Relicのメタデータ インサイトと組織を強化しました。 - -### 主な変更点 - -* [NRQL References](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/)に非集計関数を追加しました。 -* [Ruby エージェントの要件とサポートされるフレームワーク](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/)を更新しました。 -* New Relicドキュメント[のOpenTelemetryログにNew Relicカスタム](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events)イベントとしてログを追加しました。 -* [インストゥルメント化されたAzure関数の互換性と要件に関する](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes)ドキュメントの Linux、 Windows 、およびコンテナー化された関数でサポートされているランタイムを更新しました。 -* [Confluent クラウド インテグレーション](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics)のメトリクス データを更新しました。 -* GCP Cloud Run を[Node.jsエージェント設定](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/)から削除しました。 -* [AI モニタリングの互換性と要件](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/)を更新し、.NET エージェントでサポートされる追加のライブラリを追加しました。 -* New Relicテレメトリー デュアルスタック エンドポイントを[New Relicネットワーク トラフィック](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints)に追加しました。 -* [Google Cloud Load Balancing監視統合](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/)に`GcpHttpExternalRegionalLoadBalancerSample`追加しました。 -* [外形監視ジョブマネージャードキュメントのインストール](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install)方法にOpenShiftの起動手順を追加しました。 -* [Node.js エージェント バージョン 12](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/)を更新しました。 -* APIポーリングのサポートを含む、 [CloudFormation およびCloudWatch Metric Streamsを利用したNew RelicとのAWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)のシームレスな統合が追加されました。 - -### マイナーチェンジ - -* [境界トレース](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/)の保存期間として`Transaction`を追加しました。 -* [アラートルールと制限](/docs/alerts/admin/rules-limits-alerts/)に新しいカテゴリとして`Destination`追加しました。 -* [Azure ネイティブ New Relic サービスの概要](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/)ドキュメントに、Azure リソースの診断設定が正しく構成されていることを確認するか、Azure ネイティブ New Relic サービス経由の転送を無効にしてデータが New Relic プラットフォームに送信されないようにするためのコールアウトを追加しました。 -* [.NET エージェント](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/)の最新の互換ライブラリを更新しました。 -* [iOS エージェント リリース ノート](/docs/release-notes/mobile-release-notes/ios-release-notes/index/)ドキュメントにコールアウトを追加して、iOS SDK バージョン 7.5.4 以降、 変更により、以前は抑制されていた処理済み例外イベントが報告されるようになりました。 -* Kubernetes環境のリソース プロパティと非Kubernetes環境の`container.id`指定に対するサービスとコンテナの関係の要件を更新し、 [New RelicのOpenTelemetryリソース](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/)の適切なテレメトリー設定を確保します。 -* [特定のインフラストラクチャエージェント](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions)バージョンインストレーション用の CLI サポートを追加し、一貫したデプロイメントとシステム互換性を可能にします。レシピ名に`@X.XX.X`を使用してバージョンを指定します。 -* UIで**Manage Account Cardinality** \[アカウント カーディナリティの管理]、**Manage Metric Cardinality** \[メトリック カーディナリティの管理]、および**Create Pruning Rules** \[プルーニング ルールの作成]機能を使用するためのロール アクセス要件を強調するコールアウトを追加しました。[カーディナリティ管理](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table)で権限が設定されていることを確認してください。 -* [Node.js エージェントの互換性と要件を](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/)`v12.23.0`に更新しました。 -* [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration)をセットアップするために必要な最小限の権限を追加しました。 -* [NRQL形式構文](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/)の`FACET`プロパティの最大許容使用制限値を 5000 から 20000 の値に更新しました。 - -### リリースノート - -* [`SystemSample` 、 `ProcessSample` 、 `NetworkSample` 、 `StorageSample`のインフラストラクチャ イベントを対象とするドロップ ルールの](/eol/2025/05/drop-rule-filter/)サポート終了日として、2026 年 1 月 7 日が発表されました。 - -* [アラート条件の messageId およびタイムスタンプの FACET](/eol/2025/07/deprecating-alert-conditions/)のサポートが直ちに有効になります。 - -* 2025 年 10 月 28 日が[Attention Required](/eol/2025/07/upcoming-eols/)のサポート終了日として発表されました。 - -* 新着情報投稿をご覧ください: - - * [Microsoft Teams に直接通知を送信する](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [New Relicの計算オプティマイザーが一般提供されました!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [統合クエリエクスプローラーでアカウント間クエリをログに記録する](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [OpenTelemetryを使用したKubernetes監視が一般公開されました。](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [Kubernetes の Windows ノード監視がパブリック プレビューになりました](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [パフォーマンスの問題を正確に特定: ページビューと Core Web Vitals の高度なフィルタリング](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [最新のエラーで並べ替えられるようになりました](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [ブラウザデータ、条件: 新しいコントロール オプション](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [データベースの詳細なクエリ分析が一般提供開始](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [NRQL予測と予測アラートが一般提供開始](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [APM + OpenTelemetry コンバージェンス GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [GitHub Copilot と ServiceNow のエージェント統合が一般提供開始](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* 弊社の最新リリース情報を常に把握してください: - - * [Node API ランタイム v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * 脆弱性の問題を修正しました。 - - * [Ping ランタイム v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * ping ランタイムの logback-core の脆弱性を修正しました。 - * ping ランタイムの jetty サーバーの脆弱性を修正しました。 - * ping ランタイムの Ubuntu の脆弱性を修正しました。 - - * [Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * `BrowserInteraction`と`previousUrl`定義を更新します。 - * 追加の検査イベントを追加しました。 - * `finished` API `timeSinceLoad`値を修正しました。 - - * [Kubernetesインテグレーション v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * 将来のプラットフォーム互換性のために、内部バックエンドと CI 関連の調整を修正しました。 - - * [ジョブマネージャー v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * 実行時間が長い一部のモニターの結果が特定の顧客に表示されない問題を修正しました。 - - * [Pythonエージェント v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * `Azure Function Apps`のサポートが追加されました。 - * `protobuf v6`サポートを有効にするために`pb2`ファイルを修正しました。 - - * [Android エージェント v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * ログを報告するときに ANR を解決するためのパフォーマンスが向上しました。 - * アプリケーションの終了後もログの報告を継続する問題を修正しました。 - * アプリケーション状態の監視とデータ転送に関する問題を解決しました。 - * 厳密モードをオンにしたときのいくつかの違反が改善されました。 - - * [Kubernetesインテグレーション v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * `golang.org/x/crypto` `v0.39.0`に更新しました。 - * `go` `v1.24.4`に更新しました。 - - * [.NET エージェント v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Azure Service Bus のサポートが追加されました。 - * 最新の VS でのプロファイラー ビルド エラーを修正しました。 - - * [PHPエージェント v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * PHP アプリケーションで使用されるパッケージを検出するためにデフォルトで使用される Composer ランタイム API を追加しました。 - * Composer ランタイム API の未定義の動作を修正しました。 - - * [Node ブラウザ ランタイム v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * Chrome 131 の Chrome ビルダー オプションが更新されました。 - - * [iOS向けモバイルアプリv6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * より堅牢で信頼性の高いソケット接続により Ask AI 機能が強化され、シームレスなエクスペリエンスが保証されます。 - - * [Android用モバイルアプリv5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * より堅牢で信頼性の高いソケット接続により Ask AI 機能が強化され、シームレスなエクスペリエンスが保証されます。 - - * [Node.jsエージェント v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * `openai` v5 ストリーミング サポートが追加されました。 - * `openai.responses.create` API のサポートが追加されました。 - * 未定義のトレース状態ヘッダーのエラー ログを修正しました。 - - * [インフラストラクチャエージェント v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * 依存関係`newrelic/nri-winservices`を更新しました `v1.2.0` - * alpine docker タグを次のように更新しました。 `v3.22` - - * [インフラストラクチャエージェント v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * 依存関係`newrelic/nri-flex`を更新して `v1.16.6` - - * [Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * カスタムアトリビュートの競合状態の優先順位を修正しました。 - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * OTELベータコアを `v0.128.0` - - * [HTML5.JS v3.0.0 用メディアエージェント](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * 新しいイベントタイプを導入しました。 - * `PageAction`イベント タイプは非推奨になりました。 - - * [HTML5.JS v3.1.1 用メディアエージェント](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * パッケージの npm 公開を有効にして、アクセスと配布を容易にしました。 - * `cjs` 、 `esm` 、 `umd`ビルドを`dist`フォルダーに追加し、CommonJS、ES モジュール、UMD モジュール形式との互換性を確保しました。 - - * [Roku 用メディアエージェント v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * 新しいイベントタイプを導入しました。 - * `RokuVideo`イベント タイプは非推奨になりました。 - * `RokuSystem`イベント タイプは非推奨になりました。 - - * [Roku 用メディアエージェント v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * `errorName`は非推奨になったため、 `errorName`名前を`errorMessage`に変更しました。 - - * [ジョブマネージャー v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * ベースイメージのアップグレードを`ubuntu 22.04`から `ubuntu 24.4` - - * [Ping ランタイム v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * ベースイメージのアップグレードが`ubuntu 22.04`から `ubuntu 24.04` - - * [Kubernetesインテグレーション v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * KubernetesクラスタにWindowsノード監視のサポートが追加されました。 - - * [Android用モバイルアプリv5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * バグが修正され、UI が改善されてよりスムーズなエクスペリエンスが実現しました。 - - * [Node.jsエージェント v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * エントリースパンとエグジットスパンのみレポートする機能を追加しました。 - * Node.js 24 のサポートが追加されました。 - * 互換性レポートを更新しました。 - - * [Node API ランタイム v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * 脆弱性を修正しました `CVE-2024-39249` - - * [iOS向けモバイルアプリv6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * 動的プロンプトによる Ask AI 機能が強化されました。 - - * [Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * **長いタスクの**内部メッセージを追加しました。 - * ディストリビューティッド（分散）トレーシングが無効にならない問題を修正しました。 - - * [Node ブラウザ ランタイム v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * ベースイメージのアップグレード - - * [Javaエージェント v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Azure App Services のリンクされたメタデータ。 - * `MonoFlatMapMain`計装を削除しました。 - - * [Node.jsエージェント v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * 設定可能な属性値のサイズ制限を実装しました - * 互換性レポートを更新しました。 - - * [Kubernetesインテグレーション v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * kube-state-メトリクス チャートのバージョンを`5.12.1`から に更新します `5.30.1` - - * [iOS エージェント v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * セッション開始時にディストリビューティッド（分散）トレーシングに必要なアカウント情報がすべて揃っていない可能性がある問題を修正しました。 - - * [Android用モバイルアプリv5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * 動的 UI レンダリングによるフィードバックを強化しました。 - - * [Android 向けモバイルアプリ v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * バグを修正し、Teams GA フラグを更新して、ユーザー エクスペリエンスを向上させました。 - - * [Go エージェント v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * デッドロックバグのため、使用率を元に戻しました。v3.39.0 リリースに戻してください。 - * go モジュールに直接依存関係を追加した awssupport\_test.go テストを削除しました - - * [Flutterエージェント v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * ネイティブ Android エージェントをバージョン 7.6.7 にアップデートしました - * ネイティブ iOS エージェントを改善し、バージョン 7.5.6 に更新しました - - * [Node.jsエージェント v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Node.js 18のサポートを終了しました - * `fastify`の最小サポートバージョンを 3.0.0 に更新しました。`pino`を 8.0.0 に、 `koa-router`を 12.0.0 に - - * [Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * レポートの空の previousUrl を undefined として修正しました - - * [インフラストラクチャエージェント v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * 依存関係`newrelic/nri-prometheus`を v2.26.2 に更新しました - - * [iOS向けモバイルアプリv6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * 動的 UI レンダリングによるフィードバックを強化しました。 - - * [Android NDK エージェント v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * 16KBページサイズのサポートを追加 - - * [インフラストラクチャエージェント v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Windows プロセス ハンドルを変更しました。 - * `nri-docker`を`v2.5.1`に、 `nri-prometheus`を `v2.26.1` - - * [.NET エージェント v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Azure Service Bus にトピックのサポートを追加しました - - * [Node.jsエージェント v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * 計装AWS Bedrock Converse APIを修正 - - * [Node.jsエージェント v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * 設定可能な属性値のサイズ制限を実装しました - * 互換性レポートを更新しました - - * [診断 CLI (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * `/lib64/libc.so.6: version 'GLIBC_2.34'`が見つからないなどのGLIBC関連のエラーを修正しました \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx deleted file mode 100644 index 402dbc0736d..00000000000 --- a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-11-13' -version: 1.303.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Allow consent API to be invoked without localStorage access - - Allow nested registrations - - Additional validation to prepare agent for MFE registrations - - Add measure support to register API - - Add useConsentModel functionality - - Retry initial connect call - - Add custom event support to register API - - SMs for browser connect response -bugs: - - Obfuscate custom attributes for logs added after PVE - - memoize promise context propagation to avoid safari hangs -security: [] -translationType: machine ---- - -## バージョン1.303.0 - -### 特徴 - -#### ローカルストレージにアクセスせずに同意 API を呼び出すことを許可する - -収集を制御するエージェント内で共通の状態を保持することにより、localStorage アクセスを必要とせずに同意 API が機能できるようにします。localStorage アクセスがブロックされている場合、アプリケーションはハードページロードごとに API を呼び出す必要があります。 - -#### ネストされた登録を許可する - -計画された登録APIとの固有の親子関係を容易にするために、登録されたエンティティが、そのエンティティの子が登録するための独自の`.register()` APIを公開できるようにします。 コンテナ エージェントに登録するエンティティは、コンテナに関連付けられます。別の登録済みエンティティの下に登録されているエンティティは、コンテナと親エンティティの両方に関連付けられます。 - -#### MFE登録のためのエージェントの準備のための追加検証 - -MFE/v2 登録をサポートするために、MFE ターゲット`id`および`name`の不正な値を防止するためにエージェントに検証ルールを追加します。 - -#### 登録APIに測定サポートを追加 - -レジスター応答オブジェクトに測定 API のサポートを追加します。これは、将来計画されているマイクロ フロントエンドの提供をサポートするものです。 - -#### useConsentModel 機能を追加する - -use\_consent\_mode 初期プロパティと機能を追加します。consent() APIコールを追加します。 同意モデルが有効になっている場合、consent() APIコールを通じて同意が得られない限り、エージェントの収集は許可されません。 - -#### 最初の接続呼び出しを再試行する - -データ損失を防ぐために、エージェントは再試行可能なステータス コードに対して元の「RUM」呼び出しをさらに 1 回再試行するようになりました。 - -#### 登録APIにカスタムイベントのサポートを追加する - -カスタムイベントをキャプチャするためのメソッドを登録APIに追加します。これは、後で MFE サポートが確立されたときに使用されます。 - -#### ブラウザ接続応答のSM - -page\_view\_event 集約の初期化時に失敗した応答に対するサポート機能メトリクスを追加します。 - -### バグ修正 - -#### PVE 後に追加されたログのカスタムアトリビュートを難読化する - -難読化を拡張して、最初のRUM /PageViewEvent 収集後に追加されたログイベントのカスタムアトリビュートをカバーします。 - -#### safari のハングを回避するための memoize Promise コンテキスト伝搬 - -Memoize はコンテキスト伝搬を約束し、コンテキスト操作の繰り返しを回避することで Safari でブラウザがハングする可能性を防ぎます。 - -## サポートステートメント - -New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースは[サポート終了](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/)になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。 - -新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、この[ステータス ダッシュボード](https://newrelic.github.io/newrelic-browser-agent-release/)をご覧ください。 - -弊社の[ブラウザ サポート ポリシー](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types)に従い、 Browserの v1.303.0 は、 Chrome 131 ～ 141、Edge 131 ～ 141、Safari 17 ～ 26、Firefox 134 ～ 144 のブラウザとバージョン範囲を対象に構築され、テストされています。 モバイル デバイスの場合、v1.303.0 は Android OS 16 および iOS Safari 17-26 用に構築およびテストされました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx deleted file mode 100644 index 3ebdfed9e97..00000000000 --- a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-11-17' -version: rc1.3 -translationType: machine ---- - -### 改良点 - -* Chromeブラウザを142にアップグレードしました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx deleted file mode 100644 index c0a21031b24..00000000000 --- a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-11-12' -version: 1.58.0 -translationType: machine ---- - -### 改良点 - -Ping ランタイムのセキュリティ問題に対処するために、Ubuntu および Java に関連する脆弱性を修正しました。以下は修正された Java CVE です。 - -* CVE-2025-5115 -* CVE-2025-11226 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx deleted file mode 100644 index e8ceca1c51c..00000000000 --- a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ /dev/null @@ -1,652 +0,0 @@ ---- -title: コミュニケーションアクション -tags: - - workflow automation - - workflow - - workflow automation actions - - communication actions - - slack actions - - ms teams actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - この機能はまだ開発中ですが、ぜひお試しください。 - - この機能は現在、弊社の[プレリリース ポリシー](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy)に従ってプレビュー プログラムの一部として提供されています。 - - -このページでは、ワークフロー自動化アクション カタログで使用できる通信アクションの包括的なリファレンスを提供します。これらのアクションを使用すると、Slack チャネルへのメッセージの送信、反応の取得など、コミュニケーション プラットフォームをワークフロー定義に統合できます。 - -## 前提条件 - -ワークフロー自動化でコミュニケーションアクションを使用する前に、次の点を確認してください。 - -* 適切な権限を持つ Slack ワークスペース。 -* ワークフロー自動化でシークレットとして設定された Slack ボット トークン。 -* メッセージを送信する Slack チャネルへのアクセス。 - -Slack 統合の設定方法については、 [「Slack 設定の追加」を](/docs/autoflow/overview#add-the-slack-integration)参照してください。 - -## Slackアクション - - - - オプションのファイル添付を使用して、メッセージを Slack チャネルに送信します。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 例 -
- **トークン** - - 必須 - - シークレット - - `${{ :secrets:slackToken }}` -
- **チャネル** - - 必須 - - ストリング - - `my-slack-channel` -
- **テキスト** - - 必須 - - ストリング - - `Hello World!` -
- **スレッドT** - - オプション - - ストリング - - `.` -
- **添付ファイル** - - オプション - - マップ - -
- **添付ファイル.ファイル名** - - 必須 - - ストリング - - `file.txt` -
- **添付ファイルの内容** - - 必須 - - ストリング - - `Hello\nWorld!` -
- - - * **token**: Slack ボットを使用します。 これは秘密の構文として渡す必要があります。トークンの設定手順については、 [「Slack 構成の追加」](/docs/autoflow/overview#add-the-slack-integration)を参照してください。 - * **channel** : メッセージを送信するチャネルの名前、またはチャネル ID。詳細については、 [Slack API を](https://api.slack.com/methods/chat.postMessage#arg_channel/)参照してください。 - * **text** : 指定された`channel`で Slack に投稿されるメッセージ。 - * **threadTs** : 親メッセージに属するタイムスタンプ。スレッド内でメッセージの返信を作成するために使用されます。 - * **attachment** : 指定された`channel`にメッセージ付きのファイルを添付できるようにします。 - * **attachment.filename** : Slack にアップロードするファイルのファイル名を指定します。 - * **attachment.content**:UTF8 としてアップロードするファイルの内容。 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 例 -
- **スレッドT** - - ストリング - - `.` -
- **チャンネルID** - - ストリング - - `` -
- - - * **threadTs** : メッセージのタイムスタンプ。今後の postMessage 呼び出しでスレッドに返信を投稿するために使用される場合があります。 - * **channelID** : メッセージが投稿されるチャネルの ID。 - - - - - **例1: Slackチャンネルにメッセージを投稿する** - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: SendMessage - - steps: - - name: send_slack_message - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: ${{ .workflowInputs.channel }} - text: ${{ .workflowInputs.text }} - ``` - - **予想される入力:** - - ```json - { - "inputs": [ - { - "key" : "channel", - "value" : "my-channel" - }, - { - "key" : "text", - "value" : "This is my message *with bold text* and `code backticks`" - } - ] - } - ``` - - **期待される出力:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - **例2: ファイルを添付する** - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: SendFileMessage - - steps: - - name: postCsv - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel - text: "Please find the attached file:" - attachment: - filename: 'file.txt' - content: "Hello\nWorld!" - ``` - - **期待される出力:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - - - - - - - - Slack チャネルからメッセージに対する反応を取得します。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 例 -
- **トークン** - - 必須 - - シークレット - - `${{ :secrets:slackToken }}` -
- **チャンネルID** - - 必須 - - ストリング - - `C063JK1RHN1` -
- **タイムアウト** - - オプション - - int - - 60 -
- **スレッドT** - - 必須 - - ストリング - - `.` -
- **セレクター** - - オプション - - リスト - - `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` -
- - - * **token**: Slack ボットを使用します。 これは秘密の構文として渡す必要があります。トークンの設定手順については、 [「Slack 構成の追加」](/docs/autoflow/overview#add-the-slack-integration)を参照してください。 - * **channelID** : メッセージの反応を取得するためのチャネルID。 - * **timeout** : 反応を待つ時間（秒数）。デフォルトは 60 秒、最大許容時間は 600 秒 (10 分) です。 - * **threadTs** : メッセージに属するタイムスタンプ。そのメッセージの反応を取得するために使用されます。 - * **selectors** : 指定された唯一のものを出力として取得するセレクター。 - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 例 -
- **反応** - - リスト - - `` -
- - - * **reactions**: キャプチャされたすべての反応を含む要素のリスト、またはタイムアウトが発生した場合は空のリスト。 - - - - - **例1: Slackで反応を得る** - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: GetReactions - - steps: - - name: getReactions - type: action - action: slack.chat.getReactions - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channelID: ${{ .steps.promptUser.outputs.channelID }} - threadTs: ${{ .steps.promptUser.outputs.threadTs }} - timeout: ${{ .workflowInputs.timeout }} - selectors: ${{ .workflowInputs.selectors }} - ``` - - **予想される入力:** - - ```json - { - "inputs": [ - { - "key" : "channelID", - "value" : "C063JK1RHN1" - }, - { - "key" : "threadTs", - "value" : "1718897637.400609" - }, - { - "key" : "selectors", - "value" : "[{\"name\": \"reactions\", \"expression\": \".reactions \"}]" - } - ] - } - ``` - - **期待される出力:** - - ```json - [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } - ] - ``` - - またはタイムアウトになった場合: - - ```json - [] - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index 3552b490201..00000000000 --- a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,1043 +0,0 @@ ---- -title: HTTPアクション -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: A list of available HTTP actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - この機能はまだ開発中ですが、ぜひお試しください。 - - この機能は現在、弊社の[プレリリース ポリシー](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy)に従ってプレビュー プログラムの一部として提供されています。 - - -このページでは、ワークフロー自動化アクション カタログで使用できる HTTP アクションの包括的なリファレンスを提供します。これらのアクションを使用すると、ワークフロー定義の一部として外部 API およびサービスに HTTP requests ( GET 、POST、PUT、DELETE) を送信できるようになります。 - -## 前提条件 - -ワークフロー自動化で HTTP アクションを使用する前に、次の点を確認してください。 - -* 目標APIエンドポイントのURL。 -* 必要な認証資格情報 ( APIキー、VPN など)。 -* API リクエスト/レスポンス形式の理解。 - - - HTTP アクションは、任意のヘッダー値の秘密の構文をサポートしているため、 APIキーなどの機密データを安全に渡すことができます。 詳細については、[シークレット管理を](/docs/infrastructure/host-integrations/installation/secrets-management/)参照してください。 - - -## HTTPアクション - - - - HTTP GET呼び出しを実行して、 APIエンドポイントからデータを取得します。 - - - これは、任意のヘッダー値の秘密の構文をサポートします。 - - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 説明 -
- **url** - - 必須 - - 弦 - - リクエストのターゲット URL。スキームには次の内容が含まれている必要があります。 - - `https://example.com` -
- **urlパラメータ** - - オプション - - 地図 - - URL に追加するのは間違いありません。 文字列化された JSON オブジェクトを受け取ります。 -
- **ヘッダ** - - オプション - - 地図 - - リクエストに追加するヘッダー。文字列化された JSON オブジェクトを受け取ります。 -
- **セレクター** - - オプション - - リスト - - 指定されたもののみを出力として取得するセレクター。 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 説明 -
- **レスポンスボディ** - - 弦 - - 応答の本文。 -
- **ステータスコード** - - 整数 - - 応答の HTTP ステータス コード。 -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **入力例:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **出力例:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - HTTP POST 呼び出しを実行して、 APIエンドポイントにデータを送信します。 - - - これは、任意のヘッダー値の秘密の構文をサポートします。 - - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 説明 -
- **url** - - 必須 - - 弦 - - リクエストのターゲット URL。スキームには次の内容が含まれている必要があります。 - - `https://example.com` -
- **urlパラメータ** - - オプション - - 地図 - - URL に追加するのは間違いありません。 文字列化された JSON オブジェクトを受け取ります。 -
- **ヘッダ** - - オプション - - 地図 - - リクエストに追加するヘッダー。文字列化された JSON オブジェクトを受け取ります。 -
- **体** - - オプション - - 弦 - - リクエスト本体。 -
- **セレクター** - - オプション - - リスト - - 指定されたもののみを出力として取得するセレクター。 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 説明 -
- **レスポンスボディ** - - 弦 - - 応答の本文。 -
- **ステータスコード** - - 整数 - - 応答の HTTP ステータス コード。 -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **入力例:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **出力例:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - HTTP PUT リクエストを実行して、 APIエンドポイントのデータを更新します。 - - - 入力に機密データ（ `Api-Key`ヘッダーなど）を渡す必要がある場合は、 [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph ミューテーションを介して保存された値を使用できます。 - - 例： - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 説明 -
- **url** - - 必須 - - 弦 - - リクエストのターゲット URL。URL にはスキーム (例: https:// または http://) を含める必要があります。例： - - `https://example.com` -
- **urlパラメータ** - - オプション - - 地図 - - URL に追加するのは間違いありません。 文字列化された JSON オブジェクトを受け取ります。 -
- **ヘッダ** - - オプション - - 地図 - - リクエストに追加するヘッダー。文字列化された JSON オブジェクトを受け取ります。 -
- **体** - - オプション - - 弦 - - リクエスト本体。 -
- **セレクター** - - オプション - - リスト - - 指定されたもののみを出力として取得するセレクター。 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 説明 -
- **レスポンスボディ** - - 弦 - - 応答の本文。 -
- **ステータスコード** - - 整数 - - 応答の HTTP ステータス コード。 -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **入力例:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **出力例:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - HTTP DELETE リクエストを実行して、 APIエンドポイントのデータを削除します。 - - - 入力に機密データ（ `Api-Key`ヘッダーなど）を渡す必要がある場合は、 [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph ミューテーションを介して保存された値を使用できます。 - - 例： - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 説明 -
- **url** - - 必須 - - 弦 - - リクエストのターゲット URL。URL にはスキーム (例: https:// または http://) を含める必要があります。例： - - `https://example.com` -
- **urlパラメータ** - - オプション - - 地図 - - URL に追加するのは間違いありません。 文字列化された JSON オブジェクトを受け取ります。 -
- **ヘッダ** - - オプション - - 地図 - - リクエストに追加するヘッダー。文字列化された JSON オブジェクトを受け取ります。 -
- **セレクター** - - オプション - - リスト - - 指定されたもののみを出力として取得するセレクター。 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 説明 -
- **レスポンスボディ** - - 弦 - - 応答の本文。 -
- **ステータスコード** - - 整数 - - 応答の HTTP ステータス コード。 -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **入力例:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **出力例:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx deleted file mode 100644 index 006177259f6..00000000000 --- a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ /dev/null @@ -1,1210 +0,0 @@ ---- -title: New Relicアクション -tags: - - workflow automation - - workflow - - workflow automation actions - - New relic actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - この機能はまだ開発中ですが、ぜひお試しください。 - - この機能は現在、弊社の[プレリリース ポリシー](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy)に従ってプレビュー プログラムの一部として提供されています。 - - -このページでは、ワークフロー自動化アクション カタログで使用できる New Relic アクションの包括的なリファレンスを提供します。これらのアクションにより、カスタムイベントやログの送信、NerdGraph 書き込みの実行、 NRQL書き込みの実行、通知の送信など、 New Relicプラットフォームの機能をワークフロー定義に統合できます。 - -## 前提条件 - -ワークフロー自動化で New Relic アクションを使用する前に、次の点を確認してください。 - -* 適切な権限を持つ New Relic アカウント。 -* New Relicライセンスキー (データを別のアカウントに送信する場合)。 -* 使用を計画している特定の New Relic サービスに必要な権限。 - -New Relicアカウントのライセンスキーの作成および管理方法については、「[ライセンスキー」](/docs/apis/intro-apis/new-relic-api-keys/#license-key)を参照してください。 - -## 利用可能なNew Relicアクション - -カテゴリ別のすべての New Relic アクションのクイックリファレンス: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- カテゴリー - - アクション - - 目的 -
- **データの取り込み** - - [カスタムイベントを送信する](#newrelicingestsendevents) - - カスタムイベントをNew Relicに送信します。 -
- **データの取り込み** - - [ログを送信](#newrelicingestsendlogs) - - ログデータを New Relic に送信します。 -
- **NerdGraph** - - [GraphQL書き込みまたはミューテーションを実行する](#newrelicnerdgraphexecute) - - NerdGraph API に対して GraphQL コマンドを実行します。 -
- **クエリ** - - [NRDB書き込みを実行する](#newrelicnrdbquery) - - クロスアカウント NRQL クエリを実行します。 -
- **通知** - - [通知を送信](#newrelicnotificationsend) - - New Relic の宛先に通知を送信します。 -
- -## データ取り込みアクション - - - - New Relicにカスタムイベントを送信します - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 例 -
- **属性** - - オプション - - マップ - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **イベント** - - 必須 - - リスト - - `"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]` -
- **ライセンスキー** - - オプション - - ストリング - - `"{{ .secrets.secretName }}"` -
- **セレクター** - - オプション - - リスト - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: 提供される場合にすべてのイベントの一部となる共通属性。必要なイベント項目が共通定義をオーバーライドする場合、各イベント項目をマージします。 - * **events**: イベントデータのリスト。 イベントではカスタムイベント タイプを表す`eventType`フィールドを使用する必要があり、リクエストごとに許可されるイベントの最大数は 100 であることに注意してください。 - * **LicenseKey** : イベントが送信されるターゲット アカウントを指定するNew Relicアカウント ライセンスキー。 この値が指定されていない場合、ワークフローを実行しているアカウントに基づいてデフォルトのライセンスキーが想定されます。 - * **selectors** : 指定されたもののみを出力として取得するセレクター。 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 例 -
- **成功** - - ブール値 - - `true` -
- **エラーメッセージ** - - ストリング - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **期待される出力:** - - ```yaml - { - "success": true - } - ``` - - **イベントを取得:** - - ワークフローを正常に実行した後、ワークフローを実行したアカウントでクエリを実行して、関連付けられたイベントを取得できます。 - - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - New Relicへのログ送信 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力フィールド - - オプション性 - - タイプ - - 例 -
- **属性** - - オプション - - マップ - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **ログ** - - 必須 - - リスト - - `"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"` -
- **ライセンスキー** - - オプション - - ストリング - - `"{{ .secrets.secretName }}"` -
- **セレクター** - - オプション - - リスト - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: 提供された場合、すべてのログに含まれる共通属性。ログ項目で同じ属性が指定されている場合は、共通の定義が上書きされます。 - * **logs**: ログデータのリスト。 リクエストごとに許可されるログの最大数は 100 であることに注意してください。 - * **LicenseKey** : ログが送信される対象アカウントを指定するNew Relicアカウント ライセンスキー。 指定しない場合、ワークフローを実行するアカウントに基づいてデフォルトのライセンスキーが想定されます。 詳細については、 [「ライセンスキー」を](/docs/apis/intro-apis/new-relic-api-keys/#license-key)参照してください。 - * **selectors** : 指定されたもののみを出力として取得するセレクター。 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 出力フィールド - - タイプ - - 例 -
- **成功** - - ブール値 - - `true` -
- **エラーメッセージ** - - ストリング - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- ワークフローの例 -
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **期待される出力:** - - ```yaml - { - "success": true - } - ``` - - **ログを取得:** - - ワークフローを正常に実行した後、ワークフローを実行したアカウントでクエリを実行して、関連するログを取得できます。 - - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## NerdGraphアクション - - - - newrelic NerdGraph API に対して Graphql コマンドを実行します。コマンドはクエリまたはミューテーションのいずれかになります。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - タイプ - - 説明 - - 例 -
- **グラフQL** - - 必須 - - ストリング - - GraphQL 構文。コマンドの構築とテストにはGraphiQLを使用する必要があります - -
- **変数** - - 必須 - - map[string]any - - GraphQLステートメントで使用する任意のキーの値ペア変数。 - -
- **セレクター** - - オプション - - リスト - - 指定された唯一のものを出力として取得するセレクター。 - - ```yaml - { - "data": { - "actor": { - "user": { - "name": "" - } - } - } - ``` -
- - - - - - - - - - - - - - - - - - - - - - - -
- 出力 - - タイプ - - 例 -
- **データ** - - map[string]any: NerdGraphレスポンスの - - `data` - - プロパティの内容。 - - ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - - - - - - - - - - - - - - - - - - -
- 例 - - 出力 - - イベントを取得する -
- ```json - name: testLog - - steps: - - name: logStep - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - logs: - - message: 'Hello World' - ``` - - ```yaml - { - "success": true - } - ``` - - ワークフローを実行したアカウントでクエリを実行すると、関連付けられたイベントを取得できます。 - - ```yaml - SELECT message FROM Log WHERE allColumnSearch('Hello World', insensitive: true) SINCE 30 minutes ago - ``` -
- - - - - - -## クエリアクション - - - - NerdGraph API を介してクロスアカウント NRQL クエリを実行します。 - - - - - 入力 - - - - 出力 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - タイプ - - 説明 - - 例 -
- **クエリ** - - 必須 - - ストリング - - NRQL クエリ ステートメント。 - -
- **アカウント ID** - - オプション - - intのリスト - - **New Relic Account ID** - - \[New Relic アカウント ID]入力は、クエリが実行されるターゲット アカウントを指定できるターゲット ID のリストです。この値が入力として提供されない場合、クエリはワークフローの実行アカウントに関連付けられたアカウントに対して自動的に実行されます。 - -
- **セレクター** - - オプション - - リスト - - 指定された唯一のものを出力として取得するセレクター。 - - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - - - - -
- 出力 - - タイプ - - 例 -
- **results** - - : クエリの結果を含むオブジェクトの配列。 - - - - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - -## 通知アクション - - - - Slackなどの宛先と統合されたチャネルにメッセージを送信します - - - - - 入力 - - - - 出力 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - タイプ - - 説明 - - 例 -
- **タイプ** - - 必須 - - ストリング - - NewRelicの宛先の種類 - - `slack` -
- **宛先ID** - - 必須 - - 弦 - - NewRelic の宛先に関連付けられた DestinationId。 - - `123e4567-e89b-12d3-a456-426614174000` -
- **パラメーター** - - 必須 - - マップ - - 選択した宛先タイプに通知を送信するために必要なフィールド。 - - `{\"channel\": \"${{ YOUR_CHANNEL }}\", \"text\": \"Enter your text here\"}` -
- **セレクター** - - オプション - - リスト - - 指定された唯一のものを出力として取得するセレクター。 - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - -
- 出力 - - タイプ - - 例 -
- 成功 - - ブール値 - - `true/false` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index 46c4af9f971..00000000000 --- a/src/i18n/content/jp/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,634 +0,0 @@ ---- -title: ユーティリティアクション -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: A list of available utility actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - -このページでは、ワークフロー自動化アクション カタログで使用できるユーティリティ アクションのリファレンスを提供します。これらのアクションを使用すると、ワークフロー定義で一般的なデータ変換およびユーティリティ操作を実行できます。 - -## ユーティリティアクション - - - - このアクションは、エポックタイムスタンプを日付/時刻に変換するために使用されます。参照可能なもの: - - * [https://en.wikipedia.org/wiki/List\_of\_tz\_database\_time\_zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - * [https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT\_IDS](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS) - - 詳細については[fromEpochを](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html)参照してください。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - タイプ - - 説明 -
- **タイムスタンプ** - - 必須 - - int - - エポックタイムスタンプを表す整数。UNIXエポックは1970年1月1日午前0時（UTC）からの秒数であることに注意してください。 -
- **タイムスタンプ単位** - - オプション - - ストリング - - 提供されたタイムスタンプの単位を表す文字列。許容値: SECONDS、MILLISECONDS(デフォルト) -
- **タイムゾーンID** - - オプション - - ストリング - - 希望する日付/時刻のタイムゾーンを表す文字列。デフォルト: UTC -
- **パターン** - - オプション - - ストリング - - 希望する日時のパターンを表す文字列。デフォルト: ISO-8601 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- フィールド - - オプション性 - - データ型 - - 説明 -
- **日付** - - 必須 - - ストリング - - 日付の文字列表現。 -
- **時間** - - 必須 - - ストリング - - 時間の文字列表現。 -
- **データタイム** - - 必須 - - ストリング - - 日時を文字列で表現します。 -
- **タイムゾーン** - - 必須 - - マップ - - timezoneId と略語のマップ表現。 -
- - - - - - - - - - - - - - - - - - - - - - - -
- 例 - - ワークフロー入力 - - 出力 -
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - このアクションは、さまざまなタイプの入力 (JSON、マップ) を CSV 形式に変換するために使用されます。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - タイプ - - 説明 -
- **データ** - - 必須 - - どんな - - CSV に変換するデータを表す文字列。通常は JSON 文字列またはマップです。 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
- フィールド - - オプション性 - - データ型 - - 説明 -
- **csv** - - 必須 - - ストリング - - 受信したデータの CSV 表現。 -
- - - - - - - - - - - - - - - - - - - - - - -
- 例 - - ワークフロー入力 - - 出力 -
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` - -
- - - - - - - - - RFC 準拠の V4 uuid を生成します。 - - - - - 入力 - - - - 出力 - - - - 例 - - - - - - - - - - - - - - - - - - - - - - -
- 入力 - - オプション性 - - データ型 - - 説明 -
- - - - -
- - - - - - - - - - - - - - - - - - - - - - -
- フィールド - - データ型 - - 説明 -
- **uuid** - - ストリング - -
- - - - - - - - - - - - - - - - - - - - - -
- 例 - - ワークフロー入力 - - 出力 -
- - - 名前: generateUUID
手順: - - * 名前: generateUUID タイプ: アクション アクション: utils.uuid.generate バージョン: 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx deleted file mode 100644 index 076587135a5..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-10-02' -version: 'Sep 26 - Oct 02, 2025' -translationType: machine ---- - -### 주요 변경 사항 - -* Kubernetes GA 및 호스트 공개 미리 보기에 대한 포괄적인 개정 사항을 포함하여 [플릿 제어 문서를](/docs/new-relic-control/fleet-control/overview) 업데이트했습니다. 여기에는 새로운 플릿 관리 기능, 향상된 보안 기능, 업데이트된 설정 절차가 포함됩니다. -* 향상된 설정 옵션, 모니터링 기능, 문제 해결, 해결 지침을 포함하여 공개 미리 보기를 위한 광범위한 개정으로 [에이전트 제어 문서를](/docs/new-relic-control/agent-control/overview) 업데이트했습니다. -* 포괄적인 기능 세부 정보와 구현 지침을 제공하여 일반적으로 사용할 수 있도록 [마크 및 측정 문서를](/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures/) 재구성했습니다. -* 새로운 이메일 확인 단계와 대상 제한으로 [공지 공지 흐름이](/docs/alerts/admin/rules-limits-alerts) 향상되었습니다. -* [가격 책정 모델 이름을](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management/) "뉴클레릭 컴퓨팅 Public Preview 또는 Core 컴퓨트 계획"에서 "Advanced 또는 Core 컴퓨트 계획으로 업데이트했습니다. - -### 사소한 변경 사항 - -* 개선된 설정 프로세스를 위해 [WordPress 풀스택 통합](/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration) 지침이 업데이트되었습니다. -* 업데이트된 스크린샷과 개선된 예시를 통해 [대시보드 템플릿 변수](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables) 문서가 개선되었습니다. -* 향상된 컴퓨터 사용량 모니터링 기능으로 [사용량 조회 및 알림이](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) 업데이트되었습니다. -* 포괄적인 컴퓨트 관리 기능을 갖춘 향상된 [사용 UI 문서입니다](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-ui). -* [.NET 에이전트 설정](/docs/apm/agents/net-agent/configuration/net-agent-configuration) 에서 중복 앵커 참조를 수정했습니다. -* 개선된 이메일 대상 관리 기능으로 [공지통합이](/docs/alerts/get-notified/notification-integrations) 업데이트되었습니다. -* 지원되는 지역과 VPC 설정 요구 사항에 대한 언어 명확성을 개선하여 [AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink) 설명서를 업데이트했습니다. -* 콘텐츠 관리를 위한 새로운 게시물 식별자가 업데이트되었습니다. - -### 릴리즈 정보 - -* 최신 릴리스에 대한 최신 정보를 받아보세요. - - * [Node.js 에이전트 v13.4.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0): - - * 생성된 이벤트를 구독하도록 amqplib 및 cassandra-driver 측정, 리소스를 업데이트했습니다. - * 최신 지원 패키지 버전을 적용하여 Node.js 에이전트 호환성 보고서를 업데이트했습니다. - * 추적 후크에 WASM 최적화를 추가했습니다. - * 더 나은 코드 문서화를 위해 JSDoc 요구 사항이 강화되었습니다. - - * [접착제 에이전트 v11.0.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000): - - * 끌어서 3.7에 대한 지원을 제거하고 다양한 구형 API를 더 이상 사용하지 않습니다. - * AutoGen 및 Pyzeebe 프레임워크에 대한 새로운 측정, 도구가 추가되었습니다. - * AI 모니터링을 위해 MCP(Model Context Protocol) 명명된 스팬을 도입했습니다. - * psycopg에서 발생하는 충돌을 수정하고 AI 모니터링이 활성화된 경우에만 MCP 범위가 기록되도록 했습니다. - - * [인프라 에이전트 v1.69.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690): - - * AWS SDK를 V1에서 V2로, 도커 API 라이브러리를 v26에서 v28로 업그레이드했습니다. - * 여러 CPU 그룹(64개 이상의 코어)이 있는 인스턴스에 대한 고정 Windows CPU 모니터링이 추가되었습니다. - * 기본 로그인 레벨 지원으로 향상된 로그 형식 처리. - - * [Kubernetes 통합 v3.45.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3): - - * newrelic-인프라-3.50.3 및 nri-bundle-6.0.15 차트 버전에 포함되어 있습니다. - - * [NRDOT v1.5.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-25): - - * 향상된 지표 수집을 위해 nrdot-수집기-k8s에 metricsgenerationprocessor를 추가했습니다. - - * [.NET 에이전트 v10.45.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0): - - * OpenTelemetry 구현을 기반으로 분산 추적을 위한 새로운 TraceId 비율 기반 샘플러가 추가되었습니다. - * 데이터 저장 측정, 로그를 비활성화할 수 있는 MSSQL 연결 문자열 구문 분석 예외를 수정했습니다. - * 사용자 정의 측정과의 호환성 향상을 위해 Kafka "Consume" 측정, 로그 문제를 해결했습니다. - - * [뉴렐릭 Android 모바일 앱 v5.30.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5308): - - * 버그를 수정하고 개선하여 모바일 앱 성능을 향상시켰습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx deleted file mode 100644 index 0d2ad257b5a..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-11' -version: 'version: October 4-10, 2024' -translationType: machine ---- - -### 새로운 문서 - -* [릴리스 빌드에 충돌 데이터가 나타나지 않습니다(안드로이드)는](/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears) 뉴렐릭 UI 에서 충돌과 관련된 데이터가 표시되지 않는 경우 수행할 작업을 알려줍니다. -* [WSL과 CodeStream을 어떻게 사용할 수 있나요?](/docs/codestream/troubleshooting/using-wsl) 에서는 CodeStream과 함께 Windows Subsystem for Linux(WSL)를 사용하는 방법에 대한 단계별 지침을 제공합니다. -* [`UserAction`](/docs/browser/browser-monitoring/browser-pro-features/user-actions) 는 웹 애플리케이션에서 사용자 동작을 이해하는 데 도움이 되는 브라우저 모니터링의 새로운 이벤트 유형입니다. -* [WithLlmCustomAttributes(Python 에이전트 API)는](/docs/apm/agents/python-agent/python-agent-api/withllmcustomattributes-python-agent-api) 요구 사항, 레이더, 반환 값 및 예제 사용법을 포함하여 새로운 컨텍스트 관리자 API 설명합니다. - -### 사소한 변경 사항 - -* [뉴렐릭 텔레메트리 엔드포인트](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) 에 APM 에이전트에 대한 US 및 EU 데이터 센터 엔드포인트가 추가되었습니다. - -* [Visual Studio를](/docs/codestream/troubleshooting/client-logs/#visual-studio) 사용할 때 CodeStream 클라이언트 측 로그를 찾는 방법에 대한 지침이 업데이트되었습니다. - -* 더 명확한 설명을 위해 [음소거 규칙에 대한 공지 옵션을](/docs/alerts/get-notified/muting-rules-suppress-notifications/#notify) 다시 표현했습니다. - -* [계측된 모듈](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrumented-modules) 의 다음 패키지에 대한 호환성 정보가 업데이트되었습니다. - - * `@aws-sdk/client-bedrock-runtime` - * `@aws-sdk/client-dynamodb` - * `@aws-sdk/client-sns` - * `@aws-sdk/client-sqs` - * `@aws-sdk/lib-dynamodb` - * `@grpc/grpc-js` - * `@langchain/core` - * `@smithy/smithy-client` - * `next` - * `openai` - -* [데이터 수집 IP 블록](https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#ingest-blocks) 에서 두 번째 EU 데이터센터 종료포인트를 `212.32.0.0/20` 으로 수정했습니다. - -* 데이터가 [뉴렐릭의 EU 또는 미국 데이터센터](/docs/alerts/overview/#eu-datacenter) 에 저장되어 있는지 여부에 관계없이 뉴렐릭의 알림 서비스가 미국에서 실행되도록 지정되었습니다. - -* [사용자 정의 속성을](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes) 설정하는 방법에 대한 정보가 수정되었습니다. 또한, 예시를 업데이트했습니다. - -* [문제를 승인 취소하고 닫는](/docs/alerts/get-notified/acknowledge-alert-incidents/#unacknowledge-issue) 단계가 업데이트되었습니다. - -* [여러 문제를 확인하고 종결하는 방법](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#bulk-actions) 에 대한 정보가 추가되었습니다. - -* [차트 새로 고침 빈도](/docs/query-your-data/explore-query-data/use-charts/chart-refresh-rates) 소개 부분을 확장하여 새로 고침 빈도는 뉴렐릭 인력 소비 가격 책정 플랜을 사용하는 경우에만 구성할 수 있다는 점을 설명했습니다. - -* [TLS 암호화](/docs/new-relic-solutions/get-started/networks/#tls) 에서 필요한 TLS(전송 계층 보안) 버전 정보를 수정했습니다. - -* 현재 뉴렐릭 UI 와 일치하도록 [Kubernetes 통합 설치](/install/kubernetes) 절차의 6단계를 업데이트했습니다. - -* [쿼리 Kubernetes 데이터](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#view-data) 에서 테이블 뒤에 청구 불가능한 이벤트 `InternalK8sCompositeSample` 의 중요성을 기록했습니다. - -* 정확성과 명확성을 위해 [API 키를 보고 관리하는](/docs/apis/intro-apis/new-relic-api-keys/#keys-ui) 방법에 대한 지침을 다시 작성했습니다. - -* [API 탐색기 사용](/docs/apis/rest-api-v2/api-explorer-v2/use-api-explorer) 및 현재 API 탐색기와 일치하도록 [애플리케이션 ID, 호스트 ID, 인스턴스 ID 나열](/docs/apis/rest-api-v2/get-started/list-application-id-host-id-instance-id) 에서 API 탐색기를 사용하는 방법에 대한 지침이 업데이트되었습니다. - -* [OpenTlementry APM과 인프라를 연관시키는](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/#infrastructure-correlation) 예를 다시 추가했습니다. - -* [Azure Monitor 통합으로 마이그레이션할](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#migrate) 때 중복된 메트릭 이름을 피하는 방법을 알아보았습니다. - -### 릴리즈 정보 - -새로운 기능과 릴리스에 대한 정보를 알아보려면 '새로운 소식' 게시물을 확인하세요. - -* [뉴렐릭 Pathpoint는 넷플릭스를 비즈니스 KPI에 연결합니다.](/whats-new/2024/10/whats-new-10-10-pathpoint) - -최신 출시 제품에 대한 최신 정보를 받아보세요. - -* [Android v5.25.1용 유니스 인박스(errors inbox)](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-52501) - * 오류를 반복하고, 프로파일된 속성을 검사하고, 더 많은 작업을 수행할 수 있습니다. - -* [플러터 에이전트 v1.1.4](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-114) - * iOS 에이전트를 7.5.2로 업데이트합니다. - -* [Kubernetes 통합 v3.29.6](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6) - - * 업데이트 v1.23.2로 이동 - * Prometheus의 공통 라이브러리를 v0.60.0으로 업데이트합니다. - -* [파이썬 에이전트 v10.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100) - - * 끌어오기 3.13 지원 - * 새로운 컨텍스트 관리자 API를 제공합니다. - * Amazon ECS Fargate 도커 ID 보고를 지원합니다. - * 측정, 사용 포함 `SQLiteVec` - -* [유니티 에이전트 v1.4.1](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141) - - * 기본 Android 및 iOS 에이전트 업데이트 - * 버그 수정이 포함되어 있습니다 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx deleted file mode 100644 index 8cd47f739d0..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-18' -version: 'version: October 11-17, 2024' -translationType: machine ---- - -### 새로운 문서 - -* [Forward Kong Gateway 로그는](/docs/logs/forward-logs/kong-gateway/) Kubernetes 통합을 통해 이 새로운 로그 포워딩을 설치하고 사용하는 방법을 설명합니다. -* [Azure App Service 모니터링은](/docs/apm/agents/manage-apm-agents/azure/monitoring-azure-app-service/) 이 Azure 서비스를 뉴렐릭과 통합하는 방법을 설명하고, 네온, .NET, Node.js 및 Python APM 에이전트에 대해 이를 설정하는 방법에 대한 지침 링크를 제공합니다. -* [데이터 탐색기 소개에서는](/docs/query-your-data/explore-query-data/query-builder/introduction-new-data-explorer/) 새로운 데이터 탐색기 UI 사용하여 데이터를 쿼리하는 방법과 새로운 플랫폼이 어떻게 사용자를 지원하고 문제를 해결할 수 있는지에 대해 자세히 알아보는 방법을 설명합니다. -* [APM 언어 에이전트를 사용하여 Amazon ECS 환경을 모니터링하면](/docs/infrastructure/elastic-container-service-integration/monitor-ecs-with-apm-agents/) Amazon ECS 환경에 APM 에이전트를 설치하는 데 도움이 됩니다. -* [NRQL로 마이그레이션에서는](/docs/apis/rest-api-v2/migrate-to-nrql/) REST API v2 쿼리를 NRQL 쿼리로 마이그레이션하는 방법을 설명합니다. - -### 주요 변경 사항 - -* 오픈 소스 사이트의 콘텐츠를 문서 사이트로 이전했습니다. -* [Kubernetes 에이전트 운영자를](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/) 사용하여 비밀을 관리하는 방법을 명확히 했습니다. - -### 사소한 변경 사항 - -* [뉴렐릭의OpenTelemetry 지표](/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics/#otlp-summary) 에서 OpenTelemetry 요약 지표가 지원되지 않는다는 점을 명확히 했습니다. -* Kubernetes 및 Google Kubernetes Engine 타일을 찾을 수 있는 위치를 명확히 하기 위해 [권장 공지 및 대시보드](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies/#add-recommended-alert-policy) 의 스크린샷을 업데이트했습니다. -* 더 이상 관련이 없으므로, APM 에이전트와 관련된 Stackato 및 WebFaction 문서를 삭제했습니다. -* [네트워크](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) 문서에 새로운 브라우저 모니터링 엔드포인트를 추가했습니다. -* 브라우저 모니터링 문제 해결, 문서 해결 전반에 걸쳐 사소한 문제를 정리했습니다. -* [문제 해결 런타임 업그레이드 오류](/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting/#scripted-api-form) 에서는 `$http` 객체를 사용하여 이전 Node 런타임을 사용할 때 발생하는 문제를 해결하는 방법을 설명합니다. -* [.NET 에이전트 API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api) 에서 `ITransaction` API 호출에 `NewRelic.Api.Agent.NewRelic` 추가하고 새로운 `RecordDatastoreSegment` API 호출을 추가했습니다. - -### 릴리즈 정보 - -최신 출시 제품에 대한 최신 정보를 받아보세요. - -* [안드로이드 에이전트 v7.6.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-761/) - - * Android Gradle 플러그인 8.7에 대한 지원을 추가합니다. - * ProGuard/DexGuard 매핑 파일이 올바르게 업로드되지 않는 문제를 수정했습니다. - * 기타 버그 수정 - -* [브라우저 에이전트 v1.269.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0/) - - * NPM의 MicroAgent 로더가 로깅 API를 사용하여 로그 데이터를 수동으로 캡처할 수 있도록 허용합니다. - * Logging에 측정, 로그데이터 추가 - * 세션 트레이스 및 세션 리플레이 보안 정책 오류 관련 버그 수정 - -* [Go 에이전트 v3.35.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0/) - - * 보안 쿠키 이벤트 보고에 대한 지원을 추가합니다. - * 로그 속성에 `error.Error()` 값을 사용합니다. - * AMQP 서버 연결에 대한 URL 지원 향상 - * 다양한 버그 수정 - -* [람다 확장 v2.3.14](/docs/release-notes/lambda-extension-release-notes/lambda-extension-2.3.14/) - - * 확장 프로그램 시작 검사를 무시하는 기능을 추가합니다. - * `NR_TAGS` 환경 변수를 사용하는 방법에 대한 정보로 README를 업데이트합니다. - * `NEW_RELIC_ENABLED` Boolean 환경 변수에 대한 지원을 추가합니다. - -* [.NET 에이전트 v10.32.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0/) - - * 접두사가 붙은 환경 변수를 더 이상 사용하지 않습니다. `NEWRELIC_` - * 모든 환경 변수에 대해 일관된 명명 체계를 구현합니다. - * 최신 버전을 지원하도록 CosmosDB 측정, 로그를 업데이트합니다. - -* [Ping 런타임 v1.47.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.47.0/) - * 루트가 아닌 사용자에 대한 ping-런타임 제어 펼쳐보기에 대한 사용자 권한과 관련된 문제를 수정합니다. - -* [파이썬 에이전트 v10.2.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200/) - * Azure 컨테이너 앱 모니터링에 대한 해당 옵션을 지원하기 위해 Azure init 컨테이너 연산자 플래그를 추가합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx deleted file mode 100644 index d3439dbd189..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-07' -version: 'November 2 - November 7, 2025' -translationType: machine ---- - -### 새로운 문서 - -* NerdGraph API를 통해 [데이터 액세스 제어를 관리하는 실제적인 예를 제공하기 위해 NerdGraph 데이터 액세스 제어 예를](/docs/apis/nerdgraph/examples/nerdgraph-data-access-control) 추가했습니다. -* 이상치 감지 설정에 대한 지침을 제공하기 위해 [이상치 감지를](/docs/alerts/create-alert/set-thresholds/outlier-detection) 추가했습니다. -* 인프라 모니터링 설정을 위한 전제 조건에 대한 향상된 설명서를 제공하기 위해 [인프라 카탈로그를](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog/) 추가했습니다. -* 미디어 스트리밍과 브라우저/모바일 간의 관계를 이해하는 데 도움이 되는 지침을 제공하기 위해 [미디어 스트리밍 서비스 맵을](/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps/) 추가했습니다. -* [미디어 스트리밍에 대한 오류 인박스(오류 받은 편지함)를](/docs/errors-inbox/media-streaming-group-error/) 추가하여 미디어 스트리밍 오류를 그룹화하고 관리하는 방법에 대한 지침을 제공합니다. - -### 주요 변경 사항 - -* 더 나은 명확성을 위해 개정된 YAML 예제와 업데이트된 필드 이름을 사용하여 [에이전트 제어 설정을](/docs/new-relic-control/agent-control/configuration) 업데이트했습니다. -* 개선된 YAML 구성 예제를 통해 [에이전트 제어 설정이](/docs/new-relic-control/agent-control/setup) 업데이트되었습니다. -* 정확도를 높이기 위해 업데이트된 YAML 예제를 사용하여 [에이전트 제어 재계측을](/docs/new-relic-control/agent-control/reinstrumentation) 업데이트했습니다. -* 업데이트된 [에이전트 제어 문제 해결, 세련된 설정 예시로 해결](/docs/new-relic-control/agent-control/troubleshooting). - -### 사소한 변경 사항 - -* [MySQL 통합 요구 사항](/install/mysql/) 문서에 MariaDB 호환성 정보를 추가했습니다. -* 데이터 정책을 사용하여 텔레메트리 데이터에 대한 액세스를 제어하기 위한 포괄적인 지침을 제공하기 위해 [데이터 액세스 제어를](/docs/accounts/accounts-billing/new-relic-one-user-management/data-access-control) 추가했습니다. -* 최신 설정 세부정보로 [GitHub 클라우드 통합](/docs/service-architecture-intelligence/github-integration/) 문서를 업데이트했습니다. -* 버전 3.60에 대한 [진단 CLI 설명서가](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-360) 업데이트되었습니다. -* Kubernetes 에 대한 [Vizier 포트](/docs/ebpf/k8s-installation/) 설정 설명서가 업데이트되었습니다. - -### 릴리즈 정보 - -* 최신 릴리스에 대한 최신 정보를 받아보세요. - - * [끌어 당기는 에이전트 v11.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100): - - * 끌어오기 3.14에 대한 지원이 추가되었습니다. - * 속성 필터 설정을 위한 환경 변수가 추가되었습니다. - * 트랜잭션 데코레이터에 비동기 생성기에 대한 지원이 추가되었습니다. - * Claude Sonnet 3+ 모델과 지역 인식 모델을 포함한 AWS Bedrock 측정, 계측의 추가 모델에 대한 지원이 추가되었습니다. - * describe\_account\_settings, update\_account\_settings, update\_max\_record\_size, update\_stream\_warm\_throughput을 포함한 새로운 AWS Kinesis 메서드에 대한 측정 및 계측 기능이 추가되었습니다. - * ConnectionPool을 사용할 때 aiomysql에서 발생하는 RecursionError를 수정했습니다. - * 다시마 생산자에서 속성이 제대로 전달되지 않는 버그를 수정했습니다. - * 하베스트 스레드 내에서 shutdown\_agent를 호출할 때 발생하는 오류가 수정되었습니다. - - * [iOS 에이전트 v7.6.0](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760): - - * 모바일 세션 리플레이 공개 미리보기 기능이 추가되었습니다. - * 필수 iOS 버전을 iOS 16으로 올렸습니다. - * 로깅 시 발생할 수 있는 처리된 예외 문제를 해결했습니다. - * 잘못된 형식, 이름 지정 경고를 수정했습니다. - - * [안드로이드 에이전트 v7.6.12](/docs/release-notes/mobile-release-notes/android-release-notes/android-7612): - - * Jetpack Compose에 세션 리플레이 기능이 추가되었습니다. - * 공식 세션 리플레이 공개 미리보기 버전이 출시되었습니다. - * 여러 세션 리플레이 버그를 수정했습니다. - - * [Kubernetes 통합 v3.49.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0): - - * 자세한 변경 사항은 GitHub 릴리스 노트에서 확인하세요. - * newrelic-infrastructure-3.54.0 및 nri-bundle-6.0.20 차트 버전에 포함되어 있습니다. - - * [로그 v251104](/docs/release-notes/logs-release-notes/logs-25-11-04): - - * .NET 특정 로그 페이로드 형식에 대한 지원이 추가되었습니다. - * .NET 특정 로그 형식을 처리하기 위해 NEW\_RELIC\_FORMAT\_LOGS 환경 변수가 도입되었습니다. - - * [노드 브라우저 런타임 rc1.2](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.2): - - * Chrome 브라우저를 141 버전으로 업그레이드했습니다. - * 브레이스 확장에 대한 CVE-2025-5889 취약점이 수정되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx deleted file mode 100644 index 28e60717ddb..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-14' -version: 'November 08 - November 14, 2025' -translationType: machine ---- - -### 새로운 문서 - -* 브라우저 모니터링을 통해 개인정보 보호 규정을 준수하는 동의 관리 구현을 문서화하기 위해 [브라우저 동의 모드를](/docs/browser/new-relic-browser/configuration/consent-mode) 추가했습니다. -* Kubernetes 환경에서 APM 측정, 로그에 대한 설정 지침을 제공하기 위해 [Kubernetes 자동 연결에 확장을](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach) 추가했습니다. -* OpenTelemetry 캐시 설정 옵션을 문서화하기 위해 [Bring your own 캐시 설정을](/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache) 추가했습니다. - -### 주요 변경 사항 - -* 로그 기반 알림을 분석하기 위한 AI 로그 요약 기능을 갖춘 향상된 [대응 인텔리전스 AI](/docs/alerts/incident-management/response-intelligence-ai). -* 컴퓨터 관리 문서를 [소비 관리](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management) 로 이름을 바꾸고 재구성했습니다. -* Spring 프로세서 명명 옵션 및 SQL 파서 설정으로 [저항 세력 설정이](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file) 업데이트되었습니다. -* 4 Google 클라우드 서비스에 대한 권한이 수정되어 [GCP 통합 커스텀 역할이](/docs/infrastructure/google-cloud-platform-integrations/get-started/integrations-custom-roles) 업데이트되었습니다. -* 향상된 [MCP 문제 진단, 모델 컨텍스트 프로토콜 설정 시나리오 및 솔루션을 통한 문서 정리](/docs/agentic-ai/mcp/troubleshoot). -* 새로운 Sidekiq 재시도 오류 설정 옵션으로 향상된 [루비 에이전트 설정](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration). -* Debian Trixie를 지원하여 [PHP 에이전트 설치를](/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian) 업데이트했습니다. - -### 사소한 변경 사항 - -* 내구성 25 호환성 [요구 사항을](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent) 추가했습니다. -* [.NET 에이전트 호환성 요구 사항](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) 에 .NET 10 지원이 추가되었습니다. -* [서비스 수준 관리 알림이](/docs/service-level-management/alerts-slm) 업데이트되었습니다. -* Drupal 및 라라벨 버전 정보로 [PHP 대응 호환성을](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) 업데이트했습니다. -* [Kubernetes 통합 호환성이](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements) 업데이트되었습니다. -* 프레임워크 지원으로 [배터리 성능 요구사항이](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent) 업데이트되었습니다. - -### 릴리즈 정보 - -다음의 새로운 소식을 확인하세요: - -* [뉴렐릭 MCP 서버 공개 미리보기 출시](/whats-new/2025/11/whats-new-11-05-mcp-server) - -* [뉴렐릭 이상치 공개 미리 보기에서 감지](/whats-new/2025/11/whats-new-11-05-outlier-detection) - -* [AI 로그인 공지 요약(미리보기)](/whats-new/2025/11/whats-new-11-13-AI-Log-Alert-Summarization) - -* 최신 릴리스에 대한 최신 정보를 받아보세요. - - * [Node.js 에이전트 v13.6.4](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4): - - * 메시지 소비에 대한 트랜잭션을 적절히 종료하기 위해 MessageConsumerSubscriber를 수정했습니다. - * traceparent에서 샘플링된 플래그를 올바르게 설정하기 위해 MessageProducerSubscriber를 수정했습니다. - * 적절한 페이로드 역직렬화를 위해 Bedrock 미들웨어 등록 우선순위를 고정했습니다. - - * [Node.js 에이전트 v13.6.3](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3): - - * OpenAI 측정, 디지털 스트리밍 처리를 stream\_options.include\_usage로 수정했습니다. - * LlmCompletionSummary에 대한 @google/생성형 AI의 개수 할당을 수정했습니다. - * AWS Bedrock 측정, 로그아웃 개수 할당을 수정했습니다. - - * [자바 에이전트 v8.25.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250): - - * 25 지원이 추가되었습니다. - * Logback-1.5.20 지원이 추가되었습니다. - * Spring Controller 명명 설정 옵션이 도입되었습니다. - * Kotlin Coroutines v1.4+ 지원이 추가되었습니다. - * 오류 클래스 명명 구문 분석 논리를 수정했습니다. - * 대규모 스택 추적으로 인한 오류 로깅에서 발생할 수 있는 잠재적인 메모리 문제가 해결되었습니다. - - * [루비 에이전트 v9.23.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0): - - * sidekiq.ignore\_retry\_errors를 추가했습니다. 재시도 오류 캡처를 제어하는 설정 옵션입니다. - * 더 이상 사용되지 않는 Capistrano 구현, 배포 녹음(v10.0.0에서 제거). - * 보다 일관성 있는 추적을 위해 향상된 원격 상위 샘플링 설정입니다. - - * [.NET 에이전트 v10.46.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1): - - * 정확도를 높이기 위해 Azure Service Bus 프로세서 모드 트랜잭션에서 소비 기간을 제거했습니다. - * UI 명확성을 높이기 위해 ReportedConfiguration 열거형 직렬화를 업데이트했습니다. - - * [Kubernetes 통합 v3.50.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0): - - * KSM e2e 차트 버전을 2.16으로 업데이트했습니다. - * kube\_endpoint\_address 메트릭에 대한 지원이 추가되었습니다. - * Windows 지원이 활성화된 상태에서 priorityClassName 템플릿 문제가 해결되었습니다. - - * [신세틱스 Job Manager 릴리스 486](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-486): - - * CVE-2024-6763 및 CVE-2025-11226을 포함한 Ubuntu 및 분리를 수정했습니다. - - * [신세틱스 Ping Runtime v1.58.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.0): - - * CVE-2025-5115 및 CVE-2025-11226을 포함한 Ubuntu 및 분리를 수정했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx deleted file mode 100644 index 3b068a5812a..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-21' -version: 'November 17 - November 21, 2025' -translationType: machine ---- - -### 새로운 문서 - -* 기존 삭제 규칙을 새로운 파이프라인 클라우드 규칙 시스템으로 마이그레이션하기 위한 포괄적인 지침을 제공하기 위해 '삭제 규칙을 파이프라인 cloud [cloud 으로 마이그레이션'](/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules/) 기능을 추가했습니다. -* 뉴렐릭 PHP 에이전트를 사용하여PHPUnit 버전 11+ 메모리 외부 오류에 대한 문제 해결 및 해결 지침을 제공하기 위해 [PHPUnit 문제 호환성을](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) 추가했습니다. - -### 주요 변경 사항 - -* PHP 에이전트에서 PHPUnit에 대한 지원이 종료된 후 PHPUnit 테스트 데이터 분석 문서가 제거되었습니다. PHPUnit 비호환 문제에 대한 문제 해결, 해결 문서로 대체되었습니다. -* 향상된 조직을 위해 [검색 및 필터를](/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) 재구성하고 새로운 카탈로그 필터링 기능을 추가했습니다. -* 네트워크 성능 모니터링을 위한 분리 설정 옵션을 사용하여 [Kubernetes 환경에 뉴렐릭 eBPF 설치를](/docs/ebpf/k8s-installation) 업데이트했습니다. - -### 사소한 변경 사항 - -* [데이터 보존 관리](/docs/data-apis/manage-data/manage-data-retention) 문서에 미디어 스트리밍 데이터 보존 정보를 추가했습니다. -* 지원 종료 후 [PHP 에이전트 호환성 및 요구 사항](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) 호환성 표에서 PHPUnit이 제거되었습니다. -* [Usage 쿼리 및 알림](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) 에 대한 NRQL 쿼리 예제가 수정되었습니다. -* 로컬 저장소 구성 정보가 포함된 [브라우저 앱 설정 페이지가](/docs/browser/new-relic-browser/configuration/browser-app-settings-page/) 업데이트되었습니다. -* 브라우저 문서 탐색에 동의 모드가 추가되었습니다. -* 모바일 SDK에 대한 [구성 설정이](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings) 업데이트되었습니다. -* 추가 차트 유형 정보가 포함된 향상된 [차트 유형](/docs/query-your-data/explore-query-data/use-charts/chart-types) 문서입니다. -* RBAC 역할을 명확히 한 MCP에 대한 [개요](/docs/agentic-ai/mcp/overview) 및 [문제 해결이](/docs/agentic-ai/mcp/troubleshoot) 업데이트되었습니다. - -### 릴리즈 정보 - -* 최신 릴리스에 대한 최신 정보를 받아보세요. - - * [Go 에이전트 v3.42.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0): - - * 거래, 사용자 정의 Insights, 오류 및 로그에 대한 새로운 최대 샘플 설정 옵션이 추가되었습니다. - * nrlambda에 MultiValueHeaders에 대한 지원이 추가되었습니다. - * nrpxg5에서 사용되지 않는 변수를 제거했습니다. - * 오류 이벤트가 예상됨을 올바르게 표시하지 않는 버그를 수정했습니다. - - * [.NET 에이전트 v10.47.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0): - - * ASP.NET 웹 앱의 ExecutionContext를 통해 트랜잭션이 흐르도록 하는 선택적 트랜잭션 저장 메커니즘을 추가했습니다. - * Azure Service Bus 측정, 리소스 null 참조 예외가 수정되었습니다. - * 메시지가 포함될 때 채팅 완료를 처리하기 위해 OpenAI 측정, 도구가 포함되지 않는 문제를 해결했습니다. - - * [Node.js 에이전트 v13.6.5](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5): - - * 다음 처리기가 경로나 라우터를 전달할 때 명시적인 측정을 무시하도록 업데이트되었습니다. - * 약속일 경우 소비자 콜백이 끝날 때까지 기다리도록 MessageConsumerSubscriber를 업데이트했습니다. - - * [Node.js 에이전트 v13.6.6](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6): - - * app.use 또는 router.use Express Measuring, Scientific을 업데이트하여 정의된 모든 미들웨어를 적절히 래핑했습니다. - * distributed\_tracing.samplers.partial\_granularity에 대한 설정을 추가했습니다. 그리고 distributed\_tracing.samplers.full\_granularity. - - * [PHP 에이전트 v12.2.0.27](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27): - - * 라라벨 12 지원이 추가되었습니다. - * 라라벨 10.x+ 및 PHP 8.1+에 라라벨 Horizon 지원이 추가되었습니다. - * 고정된 라라벨 대기열 작업 예외 처리. - * Golang 버전을 1.25.3으로 올렸습니다. - - * [Kubernetes 통합 v3.50.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1): - - * 버그 수정 및 개선 사항을 적용하여 버전 3.50.1로 업데이트되었습니다. - - * [인프라 에이전트 v1.71.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711): - - * 의존성/종속성 newrelic/nri-docker v2.6.3으로 업데이트했습니다. - * 의존성/종속성 newrelic/nri-flex를 v1.17.1로 업데이트했습니다. - * Go 버전을 1.25.4로 업그레이드했습니다. - * 의존성/종속성 newrelic/nri-prometheus를 v2.27.3으로 업데이트했습니다. - - * [로그 25-11-20](/docs/release-notes/logs-release-notes/logs-25-11-20): - - * AWS-log-ingestion 람다의 CVE-2025-53643을 수정했습니다. - * aiohttp 라이브러리를 3.13.2로 업데이트했습니다. 그리고 시 버전은 1.8.3입니다. - - * [노드 브라우저 런타임 rc1.3](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.3): - - * Chrome 브라우저를 142로 업그레이드했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx deleted file mode 100644 index 8279ab6d924..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-05-24' -version: 'version: May 17-23, 2024' -translationType: machine ---- - -### 새로운 문서 - -* 우리의 새로운 [아파치 Mesos 통합은](/docs/infrastructure/host-integrations/host-integrations-list/apache-mesos-integration) 여러분의 양방향 시스템 커널 성능을 모니터하는 데 도움이 됩니다. -* 새로운 [Temporal 클라우드 통합은](/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration) Temporal Cloud의 업무 흐름, 삭제스페이스 및 확장 가능한 업무를 모니터링하고 진단하는 데 도움이 됩니다. -* [AWS Elastic Beanstalk에 .NET 앱이](/docs/apm/agents/net-agent/install-guides/install-net-agent-on-aws-elastic-beanstalk) 있나요? 이 새로운 설치 문서는 해당 데이터를 플랫폼으로 수집하는 명확한 경로를 보여줍니다. - -### 주요 변경 사항 - -* [신세틱 모델 모범 사례](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide) 및 [합성 스크립트 브라우저 참조](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100) 에 합성 및 브라우저 스크립트 모니터 코드 예제를 추가하고 업데이트했습니다. 코드 예제는 독자들이 가장 많이 요청하는 것 중 하나이므로, 이런 예제가 더 많이 나오기를 항상 기대합니다. - -* 네트워크 성능 모니터링 문서에서 많은 작은 업데이트가 주요 변경 사항으로 이어졌습니다. 17개 문서에서 Podman에 대한 지원 환경이 업데이트되었습니다. - -* [로그 기록 라이브 아카이브의](/docs/logs/get-started/live-archives) 작동 방식과 해당 [로그 기록 데이터를 언제 사용할 수 있는지](/docs/logs/get-started/live-archives-billing) 명확히 설명했습니다. - -* Lambda 모니터링을 [통해 컨테이너화된 이미지 계층](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images/) 에 다이어그램과 환경 변수를 추가했습니다. - -* 뉴렐릭의 REST API v1은 완전히 EOL되었으며, 관련 문서 몇 개를 삭제했습니다. - -* 인프라 모니터링 문서를 대대적으로 조사했습니다. - - * 이를 스타일 가이드에 맞춰 조정하세요. - * 불필요한 내용을 제거하세요. - * 설치 문서를 왼쪽 탐색창에서 더 눈에 띄게 만드세요. - * 설치 문서의 흐름을 개선합니다. - -* 개발자-문서 사이트 마이그레이션이 계속 진행 중이며, 이번 주에 30개 이상의 문서가 마이그레이션되었습니다. - -* 2024년 5월 23일 현재 AI 모니터링은 이후를 지원합니다. 이 중요한 업데이트를 반영하기 위해 여러 AI 모니터링 문서를 업데이트했습니다. - -### 사소한 변경 사항 - -* 링크 준수 보고서를 통해 [개인 정보 보호를 위한 클라우드 데이터 스토리지 보안 제어를](/docs/security/security-privacy/data-privacy/security-controls-privacy/#cloud-data-storage) 업데이트했습니다. -* [.NET yum 설치](/install/dotnet/installation/linuxInstall2/#yum) 단계를 간소화했습니다. -* 이제 끌어오기 3.12를 지원함을 보여주기 위해 [끌어오기 호환성](/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent/#basic) 문서를 업데이트했습니다. -* `Elastic.Clients.Elasticsearch` 버전 8.13.12 데이터스토어를 지원한다는 내용을 추가하여 [.NET 호환성을](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) 업데이트했습니다. -* [Node.js APM 에이전트 호환성이](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) 향상된 모듈 표를 업데이트했습니다. -* [AWS Privatelink에서](/docs/data-apis/custom-data/aws-privatelink) 지원하는 지역 및 영역 엔드포인트가 업데이트되었습니다. -* 인프라 에이전트는 이제 Ubuntu 24.04(Noble Numbat)를 지원하지만, 이 Ubuntu 버전에서는 인프라 플러스 로그를 아직 지원하지 않습니다. -* Windows 인증을 사용하여 [CyberARK와 Microsoft SQL Server를](/docs/infrastructure/host-integrations/installation/secrets-management/#cyberark-api) 사용하는 경우 사용자 이름 앞에 도메인을 추가해야 한다는 점을 명확히 했습니다. -* [.NET APM 에이전트 설정](/docs/apm/agents/net-agent/configuration/net-agent-configuration/#error-ignoreErrors) 에서 무시되는 상태 코드와 예상되는 상태 코드에 대한 환경 변수를 추가했습니다. -* [귀하의 차트를 사용하여](/docs/query-your-data/explore-query-data/use-charts/use-your-charts) KB, MB, GB, TB의 의미를 명확히 설명했습니다. (우리는 계산에 10의 거듭제곱을 사용하는 국제단위계를 사용합니다.) -* [이메일 설정](/docs/accounts/accounts/account-maintenance/account-email-settings) 에서 뉴렐릭 사용자 이메일 주소에 허용되는 문자와 제한을 명확히 했습니다. -* IAST 유효성 검사기 서비스 URL 엔드포인트를 [네트워크 뉴웰](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) 릭 텔레메트리 엔드포인트 테이블에 추가했습니다. -* [SNMP 성능 모니터링](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring) 에서 하나의 호스트에서 여러 SNMP 트랩 버전을 모니터링하는 방법에 대한 팁을 추가했습니다. -* [Node.js 측정, 계측을 확장하여 Apollo Server를 포함하려는](/docs/apm/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs/#extend-instrumentation) 경우 유용한 GitHub README에 대한 링크를 추가했습니다. -* [AI 모니터링 호환성 및 요구 사항](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#compatibility) 에 .NET 호환성 정보를 추가했습니다. - -### 릴리스 노트 및 새로운 소식 게시물 - -* [브라우저 에이전트 v1.260.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1) -* [인프라 에이전트 v1.52.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523) -* [자바 에이전트 v8.12.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120) -* [작업 관리자 v370](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-370) -* [Kubernetes 통합 v3.28.7](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7) -* [Android v5.18.0용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5180) -* [.NET 에이전트 v10.25.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0) -* [노드 API 런타임 v1.2.1](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.1) -* [노드 API 런타임 v1.2.58](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.58) -* [노드 API 런타임 v1.2.67](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.67) -* [노드 API 런타임 v1.2.72](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.72) -* [노드 API 런타임 v1.2.75](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.75) -* [노드 API 런타임 v1.2.8](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.8) -* [Node.js 에이전트 v11.17.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0) -* [PHP 에이전트 v10.21.0.11](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11) \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx deleted file mode 100644 index aa7ae9bf42e..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-06-28' -version: 'version: June 21-27, 2024' -translationType: machine ---- - -### 새로운 문서 - -* 모바일 모니터링의 기능 [무응답](/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding) 기능은 안드로이드가 5초 이상 차단된 시기와 이유를 추적하고 분석하는 데 도움이 됩니다. -* 새로운 브라우저 모니터링 [`log()`](/docs/browser/new-relic-browser/browser-apis/log) 및 [`wrapLogger()`](/docs/browser/new-relic-browser/browser-apis/wraplogger) API 문서는 이러한 새로운 측면포인트를 사용하는 방법에 대한 구문, 요구 사항, 모범 사례 및 예제를 정의합니다. - -### 주요 변경 사항 - -* 최상위 `Other capabilities` 카테고리를 제거하고 해당 카테고리에 있던 모든 내용을 더 적절한 카테고리로 이전했습니다. 모든 것이 제자리에 있으면 원하는 것을 더 쉽게 찾을 수 있습니다. -* 문서 사이트의 OpenTelemetry 수집기 예제를 `newrelic-opentelemetry-examples`]\([https://github.com/newrelic/newrelic-opentelemetry-examples](https://github.com/newrelic/newrelic-opentelemetry-examples))으로 옮겼습니다. GitHub 저장소를 통해 유지관리를 보다 쉽게 만들고 오픈 소스 가시성을 개선합니다. -* 우리의 AI 모니터링은 [NVIDIA NIM 모델을](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#deploy-at-scale) 지원하며 수동 또는 UI기반 설치 흐름 이외의 추가 설정이 필요하지 않습니다. 자세한 내용은 [NVIDIA NIM을 위한 AI 모니터링](https://newrelic.com/blog/how-to-relic/ai-monitoring-for-nvidia-nim) 블로그에서 확인하세요. - -### 사소한 변경 사항 - -* [FedRAMP 호환 엔드포인트](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#agents) 및 [네트워크](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) 에 IAST 검증 서비스 URL 엔드포인트를 추가했습니다. -* [IAST 문제 진단을 업데이트하여 특정 IP 범위를 화이트리스트/포함으로 해결합니다](/docs/iast/troubleshooting/#see-my-application). -* `NEW_RELIC_INSTRUMENTATION_AWS_SQS` 측정, 자동 로그 설정 정보로 자동 [루비 에이전트 설정이](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/#instrumentation-aws_sqs) 업데이트되었습니다. -* UI에서 이 작업을 수행할 수 있으므로 [모바일 모니터링 설정 구성](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings) 에서 `ApplicationExitInfo` 보고 구성 정보를 제거했습니다. -* [에스텔라우 강화 기능은](/docs/alerts/get-notified/incident-workflows/#enrichments) 여러 변수를 지원하므로 사용자의 요구 사항에 맞게 데이터를 더욱 구체적으로 사용자 지정할 수 있습니다. -* 데이터 사전에 [MobileApplicationExit](/attribute-dictionary/?dataSource=Mobile&event=MobileApplicationExit) 속성을 추가했습니다. 데이터 사전은 문서 리소스일 뿐만 아니라, 예를 들어 쿼리 빌더에서 NRQL 쿼리를 작성할 때 속성 정의를 UI에 직접 제공합니다. -* 오래된 알림 REST API와 관련된 문서를 제거했습니다. - -### 릴리스 노트 및 새로운 소식 게시물 - -* [뉴렐릭 AI 모니터링의 새로운 기능, 이제 NVIDIA NIM 감소 마이크로서비스와 통합됩니다.](/whats-new/2024/06/whats-new-06-24-nvidianim) - -* [합성 모니터에 영향을 미치지 않도록 새로운 합성 모니터 런타임에 대한 업데이트](/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm)의 새로운 기능 - -* [안드로이드 에이전트 v7.4.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-741) - * `ApplicationExitInfo` 기본적으로 보고가 활성화됨 - -* [브라우저 에이전트 v1.261.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0) - - * 향상된 확장성을 위해 객체로 전달된 로깅 API 인수 - * 기타 다양한 새로운 기능 및 버그 수정 - -* [진단 CLI(nrdiag) v3.2.7](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-327) - -* [Kubernetes 통합 v3.29.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0) - - * 1.29 및 1.30 지원 추가, 1.24 및 1.25 지원 삭제 - * 업데이트된 의존성/종속성: Kubernetes 패키지 v0.30.2 및 Arcin v3.20.1 - -* [iOS v6.5.0용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6050) - - * 워크로드의 일부인 모든 부분 보기 - * 대시보드 사용자 정의 옵션 추가 - * 기타 다양한 개선 사항 - -* [Node.js 에이전트 v11.20.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0) - - * Anthropic's Claude 3 메시지 API지원 - * 기타 다양한 개선 사항 - -* [Node.js 에이전트 v11.21.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0) - * ECS 메타데이터 API에서 컨테이너 ID 가져오기 지원 - -* [PHP 에이전트 v10.22.0.12](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12) - - * PHP 7.0 및 7.1에 대한 EOL 지원 - * 다양한 버그 수정 - -* [루비 에이전트 v9.11.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0) - - * `aws-sdk-sqs` gem에 대한 새 측정, 도구 - * 몇 가지 버그 수정 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index a5346391a9b..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### 새로운 문서 - -* 에이전트 버전 1.285.0 이상에서 향상된 문제 해결을 위한 세부 로깅, 네트워크 요청 모니터링, 검사 이벤트를 포함하여 [뉴렐릭 브라우저 에이전트 문제를 디버깅하는 방법](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/) 에 대한 새로운 기능이 추가되었습니다. -* `python` 및 `.node.js` 함수 모니터링에 대한 [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) 지원이 추가되었습니다. -* 컴퓨트 효율을 향상시키기 위해 실행 가능한 인사이트용 [컴퓨트 최적화 도구를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) 추가했으며, 비효율성을 식별하고 최적화 권장 사항을 제공하며 뉴렐릭 플랫폼에서 CCU 절감액을 추정하는 기능을 제공합니다. -* [클라우드 비용 인텔리전스](/docs/cci/getting-started/overview) 가 추가되어 포괄적인 비용 분석, Kubernetes 비용 할당, 미래 비용 추정, 계정 간 데이터 수집 등의 기능을 포함하여 cloud 비용의 가시성과 관리를 위한 도구를 제공하며 현재는 AWS 클라우드 비용만 지원합니다. -* Helm 차트를 통한 클러스터의 원활한 모니터링을 위해 [뉴렐릭 기능 제공자 독립적 통합이 포함된 Kubernetes 용OpenTelemetry 옵저버빌리티가](/docs/kubernetes-pixie/k8s-otel/intro/) 추가되었으며, 메트릭, 이벤트에 대한 텔메트리 신호가 향상되고 뉴렐릭 도구와 대시보드로 전송됩니다. -* [Windows 통합에 대한 제한 사항 및 문제 해결, 해결](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)추가 -* [CloudFormation 및 CloudWatch Metric Streams를](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/) 통해 AWS 통합을 추가하여 지원되지 않는 서비스에 대한 API 폴링을 지원합니다. -* MySQL 및 MS SQL Server용 온호스트 통합을 통해 데이터베이스 부분 모니터용 [뉴렐릭 데이터베이스 처리에 대한 향상된 태그를](/docs/infrastructure/host-integrations/db-entity-tags/) 추가하여 청구 또는 기존 텔레메트리에 영향을 주지 않고 메타데이터 인사이트 및 뉴렐릭 조직을 강화했습니다. - -### 주요 변경 사항 - -* [NRQL 참조](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/) 에 집계자 이외의 함수를 추가했습니다. -* [루비 에이전트 요구 사항을 업데이트하고 프레임워크를 지원했습니다](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/). -* [뉴렐릭 문서의OpenTelemetry 로그인에](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events) 뉴렐릭 커스텀 대시보드로 로그를 추가했습니다. -* [범용 Azure Functions에 대한 호환성 및 요구 사항](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes) 문서에서 Linux, Windows 및 컨테이너화된 함수에 대해 지원되는 런타임이 업데이트되었습니다. -* [Confluent 클라우드 통합에](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics) 대한 메트릭 데이터를 업데이트했습니다. -* [Node.js 에이전트 설정](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) 에서 GCP Cloud Run을 삭제했습니다. -* .NET 에이전트에서 지원하는 추가 라이브러리를 포함하도록 [AI 모니터링에 대한 호환성 및 요구 사항이](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) 업데이트되었습니다. -* [뉴렐릭 네트워크 트래픽](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) 에 뉴렐릭 플래메트리 듀얼 스택 엔드포인트를 추가했습니다. -* [Google Cloud Load Balancing 모니터링 통합](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/) 에 `GcpHttpExternalRegionalLoadBalancerSample` 추가했습니다. -* [신세틱스 작업 관리자 문서를 설치하는](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install) 방법에 대한 OpenShift 시작 절차를 추가했습니다. -* [Node.js 에이전트 버전 12를](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) 업데이트했습니다. -* [CloudFormation 및 CloudWatch Metric Streams활용한AWS ](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)용 원활한 통합을 추가했으며, API 폴링도 지원합니다. - -### 사소한 변경 사항 - -* [프로세서 트레이스](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/) 의 보존 기간으로 `Transaction` 추가했습니다. -* [알림 규칙 및 제한](/docs/alerts/admin/rules-limits-alerts/) 에 `Destination` 새 카테고리로 추가했습니다. -* [Azure Native 서비스 소개](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) 문서에 Azure 리소스의 진단 설정이 올바르게 구성되었는지 확인하거나 Azure Native 서비스를 통한 전달을 비활성화하여 데이터가 Azure Native 플랫폼으로 전송되지 않도록 하는 콜아웃을 추가했습니다. -* [.NET 에이전트](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) 에 대한 최신 호환 라이브러리를 업데이트했습니다. -* iOS SDK 버전 7.5.4부터 시작되는 내용을 알리기 위해 [iOS 에이전트 릴리스 노트](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) 문서에 콜아웃을 추가했습니다. 이제 변경 사항으로 인해 이전에 억제되었던 처리된 예외 이벤트가 보고됩니다. -* Kubernetes 환경에 대한 리소스 속성 및Kubernetes 가 아닌 환경에 대한 `container.id` 지정에 대한 서비스-컨테이너 관계에 대한 요구 사항을 업데이트하여 [뉴렐릭에서OpenTelemetry 리소스](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/) 에 대한 적절한 텔레메트리 설정을 보장합니다. -* [특정 구현 에이전트](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions) 버전 설치에 대한 CLI 지원이 추가되어 일관된 구현, 배포 및 시스템 호환성이 가능해졌습니다. 레시피 이름에 `@X.XX.X` 사용하여 버전을 지정합니다. -* UI 에서 **Manage Account Cardinality**, **Manage Indicator Cardinality**, **Create Pruning Rules** 기능을 사용하기 위한 역할 액세스 요구 사항을 강조하는 콜아웃을 추가했습니다. [Cardinality Management](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table) 에서 권한이 설정되어 있는지 확인하세요. -* [Node.js 에이전트의 호환성 및 요구 사항을](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) `v12.23.0` 으로 업데이트했습니다. -* [Elasticsearch를](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration) 설정하는 데 필요한 최소 권한을 추가했습니다. -* [NRQL 공지 구문](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/) 에 대한 `FACET` 속성 최대 허용 제한 사용 값을 5000에서 20000으로 업데이트했습니다. - -### 릴리즈 정보 - -* [`SystemSample`, `ProcessSample`, `NetworkSample` 및 `StorageSample`의 인프라 이벤트를 타겟으로 하는 삭제 규칙](/eol/2025/05/drop-rule-filter/)의 수명 종료 날짜로 2026년 1월 7일을 발표함 - -* [공지 조건의 messageId 및 타임스탬프에 대한 FACET](/eol/2025/07/deprecating-alert-conditions/) 의 수명 종료가 즉시 발효됩니다. - -* 2025년 10월 28일을 [Attention Required](/eol/2025/07/upcoming-eols/) 의 수명 종료일로 발표했습니다. - -* 새로운 소식 게시물을 확인하세요. - - * [Microsoft Teams에 직접 공지 보내기](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [뉴렐릭 컴퓨팅 Optimizer가 정식 출시되었습니다!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [통합 쿼리 탐색기에서 계정 간 쿼리 로그](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [OpenTelemetry를 활용한 Kubernetes 모니터링이 정식 출시되었습니다!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [Kubernetes용 Windows 노드 모니터링이 이제 공개 미리 보기로 제공됩니다.](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [성능 문제 정확히 파악: 페이지 뷰 및 Core Web Vitals에 대한 고급 필터링](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [이제 최신 오류별로 정렬할 수 있습니다.](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [귀하의 브라우저 데이터, 귀하의 이용 약관: 새로운 제어 옵션](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [데이터베이스에 대한 심층 쿼리 분석이 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [NRQL 프리딕션 및 예측 경보가 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [APM + OpenTelemetry Convergence GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [GitHub Copilot 및 ServiceNow용 Agentic 통합이 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* 최신 릴리스에 대한 최신 정보를 받아보세요. - - * [노드 API 런타임 v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * 취약점 문제가 해결되었습니다. - - * [Ping 런타임 v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * ping 런타임에 대한 logback-core 취약점이 수정되었습니다. - * ping 런타임에 대한 jetty-server 취약점이 수정되었습니다. - * ping 런타임에 대한 Ubuntu 취약점이 수정되었습니다. - - * [브라우저 에이전트 v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * `BrowserInteraction` 및 `previousUrl` 정의를 업데이트합니다. - * 추가 검사 이벤트를 추가했습니다. - * `finished` API `timeSinceLoad` 값이 고정되었습니다. - - * [Kubernetes 통합 v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * 향후 플랫폼 호환성을 위해 백앤드 및 CI 관련 내부 조정을 수정했습니다. - - * [작업 관리자 v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * 일부 모니터에서 실행 시간이 길어서 일부 고객이 결과를 볼 수 없었던 문제를 해결했습니다. - - * [파이썬 에이전트 v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * `Azure Function Apps` 에 대한 지원이 추가되었습니다. - * `protobuf v6` 지원을 활성화하기 위해 `pb2` 파일을 수정했습니다. - - * [안드로이드 에이전트 v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * 로그를 보고할 때 ANR을 해결하는 성능이 향상되었습니다. - * 애플리케이션을 종료한 후에도 로그 보고를 계속하도록 문제를 해결했습니다. - * 애플리케이션 상태 모니터링 및 데이터 전송과 관련된 문제가 해결되었습니다. - * strictmode를 켜면 몇 가지 위반 사항이 개선되었습니다. - - * [Kubernetes 통합 v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * `golang.org/x/crypto` `v0.39.0` 로 업데이트했습니다. - * `go` `v1.24.4` 로 업데이트했습니다. - - * [.NET 에이전트 v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Azure Service Bus에 대한 지원이 추가되었습니다. - * 최신 VS에서 발생한 프로필러 빌드 오류를 수정했습니다. - - * [PHP 에이전트 v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * PHP 애플리케이션에서 사용하는 패키지를 감지하기 위해 기본적으로 사용되는 Composer 런타임 API를 추가했습니다. - * Composer 런타임 API에서 정의되지 않은 동작이 수정되었습니다. - - * [노드 브라우저 런타임 v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * 크롬 131에 대한 크롬 빌더 옵션이 업데이트되었습니다. - - * [iOS v6.9.8용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * 더욱 견고하고 안정적인 소켓 연결로 Ask AI 기능을 향상시켜 원활한 경험을 보장합니다. - - * [Android v5.29.7용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * 더욱 견고하고 안정적인 소켓 연결로 Ask AI 기능을 향상시켜 원활한 경험을 보장합니다. - - * [Node.js 에이전트 v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * `openai` v5 스트리밍 지원이 추가되었습니다. - * `openai.responses.create` API에 대한 지원이 추가되었습니다. - * 정의되지 않은 tracestate 헤더에 대한 오류 로깅이 수정되었습니다. - - * [인프라 에이전트 v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * 의존성/종속성 `newrelic/nri-winservices` 을(를) 다음으로 업데이트했습니다. `v1.2.0` - * 알파인 도커 태그가 업데이트되었습니다. `v3.22` - - * [인프라 에이전트 v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * 의존성/종속성 `newrelic/nri-flex` 을(를) 다음으로 업데이트하세요. `v1.16.6` - - * [브라우저 에이전트 v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * 사용자 정의 속성 경쟁 조건 우선 순위를 수정했습니다. - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * OTEL 베타 코어를 범프했습니다. `v0.128.0` - - * [HTML5.JS v3.0.0용 미디어 에이전트](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * 새로운 이벤트 유형을 도입했습니다. - * `PageAction` 이벤트 유형이 더 이상 사용되지 않습니다. - - * [HTML5.JS v3.1.1용 미디어 에이전트](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * 패키지에 대한 npm 게시를 활성화하여 쉬운 접근성과 배포를 보장했습니다. - * CommonJS, ES 모듈 및 UMD 모듈 형식과의 호환성을 보장하기 위해 `dist` 폴더에 `cjs`, `esm` 및 `umd` 빌드를 추가했습니다. - - * [Roku v4.0.0용 미디어 에이전트](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * 새로운 이벤트 유형을 도입했습니다. - * `RokuVideo` 이벤트 유형이 더 이상 사용되지 않습니다. - * `RokuSystem` 이벤트 유형이 더 이상 사용되지 않습니다. - - * [Roku v4.0.1용 미디어 에이전트](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * `errorName` 더 이상 사용되지 않으므로 `errorName` 의 이름이 `errorMessage` 로 변경되었습니다. - - * [작업 관리자 v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * `ubuntu 22.04` 에서 고정 기본 이미지 업그레이드 `ubuntu 24.4` - - * [핑 런타임 v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * `ubuntu 22.04` 에서 기본 이미지 업그레이드가 개선되었습니다. `ubuntu 24.04` - - * [Kubernetes 통합 v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * 쿠버네티스 클러스터에 Windows 노드 모니터링 지원이 추가되었습니다. - - * [Android v5.29.8용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * 버그를 수정하고 UI를 개선하여 더욱 원활한 경험을 제공했습니다. - - * [Node.js 에이전트 v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * 진입 및 종료 기간에 대해서만 보고하는 기능이 추가되었습니다. - * Node.js 24 지원이 추가되었습니다. - * 호환성 보고서가 업데이트되었습니다. - - * [노드 API 런타임 v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * 취약점을 수정했습니다. `CVE-2024-39249` - - * [iOS v6.9.9용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * 동적 프롬프트를 통해 AI 질문 기능을 향상시켰습니다. - - * [브라우저 에이전트 v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * **긴 작업** 내부 메시지를 추가했습니다. - * 내보내기 트레이스가 비활성화되지 않도록 하는 문제를 해결했습니다. - - * [노드 브라우저 런타임 v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * 업그레이드된 기본 이미지 - - * [자바 에이전트 v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Azure App Services에 대한 연결된 메타데이터입니다. - * `MonoFlatMapMain` 측정, 로그를 삭제했습니다. - - * [Node.js 에이전트 v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * 구성 가능한 속성 값 크기 제한을 구현했습니다. - * 호환성 보고서가 업데이트되었습니다. - - * [Kubernetes 통합 v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * kube-state-Metric 차트 버전을 `5.12.1` 에서 업데이트합니다. `5.30.1` - - * [iOS 에이전트 v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * 세션 시작 시 분산 추적에 필요한 모든 계정 정보가 포함되지 않는 문제를 해결했습니다. - - * [Android v5.29.9용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * 동적 UI 렌더링으로 피드백을 향상시켰습니다. - - * [Android v5.30.0용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * 버그를 수정하고 Teams GA 플래그를 업데이트하여 사용자 경험을 개선했습니다. - - * [Go 에이전트 v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * 교착 상태 버그로 인해 활용도가 되돌려졌습니다. v3.39.0 릴리스로 돌아갑니다. - * go 모듈에 직접 의존성/종속성을 추가한 awssupport\_test.go 테스트를 제거했습니다. - - * [플러터 에이전트 v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * 네이티브 안드로이드 에이전트가 7.6.7 버전으로 업데이트되었습니다. - * 네이티브 iOS 에이전트가 7.5.6 버전으로 업데이트되어 개선되었습니다. - - * [Node.js 에이전트 v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Node.js 18에 대한 지원이 중단되었습니다. - * `fastify` 에 대한 최소 지원 버전을 3.0.0으로 업데이트했습니다. `pino` 에서 8.0.0으로, `koa-router` 에서 12.0.0으로 - - * [브라우저 에이전트 v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * 고정 보고서가 비어 있는 previousUrl을 정의되지 않은 것으로 표시했습니다. - - * [인프라 에이전트 v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * 의존성/종속성 `newrelic/nri-prometheus` 을 v2.26.2로 업데이트했습니다. - - * [iOS v6.9.10용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * 동적 UI 렌더링으로 피드백을 향상시켰습니다. - - * [안드로이드 NDK 에이전트 v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * 16KB 페이지 크기에 대한 지원이 추가되었습니다. - - * [인프라 에이전트 v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Windows 프로세스 핸들이 변경되었습니다. - * `nri-docker` `v2.5.1` 로, `nri-prometheus` 로 올렸습니다. `v2.26.1` - - * [.NET 에이전트 v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Azure Service Bus에 대한 항목 지원이 추가되었습니다. - - * [Node.js 에이전트 v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * 수정된 리소스입니다. AWS Bedrock Converse API - - * [Node.js 에이전트 v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * 구성 가능한 속성 값 크기 제한을 구현했습니다. - * 업데이트된 호환성 보고서 - - * [진단 CLI(nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * `/lib64/libc.so.6: version 'GLIBC_2.34'` 찾을 수 없음과 같은 GLIBC 관련 오류가 해결되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx deleted file mode 100644 index bd0e522d4ce..00000000000 --- a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-11-13' -version: 1.303.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Allow consent API to be invoked without localStorage access - - Allow nested registrations - - Additional validation to prepare agent for MFE registrations - - Add measure support to register API - - Add useConsentModel functionality - - Retry initial connect call - - Add custom event support to register API - - SMs for browser connect response -bugs: - - Obfuscate custom attributes for logs added after PVE - - memoize promise context propagation to avoid safari hangs -security: [] -translationType: machine ---- - -## v1.303.0 - -### 특징 - -#### localStorage 액세스 없이 동의 API를 호출하도록 허용 - -수집을 제어하는 에이전트에서 공통 상태를 유지함으로써 localStorage 액세스가 필요 없이 동의 API가 작동할 수 있도록 합니다. localStorage 액세스가 차단되면 애플리케이션은 모든 하드 페이지 로드 시 API를 호출해야 합니다. - -#### 중첩된 등록 허용 - -계획된 등록 API 사용하여 내재적인 부모-자식 관계를 용이하게 하려면 등록된가 해당의 자식이 등록할 수 있는 자체 `.register()` API 노출하도록 허용하세요. 컨테이너 에이전트에 등록한 사람은 컨테이너와 관련이 있습니다. 다른 등록된 부분에 속하는 부분은 해당 부분뿐만 아니라 상위 부분에도 관련됩니다. - -#### MFE 등록을 위한 에이전트 준비를 위한 추가 검증 - -MFE/v2 등록을 지원하는 목표 `id` 및 `name` 에 대한 잘못된 값을 방지하기 위해 에이전트에 유효성 검사 규칙을 추가합니다. - -#### API 등록에 측정 지원 추가 - -등록 응답 개체에서 측정 API에 대한 지원을 추가합니다. 이는 향후 계획된 마이크로 프론트엔드 제공을 지원하기 위한 것입니다. - -#### useConsentModel 기능 추가 - -use\_consent\_mode init 속성과 기능을 추가합니다. consent() API 호출을 추가합니다. 동의 모델이 활성화된 경우, consent() API 호출을 통해 동의가 제공되지 않는 한 에이전트 수집이 허용되지 않습니다. - -#### 초기 연결 호출을 다시 시도하세요 - -데이터 손실을 방지하기 위해 이제 에이전트는 재시도 가능한 상태 코드에 대해 원래 "RUM" 호출을 추가 시간 동안 재시도합니다. - -#### API등록을 위한 맞춤형 대시보드 지원 추가 - -MFE 지원이 확립되면 나중에 사용할 수 있도록 사용자 정의 대시보드를 캡처하는 방법을 등록 API 에 추가합니다. - -#### 브라우저 연결 응답을 위한 SMS - -page\_view\_event 집계를 초기화할 때 실패한 응답에 대한 지원 가능성 메트릭을 추가합니다. - -### 버그 수정 - -#### PVE 이후에 추가된 로그인에 대한 난독화 사용자 정의 속성 - -난독화를 확장하여 초기 RUM/PageViewEvent 수집 후 추가된 로깅 이벤트에 대한 사용자 지정 속성을 처리합니다. - -#### Safari 중단을 방지하기 위해 메모라이즈 약속 컨텍스트 전파 - -Safari에서 반복되는 컨텍스트 작업을 피함으로써 잠재적인 브라우저 중단을 방지하기 위해 약속 컨텍스트 전파를 메모화합니다. - -## 지지 성명 - -뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. - -새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. - -[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.303.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 131-141, Edge 131-141, Safari 17-26, Firefox 134-144. 모바일 장치의 경우 v1.303.0이 Android OS 16 및 iOS Safari 17-26용으로 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx deleted file mode 100644 index 6973fb0305e..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-11-17' -version: rc1.3 -translationType: machine ---- - -### 개량 - -* Chrome 브라우저를 142로 업그레이드했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx deleted file mode 100644 index 6d8c01e6212..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-11-12' -version: 1.58.0 -translationType: machine ---- - -### 개량 - -Ping 런타임의 보안 문제를 해결하기 위해 Ubuntu와 Java에 관련된 취약점을 수정했습니다. 아래는 수정된 Java CVE입니다. - -* CVE-2025-5115 -* CVE-2025-11226 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx deleted file mode 100644 index b9438fd5629..00000000000 --- a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ /dev/null @@ -1,652 +0,0 @@ ---- -title: 커뮤니케이션 작업 -tags: - - workflow automation - - workflow - - workflow automation actions - - communication actions - - slack actions - - ms teams actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - 이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다! - - 이 기능은 현재 [출시 전 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy) 에 따라 미리보기 프로그램의 일부로 제공됩니다. - - -이 페이지에서는 fl.flo 자동화 작업 카탈로그에서 사용 가능한 통신 작업에 대한 포괄적인 참조를 제공합니다. 이러한 작업을 통해 Slack 채널에 메시지를 보내고, 반응을 검색하는 등 커뮤니케이션 플랫폼을 팰팍우 정의에 통합할 수 있습니다. - -## 전제 조건 - -블리자드 자동화에서 통신 작업을 사용하기 전에 다음 사항이 있는지 확인하세요. - -* 적절한 권한이 있는 Slack 작업 공간. -* 흐름 자동화에서 비밀로 구성된 Slack 봇의 의미입니다. -* 메시지를 보내고 싶은 Slack 채널에 접속합니다. - -Slack 통합을 설정하는 방법에 대한 자세한 내용은 [Slack 구성 추가를](/docs/autoflow/overview#add-the-slack-integration) 참조하세요. - -## 슬랙 동작 - - - - 선택적으로 파일을 첨부하여 Slack 채널로 메시지를 보냅니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 예시 -
- **토큰** - - 필수의 - - 비밀 - - `${{ :secrets:slackToken }}` -
- **채널** - - 필수의 - - 끈 - - `my-slack-channel` -
- **텍스트** - - 필수의 - - 끈 - - `Hello World!` -
- **스레드** - - 선택 과목 - - 끈 - - `.` -
- **부착** - - 선택 과목 - - 지도 - -
- **첨부 파일 이름** - - 필수의 - - 끈 - - `file.txt` -
- **첨부 파일.내용** - - 필수의 - - 끈 - - `Hello\nWorld!` -
- - - * **token**: 사용할 Slack 봇 토큰입니다. 이것은 비밀 구문으로 전달되어야 합니다. 토큰을 설정하는 방법에 대한 지침은 [Slack 구성 추가](/docs/autoflow/overview#add-the-slack-integration) 를 참조하세요. - * **channel**: 메시지를 보낼 채널의 이름 또는 채널ID입니다. 자세한 내용은 [Slack API를](https://api.slack.com/methods/chat.postMessage#arg_channel/) 참조하세요. - * **text**: 지정된 `channel` 에 Slack에 게시할 메시지입니다. - * **threadTs**: 부모 메시지에 속하는 타임스탬프로, 스레드에서 메시지 회신을 생성하는 데 사용됩니다. - * **attachment**: 지정된 `channel` 에 메시지가 포함된 파일을 첨부할 수 있습니다. - * **attachment.filename**: Slack에 업로드된 파일의 파일 이름을 지정합니다. - * **attachment.content**: 업로드할 파일의 내용은 UTF8입니다. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **스레드** - - 끈 - - `.` -
- **채널ID** - - 끈 - - `` -
- - - * **threadTs**: 메시지의 타임스탬프. 스레드에 답변을 게시하기 위해 향후 postMessage 호출에 사용될 수 있습니다. - * **channelID**: 메시지가 게시된 채널의 ID입니다. - - - - - **예 1: Slack 채널에 메시지 게시** - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: SendMessage - - steps: - - name: send_slack_message - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: ${{ .workflowInputs.channel }} - text: ${{ .workflowInputs.text }} - ``` - - **예상 입력:** - - ```json - { - "inputs": [ - { - "key" : "channel", - "value" : "my-channel" - }, - { - "key" : "text", - "value" : "This is my message *with bold text* and `code backticks`" - } - ] - } - ``` - - **예상 출력:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - **예 2: 파일 첨부** - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: SendFileMessage - - steps: - - name: postCsv - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel - text: "Please find the attached file:" - attachment: - filename: 'file.txt' - content: "Hello\nWorld!" - ``` - - **예상 출력:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - - - - - - - - Slack 채널에서 메시지에 대한 반응을 받아보세요. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 예시 -
- **토큰** - - 필수의 - - 비밀 - - `${{ :secrets:slackToken }}` -
- **채널ID** - - 필수의 - - 끈 - - `C063JK1RHN1` -
- **시간 초과** - - 선택 과목 - - 정수 - - 60 -
- **스레드** - - 필수의 - - 끈 - - `.` -
- **선택기** - - 선택 과목 - - 목록 - - `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` -
- - - * **token**: 사용할 Slack 봇 토큰입니다. 이것은 비밀 구문으로 전달되어야 합니다. 토큰을 설정하는 방법에 대한 지침은 [Slack 구성 추가](/docs/autoflow/overview#add-the-slack-integration) 를 참조하세요. - * **channelID**: 메시지 반응을 얻기 위한 channelID입니다. - * **timeout**: 반응을 기다리는 시간(초)입니다. 기본값은 60초이고, 최대 허용 시간은 600초(10분)입니다. - * **threadTs**: 메시지에 속한 타임스탬프로, 해당 메시지에 대한 반응을 얻는 데 사용됩니다. - * **selectors**: 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **반응** - - 목록 - - `` -
- - - * **reactions**: 캡처된 모든 반응이 포함된 요소 목록이거나 시간 초과가 발생한 경우 비어 있는 목록입니다. - - - - - **예 1: Slack에서 반응 얻기** - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: GetReactions - - steps: - - name: getReactions - type: action - action: slack.chat.getReactions - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channelID: ${{ .steps.promptUser.outputs.channelID }} - threadTs: ${{ .steps.promptUser.outputs.threadTs }} - timeout: ${{ .workflowInputs.timeout }} - selectors: ${{ .workflowInputs.selectors }} - ``` - - **예상 입력:** - - ```json - { - "inputs": [ - { - "key" : "channelID", - "value" : "C063JK1RHN1" - }, - { - "key" : "threadTs", - "value" : "1718897637.400609" - }, - { - "key" : "selectors", - "value" : "[{\"name\": \"reactions\", \"expression\": \".reactions \"}]" - } - ] - } - ``` - - **예상 출력:** - - ```json - [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } - ] - ``` - - 또는 시간이 초과된 경우: - - ```json - [] - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index 7837ce4850c..00000000000 --- a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,1043 +0,0 @@ ---- -title: HTTP 동작 -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: A list of available HTTP actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - 이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다! - - 이 기능은 현재 [출시 전 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy) 에 따라 미리보기 프로그램의 일부로 제공됩니다. - - -이 페이지에서는 fl.flo 자동화 작업 카탈로그에서 사용할 수 있는 HTTP 작업에 대한 포괄적인 참조를 제공합니다. 이러한 작업을 통해 폴리스우 정의의 일부로 외부 API 및 서비스에 대한 HTTP requests (GET, POST, PUT, DELETE)을 수행할 수 있습니다. - -## 전제 조건 - -블리자드 자동화에서 HTTP 작업을 사용하기 전에 다음 사항이 있는지 확인하세요. - -* 부채, 목표 API 포인트 포인트 URL. -* 필요한 인증 자격 증명(API 키, 토큰 등) -* API 요청/응답 형식에 대한 이해. - - - HTTP 액션은 모든 헤더 값에 대해 비밀 구문을 지원하므로 API 키와 같은 민감한 데이터를 안전하게 전달할 수 있습니다. 자세한 내용은 [비밀 관리를](/docs/infrastructure/host-integrations/installation/secrets-management/) 참조하세요. - - -## HTTP 동작 - - - - API 엔드포인트에서 데이터를 검색하려면 HTTP GET 호출을 수행합니다. - - - 이는 모든 헤더 값에 대한 비밀 구문을 지원합니다. - - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 설명 -
- **URL** - - 필수의 - - 문자열 - - 요청에 대한 타겟 URL입니다. 계획에는 다음이 포함되어야 합니다. - - `https://example.com` -
- **url 매개변수** - - 선택 과목 - - 지도 - - URL에 추가하려면 쿼리를 수행해야 합니다. 문자열화된 JSON 객체를 사용합니다. -
- **헤더** - - 선택 과목 - - 지도 - - 요청에 추가할 헤더입니다. 문자열화된 JSON 객체를 사용합니다. -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 음색만 출력으로 가져오는 선택기입니다. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 설명 -
- **응답 본문** - - 문자열 - - 응답의 본문. -
- **상태 코드** - - 정수 - - 응답의 HTTP 상태 코드입니다. -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **입력 예시:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **출력 예시:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - API 엔드포인트에 데이터를 전송하기 위해 HTTP POST 호출을 수행합니다. - - - 이는 모든 헤더 값에 대한 비밀 구문을 지원합니다. - - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 설명 -
- **URL** - - 필수의 - - 문자열 - - 요청에 대한 타겟 URL입니다. 계획에는 다음이 포함되어야 합니다. - - `https://example.com` -
- **url 매개변수** - - 선택 과목 - - 지도 - - URL에 추가하려면 쿼리를 수행해야 합니다. 문자열화된 JSON 객체를 사용합니다. -
- **헤더** - - 선택 과목 - - 지도 - - 요청에 추가할 헤더입니다. 문자열화된 JSON 객체를 사용합니다. -
- **몸** - - 선택 과목 - - 문자열 - - 요청 본문. -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 음색만 출력으로 가져오는 선택기입니다. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 설명 -
- **응답 본문** - - 문자열 - - 응답의 본문. -
- **상태 코드** - - 정수 - - 응답의 HTTP 상태 코드입니다. -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **입력 예시:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **출력 예시:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - API 엔드포인트에서 데이터를 업데이트하기 위해 HTTP PUT 요청을 수행합니다. - - - 예를 들어 `Api-Key` 헤더와 같이 민감한 데이터를 입력에 전달해야 하는 경우 [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph 뮤테이션을 통해 저장된 값을 사용할 수 있습니다. - - 예시: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 설명 -
- **URL** - - 필수의 - - 문자열 - - 요청에 대한 타겟 URL입니다. URL에는 스키마(예: https:// 또는 http://)가 포함되어야 합니다. 예: - - `https://example.com` -
- **url 매개변수** - - 선택 과목 - - 지도 - - URL에 추가하려면 쿼리를 수행해야 합니다. 문자열화된 JSON 객체를 사용합니다. -
- **헤더** - - 선택 과목 - - 지도 - - 요청에 추가할 헤더입니다. 문자열화된 JSON 객체를 사용합니다. -
- **몸** - - 선택 과목 - - 문자열 - - 요청 본문. -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 음색만 출력으로 가져오는 선택기입니다. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 설명 -
- **응답 본문** - - 문자열 - - 응답의 본문. -
- **상태 코드** - - 정수 - - 응답의 HTTP 상태 코드입니다. -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **입력 예시:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **출력 예시:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - API 엔드포인트에서 데이터를 제거하기 위해 HTTP DELETE 요청을 수행합니다. - - - 예를 들어 `Api-Key` 헤더와 같이 민감한 데이터를 입력에 전달해야 하는 경우 [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) NerdGraph 뮤테이션을 통해 저장된 값을 사용할 수 있습니다. - - 예시: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 설명 -
- **URL** - - 필수의 - - 문자열 - - 요청에 대한 타겟 URL입니다. URL에는 스키마(예: https:// 또는 http://)가 포함되어야 합니다. 예: - - `https://example.com` -
- **url 매개변수** - - 선택 과목 - - 지도 - - URL에 추가하려면 쿼리를 수행해야 합니다. 문자열화된 JSON 객체를 사용합니다. -
- **헤더** - - 선택 과목 - - 지도 - - 요청에 추가할 헤더입니다. 문자열화된 JSON 객체를 사용합니다. -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 음색만 출력으로 가져오는 선택기입니다. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 설명 -
- **응답 본문** - - 문자열 - - 응답의 본문. -
- **상태 코드** - - 정수 - - 응답의 HTTP 상태 코드입니다. -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **입력 예시:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **출력 예시:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx deleted file mode 100644 index 98fdfc4ce4f..00000000000 --- a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ /dev/null @@ -1,1900 +0,0 @@ ---- -title: 뉴렐릭 액션 -tags: - - workflow automation - - workflow - - workflow automation actions - - New relic actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - 이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다! - - 이 기능은 현재 [출시 전 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy) 에 따라 미리보기 프로그램의 일부로 제공됩니다. - - -이 페이지는 폴리스우 자동화 작업 카탈로그에서 사용할 수 있는 뉴렐릭 작업에 대한 포괄적인 참조를 제공합니다. 이러한 작업을 사용하면 커스텀 대시보드 및 로그 보내기, NerdGraph 쿼리 실행, NRQL 쿼리 실행, 공지 보내기 등의 워크플로우 정의에 워크플로우 정의에 통합할 수 있습니다. - -## 전제 조건 - -블로우 자동화에서 뉴렐릭 작업을 사용하기 전에 다음 사항이 있는지 확인하세요. - -* 적절한 권한이 있는 뉴렐릭 계정. -* 뉴렐릭 클러스터 키(데이터를 다른 계정으로 보내는 경우). -* 사용하려는 특정 뉴렐릭 서비스에 필요한 권한입니다. - -블루렐릭 계정 키를 생성하고 관리하는 방법에 대한 자세한 내용은 [볼륨 키를](/docs/apis/intro-apis/new-relic-api-keys/#license-key) 참조하세요. - -## 데이터 수집 작업 - - - - 사용자 정의 대시보드를 뉴렐릭에게 보냅니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 예시 -
- **속성** - - 선택 과목 - - 지도 - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **이벤트** - - 필수의 - - 목록 - - `"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]` -
- **라이센스 키** - - 선택 과목 - - 끈 - - `"{{ .secrets.secretName }}"` -
- **선택기** - - 선택 과목 - - 목록 - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: 제공되는 경우 모든 이벤트에 포함되는 공통 속성입니다. 필요한 경우 각 이벤트 항목을 병합하면 이벤트 항목이 일반적인 정의를 재정의합니다. - * **events**: 이벤트 데이터 목록입니다. 이벤트에는 사용자 정의 대시보드 유형을 나타내는 `eventType` 필드를 사용해야 하며 요청당 허용되는 최대 이벤트는 100개입니다. - * **LicenseKey**: 이벤트가 전송되는 구간, 목표 계정을 지정하는 뉴렐릭 계정 볼륨 키입니다. 이 값을 제공하지 않을 경우, 해당 워크플로우를 실행하는 계정을 기준으로 기본 볼륨 키를 가정합니다. - * **selectors**: 지정된 소스만 출력으로 가져오는 선택기입니다. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **성공** - - 부울 - - `true` -
- **오류 메시지** - - 끈 - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **예상 출력:** - - ```yaml - { - "success": true - } - ``` - - **이벤트 검색:** - - 워크플로우를 성공적으로 실행한 후 해당 이벤트를 실행한 계정에서 쿼리를 실행하면 관련 이벤트를 검색할 수 있습니다. - - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - New Relic에 로그 보내기 - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 유형 - - 예시 -
- **속성** - - 선택 과목 - - 지도 - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **로그** - - 필수의 - - 목록 - - `"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"` -
- **라이센스 키** - - 선택 과목 - - 끈 - - `"{{ .secrets.secretName }}"` -
- **선택기** - - 선택 과목 - - 목록 - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: 제공되는 경우 모든 로그에 포함되는 공통 속성입니다. 로그 항목이 동일한 속성을 지정하는 경우 일반적인 정의가 재정의됩니다. - * **logs**: 로그인 데이터 목록입니다. 요청당 허용되는 최대 로그 수는 100개입니다. - * **LicenseKey**: 로그가 전송되는 구간, 주요 계정을 지정하는 뉴렐릭 계정 볼륨 키입니다. 제공하지 않을 경우, 해당 워크플로우를 실행하는 계정을 기준으로 기본 볼륨 키를 가정합니다. 자세한 내용은 [라이선스 키를](/docs/apis/intro-apis/new-relic-api-keys/#license-key) 참조하세요. - * **selectors**: 지정된 소스만 출력으로 가져오는 선택기입니다. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **성공** - - 부울 - - `true` -
- **오류 메시지** - - 끈 - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **예상 출력:** - - ```yaml - { - "success": true - } - ``` - - **로그 검색:** - - 워크플로우를 성공적으로 실행한 후 해당 로그플로우를 실행한 계정에서 쿼리를 실행하여 관련 로그플로우를 검색할 수 있습니다. - - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## NerdGraph 작업 - - - - newrelic NerdGraph API에 대해 Graphql 명령을 실행합니다. 명령은 쿼리이거나 뮤테이션일 수 있습니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 유형 - - 설명 - - 예시 -
- **그래프QL** - - 필수의 - - 끈 - - GraphQL 구문. 명령을 빌드하고 테스트하려면 GraphiQL을 사용해야 합니다. - -
- **변수** - - 필수의 - - map[string]any - - GraphQL 명령문과 함께 사용할 핵심 가치 쌍 변수입니다. - -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - ```yaml - steps: - - name: findingVar - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query GetEntity($entityGuid: EntityGuid!) { - actor { - entity(guid: $entityGuid) { - alertSeverity - } - } - } - variables: - entityGuid: ${{ .workflowInputs.entityGuid }} - - name: findingInline - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - { - actor { - entity(guid: "${{ .workflowInputs.entityGuid }}") { - alertSeverity - } - } - } - selectors: - - name: entities - expression: '.data' - ``` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 산출 - - 유형 - - 설명 -
- **data** - - map[string]any - - NerdGraph 응답의 - - `data` - - 속성 내용입니다. -
- **성공** - - 부울 - - Status of the request.s -
- **오류 메시지** - - 문자열 - - 실패 이유를 메시지로 전달합니다. -
- - - - - - - - - - - - - - - -
- 예시 -
- ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - -## 쿼리 작업 - - - - NerdGraph API를 통해 교차 계정 NRQL 쿼리를 실행합니다. - - - - - 입력 - - - - 출력 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 유형 - - 설명 - - 예시 -
- **질문** - - 필수의 - - 끈 - - NRQL 쿼리 문. - -
- **계정 ID** - - 선택 과목 - - int 목록 - - **New Relic Account ID** - - \[뉴렐릭 계정 ID] 입력은 쿼리가 실행되는 퀴, 목표 계정을 지정할 수 있는 롤리, 목표 ID 목록입니다. 이 값을 입력으로 제공하지 않으면 쿼리는 자동으로 RPG우의 실행 계정과 연결된 계정에 대해 실행됩니다. - -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - - - - -
- 산출 - - 유형 - - 예시 -
- **results** - - : 쿼리 결과를 포함하는 객체의 목록입니다. - - - - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - -## 공지사항 - - - - 예를 들어 Slack과 같은 대상과 통합된 채널로 메시지를 보냅니다. - - - - - 입력 - - - - 출력 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 유형 - - 설명 - - 예시 -
- **유형** - - 필수의 - - 끈 - - Newrelic 목적지 유형 - - `slack` -
- **목적지 ID** - - 필수의 - - 문자열 - - Newrelic 대상과 연관된 DestinationId입니다. - - `123e4567-e89b-12d3-a456-426614174000` -
- **매개변수** - - 필수의 - - 지도 - - 선택한 대상 유형으로 공지를 보내는 데 필요한 필드입니다. - - `{\"channel\": \"${{ YOUR_CHANNEL }}\", \"text\": \"Enter your text here\"}` -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - -
- 산출 - - 유형 - - 예시 -
- 성공 - - 부울 - - `true/false` -
- - - - - - - - - 목적지와 통합된 MS 팀 채널로 메시지를 보냅니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 데이터 유형 - - 설명 - - 예시 -
- **목적지 ID** - - 필수의 - - 문자열 - - Newrelic 대상과 연관된 DestinationId입니다. - - 새 대상을 구성하고 대상 ID를 나열하는 방법에 대한 단계는 [Microsoft Teams용 뉴렐릭 통합을](/docs/alerts/get-notified/microsoft-teams-integrations/) 참조하세요. - - 목적지에 대한 자세한 내용을 알아보려면 [목적지를](/docs/alerts/get-notified/destinations/) 참조하세요. - - - - ```sh - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **teamName** - - 필수의 - - 문자열 - - 지정된 목적지 ID와 연결된 팀 이름 - - `TEST_TEAM` -
- **channelName** - - 필수의 - - 문자열 - - 메시지를 보내야 하는 채널 이름 - - `StagingTesting` -
- **메시지** - - 필수의 - - 문자열 - - 보내야 할 문자 메시지 - - `Hello! this message from Workflow` -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **성공** - - 부울 - - `true/false` -
- **sessionId** - - 문자열 - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **오류 메시지** - - 문자열 - - `Message is a required field in the notification send"` -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: msTeam_notification_workflow - description: This is a test workflow to test MSTeam notification send action - steps: - - name: SendMessageUsingMSTeam - type: action - action: newrelic.notification.sendMicrosoftTeams - version: 1 - inputs: - destinationId: acc24dc2-d4fc-4eba-a7b4-b3ad0170f8aa - channel: DEV_TESTING - teamName: TEST_TEAM_DEV - message: Hello from Workflow - ``` -
- - - - - - - - - 첨부 파일이 있거나 없는 NewRelic 이메일 대상에 이메일을 보냅니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 필드 - - 선택성 - - 데이터 유형 - - 설명 - - 예시 -
- **목적지 ID** - - 필수의 - - 문자열 - - Newrelic 대상과 연관된 DestinationId입니다. - - 새 대상을 구성하고 대상 ID를 나열하는 방법에 대한 단계는 [Microsoft Teams용 뉴렐릭 통합을](/docs/alerts/get-notified/microsoft-teams-integrations/) 참조하세요. - - 목적지에 대한 자세한 내용을 알아보려면 [목적지를](/docs/alerts/get-notified/destinations/) 참조하세요. - - - - ```yaml - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: EMAIL, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **주제** - - 필수의 - - 문자열 - - 이메일 제목 - - `workflow-notification` -
- **메시지** - - 필수의 - - 문자열 - - 이메일로 보내야 할 메시지 - - `Hello! from Workflow Automation` -
- **첨부 파일** - - 선택 과목 - - 목록 - - 선택적 첨부 파일 목록 - -
- **attachment.type** - - 필수의 - - 열거형 - - 다음 중 하나: - - `QUERY` - - , - - `RAW` - -
- **attachment.query** - - 선택 과목 - - 문자열 - - `QUERY` - - 유형의 경우 이는 NRQL 쿼리 문입니다. - - `SELECT * FROM LOG` -
- *attachment.accountIds* - - \* - - 선택 과목 - - 목록 - - `QUERY` - - 의 경우 쿼리를 실행하기 위한 - - **New Relic Account IDs** - - \[뉴렐릭 계정 ID입니다]. 제공되지 않으면 fl.oxo 실행과 관련된 계정이 사용됩니다. - - `[12345567]` -
- **attachment.format** - - 선택 과목 - - 열거형 - - `QUERY` - - 의 경우 결과에 대한 유형을 지정합니다. 기본값은 다음과 같습니다. - - `JSON` - - `JSON CSV` -
- **첨부 파일.내용** - - 선택 과목 - - 문자열 - - `RAW` - - 의 경우, 이는 UTF-8 형식의 첨부 파일 콘텐츠입니다. - - `A,B,C\n1,2,3` -
- **첨부 파일 이름** - - 선택 과목 - - 문자열 - - 첨부 파일의 파일 이름 - - `log_count.csv` -
- **선택기** - - 선택 과목 - - 목록 - - 지정된 유일한 델파이를 출력으로 가져오는 선택기입니다. - - `[{\"name\": \"success\", \"expression\": \".success\"},{\"name\": \"attachments\", \"expression\": \".response.attachments\"},{\"name\": \"sessionId\", \"expression\": \".response.sessionId\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 출력 필드 - - 유형 - - 예시 -
- **성공** - - 부울 - - `true/false` -
- **sessionId** - - 문자열 - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **오류 메시지** - - 문자열 - - `Channel is a required field in the notification send"` -
- **첨부 파일** - - 목록 - - ```yaml - [{ - "blobId": "43werdtfgvhiu7y8t6r5e4398yutfgvh", - "rowCount": 100 - }] - ``` -
- - - - - - - - - - - - - - - -
- 워크플로 예 -
- ```yaml - name: email_testing_with_attachment - description: Workflow to test sending an email notification via NewRelic with log step - workflowInputs: - destinationId: - type: String - steps: - - name: sendEmailNotification - type: action - action: newrelic.notification.sendEmail - version: '1' - inputs: - destinationId: ${{ .workflowInputs.destinationId }} - subject: "workflow notification" - message: "Workflow Email Notification Testing from local" - attachments: - - type: QUERY - query: "SELECT * FROM Log" - format: JSON - filename: "log_count.json" - selectors: - - name: success - expression: '.success' - - name: sessionId - expression: '.response.sessionId' - - name: attachments - expression: '.response.attachments' - - name: logOutput - type: action - action: newrelic.ingest.sendLogs - version: '1' - inputs: - logs: - - message: "Hello from cap check Testing staging server user2 : ${{ .steps.sendEmailNotification.outputs.result.attachments }}" - licenseKey: ${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }} - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index 2dde4295328..00000000000 --- a/src/i18n/content/kr/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,634 +0,0 @@ ---- -title: 유틸리티 작업 -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: A list of available utility actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - -이 페이지에서는 fl.flo 자동화 작업 카탈로그에서 사용 가능한 유틸리티 작업에 대한 참조를 제공합니다. 이러한 작업을 통해 폴리스우 정의에서 일반적인 데이터 변환 및 유틸리티 작업을 수행할 수 있습니다. - -## 유틸리티 작업 - - - - 이 작업은 에포크 타임스탬프를 날짜/시간으로 변환하는 데 사용됩니다. 가능한 참조: - - * [https://en.wikipedia.org/wiki/List\_of\_tz\_database\_time\_zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - * [https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT\_IDS](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS) - - 자세한 내용은 [Epoch를](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) 참조하세요. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 유형 - - 설명 -
- **타임스탬프** - - 필수의 - - 정수 - - 에포크 타임스탬프를 나타내는 정수입니다. 참고로, UNIX 에포크는 1970년 1월 1일 자정 UTC(00:00) 이후의 초 수입니다. -
- **타임스탬프 단위** - - 선택 과목 - - 끈 - - 제공된 타임스탬프의 단위를 나타내는 문자열입니다. 허용 가능한 값: SECONDS, MILLISECONDS(기본값) -
- **시간대 ID** - - 선택 과목 - - 끈 - - 원하는 날짜/시간의 시간대를 나타내는 문자열, 기본값: UTC -
- **pattern** - - 선택 과목 - - 끈 - - 원하는 날짜/시간 패턴을 나타내는 문자열, 기본값: ISO-8601 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 들 - - 선택성 - - 데이터 유형 - - 설명 -
- **날짜** - - 필수의 - - 끈 - - 날짜의 문자열 표현입니다. -
- **시간** - - 필수의 - - 끈 - - 시간을 나타내는 문자열입니다. -
- **날짜 시간** - - 필수의 - - 끈 - - datetime의 문자열 표현입니다. -
- **시간대** - - 필수의 - - 지도 - - 시간대 ID와 약어를 지도로 표현한 것입니다. -
- - - - - - - - - - - - - - - - - - - - - - - -
- 예시 - - 흐름흐름 입력 - - 출력 -
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - 이 작업은 다양한 유형의 입력(JSON, 맵)을 CSV 형식으로 변환하는 데 사용됩니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 유형 - - 설명 -
- **data** - - 필수의 - - 어느 - - CSV로 변환할 데이터를 나타내는 문자열로, 일반적으로 JSON 문자열이나 맵입니다. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 들 - - 선택성 - - 데이터 유형 - - 설명 -
- **CSV** - - 필수의 - - 끈 - - 수신된 데이터의 CSV 표현입니다. -
- - - - - - - - - - - - - - - - - - - - - - -
- 예시 - - 흐름흐름 입력 - - 출력 -
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` - -
- - - - - - - - - RFC 규격에 맞는 V4 UUID를 생성합니다. - - - - - 입력 - - - - 출력 - - - - 예시 - - - - - - - - - - - - - - - - - - - - - - -
- 입력 - - 선택성 - - 데이터 유형 - - 설명 -
- - - - -
- - - - - - - - - - - - - - - - - - - - - - -
- 들 - - 데이터 유형 - - 설명 -
- **uuid** - - 끈 - -
- - - - - - - - - - - - - - - - - - - - - -
- 예시 - - 흐름흐름 입력 - - 출력 -
- - - 이름: generateUUID
단계: - - * 이름: generateUUID 유형: 작업 작업: utils.uuid.generate 버전: 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx deleted file mode 100644 index e2c7ee579a9..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-02-2025.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-10-02' -version: 'Sep 26 - Oct 02, 2025' -translationType: machine ---- - -### Grandes mudanças - -* [Documentação atualizada do Controle de Agentes](/docs/new-relic-control/fleet-control/overview) com revisões abrangentes para Kubernetes GA e visualização pública de Hosts, incluindo novos recursos de gerenciamento de frota, recursos de segurança aprimorados e procedimentos de configuração atualizados. -* [Documentação atualizada de controle de agentes](/docs/new-relic-control/agent-control/overview) com revisões extensas para visualização pública, incluindo opções aprimoradas de configuração, recursos de monitoramento e orientação de resolução de problemas. -* [Documentação de marcas e medidas](/docs/browser/new-relic-browser/browser-pro-features/marks-and-measures/) reestruturada para disponibilidade geral com detalhes abrangentes de recursos e orientação de implementação. -* [Fluxo de trabalho de notificação de alerta](/docs/alerts/admin/rules-limits-alerts) aprimorado com novas etapas de validação de e-mail e limites de destino. -* Atualizamos o [nome do modelo de preços](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management/) de "Planos de pré-visualização pública New Relic Compute ou planos Core" para "Planos avançados ou planos Core". - -### Pequenas mudanças - -* Instruções [de integração fullstack do WordPress](/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration) atualizadas para melhorar o processo de configuração. -* Documentação aprimorada [de variáveis de modelo de dashboard](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables) com captura de tela atualizada e exemplos melhorados. -* [Consultas e alertas de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) atualizados com recursos aprimorados de monitoramento de uso do computador. -* [Documentação de interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-ui) aprimorada com recurso abrangente de gerenciamento de computador. -* Referência de âncora duplicada corrigida na [configuração do agente .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration). -* [Integração de notificação](/docs/alerts/get-notified/notification-integrations) atualizada com gerenciamento aprimorado de destino de e-mail. -* Documentação [do AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink) atualizada com maior clareza de linguagem para regiões suportadas e requisitos de configuração de VPC. -* Atualizado o identificador de postagem O que há de novo para gerenciamento de conteúdo. - -### Notas de versão - -* Fique por dentro dos nossos últimos lançamentos: - - * [AgenteNode.js v13.4.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0): - - * Atualizada a instrumentação amqplib e cassandra-driver para subscrever eventos emitidos. - * Relatório de compatibilidade do agente Node.js atualizado com as versões mais recentes dos pacotes suportados. - * Adicionadas otimizações WASM para rastreamento de ganchos. - * Requisitos JSDoc aprimorados para melhor documentação de código. - - * [AgentePython v11.0.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000): - - * Removido o suporte para Python 3.7 e descontinuado várias APIs lendárias. - * Adicionada nova instrumentação para o framework AutoGen e Pyzeebe. - * Introduziu intervalos nomeados MCP (Model Context Protocol) para monitoramento de IA. - * Corrigida a falha no psycopg e garantido que o MCP abrange apenas registros quando o Monitoramento de IA está habilitado. - - * [agente de infraestrutura v1.69.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690): - - * AWS SDK atualizado de V1 para V2 e biblioteca de API do Docker de v26 para v28. - * Corrigido monitoramento de CPU Windows para instância com múltiplos grupos de CPU (mais de 64 núcleos). - * Manipulação de formato de log aprimorada com suporte de nível de log padrão. - - * [Integração Kubernetes v3.45.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3): - - * Incluído nas versões de gráficos newrelic-infrastructure-3.50.3 e nri-bundle-6.0.15. - - * [NRDOT v1.5.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-25): - - * Adicionado metricsgenerationprocessor ao nrdot-coletor-k8s para coleta métrica aprimorada. - - * [Agente .NET v10.45.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0): - - * Adicionado novo TraceId Ratio-Based Sampler para distributed tracing com base na implementação OpenTelemetry. - * Corrigidas exceções de análise de cadeia de conexão MSSQL que poderiam desabilitar o armazenamento de instrumentação de dados. - * Problemas de instrumentação "Consume" do Kafka resolvidos para melhor compatibilidade com instrumentação personalizada. - - * [Aplicativo móvel New Relic Android v5.30.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5308): - - * Correções de bugs e melhorias para melhor desempenho do aplicativo móvel. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx deleted file mode 100644 index 658bb02c925..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-11-2024.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-11' -version: 'version: October 4-10, 2024' -translationType: machine ---- - -### Novos documentos - -* [A mensagem "Nenhum dado de falha aparece na versão de lançamento (Android)"](/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears) informa o que fazer se você não visualizar dados relacionados a uma falha do aplicativo na interface do usuário do New Relic. -* [Como posso usar o WSL e o CodeStream?](/docs/codestream/troubleshooting/using-wsl) fornece instruções passo a passo sobre como usar o Subsistema Windows para Linux (WSL) com o CodeStream. -* [`UserAction`](/docs/browser/browser-monitoring/browser-pro-features/user-actions) é um novo tipo de evento no monitoramento do navegador que ajuda você a entender o comportamento do usuário com seu aplicativo web. -* [WithLlmCustomAttributes (API Python do agente)](/docs/apm/agents/python-agent/python-agent-api/withllmcustomattributes-python-agent-api) descreve a nova API do gerenciador de contexto, incluindo seus requisitos, parâmetros, valores de retorno e um exemplo de uso. - -### Pequenas mudanças - -* Adicionado endpoint data center dos EUA e da UE para o agente APM no [endpoint de telemetriaNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). - -* Instruções atualizadas sobre como encontrar os logs do lado do cliente do CodeStream ao usar [o Visual Studio](/docs/codestream/troubleshooting/client-logs/#visual-studio). - -* [Opções de notificação reformuladas para regras de silenciamento,](/docs/alerts/get-notified/muting-rules-suppress-notifications/#notify) visando maior clareza. - -* Atualizei as informações de compatibilidade para os seguintes pacotes nos [módulos instrumentados](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrumented-modules): - - * `@aws-sdk/client-bedrock-runtime` - * `@aws-sdk/client-dynamodb` - * `@aws-sdk/client-sns` - * `@aws-sdk/client-sqs` - * `@aws-sdk/lib-dynamodb` - * `@grpc/grpc-js` - * `@langchain/core` - * `@smithy/smithy-client` - * `next` - * `openai` - -* Corrigido o segundo endpoint data center da UE para `212.32.0.0/20` nos [blocos IP de ingestão de dados](https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#ingest-blocks). - -* Especifique que o serviço de alertas da New Relic é executado nos Estados Unidos, independentemente de seus dados estarem armazenados no [data center da New Relic na UE ou nos EUA](/docs/alerts/overview/#eu-datacenter). - -* Informações modificadas sobre como definir um [atributo personalizado](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes). Os exemplos também foram atualizados. - -* Atualizei os passos para [cancelar o reconhecimento e fechar uma ocorrência](/docs/alerts/get-notified/acknowledge-alert-incidents/#unacknowledge-issue). - -* Adicionadas informações sobre [como reconhecer e encerrar várias ocorrências](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/#bulk-actions). - -* Ampliamos a introdução sobre [as taxas de atualização do gráfico](/docs/query-your-data/explore-query-data/use-charts/chart-refresh-rates) para destacar que a taxa de atualização só é configurável se você estiver no plano de preços de consumo New Relic Compute. - -* Corrigidas as informações necessárias sobre a versão do Transport Layer Security (TLS) na [criptografia TLS](/docs/new-relic-solutions/get-started/networks/#tls). - -* Atualizou-se a etapa 6 do procedimento [de instalação da integração com o Kubernetes](/install/kubernetes) para corresponder à interface de usuário atual do New Relic. - -* Observou-se a importância do evento não faturável, `InternalK8sCompositeSample`, em [consulta de dados Kubernetes ](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#view-data), após a tabela. - -* Reescrevi as instruções para [visualizar e gerenciar a chave de API](/docs/apis/intro-apis/new-relic-api-keys/#keys-ui) para maior precisão e clareza. - -* Instruções atualizadas sobre como usar o explorador de API em [Usar o explorador de API](/docs/apis/rest-api-v2/api-explorer-v2/use-api-explorer) e [listar o ID do aplicativo, o ID do host e o ID da instância](/docs/apis/rest-api-v2/get-started/list-application-id-host-id-instance-id) para corresponder ao explorador de API atual. - -* Adicionado novamente o exemplo de [correlação de infraestrutura com o OpenTelementry APM](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro/#infrastructure-correlation). - -* Anotado como evitar nomes de métricas duplicados ao [migrar para a integração com o Azure Monitor](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#migrate). - -### Notas de versão - -Confira nossas postagens de Novidades para saber sobre novos recursos e lançamentos: - -* [O New Relic Pathpoint conecta a telemetria aos KPIs de negócios.](/whats-new/2024/10/whats-new-10-10-pathpoint) - -Fique por dentro dos nossos lançamentos mais recentes: - -* [Caixa de entrada de erros para Android v5.25.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-52501) - * Permite iterar pelos erros, inspecionar atributos perfilados e muito mais. - -* [Flutter agente v1.1.4](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-114) - * Atualiza o agente iOS para a versão 7.5.2. - -* [Integração Kubernetes v3.29.6](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6) - - * Atualizações: Acesse a versão 1.23.2. - * Atualiza a biblioteca comum do Prometheus para a versão 0.60.0. - -* [Agente Python v10.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100) - - * Compatível com Python 3.13 - * Fornece uma nova API de gerenciamento de contexto. - * Suporta a geração de relatórios de IDs do Docker no Amazon ECS Fargate. - * Inclui instrumentação para `SQLiteVec` - -* [Agente Unity v1.4.1](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141) - - * Atualiza o agente nativo Android e do iOS - * Contém correções de erros. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx deleted file mode 100644 index c776e680373..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-10-18-2024.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-10-18' -version: 'version: October 11-17, 2024' -translationType: machine ---- - -### Novos documentos - -* [O documento "Forward Kong Gateway logs"](/docs/logs/forward-logs/kong-gateway/) descreve como instalar e usar este novo plug-in de encaminhamento de logs por meio da integração com o Kubernetes. -* [O monitoramentoAzure App Service](/docs/apm/agents/manage-apm-agents/azure/monitoring-azure-app-service/) descreve como integrar esse serviço Azure com o New Relic e fornece instruções sobre como configurá-lo para nossos agentes APM Java, .NET, Node.js e Python. -* [A Introdução ao Explorador de Dados](/docs/query-your-data/explore-query-data/query-builder/introduction-new-data-explorer/) descreve como usar nossa nova interface do Explorador de Dados para consultar seus dados e obter insights mais profundos sobre como a plataforma New Relic pode te ajudar e resolver seus problemas. -* [Monitore ambientes Amazon ECS com o agente de linguagem APM,](/docs/infrastructure/elastic-container-service-integration/monitor-ecs-with-apm-agents/) que ajuda você a instalar nosso agente APM em seu ambiente Amazon ECS. -* [O documento "Migrar para NRQL](/docs/apis/rest-api-v2/migrate-to-nrql/) descreve como migrar sua API REST v2 consulta para NRQL consulta. - -### Grandes mudanças - -* Migramos o conteúdo do nosso site de código aberto para o nosso site de documentação. -* Esclarecemos como gerenciar segredos com o [operador do agente Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/). - -### Pequenas mudanças - -* Em ["MétricasOpenTelemetry no New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics/#otlp-summary), esclarecemos que as métricas de resumo OpenTelemetry não são suportadas. -* Atualizamos uma captura de tela nas [políticas de alertas recomendadas e no dashboards](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies/#add-recommended-alert-policy) para esclarecer onde encontrar os blocos Kubernetes e do Google Kubernetes Engine. -* Apaguei a documentação do Stackato e do WebFaction relacionada ao agente APM em Python, pois não é mais relevante. -* Adicionamos um novo endpoint de monitoramento de navegador à nossa documentação [de Redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Resolvemos pequenos problemas em nossos documentos de monitoramento de resolução de problemas do navegador. -* Na [seção de solução de problemas de atualização de tempo de execução,](/docs/synthetics/synthetic-monitoring/troubleshooting/runtime-upgrade-troubleshooting/#scripted-api-form) descrevemos como resolver problemas ao usar tempos de execução Node mais antigos com objetos `$http`. -* Na [API do agente .NET](/docs/apm/agents/net-agent/net-agent-api/net-agent-api), adicionamos `NewRelic.Api.Agent.NewRelic` à chamada de API `ITransaction` e adicionamos a nova chamada de API `RecordDatastoreSegment`. - -### Notas de versão - -Fique por dentro dos nossos lançamentos mais recentes: - -* [Agente Android v7.6.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-761/) - - * Adiciona suporte ao plug-in do Gradle Android versão 8.7. - * Corrige problemas com o carregamento correto de arquivos de mapeamento ProGuard/DexGuard. - * Outras correções de bugs - -* [Agente do browser v1.269.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0/) - - * Permite que o carregador MicroAgent no NPM use APIs logging para capturar dados de log manualmente. - * Adiciona instrumentação metadados à carga de logging - * Corrige erros relacionados ao rastreamento da sessão e à política de segurança de reprodução de sessão. - -* [Agente Go v3.35.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0/) - - * Adiciona suporte para relatórios seguros de eventos de cookies. - * Usa o valor `error.Error()` para o atributo de log. - * Aprimora o suporte a URLs para conexões de servidor AMQP. - * Diversas correções de bugs - -* [Extensão Lambda v2.3.14](/docs/release-notes/lambda-extension-release-notes/lambda-extension-2.3.14/) - - * Adiciona um recurso para ignorar as verificações de inicialização da extensão. - * Atualiza o arquivo README com informações sobre como usar a variável de ambiente `NR_TAGS` - * Adiciona suporte à variável de ambiente booleana `NEW_RELIC_ENABLED` - -* [Agente .NET v10.32.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0/) - - * Descontinua o uso de variáveis de ambiente com prefixo. `NEWRELIC_` - * Implementa um esquema de nomenclatura consistente para todas as variáveis de ambiente. - * Atualiza a instrumentação do CosmosDB para suportar a versão mais recente. - -* [Ping Runtime v1.47.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.47.0/) - * Corrige um problema relacionado às permissões de usuário para o script de controle ping-runtime para usuários não root. - -* [Agente Python v10.2.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200/) - * Adiciona sinalizador de operador de contêiner init Azure para dar suporte a essa opção para monitoramento de aplicativos de contêiner Azure \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx deleted file mode 100644 index 3e5b2e6b145..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-07-2025.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-07' -version: 'November 2 - November 7, 2025' -translationType: machine ---- - -### Novos documentos - -* Adicionamos [exemplos de controle de acesso a dados do NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-data-access-control) para fornecer exemplos práticos de gerenciamento de controle de acesso a dados por meio da API do NerdGraph. -* Adicionada [detecção de valores discrepantes](/docs/alerts/create-alert/set-thresholds/outlier-detection) para fornecer orientação para configurar a condição de alerta de detecção de outlier. -* Adicionado [catálogo de infraestrutura](/docs/service-architecture-intelligence/catalogs/infrastructure-catalog/) para fornecer documentação aprimorada com os pré-requisitos para a configuração do monitoramento de infraestrutura. -* Adicionamos [mapas de serviços de streaming de mídia](/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps/) para orientar a compreensão das relações entre o streaming de mídia e as entidades de navegador/dispositivo móvel. -* Adicionada [uma caixa de entrada de erros para streaming de mídia,](/docs/errors-inbox/media-streaming-group-error/) a fim de fornecer instruções sobre como agrupar e gerenciar erros de streaming de mídia. - -### Grandes mudanças - -* [Configuração de controle de agentes](/docs/new-relic-control/agent-control/configuration) atualizada com exemplos YAML revisados para maior clareza e nomes de campos atualizados. -* [Configuração de controle do agente](/docs/new-relic-control/agent-control/setup) atualizada com exemplos de configuração YAML aprimorados. -* [Reinstrumentação atualizada do controle do agente](/docs/new-relic-control/agent-control/reinstrumentation) com exemplos YAML atualizados para maior precisão. -* [Resolução de problemas de controle de agente](/docs/new-relic-control/agent-control/troubleshooting) atualizada com exemplos de configuração refinados. - -### Pequenas mudanças - -* Adicionadas informações de compatibilidade com MariaDB à documentação de [requisitos de integração com MySQL](/install/mysql/). -* Adicionamos [controle de acesso a dados](/docs/accounts/accounts-billing/new-relic-one-user-management/data-access-control) para fornecer orientações abrangentes sobre como controlar o acesso a dados de telemetria usando políticas de dados. -* Documentação atualizada [do GitHub integração na nuvem](/docs/service-architecture-intelligence/github-integration/) com os detalhes de configuração mais recentes. -* [Documentação atualizada da CLI de diagnóstico](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-360) para a versão 3.60. -* Documentação atualizada sobre a configuração [de portas do Vizier](/docs/ebpf/k8s-installation/) para Kubernetes. - -### Notas de versão - -* Fique por dentro dos nossos últimos lançamentos: - - * [Agente Python v11.1.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100): - - * Adicionado suporte para Python 3.14. - * Adicionadas variáveis de ambiente para configurações de filtro de atributos. - * Adicionado suporte para geradores assíncronos em decoradores de transação. - * Adicionado suporte para modelos adicionais na instrumentação do AWS Bedrock, incluindo modelos Claude Sonnet 3+ e modelos com reconhecimento de região. - * Adicionada instrumentação para novos métodos do AWS Kinesis, incluindo describe\_account\_settings, update\_account\_settings, update\_max\_record\_size e update\_stream\_warm\_throughput. - * Corrigido o erro de recursão (RecursionError) no aiomysql ao usar o ConnectionPool. - * Corrigido um bug que impedia a passagem correta de propriedades no produtor Kombu. - * Corrigido erro que ocorria quando shutdown\_agent era chamado de dentro da thread de colheita. - - * [Agente iOS v7.6.0](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760): - - * Adicionada a funcionalidade de pré-visualização pública do Mobile Session Replay. - * A versão do iOS necessária foi atualizada para iOS 16. - * Corrigido problema com exceções tratadas que podiam ocorrer durante o logging. - * Corrigido o aviso de nomenclatura de parâmetro incorreta. - - * [Agente Android v7.6.12](/docs/release-notes/mobile-release-notes/android-release-notes/android-7612): - - * Adicionada a funcionalidade de reprodução de sessão para o Jetpack Compose. - * Lançada a versão oficial de pré-visualização pública do Session Replay. - * Corrigidos vários bugs relacionados à reprodução de sessões. - - * [Integração Kubernetes v3.49.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0): - - * Veja as alterações detalhadas nas notas de lançamento do GitHub. - * Incluído nas versões de gráficos newrelic-infrastructure-3.54.0 e nri-bundle-6.0.20. - - * [Logs v251104](/docs/release-notes/logs-release-notes/logs-25-11-04): - - * Adicionado suporte para formatos de carregamento de log específicos do .NET. - * Introduzida a variável de ambiente NEW\_RELIC\_FORMAT\_LOGS para processar formatos de log específicos do .NET. - - * [Node browser runtime rc1.2](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.2): - - * Atualizei o navegador Chrome para a versão 141. - * Vulnerabilidades corrigidas: CVE-2025-5889 para expansão de chaves. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx deleted file mode 100644 index 752b552b852..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-14-2025.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-14' -version: 'November 08 - November 14, 2025' -translationType: machine ---- - -### Novos documentos - -* Adicionado [o modo de consentimento do Browser ](/docs/browser/new-relic-browser/configuration/consent-mode)para documentar a implementação do gerenciamento de consentimento para monitoramento da conformidade do navegador com as regulamentações de privacidade. -* Adicionadas [extensões Java no recurso de anexação automática do Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach) para fornecer orientações de configuração para instrumentação Java APM em ambientes Kubernetes. -* Adicionado [Traga sua própria configuração de cache](/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache) para documentar as opções de configuração de cache OpenTelemetry para distributed tracing. - -### Grandes mudanças - -* [Inteligência de resposta](/docs/alerts/incident-management/response-intelligence-ai) aprimorada com IA, que inclui recursos de sumarização de logs para análise de alertas baseados em logs. -* Renomeamos e reestruturamos a documentação de Gerenciamento de Computadores para [Gerenciamento de Consumo](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/consumption-management). -* [Configuração do agente Java ](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file)atualizada com opções de nomenclatura de transações Spring e configuração do analisador SQL. -* [Funções personalizadas de integração do GCP](/docs/infrastructure/google-cloud-platform-integrations/get-started/integrations-custom-roles) atualizadas com permissões revisadas para 4 serviços do Google na nuvem. -* Documentação aprimorada [para resolução de problemas do MCP,](/docs/agentic-ai/mcp/troubleshoot) incluindo cenários e soluções de configuração do Protocolo de Contexto do Modelo. -* [Configuração aprimorada do agenteRuby ](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration)com novas opções de configuração de erro de nova tentativa do Sidekiq. -* Atualização [da instalação do agente PHP](/docs/apm/agents/php-agent/installation/php-agent-installation-ubuntu-debian) com suporte para Debian Trixie. - -### Pequenas mudanças - -* Adicionada compatibilidade com Java 25 aos [requisitos de compatibilidade do agente Java](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent). -* Adicionado suporte ao .NET 10 aos [requisitos de compatibilidade do agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). -* [Gerenciamento atualizado do nível de serviço alertas](/docs/service-level-management/alerts-slm). -* Informações atualizadas [sobre a compatibilidade do agente PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) com as versões do Drupal e do Laravel. -* [Compatibilidade de integração com Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements) atualizada. -* [Requisitos de compatibilidade do agente Java](/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent) atualizados com suporte ao framework. - -### Notas de versão - -Confira as novidades em: - -* [Lançamento New Relic MCP em visualização pública](/whats-new/2025/11/whats-new-11-05-mcp-server) - -* [Detecção de outliers New Relic em pré-visualização pública](/whats-new/2025/11/whats-new-11-05-outlier-detection) - -* [Resumo de alertas de log de IA (pré-visualização)](/whats-new/2025/11/whats-new-11-13-AI-Log-Alert-Summarization) - -* Fique por dentro dos nossos últimos lançamentos: - - * [Agente Node.js v13.6.4](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4): - - * Corrigido o MessageConsumerSubscriber para finalizar corretamente as transações de consumo de mensagens. - * Corrigido o MessageProducerSubscriber para definir corretamente o sinalizador de amostragem no traceparent. - * Prioridade de registro do middleware Bedrock corrigida para a desserialização adequada da carga útil. - - * [Agente Node.js v13.6.3](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3): - - * Correção no tratamento de streaming de instrumentação OpenAI com stream\_options.include\_usage. - * Corrigida a atribuição da contagem de token do @google/GenAI ao LlmCompletionSummary. - * Corrigida atribuição de contagem de token de instrumentação AWS Bedrock. - - * [Agente Java v8.25.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250): - - * Adicionado suporte ao Java 25. - * Adicionado suporte ao Logback-1.5.20. - * Introduzida a opção de configuração de nomenclatura de transação do Spring Controller. - * Adicionado suporte para Kotlin Coroutines v1.4+. - * Correção na lógica de análise sintática de nomenclatura de classes. - * Corrigido possível problema de memória no logging de erros com rastreamento stack extenso. - - * [Agente Ruby v9.23.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0): - - * Adicionado sidekiq.ignore\_retry\_errors Opção de configuração para controlar a captura de erros de repetição. - * Gravação de implantação do Capistrano obsoleta (removida na versão 10.0.0). - * Aplicativo aprimorado de configuração de amostragem de pai remoto para distributed tracing mais consistente. - - * [Agente .NET v10.46.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1): - - * Removemos o intervalo de consumo das transações do modo de processador do Azure Service Bus para melhorar a precisão. - * Atualização da serialização da enumeração ReportedConfiguration para maior clareza da interface do usuário. - - * [Integração Kubernetes v3.50.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0): - - * Atualização da versão do gráfico KSM e2e para 2.16. - * Adicionado suporte para a métrica kube\_endpoint\_address. - * Corrigido problema de modelagem de priorityClassName com suporte para Windows ativado. - - * [Sintéticos Job Manager versão 486](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-486): - - * Correção de vulnerabilidades no Ubuntu e no Java, incluindo CVE-2024-6763 e CVE-2025-11226. - - * [Sintéticos Ping Runtime v1.58.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.0): - - * Correção de vulnerabilidades no Ubuntu e no Java, incluindo CVE-2025-5115 e CVE-2025-11226. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx deleted file mode 100644 index 9bca2a6e006..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-21-2025.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-11-21' -version: 'November 17 - November 21, 2025' -translationType: machine ---- - -### Novos documentos - -* Adicionamos a opção ["Migrar regras de descarte" às regras cloud do pipeline](/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules/) para fornecer orientações completas sobre como migrar as regras de descarte existentes para o novo sistema de regras cloud do pipeline. -* Adicionada [a incompatibilidadePHPUnit ](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility)para fornecer orientações sobre a resolução de problemas relacionados a erros de falta de memória no PHPUnit versão 11+ com o agente PHP New Relic. - -### Grandes mudanças - -* A documentação de análise de dados de teste do PHPUnit foi removida após o fim do suporte do agente PHP para o PHPUnit. Substituído por documentação de resolução de problemas para questões de incompatibilidade do PHPUnit. -* Reestruturou [a entidade de busca e filtro](/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) para melhorar a organização e adicionou novo recurso de filtragem de catálogo. -* Atualização: [Instale o New Relic eBPF em ambientes Kubernetes](/docs/ebpf/k8s-installation) com opções de configuração de desacoplamento para monitoramento de desempenho de rede. - -### Pequenas mudanças - -* Adicionadas informações sobre retenção de dados de streaming de mídia à documentação [de gerenciamento de retenção de dados](/docs/data-apis/manage-data/manage-data-retention). -* PHPUnit foi removido da tabela de compatibilidade [de agentes e requisitos do PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) após o fim do suporte. -* Corrigido exemplo de consulta NRQL para [consultas e alertas de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). -* [Página de configurações do aplicativoBrowser ](/docs/browser/new-relic-browser/configuration/browser-app-settings-page/)atualizada com informações de configuração do armazenamento local. -* Adicionado modo de consentimento à navegação na documentação do browser. -* [Configurações](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings) atualizadas para o SDK móvel. -* Documentação aprimorada [sobre tipos de gráficos,](/docs/query-your-data/explore-query-data/use-charts/chart-types) com informações adicionais sobre cada tipo. -* [Visão geral](/docs/agentic-ai/mcp/overview) e [solução de problemas](/docs/agentic-ai/mcp/troubleshoot) atualizadas para MCP com esclarecimentos sobre as funções RBAC. - -### Notas de versão - -* Fique por dentro dos nossos últimos lançamentos: - - * [Agente Go v3.42.0](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0): - - * Adicionadas novas opções de configuração de número máximo de amostras para Transações, Insights Personalizados, Erros e Logs. - * Adicionado suporte para MultiValueHeaders em nrlambda. - * Variáveis não utilizadas foram removidas em nrpxg5. - * Corrigido um bug em que o evento de erro não marcava corretamente o erro esperado. - - * [Agente .NET v10.47.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0): - - * Adicionamos um mecanismo opcional de armazenamento de transações para permitir que as transações fluam com o ExecutionContext para aplicativos web ASP.NET. - * Corrigida a exceção de referência nula na instrumentação do Azure Service Bus. - * Corrigida a instrumentação da OpenAI para lidar com as conclusões de bate-papo quando o parâmetro de mensagens não for uma matriz. - - * [AgenteNode.js v13.6.5](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5): - - * Atualizada a instrumentação expressa para erro ignorado quando o próximo manipulador passar por rota ou roteador. - * Atualizei o MessageConsumerSubscriber para aguardar o término do retorno de chamada do consumidor quando se tratar de uma promessa. - - * [Agente Node.js v13.6.6](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6): - - * Atualizei a instrumentação do Express para app.use ou router.use a fim de encapsular corretamente todos os middlewares definidos. - * Adicionada configuração para distributed\_tracing.samplers.partial\_granularity e distributed\_tracing.samplers.full\_granularity. - - * [Agente PHP v12.2.0.27](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27): - - * Adicionado suporte ao Laravel 12. - * Adicionado suporte ao Laravel Horizon no Laravel 10.x+ e PHP 8.1+. - * Correção no tratamento de exceções em tarefas da fila do Laravel. - * A versão do golang foi atualizada para 1.25.3. - - * [Integração Kubernetes v3.50.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1): - - * Atualizado para a versão 3.50.1 com correções de erros e melhorias. - - * [Agente de infraestrutura v1.71.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711): - - * Atualizada a dependência newrelic/docker para v2.6.3. - * Dependência newrelic/nri-flex atualizada para v1.17.1. - * Atualizei a versão do Go para 1.25.4. - * Dependência newrelic/nri-prometheus atualizada para v2.27.3. - - * [Logs de 25/11/2020](/docs/release-notes/logs-release-notes/logs-25-11-20): - - * Corrigida a vulnerabilidade CVE-2025-53643 na função Lambda de aws-log-ingestion. - * Biblioteca aiohttp atualizada para a versão 3.13.2. e versão de poesia para 1.8.3. - - * [Node browser runtime rc1.3](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.3): - - * Atualizei o navegador Chrome para a versão 142. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx deleted file mode 100644 index ccd856036d0..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-5-24-2024.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-05-24' -version: 'version: May 17-23, 2024' -translationType: machine ---- - -### Novos documentos - -* Nossa nova [integraçãoApache Mesos](/docs/infrastructure/host-integrations/host-integrations-list/apache-mesos-integration) ajuda você a monitorar o desempenho do kernel de seus sistemas distribuídos. -* Nossa nova [integração Temporal na nuvem](/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration) ajuda você a monitorar e diagnosticar problemas de fluxo de trabalho, namespace e aplicativos escaláveis em sua Nuvem Temporal. -* Você tem um [aplicativo .NET no AWS Elastic Beanstalk](/docs/apm/agents/net-agent/install-guides/install-net-agent-on-aws-elastic-beanstalk)? Este novo documento de instalação mostra um caminho claro para a ingestão desses dados em nossa plataforma. - -### Grandes mudanças - -* Adicionados e atualizados exemplos de código do monitor com script do Sintético e do navegador para [monitoramento sintético, práticas recomendadas](/docs/new-relic-solutions/best-practices-guides/full-stack-observability/synthetic-monitoring-best-practices-guide) e [referência do navegador com script do Sintético](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100). Exemplos de código são uma das coisas que nossos leitores mais pedem, então sempre ficamos felizes em ver mais deles. - -* Em nossa documentação sobre monitoramento de desempenho de rede, várias pequenas atualizações levaram a uma grande mudança: atualizamos os ambientes suportados pelo Podman em 17 documentos. - -* Esclarecemos como funcionam [os logs live archives](/docs/logs/get-started/live-archives) e quando esses [dados de log estão disponíveis](/docs/logs/get-started/live-archives-billing). - -* Adicionamos um diagrama e variáveis de ambiente ao [instrumento de monitoramento Lambda para sua camada de imagem conteinerizada](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/containerized-images/). - -* A API REST v1 da New Relic foi totalmente descontinuada e excluímos diversos documentos relacionados a ela. - -* Uma varredura completa de nossa documentação de monitoramento de infraestrutura para: - - * Alinhe-o ao nosso guia de estilo. - * Remova o conteúdo desnecessário. - * Torne o documento de instalação mais visível na barra de navegação à esquerda. - * Melhore o fluxo do documento de instalação. - -* A migração do nosso site de desenvolvedores para a seção de documentação continua, com mais de 30 documentos migrados esta semana. - -* A partir de 23 de maio de 2024, o AI Monitoring oferece suporte Java. Atualizamos vários documentos sobre Monitoramento de IA para refletir essa importante atualização. - -### Pequenas mudanças - -* [Controles de segurança de armazenamento de dados em nuvem atualizados para privacidade,](/docs/security/security-privacy/data-privacy/security-controls-privacy/#cloud-data-storage) com um relatório de conformidade vinculado. -* Simplificamos os passos [de instalação do yum para .NET](/install/dotnet/installation/linuxInstall2/#yum). -* Documentação [de compatibilidade com Python](/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent/#basic) atualizada para indicar que agora oferecemos suporte ao Python 3.12. -* Atualizou-se [a compatibilidade com o .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) para adicionar suporte ao armazenamento de dados `Elastic.Clients.Elasticsearch` versão 8.13.12. -* Tabela de módulos instrumentados [de compatibilidade com o agente APM Node.js ](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent)atualizada. -* Endpoint atualizado para regiões e zonas compatíveis com [AWS PrivateLink](/docs/data-apis/custom-data/aws-privatelink). -* O agente de infraestrutura agora é compatível com o Ubuntu 24.04 (Noble Numbat), mas ainda não oferecemos suporte à infraestrutura com logs nessa versão do Ubuntu. -* Se você estiver usando [o CyberARK e o Microsoft SQL Server](/docs/infrastructure/host-integrations/installation/secrets-management/#cyberark-api) com a Autenticação do Windows, esclarecemos que é necessário preceder seu nome de usuário com o domínio. -* Em nossa [configuração APM para o agente .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration/#error-ignoreErrors), adicionamos variáveis de ambiente para códigos de status ignorados e esperados. -* Em ["Use seus gráficos"](/docs/query-your-data/explore-query-data/use-charts/use-your-charts), esclarecemos o que queremos dizer com KB, MB, GB e TB. (Utilizamos o Sistema Internacional de Unidades, que usa potências de 10 para os cálculos.) -* Nas [configurações de e-mail](/docs/accounts/accounts/account-maintenance/account-email-settings), esclarecemos os caracteres permitidos e os limites para endereços de e-mail de usuários New Relic. -* Adicionamos o endpoint da URL do serviço de validação IAST à nossa tabela de endpoints de telemetria New Relic em nossas [redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Adicionada uma dica sobre como monitorar várias versões de traps SNMP em um host no [monitoramento de desempenho SNMP](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring). -* Se você deseja estender sua [instrumentação do Node.js para incluir o Apollo Server](/docs/apm/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs/#extend-instrumentation), adicionamos links para arquivos README úteis no GitHub. -* Adicionadas informações de compatibilidade com .NET à [compatibilidade e aos requisitos do Monitoramento de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#compatibility). - -### Postagens com notas de lançamento e novidades - -* [Agente do browser v1.260.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1) -* [Agente de infraestrutura v1.52.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523) -* [Agente Java v8.12.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120) -* [Gerenciador de tarefas v370](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-370) -* [Integração Kubernetes v3.28.7](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7) -* [Aplicativo móvel para Android v5.18.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5180) -* [Agente .NET v10.25.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0) -* [Runtime da API Node v1.2.1](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.1) -* [Runtime da API Node v1.2.58](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.58) -* [Runtime da API Node v1.2.67](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.67) -* [Runtime da API Node v1.2.72](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.72) -* [Runtime da API Node v1.2.75](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.75) -* [Runtime da API Node v1.2.8](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.8) -* [Agente Node.js v11.17.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0) -* [Agente PHP v10.21.0.11](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11) \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx deleted file mode 100644 index c94fa31d4b2..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-6-28-2024.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -subject: Docs -releaseDate: '2024-06-28' -version: 'version: June 21-27, 2024' -translationType: machine ---- - -### Novos documentos - -* O recurso de monitoramento de [aplicativo móvel que não responde](/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding) ajuda você a rastrear e analisar quando e por que seu aplicativo Android fica bloqueado por mais de cinco segundos. -* A nova documentação API de monitoramento do navegador [`log()`](/docs/browser/new-relic-browser/browser-apis/log) e [`wrapLogger()`](/docs/browser/new-relic-browser/browser-apis/wraplogger) define a sintaxe, os requisitos, os parâmetros e os exemplos de como usar esses novos endpoints. - -### Grandes mudanças - -* Removemos nossa categoria de nível superior `Other capabilities` e migramos tudo o que estava lá para categorias mais apropriadas. Com tudo em seu devido lugar, fica mais fácil encontrar o que você procura. -* Movemos os exemplos do coletor OpenTelemetry em nosso site de documentação para o nosso `newrelic-opentelemetry-examples`]\([https://github.com/newrelic/newrelic-opentelemetry-examples](https://github.com/newrelic/newrelic-opentelemetry-examples)) Repositório GitHub para facilitar a manutenção e melhorar a visibilidade do código aberto. -* Nosso monitoramento de IA suporta [modelos NVIDIA NIM](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/#deploy-at-scale) e não requer nenhuma configuração extra fora de nossos fluxos de instalação manuais ou baseados em interface. Leia mais sobre isso em nosso blog [: Monitoramento de IA para NVIDIA NIM](https://newrelic.com/blog/how-to-relic/ai-monitoring-for-nvidia-nim). - -### Pequenas mudanças - -* Adicionada a URL de endpoint do serviço de validação IAST aos [endpoints](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#agents) e [redes](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints) compatíveis com FedRAMP. -* Atualizada [a resolução de problemasIAST ](/docs/iast/troubleshooting/#see-my-application)com intervalos de IP específicos para a lista de permissões caso você não esteja vendo seu aplicativo. -* Atualização [do agente de configuraçãoRuby ](/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/#instrumentation-aws_sqs)com informações de `NEW_RELIC_INSTRUMENTATION_AWS_SQS` instrumentação automática de configuração. -* Informações de configuração de relatório `ApplicationExitInfo` removidas de [configurar monitoramento de configurações móveis](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/configure-settings), porque você pode fazer isso na interface. -* [Os recursos de enriquecimento de fluxo de trabalho](/docs/alerts/get-notified/incident-workflows/#enrichments) suportam múltiplas variáveis, permitindo que você personalize seus dados de forma mais específica para suas necessidades. -* Adicionamos o atributo [MobileApplicationExit](/attribute-dictionary/?dataSource=Mobile&event=MobileApplicationExit) ao nosso dicionário de dados. Nosso dicionário de dados não é apenas um recurso de documentação, mas também fornece definições de atributos diretamente para a interface, por exemplo, quando você está escrevendo uma consulta NRQL em nosso criador de consultas. -* Documentação relacionada à API REST de alertas desatualizada foi removida. - -### Postagens com notas de lançamento e novidades - -* O que há de novo no [New Relic AI Monitoring? Agora ele se integra aos microsserviços de inferência do NVIDIA NIM.](/whats-new/2024/06/whats-new-06-24-nvidianim) - -* Novidades na [atualização do runtime do monitor Sintético para evitar impactos nos seus monitores Sintético.](/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm) - -* [Agente Android v7.4.1](/docs/release-notes/mobile-release-notes/android-release-notes/android-741) - * `ApplicationExitInfo` O envio de relatórios está ativado por padrão. - -* [Agente do browser v1.261.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0) - - * Argumentos da API de logging passados como objetos para maior extensibilidade. - * Diversos outros novos recursos e correções de bugs. - -* [CLI de diagnóstico (nrdiag) v3.2.7](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-327) - -* [Integração Kubernetes v3.29.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0) - - * Adicionado suporte para as versões 1.29 e 1.30, removido suporte para as versões 1.24 e 1.25. - * Substituição atualizada: Pacotes Kubernetes v0.30.2 e Alpine v3.20.1 - -* [Aplicativo móvel para iOS v6.5.0](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6050) - - * Veja todas as entidades que fazem parte de uma workload - * Mais opções de personalização dashboard - * Diversas outras melhorias - -* [Agente Node.js v11.20.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0) - - * Suporte para APIde mensagens Anthropic's Claude - * Diversas outras melhorias - -* [Agente Node.js v11.21.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0) - * Suporte para obtenção de IDs de contêineres da APIde metadados do ECS - -* [Agente PHP v10.22.0.12](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12) - - * Fim do suporte para PHP 7.0 e 7.1 - * Diversas correções de bugs - -* [Agente Ruby v9.11.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0) - - * Nova instrumentação para a gema `aws-sdk-sqs` - * Algumas correções de bugs. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index e16818e58b1..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### Novos documentos - -* Adicionado novo recurso sobre [como depurar problemas de agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), incluindo logging detalhado, monitoramento de solicitação de rede e evento de inspeção para melhor resolução de problemas em agentes versões 1.285.0 e superiores. -* Adicionado suporte [ao Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para monitoramento de funções `python` e `.node.js`. -* Adicionamos [um otimizador de computação](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) para fornecer insights acionáveis que visam aprimorar a eficiência computacional, com recursos para identificar ineficiências, oferecer recomendações de otimização e estimar a economia de CCU na plataforma New Relic. -* Adicionada [Inteligência de Custos na Nuvem](/docs/cci/getting-started/overview), oferecendo ferramentas para visibilidade e gerenciamento de custos cloud, incluindo recursos como detalhamentos abrangentes de custos, alocação de custos Kubernetes, estimativa de custos em tempo real e coleta de dados entre contas, atualmente suportando apenas custos da Nuvem da AWS. -* Adicionada [observabilidade OpenTelemetry para Kubernetes com integração independente de provedor de recursos New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para monitoramento contínuo do cluster por meio do gráfico Helm, aprimorando os sinais de telemetria para métricas, eventos e logs transmitidos para as ferramentas e o painel do New Relic. -* Adicionada [limitação e resolução de problemas para integração Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) -* Adicionada integração com AWS via [CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), com suporte à API Polling para serviços não suportados. -* Adicionada [tag aprimorada para banco de dados entidade New Relic ](/docs/infrastructure/host-integrations/db-entity-tags/)para banco de dados entidade monitorada via integração no host para MySQL e MS SQL Server, enriquecendo insights e organização de metadados no New Relic sem afetar o faturamento ou a telemetria existente. - -### Grandes mudanças - -* Adicionadas funções não agregadoras às [referênciasNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/). -* Atualizados os [requisitos do agenteRuby e a estrutura suportada](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/). -* Adicionados logs como evento personalizado New Relic aos [logs do OpenTelemetry no documento New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events). -* Atualizados os tempos de execução com suporte para funções Linux, Windows e em contêineres no documento [Compatibilidade e requisitos para funções Azure instrumentadas](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes). -* Atualizados os dados métricos do [Confluent integração na nuvem](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics). -* O GCP Cloud Run foi removido da [configuração do agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) -* [Compatibilidade e requisitos atualizados para monitoramento de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) para incluir bibliotecas adicionais suportadas pelo agente .NET. -* Adicionado o endpoint dualstack de telemetria New Relic ao [tráfego de redeNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-dualstack-endpoints). -* Adicionado `GcpHttpExternalRegionalLoadBalancerSample` à [integração de monitoramento do Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/). -* Adicionado o procedimento de inicialização do OpenShift sobre como [instalar o documento do gerenciador de tarefas do Sintéticos](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install). -* Atualizada a [versão 12 do agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) -* Adicionada integração perfeita para [AWS com New Relic utilizando CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), incluindo suporte para pesquisa de API. - -### Pequenas mudanças - -* Adicionado `Transaction` como período de retenção para [rastreamento da transação](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/). -* Adicionado `Destination` como uma nova categoria para [Regras e limites de alerta](/docs/alerts/admin/rules-limits-alerts/). -* Foi adicionado um destaque na [Introdução ao documento do Azure Native New Relic Service](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) para garantir que as configurações de diagnóstico nos recursos do Azure estejam configuradas corretamente ou desabilitar o encaminhamento por meio do Azure Native New Relic Service para impedir que dados sejam enviados para a plataforma New Relic. -* Atualizou a última biblioteca compatível para [o agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/). -* Adicionou um aviso no documento [de notas de versão do agente iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) para anunciar que, a partir da versão 7.5.4 do iOS SDK, uma alteração agora resulta no relato de evento Handled Exception suprimido anteriormente. -* Requisitos atualizados para relacionamentos de contêiner de serviço para especificar atributos de recursos para ambientes Kubernetes e `container.id` para ambientes não-Kubernetes, garantindo a configuração de telemetria adequada para [recursosOpenTelemetry no New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/). -* Adicionado suporte CLI para instalação de versão de [agente de infraestrutura específica](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), permitindo implantação consistente e compatibilidade de sistema; especifique a versão usando `@X.XX.X` no nome da receita. -* Foi adicionado um destaque para enfatizar os requisitos de acesso de função para usar os recursos **Manage Account Cardinality**, **Manage Metric Cardinality** e **Create Pruning Rules** na interface; certifique-se de que as permissões estejam definidas no [Gerenciamento de Cardinalidade](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table). -* Atualizada a [compatibilidade e os requisitos para o agente Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) para `v12.23.0`. -* Adicionadas permissões mínimas necessárias para configurar um [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration). -* Atualizou o atributo `FACET` limite máximo de uso aceitável de 5.000 para 20.000 valores para [sintaxe de alerta NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). - -### Notas de versão - -* Anunciado 7 de janeiro de 2026 como a data de fim de vida para as [regras de descarte direcionadas a infraestrutura evento em `SystemSample`, `ProcessSample`, `NetworkSample` e `StorageSample`](/eol/2025/05/drop-rule-filter/) - -* Com efeito imediato, o Fim da Vida Útil do [FACET em messageId e timestamp na condição do alerta](/eol/2025/07/deprecating-alert-conditions/). - -* Anunciado 28 de outubro de 2025 como a data de fim da vida útil do [Attention Required](/eol/2025/07/upcoming-eols/). - -* Confira nossas postagens de Novidades: - - * [Envie notificação diretamente para o Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [O New Relic Compute Optimizer já está disponível para todos!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [Consulta de Logs Cross Account no Unified consulta Explorer](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [O monitoramento do Kubernetes com OpenTelemetry já está disponível!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [O monitoramento de nós do Windows para Kubernetes agora está em versão de visualização pública](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [Identificar problemas de desempenho: filtragem avançada para visualizações de página e Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [Agora você pode classificar pelos erros mais recentes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [Seus dados do navegador, seus termos: Novas opções de controle](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [Análise de consulta profunda para banco de dados agora disponível para todos](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [NRQL Previsões e Alertas Preditivos agora estão disponíveis para o público em geral](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [Convergência APM + OpenTelemetry GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [Integração Agentic para GitHub Copilot e ServiceNow agora disponível para todos](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* Fique por dentro dos nossos últimos lançamentos: - - * [Tempo de execução da API do Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * Corrigidos problemas de vulnerabilidades. - - * [Tempo de execução do Ping v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * Vulnerabilidades de logback-core corrigidas para tempo de execução de ping. - * Vulnerabilidades do servidor jetty corrigidas para tempo de execução de ping. - * Vulnerabilidades corrigidas do Ubuntu para tempo de execução de ping. - - * [Agente Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * Atualizar definição de `BrowserInteraction` e `previousUrl`. - * Adicionado evento de inspeção adicional. - * Valor fixo da API `finished` `timeSinceLoad`. - - * [Integração Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * Ajustes internos corrigidos no backend e relacionados ao CI para compatibilidade futura da plataforma. - - * [Gerenciador de tarefas v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * Corrigido um problema que impedia que certos clientes vissem resultados para alguns monitores com tempos de execução mais longos. - - * [Agente Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * Adicionado suporte para `Azure Function Apps`. - * Arquivos `pb2` corrigidos para habilitar o suporte `protobuf v6`. - - * [Agente Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * Desempenho aprimorado para resolver ANRs ao relatar logs. - * Corrigido um problema para continuar relatando logs após o encerramento do aplicativo. - * Foi resolvido um problema com o monitoramento do estado do aplicativo e a transmissão de dados. - * Poucas violações foram melhoradas ao ativar o modo estrito. - - * [Integração Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * Atualizado `golang.org/x/crypto` para `v0.39.0`. - * Atualizado `go` para `v1.24.4`. - - * [.NET agente v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Adicionado suporte para o Azure Service Bus. - * Erros de compilação do profiler corrigidos com o VS mais recente. - - * [agente PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * Adicionada API de tempo de execução do Composer para ser usada por padrão para detectar pacotes usados pelo aplicativo PHP. - * Corrigido comportamento indefinido na API de tempo de execução do Composer. - - * [Tempo de execução do navegador Node v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * Opções do construtor de cromo atualizadas para o Chrome 131. - - * [Aplicativo móvel para iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * O recurso Ask AI foi aprimorado com uma conexão de soquete mais robusta e confiável, garantindo uma experiência perfeita. - - * [Aplicativo móvel para Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * O recurso Ask AI foi aprimorado com uma conexão de soquete mais robusta e confiável, garantindo uma experiência perfeita. - - * [Agente Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * Adicionado suporte para streaming `openai` v5. - * Adicionado suporte para api `openai.responses.create`. - * Corrigido o log de erro para cabeçalho tracestate indefinido. - - * [agente de infraestrutura v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * Dependência atualizada `newrelic/nri-winservices` para `v1.2.0` - * tag do docker alpina atualizada para `v3.22` - - * [agente de infraestrutura v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * atualizar dependência `newrelic/nri-flex` para `v1.16.6` - - * [Agente Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * Corrigida a precedência da condição de corrida do atributo personalizado. - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * Aumentou o núcleo beta do OTEL para `v0.128.0` - - * [Agente de mídia para HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * Foi introduzido um novo tipo de evento. - * O tipo de evento `PageAction` foi descontinuado. - - * [Agente de mídia para HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * Publicação npm habilitada para o pacote, garantindo fácil acessibilidade e distribuição. - * As compilações `cjs`, `esm` e `umd` foram adicionadas à pasta `dist`, garantindo compatibilidade com os formatos de módulo CommonJS, ES Modules e UMD. - - * [Agente de mídia para Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * Foi introduzido um novo tipo de evento. - * O tipo de evento `RokuVideo` foi descontinuado. - * O tipo de evento `RokuSystem` foi descontinuado. - - * [Agente de mídia para Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * Renomeado `errorName` com `errorMessage`, pois `errorName` foi descontinuado. - - * [Gerenciador de tarefas v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * Atualização de imagem base fixa de `ubuntu 22.04` para `ubuntu 24.4` - - * [Tempo de execução do Ping v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * Atualização da imagem base aprimorada de `ubuntu 22.04` para `ubuntu 24.04` - - * [Kubernetes integração v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * Adicionado suporte para monitoramento de nós Windows no cluster do Kubernetes. - - * [Aplicativo móvel para Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * Bug corrigido e interface de usuário melhorada para uma experiência mais suave. - - * [Agente Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * Adicionada a capacidade de gerar relatórios apenas sobre os intervalos de entrada e saída. - * Adicionado suporte ao Node.js 24. - * Relatório de compatibilidade atualizado. - - * [Tempo de execução da API do Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * Corrigidas as vulnerabilidades para `CVE-2024-39249` - - * [Aplicativo móvel para iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * O recurso Ask AI foi aprimorado com prompt dinâmico. - - * [Agente Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * Adicionada mensagem interna **para tarefas longas**. - * Resolvido o problema que impedia que o rastreamento distribuído fosse desabilitado. - - * [Tempo de execução do navegador Node v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * Imagem base atualizada - - * [Agente Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Metadados vinculados para serviços de aplicativos Azure. - * Removido `MonoFlatMapMain` instrumentação. - - * [Agente Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Implementado limite de tamanho de valor de atributo configurável - * Relatório de compatibilidade atualizado. - - * [Integração Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * Atualizar a versão do gráfico kube-state-métrica de `5.12.1` para `5.30.1` - - * [Agente iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * Corrigido um problema que poderia fazer com que distributed tracing não tivesse todas as informações de conta necessárias no início de uma sessão. - - * [Aplicativo móvel para Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * Feedback aprimorado com renderização dinâmica da interface do usuário. - - * [Aplicativo móvel para Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * Corrigimos bugs e atualizamos os sinalizadores do Teams GA para uma melhor experiência do usuário. - - * [Go agente v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * Utilização revertida. Voltar para a versão v3.39.0 devido a bug de deadlock - * Removidos os testes awssupport\_test.go que adicionavam dependência direta ao módulo go - - * [Agente Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * Melhorou o agente nativo do Android atualizado para a versão 7.6.7 - * Melhorou o agente nativo do iOS atualizado para a versão 7.5.6 - - * [Agente Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Suporte abandonado para Node.js 18 - * Versão mínima suportada atualizada para `fastify` para 3.0.0, `pino` para 8.0.0 e `koa-router` para 12.0.0 - - * [Agente Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * Corrigido o relatório previousUrl vazio como indefinido - - * [agente de infraestrutura v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * Atualizou a dependência `newrelic/nri-prometheus` para v2.26.2 - - * [Aplicativo móvel para iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * Feedback aprimorado com renderização dinâmica da interface do usuário. - - * [Agente Android NDK v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * Adicionado suporte para tamanho de página de 16 KB - - * [agente de infraestrutura v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Alça de processo do Windows alterada. - * Colidiu `nri-docker` para `v2.5.1`, `nri-prometheus` para `v2.26.1` - - * [.NET agente v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Adicionado suporte para tópicos no Azure Service Bus - - * [Agente Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * Instrumento fixo AWS Bedrock Converse API - - * [Agente Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Implementado limite de tamanho de valor de atributo configurável - * Relatório de compatibilidade atualizado - - * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * Erros corrigidos relacionados ao GLIBC, como `/lib64/libc.so.6: version 'GLIBC_2.34'` não encontrado, foram resolvidos \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx deleted file mode 100644 index bb27fecde7e..00000000000 --- a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-11-13' -version: 1.303.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Allow consent API to be invoked without localStorage access - - Allow nested registrations - - Additional validation to prepare agent for MFE registrations - - Add measure support to register API - - Add useConsentModel functionality - - Retry initial connect call - - Add custom event support to register API - - SMs for browser connect response -bugs: - - Obfuscate custom attributes for logs added after PVE - - memoize promise context propagation to avoid safari hangs -security: [] -translationType: machine ---- - -## v1.303.0 - -### Recurso - -#### Permitir que a API de consentimento seja invocada sem acesso ao localStorage. - -Permite que a API de consentimento funcione sem exigir acesso ao localStorage, mantendo um estado comum no agente que controla as coletas. O aplicativo deve invocar a API a cada carregamento de página complexo quando o acesso ao localStorage estiver bloqueado. - -#### Permitir registros aninhados - -Para facilitar as relações inerentes de pai-filho com a API de registro planejada, permita que a entidade registrada exponha sua própria API `.register()` para que os filhos dessa entidade se registrem. entidade que se cadastrar no contêiner agente será vinculada ao contêiner. entidade que se registrar sob outra entidade cadastrada estará relacionada tanto ao contêiner quanto à entidade controladora. - -#### Validação adicional para preparar o agente para os registos MFE - -Adicionando regras de validação no agente para evitar valores inválidos para MFE destino `id` e `name` em suporte a registros MFE/v2. - -#### Adicionar suporte a medidas à API de registro - -Adiciona suporte à API de medição no objeto de resposta de registro. Isso visa dar suporte à futura oferta de micro front-ends planejada. - -#### Adicionar funcionalidade useConsentModel - -Adiciona a propriedade e funcionalidade de inicialização use\_consent\_mode. Adiciona a chamada de API consent(). O modelo de consentimento, se ativado, impede a coleta de dados pelo agente, a menos que o consentimento seja dado por meio da chamada de API consent(). - -#### Tente novamente a chamada de conexão inicial. - -Para ajudar a evitar a perda de dados, o agente agora tentará novamente a chamada "RUM" original uma vez extra para códigos de status que permitam nova tentativa. - -#### Adicionar suporte a eventos personalizados para registrar API - -Adiciona métodos para capturar eventos personalizados à API de registro, para serem usados posteriormente quando o suporte a MFE for estabelecido. - -#### SMs para resposta de conexão do navegador - -Adiciona a métrica de suporte para respostas com falha na inicialização do agregado page\_view\_event. - -### Correções de bugs - -#### Ofuscar atributo personalizado para logs adicionados após PVE - -Estende a ofuscação para cobrir o atributo personalizado no registro de eventos adicionados após a colheita inicial RUM/PageViewEvent. - -#### memoize promessa de propagação de contexto para evitar travamentos no safari - -Memoriza promessas de contexto para evitar possíveis travamentos do browser no Safari, evitando operações de contexto repetidas. - -## Declaração de apoio - -New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem [ao fim de sua vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). As datas de lançamento refletem a data de publicação original da versão do agente. - -Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este [dashboard de status](https://newrelic.github.io/newrelic-browser-agent-release/) para obter mais informações. - -Em conformidade com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão 1.303.0 do navegador agente foi desenvolvida e testada nos seguintes navegadores e faixas de versão: Chrome 131-141, Edge 131-141, Safari 17-26 e Firefox 134-144. Para dispositivos móveis, a versão 1.303.0 foi compilada e testada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx deleted file mode 100644 index 505dc3c6915..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-rc1.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-11-17' -version: rc1.3 -translationType: machine ---- - -### Melhorias - -* Atualizei o navegador Chrome para a versão 142. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx deleted file mode 100644 index 664bd9ed387..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.58.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-11-12' -version: 1.58.0 -translationType: machine ---- - -### Melhorias - -Foram corrigidas vulnerabilidades relacionadas ao Ubuntu e ao Java para solucionar problemas de segurança no ambiente de execução do Ping. Abaixo estão as CVEs do Java corrigidas. - -* CVE-2025-5115 -* CVE-2025-11226 \ No newline at end of file diff --git a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx b/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx deleted file mode 100644 index eeb440445ab..00000000000 --- a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/communication.mdx +++ /dev/null @@ -1,652 +0,0 @@ ---- -title: Ações de comunicação -tags: - - workflow automation - - workflow - - workflow automation actions - - communication actions - - slack actions - - ms teams actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse! - - Atualmente, esse recurso é fornecido como parte de um programa de visualização de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página fornece uma referência completa para as ações de comunicação disponíveis no catálogo de ações de automação de fluxo de trabalho. Essas ações permitem que você integre a plataforma de comunicação às suas definições de fluxo de trabalho, incluindo o envio de mensagens para canais do Slack, a recuperação de reações e muito mais. - -## Pré-requisitos - -Antes de usar ações de comunicação na automação de fluxo de trabalho, certifique-se de ter: - -* Um espaço de trabalho do Slack com as permissões apropriadas. -* Um token de bot do Slack configurado como um segredo na automação de fluxo de trabalho. -* Acesso aos canais do Slack onde você deseja enviar mensagens. - -Consulte a seção [Adicionar configuração do Slack](/docs/autoflow/overview#add-the-slack-integration) para obter informações sobre como configurar a integração com o Slack. - -## Ações do Slack - - - - Envia uma mensagem para um canal do Slack, com a opção de anexar um arquivo. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Exemplo -
- **token** - - Obrigatório - - segredo - - `${{ :secrets:slackToken }}` -
- **canal** - - Obrigatório - - corda - - `my-slack-channel` -
- **texto** - - Obrigatório - - corda - - `Hello World!` -
- **threadTs** - - Opcional - - corda - - `.` -
- **anexo** - - Opcional - - map - -
- **anexo.nome do arquivo** - - Obrigatório - - corda - - `file.txt` -
- **anexo.conteúdo** - - Obrigatório - - corda - - `Hello\nWorld!` -
- - - * **token**: O token do bot do Slack a ser usado. Isso deve ser passado como uma sintaxe secreta. Consulte a seção [Adicionar configuração do Slack](/docs/autoflow/overview#add-the-slack-integration) para obter instruções sobre como configurar um token. - * **channel**: O nome do canal, ou um ID de canal, para enviar a mensagem. Consulte [a API do Slack](https://api.slack.com/methods/chat.postMessage#arg_channel/) para obter mais informações. - * **text**: A mensagem a ser postada no Slack no `channel` especificado. - * **threadTs**: carimbo de data/hora pertencente à mensagem principal, usado para criar uma resposta em uma thread. - * **attachment**: Permite anexar um arquivo com uma mensagem no `channel` especificado. - * **attachment.filename**: Especifique o nome do arquivo que será carregado no Slack. - * **attachment.content**: O conteúdo do arquivo a ser carregado está em UTF-8. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **threadTs** - - corda - - `.` -
- **ID do canal** - - corda - - `` -
- - - * **threadTs**: carimbo de data/hora da mensagem. Pode ser usado em futuras chamadas postMessage para postar uma resposta em um tópico. - * **channelID**: ID do canal onde a mensagem foi postada. - - - - - **Exemplo 1: Publicar uma mensagem em um canal do Slack** - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: SendMessage - - steps: - - name: send_slack_message - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: ${{ .workflowInputs.channel }} - text: ${{ .workflowInputs.text }} - ``` - - **Entradas esperadas:** - - ```json - { - "inputs": [ - { - "key" : "channel", - "value" : "my-channel" - }, - { - "key" : "text", - "value" : "This is my message *with bold text* and `code backticks`" - } - ] - } - ``` - - **Resultado esperado:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - **Exemplo 2: Anexar um arquivo** - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: SendFileMessage - - steps: - - name: postCsv - type: action - action: slack.chat.postMessage - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channel: my-channel - text: "Please find the attached file:" - attachment: - filename: 'file.txt' - content: "Hello\nWorld!" - ``` - - **Resultado esperado:** - - ```json - [ - { - "threadTs": "1718897637.400609", - "channelID": "C063JK1RHN1" - } - ] - ``` -
- - - - - - - - - Receba uma reação a uma mensagem de um canal do Slack. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Exemplo -
- **token** - - Obrigatório - - segredo - - `${{ :secrets:slackToken }}` -
- **ID do canal** - - Obrigatório - - corda - - `C063JK1RHN1` -
- **Tempo esgotado** - - Opcional - - int - - 60 -
- **threadTs** - - Obrigatório - - corda - - `.` -
- **seletores** - - Opcional - - list - - `[{\"name\": \"reactions\", \"expression\": \".reactions \"}]` -
- - - * **token**: O token do bot do Slack a ser usado. Isso deve ser passado como uma sintaxe secreta. Consulte a seção [Adicionar configuração do Slack](/docs/autoflow/overview#add-the-slack-integration) para obter instruções sobre como configurar um token. - * **channelID**: O ID do canal para receber as reações às mensagens. - * **timeout**: O tempo em segundos que se deve esperar por qualquer reação. O valor padrão é 60 segundos, o máximo permitido é 600 segundos (10 minutos). - * **threadTs**: carimbo de data/hora pertencente à mensagem, usado para obter a reação a essa mensagem. - * **selectors**: Os seletores para obter apenas o parâmetro especificado como saída. - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **reações** - - list - - `` -
- - - * **reactions**: Lista de elementos com todas as reações registradas ou uma lista vazia caso tenha ocorrido um tempo limite. - - - - - **Exemplo 1: Slack recebe reações** - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: GetReactions - - steps: - - name: getReactions - type: action - action: slack.chat.getReactions - version: 1 - inputs: - token: ${{ :secrets:slackToken }} - channelID: ${{ .steps.promptUser.outputs.channelID }} - threadTs: ${{ .steps.promptUser.outputs.threadTs }} - timeout: ${{ .workflowInputs.timeout }} - selectors: ${{ .workflowInputs.selectors }} - ``` - - **Entradas esperadas:** - - ```json - { - "inputs": [ - { - "key" : "channelID", - "value" : "C063JK1RHN1" - }, - { - "key" : "threadTs", - "value" : "1718897637.400609" - }, - { - "key" : "selectors", - "value" : "[{\"name\": \"reactions\", \"expression\": \".reactions \"}]" - } - ] - } - ``` - - **Resultado esperado:** - - ```json - [ - { - "name": "grinning", - "users": [ - "W222222" - ], - "count": 1 - }, - { - "name": "question", - "users": [ - "W333333" - ], - "count": 1 - } - ] - ``` - - Ou, se o tempo limite tiver expirado: - - ```json - [] - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx b/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx deleted file mode 100644 index 4d9cad0e3b5..00000000000 --- a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/http.mdx +++ /dev/null @@ -1,1043 +0,0 @@ ---- -title: Ações HTTP -tags: - - workflow automation - - workflow - - workflow automation actions - - HTTP actions -metaDescription: A list of available HTTP actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse! - - Atualmente, esse recurso é fornecido como parte de um programa de visualização de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página fornece uma referência completa para as ações HTTP disponíveis no catálogo de ações de automação de fluxo de trabalho. Essas ações permitem que você faça requests HTTP (GET, POST, PUT, DELETE) para APIs e serviços externos como parte das suas definições de fluxo de trabalho. - -## Pré-requisitos - -Antes de usar ações HTTP na automação de fluxo de trabalho, certifique-se de ter: - -* endpointde destino de URLs API. -* Quaisquer credenciais de autenticação necessárias (chave de API, token, etc.). -* Compreensão dos formatos de requisição/resposta da API. - - - As ações HTTP suportam sintaxe secreta para qualquer valor de cabeçalho, permitindo que você passe dados sensíveis com segurança, como a chave de API. Consulte [a seção de gerenciamento de segredos](/docs/infrastructure/host-integrations/installation/secrets-management/) para obter mais informações. - - -## Ações HTTP - - - - Realize uma chamada HTTP GET para recuperar dados de um endpointda API. - - - Isso permite o uso de sintaxe secreta para qualquer valor de cabeçalho. - - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Descrição -
- **url** - - Obrigatório - - Corda - - A URL de destino da solicitação. O esquema deve ser incluído: - - `https://example.com` -
- **parâmetros da URL** - - Opcional - - Mapa - - O parâmetro de consulta deve ser adicionado à URL. Recebe um objeto JSON em formato de string. -
- **cabeçalhos** - - Opcional - - Mapa - - Os cabeçalhos a serem adicionados à solicitação. Recebe um objeto JSON em formato de string. -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter apenas o parâmetro especificado como saída. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Descrição -
- **respostaCorpo** - - Corda - - O corpo da resposta. -
- **código de status** - - Inteiro - - O código de status HTTP da resposta. -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: httpGetTest - description: 'Performs an HTTP GET request to retrieve data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - steps: - - name: query - type: action - action: http.get - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - next: end - ``` - - **Exemplos de entradas:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}" - } - ``` - - **Exemplos de saída:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - - - Executa uma chamada HTTP POST para enviar dados para um endpointda API. - - - Isso permite o uso de sintaxe secreta para qualquer valor de cabeçalho. - - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Descrição -
- **url** - - Obrigatório - - Corda - - A URL de destino da solicitação. O esquema deve ser incluído: - - `https://example.com` -
- **parâmetros da URL** - - Opcional - - Mapa - - O parâmetro de consulta deve ser adicionado à URL. Recebe um objeto JSON em formato de string. -
- **cabeçalhos** - - Opcional - - Mapa - - Os cabeçalhos a serem adicionados à solicitação. Recebe um objeto JSON em formato de string. -
- **corpo** - - Opcional - - Corda - - O corpo da requisição. -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter apenas o parâmetro especificado como saída. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Descrição -
- **respostaCorpo** - - Corda - - O corpo da resposta. -
- **código de status** - - Inteiro - - O código de status HTTP da resposta. -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: httpPostTest - description: 'Performs an HTTP POST request to send data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - steps: - - name: query - type: action - action: http.post - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - next: end - ``` - - **Exemplos de entradas:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}" - } - ``` - - **Exemplos de saída:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Executa uma solicitação HTTP PUT para atualizar dados em um endpointda API. - - - Se você precisar passar dados sensíveis para uma entrada, por exemplo um cabeçalho `Api-Key`, você pode usar valores armazenados por meio da mutação [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) do NerdGraph. - - Exemplo: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Descrição -
- **url** - - Obrigatório - - Corda - - A URL de destino da solicitação. O URL deve incluir o esquema (por exemplo, https:// ou http://). Exemplo: - - `https://example.com` -
- **parâmetros da URL** - - Opcional - - Mapa - - O parâmetro de consulta deve ser adicionado à URL. Recebe um objeto JSON em formato de string. -
- **cabeçalhos** - - Opcional - - Mapa - - Os cabeçalhos a serem adicionados à solicitação. Recebe um objeto JSON em formato de string. -
- **corpo** - - Opcional - - Corda - - O corpo da requisição. -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter apenas o parâmetro especificado como saída. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Descrição -
- **respostaCorpo** - - Corda - - O corpo da resposta. -
- **código de status** - - Inteiro - - O código de status HTTP da resposta. -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: httpPutTest - description: 'Performs an HTTP PUT request to update data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - body: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.put - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - body: ${{ .workflowInputs.body }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Exemplos de entradas:** - - ```json - { - "url": "https://example.com", - "headers": "{\"Content-Type\":\"application/json\"}", - "urlParams": "{\"foo\": \"bar\"}", - "body": "{\"foo\": \"bar\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Exemplos de saída:** - - ```json - { - "responseBody": "", - "statusCode": 200 - } - ``` -
- - - - - - - Executa uma solicitação HTTP DELETE para remover dados em um endpointda API. - - - Se você precisar passar dados sensíveis para uma entrada, por exemplo um cabeçalho `Api-Key`, você pode usar valores armazenados por meio da mutação [secretsManagementCreateSecret](https://one.newrelic.com/nerdgraph-graphiql) do NerdGraph. - - Exemplo: - - ```json - { - "headers": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}" - } - ``` - - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Descrição -
- **url** - - Obrigatório - - Corda - - A URL de destino da solicitação. O URL deve incluir o esquema (por exemplo, https:// ou http://). Exemplo: - - `https://example.com` -
- **parâmetros da URL** - - Opcional - - Mapa - - O parâmetro de consulta deve ser adicionado à URL. Recebe um objeto JSON em formato de string. -
- **cabeçalhos** - - Opcional - - Mapa - - Os cabeçalhos a serem adicionados à solicitação. Recebe um objeto JSON em formato de string. -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter apenas o parâmetro especificado como saída. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Descrição -
- **respostaCorpo** - - Corda - - O corpo da resposta. -
- **código de status** - - Inteiro - - O código de status HTTP da resposta. -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: httpDeleteTest - description: 'Performs an HTTP DELETE request to remove data' - workflowInputs: - url: - type: String - urlParams: - type: String - headers: - type: String - selectors: - type: String - steps: - - name: query - type: action - action: http.delete - version: '1' - inputs: - url: ${{ .workflowInputs.url }} - urlParams: ${{ .workflowInputs.urlParams }} - headers: ${{ .workflowInputs.headers }} - selectors: ${{ .workflowInputs.selectors }} - next: end - ``` - - **Exemplos de entradas:** - - ```json - { - "url": "https://example.com", - "urlParams": "{\"foo\": \"bar\"}", - "headers": "{\"baz\": \"bat\"}", - "selectors": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]" - } - ``` - - **Exemplos de saída:** - - ```json - { - "responseBody": "\n...\n", - "statusCode": 200 - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx b/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx deleted file mode 100644 index 15ef0c5097e..00000000000 --- a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic.mdx +++ /dev/null @@ -1,1910 +0,0 @@ ---- -title: Ações da New Relic -tags: - - workflow automation - - workflow - - workflow automation actions - - New relic actions -metaDescription: A list of available actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - - - Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse! - - Atualmente, esse recurso é fornecido como parte de um programa de visualização de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Esta página fornece uma referência completa das ações do New Relic disponíveis no catálogo de ações de automação de fluxo de trabalho. Essas ações permitem integrar recursos da plataforma New Relic em suas definições de fluxo de trabalho, incluindo envio de eventos personalizados e logs, execução de consulta NerdGraph, execução de consulta NRQL e envio de notificação. - -## Pré-requisitos - -Antes de usar as ações New Relic na automação do fluxo de trabalho, certifique-se de ter: - -* Uma conta New Relic com as permissões apropriadas. -* Uma chave de licença do New Relic (caso esteja enviando dados para uma conta diferente). -* As permissões necessárias para os serviços específicos do New Relic que você planeja usar. - -Consulte [chave de licença](/docs/apis/intro-apis/new-relic-api-keys/#license-key) para obter informações sobre como criar e gerenciar sua conta New Relic chave de licença. - -## Ações de ingestão de dados - - - - Envia um evento personalizado para New Relic - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Exemplo -
- **atributo** - - Opcional - - Mapa - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **eventos** - - Obrigatório - - list - - `"[{\"eventType\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"eventType\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]` -
- **chave de licença** - - Opcional - - corda - - `"{{ .secrets.secretName }}"` -
- **seletores** - - Opcional - - list - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Atributo comum que faz parte de todos os eventos quando fornecido. A fusão de cada item de evento, quando necessário, substitui a definição comum. - * **events**: A lista de dados do evento. Observe que o evento requer o uso de um campo `eventType` que representa o tipo personalizado do evento e o número máximo de eventos permitidos por solicitação é 100. - * **licenseKey**: A chave de licença da conta New Relic que especifica a conta de destino para onde os eventos são enviados. Caso esse valor não seja fornecido, será assumida uma chave de licença padrão com base na conta que executa o fluxo de trabalho. - * **selectors**: Os seletores para obter apenas o parâmetro especificado como saída. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **sucesso** - - Boleano - - `true` -
- **mensagem de erro** - - corda - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: heartbeat_newrelicIngestSendEvents - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendEvents - version: 1 - inputs: - attributes: - colour: red - id: 1234 - events: - - eventType: HeartBeat - test: "OK" - attributes: - foo: bar - - eventType: HeartBeat1234 - test: "OK1234" - attributes: - foo: bar - - eventType: HeartBeat12345 - test: "OK12345" - attributes: - foo: bar - colour: yellow - - eventType: HeartBeat12345678 - test: "OK12345678" - selectors: - - name: success - expression: ".success" - ``` - - **Resultado esperado:** - - ```yaml - { - "success": true - } - ``` - - **Recuperar evento:** - - Após executar um fluxo de trabalho com sucesso, você pode recuperar o evento associado executando uma consulta na conta que executou o fluxo de trabalho: - - ```sql - SELECT * FROM HeartBeat - ``` -
- - - - - - - - - Enviar registro para New Relic - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo - - Exemplo -
- **atributo** - - Opcional - - map - - `"{\"page\": \"1\", \"limit\": \"10\"}"` -
- **logs** - - Obrigatório - - list - - `"[{\"message\":\"XYZ\",\"attributes\":{\"foo\":\"bar\"}}, {\"message\":\"ABC\",\"value\":\"1234\",\"attributes\":{\"color\":\"red\"}}]"` -
- **chave de licença** - - Opcional - - corda - - `"{{ .secrets.secretName }}"` -
- **seletores** - - Opcional - - list - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - * **attributes**: Atributo comum incluído em todos os logs quando fornecido. Se um item de log especificar o mesmo atributo, ele substituirá a definição comum. - * **logs**: A lista de dados de logs. Observe que o número máximo de logs permitidos por solicitação é 100. - * **licenseKey**: A chave de licença da conta New Relic que especifica a conta de destino para onde os logs são enviados. Caso não seja fornecida, será assumida uma chave de licença padrão com base na conta que executa o fluxo de trabalho. Consulte [a chave de licença](/docs/apis/intro-apis/new-relic-api-keys/#license-key) para obter mais informações. - * **selectors**: Os seletores para obter apenas o parâmetro especificado como saída. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **sucesso** - - Boleano - - `true` -
- **mensagem de erro** - - corda - - `"Error message if operation failed"` -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: heartbeat_newrelicIngestSendLogs - - workflowInputs: - cellName: - type: String - - steps: - - name: runAction - type: action - action: newrelic.ingest.sendLogs - version: 1 - inputs: - attributes: - colour: red - id: 1234 - logs: - - message: 'Heartbeat sendLogs Action Test Message' - attributes: - foo: bar - - message: 'HeartBeat1234' - attributes: - foo: bar - - message: 'HeartBeat12345' - attributes: - foo: bar - colour: yellow - - message: 'HeartBeat12345678' - selectors: - - name: success - expression: ".success" - ``` - - **Resultado esperado:** - - ```yaml - { - "success": true - } - ``` - - **Recuperar logs:** - - Após executar um fluxo de trabalho com sucesso, você pode recuperar o log associado executando uma consulta na conta que executou o fluxo de trabalho: - - ```sql - SELECT * FROM Log - ``` -
- - - - - - -## Ações do NerdGraph - - - - Executa um comando GraphQL na API NerdGraph do New Relic. O comando pode ser uma consulta ou uma mutação. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo - - Descrição - - Exemplo -
- **graphql** - - Obrigatório - - corda - - Uma sintaxe GraphQL. Você deve usar o GraphiQL para construir e testar seu comando. - -
- **variáveis** - - Obrigatório - - map[string]any - - Quaisquer variáveis de par principal-valor para usar com a instrução GraphQL. - -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter como saída apenas o parâmetro especificado. - - ```yaml - steps: - - name: findingVar - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query GetEntity($entityGuid: EntityGuid!) { - actor { - entity(guid: $entityGuid) { - alertSeverity - } - } - } - variables: - entityGuid: ${{ .workflowInputs.entityGuid }} - - name: findingInline - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - { - actor { - entity(guid: "${{ .workflowInputs.entityGuid }}") { - alertSeverity - } - } - } - selectors: - - name: entities - expression: '.data' - ``` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Saída - - Tipo - - Descrição -
- **dados** - - map[string]any - - Conteúdo da propriedade - - `data` - - de uma resposta do NerdGraph. -
- **sucesso** - - Boleano - - Status of the request.s -
- **mensagem de erro** - - Corda - - Motivo da falha como mensagem. -
- - - - - - - - - - - - - - - -
- Exemplo -
- ```yaml - steps: - - name: currentUserId - type: action - action: newrelic.nerdgraph.execute - version: 1 - inputs: - graphql: | - query userId { - currentUser { - id - } - } - - name: sayHello - type: action - action: example.messaging.sayHello - version: 1 - inputs: - name: ${{ .steps.currentUserId.outputs.data.currentUser.id }} - ``` -
- - - - - - -## Ações de consulta - - - - Executa uma consulta NRQL entre contas através da API do NerdGraph. - - - - - Entradas - - - - Saídas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo - - Descrição - - Exemplo -
- **consulta** - - Obrigatório - - corda - - A instrução de consulta NRQL. - -
- **IDs da conta** - - Opcional - - lista de inteiros - - O campo - - **New Relic Account ID** - - é uma lista de IDs de destino que permite especificar as contas de destino nas quais a consulta será executada. Caso esse valor não seja fornecido como entrada, a consulta será executada automaticamente na conta associada à conta de execução do fluxo de trabalho. - -
- **seletores** - - Opcional - - list - - Os seletores permitem obter como saída apenas o parâmetro especificado. - - ```json - steps: - - name: queryForLog - type: action - action: newrelic.nrdb.query - version: 1 - inputs: - accountIds: [12345] - query: FROM Log SELECT * WHERE message LIKE 'DEMO%' - selectors: - - name: resultsAsString - expression: '.results | tostring' - ``` -
- - - - - - - - - - - - - - - - - - - - - -
- Saída - - Tipo - - Exemplo -
- **results** - - : Uma matriz de objetos contendo os resultados da consulta. - - - - ```yaml - { - results=[ - { message=[INFO] - Workflow: test has ended, messageId=39af98 }, - { message=[INFO] - Workflow: test - Step query has started, messageId=649c612 }, - ... - ] - } - ``` -
- - - - - - -## ações de notificação - - - - Envia uma mensagem para um canal, integrado com destinos, por exemplo, o Slack. - - - - - Entradas - - - - Saídas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo - - Descrição - - Exemplo -
- **tipo** - - Obrigatório - - corda - - Tipo de destino do New Relic - - `slack` -
- **id de destino** - - Obrigatório - - Corda - - DestinationId associado ao destino New Relic. - - `123e4567-e89b-12d3-a456-426614174000` -
- **parâmetro** - - Obrigatório - - map - - Campos obrigatórios para enviar notificação ao tipo de destino escolhido. - - `{\"channel\": \"${{ YOUR_CHANNEL }}\", \"text\": \"Enter your text here\"}` -
- **seletores** - - Opcional - - list - - Os seletores permitem obter como saída apenas o parâmetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - -
- Saída - - Tipo - - Exemplo -
- sucesso - - boleano - - `true/false` -
- - - - - - - - - Envia uma mensagem para um canal do Microsoft Teams, integrado com destinos. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo de dados - - Descrição - - Exemplo -
- **id de destino** - - Obrigatório - - Corda - - DestinationId associado ao destino New Relic. - - Consulte [a integração do New Relic com o Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) para obter instruções sobre como configurar um novo destino e listar os IDs de destino. - - Consulte a [seção Destinos](/docs/alerts/get-notified/destinations/) para saber mais sobre os destinos. - - - - ```sh - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: MICROSOFT_TEAMS, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **teamName** - - Obrigatório - - Corda - - Nome da equipe associada ao ID de destino fornecido - - `TEST_TEAM` -
- **channelName** - - Obrigatório - - Corda - - Nome do canal para onde a mensagem deve ser enviada. - - `StagingTesting` -
- **mensagem** - - Obrigatório - - Corda - - Mensagem de texto que precisa ser enviada - - `Hello! this message from Workflow` -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter como saída apenas o parâmetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **sucesso** - - Boleano - - `true/false` -
- **sessionId** - - Corda - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **mensagem de erro** - - Corda - - `Message is a required field in the notification send"` -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: msTeam_notification_workflow - description: This is a test workflow to test MSTeam notification send action - steps: - - name: SendMessageUsingMSTeam - type: action - action: newrelic.notification.sendMicrosoftTeams - version: 1 - inputs: - destinationId: acc24dc2-d4fc-4eba-a7b4-b3ad0170f8aa - channel: DEV_TESTING - teamName: TEST_TEAM_DEV - message: Hello from Workflow - ``` -
- - - - - - - - - Envia um e-mail para destinatários de e-mail do New Relic com ou sem anexos. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de entrada - - Opcionalidade - - Tipo de dados - - Descrição - - Exemplo -
- **id de destino** - - Obrigatório - - Corda - - DestinationId associado ao destino New Relic. - - Consulte [a integração do New Relic com o Microsoft Teams](/docs/alerts/get-notified/microsoft-teams-integrations/) para obter instruções sobre como configurar um novo destino e listar os IDs de destino. - - Consulte a [seção Destinos](/docs/alerts/get-notified/destinations/) para saber mais sobre os destinos. - - - - ```yaml - { - actor { - account(id: 12345678) { - aiNotifications { - destinations(filters: {type: EMAIL, active: true}) { - entities { - createdAt - id - name - active - } - } - } - } - } - } - ``` - - - - `123e4567-e89b-12d3-a456-426614174000` -
- **assunto** - - Obrigatório - - Corda - - Assunto do e-mail - - `workflow-notification` -
- **mensagem** - - Obrigatório - - Corda - - Mensagem que precisa ser enviada por e-mail - - `Hello! from Workflow Automation` -
- **anexos** - - Opcional - - Lista - - Lista de anexos opcionais - -
- **attachment.type** - - Obrigatório - - Enum - - Um dos seguintes: - - `QUERY` - - , - - `RAW` - -
- **attachment.query** - - Opcional - - Corda - - Para o tipo - - `QUERY` - - , esta é uma instrução de consulta NRQL. - - `SELECT * FROM LOG` -
- *attachment.accountIds* - - \* - - Opcional - - Lista - - Para - - `QUERY` - - , os - - **New Relic Account IDs** - - para executar a consulta. Caso não seja fornecida, será utilizada a conta associada à execução do fluxo de trabalho. - - `[12345567]` -
- **attachment.format** - - Opcional - - Enum - - Para - - `QUERY` - - , especifique o tipo para os resultados, padrão - - `JSON` - - `JSON CSV` -
- **anexo.conteúdo** - - Opcional - - Corda - - Para - - `RAW` - - , este é o conteúdo do anexo em UTF-8. - - `A,B,C\n1,2,3` -
- **anexo.nome do arquivo** - - Opcional - - Corda - - Um nome de arquivo para o anexo. - - `log_count.csv` -
- **seletores** - - Opcional - - Lista - - Os seletores permitem obter como saída apenas o parâmetro especificado. - - `[{\"name\": \"success\", \"expression\": \".success\"},{\"name\": \"attachments\", \"expression\": \".response.attachments\"},{\"name\": \"sessionId\", \"expression\": \".response.sessionId\"}]` -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo de saída - - Tipo - - Exemplo -
- **sucesso** - - Boleano - - `true/false` -
- **sessionId** - - Corda - - `"sessionId": "7fa97f26-3791-492e-a39b-53793163dfb9"` -
- **mensagem de erro** - - Corda - - `Channel is a required field in the notification send"` -
- **anexos** - - Lista - - ```yaml - [{ - "blobId": "43werdtfgvhiu7y8t6r5e4398yutfgvh", - "rowCount": 100 - }] - ``` -
- - - - - - - - - - - - - - - -
- Exemplo de fluxo de trabalho -
- ```yaml - name: email_testing_with_attachment - description: Workflow to test sending an email notification via NewRelic with log step - workflowInputs: - destinationId: - type: String - steps: - - name: sendEmailNotification - type: action - action: newrelic.notification.sendEmail - version: '1' - inputs: - destinationId: ${{ .workflowInputs.destinationId }} - subject: "workflow notification" - message: "Workflow Email Notification Testing from local" - attachments: - - type: QUERY - query: "SELECT * FROM Log" - format: JSON - filename: "log_count.json" - selectors: - - name: success - expression: '.success' - - name: sessionId - expression: '.response.sessionId' - - name: attachments - expression: '.response.attachments' - - name: logOutput - type: action - action: newrelic.ingest.sendLogs - version: '1' - inputs: - logs: - - message: "Hello from cap check Testing staging server user2 : ${{ .steps.sendEmailNotification.outputs.result.attachments }}" - licenseKey: ${{ :secrets:STAGING_NEW_RELIC_LICENSE_KEY }} - ``` -
- - - - - \ No newline at end of file diff --git a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx b/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx deleted file mode 100644 index c723ac5f26e..00000000000 --- a/src/i18n/content/pt/docs/workflow-automation/setup-and-configuration/actions-catalog/others.mdx +++ /dev/null @@ -1,634 +0,0 @@ ---- -title: Ações de utilidade -tags: - - workflow automation - - workflow - - workflow automation actions - - utility actions -metaDescription: A list of available utility actions in the actions catalog for workflow definitions -freshnessValidatedDate: never -translationType: machine ---- - -Esta página fornece uma referência para as ações de utilitário disponíveis no catálogo de ações de automação de fluxo de trabalho. Essas ações permitem que você execute operações comuns de transformação de dados e utilitários em suas definições de fluxo de trabalho. - -## Ações de utilidade - - - - Esta ação é usada para transformar um timestamp Unix (ou timestamp da época) em data/hora. Possíveis referências: - - * [https://en.wikipedia.org/wiki/List\_of\_tz\_database\_time\_zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - * [https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT\_IDS](https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html#SHORT_IDS) - - Consulte [a Epoch](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html) para obter mais informações. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo - - Descrição -
- **Timestamp** - - Obrigatório - - int - - Um número inteiro que representa o timestamp da época. Note que as épocas UNIX são o número de segundos após 1º de janeiro de 1970, meia-noite UTC (00:00). -
- **timestampUnit** - - Opcional - - corda - - Uma string representando a unidade do timestamp fornecido. Valores aceitáveis: SEGUNDOS, MILISSEGUNDOS (PADRÃO) -
- **ID do fuso horário** - - Opcional - - corda - - Uma string que representa o fuso horário para a data/hora desejada, padrão: UTC -
- **padrão** - - Opcional - - corda - - Uma string que representa o padrão para a data e hora desejadas, padrão: ISO-8601 -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Opcionalidade - - Tipo de dados - - Descrição -
- **data** - - Obrigatório - - corda - - Uma representação em formato de string de uma data. -
- **tempo** - - Obrigatório - - corda - - Uma representação em forma de string do tempo. -
- **data e hora** - - Obrigatório - - corda - - Uma representação em formato de string de data e hora. -
- **fuso horário** - - Obrigatório - - map - - Representação em mapa do ID do fuso horário e sua abreviação. -
- - - - - - - - - - - - - - - - - - - - - - - -
- Exemplo - - Entrada de fluxo de trabalho - - Saídas -
- ```yaml - name: from_epoch - - workflowInputs: - timestamp: - type: Int - timestampUnit: - type: String - timezoneId: - type: String - pattern: - type: String - - steps: - - name: epochTime - type: action - action: utils.datetime.fromEpoch - version: 1 - inputs: - timestamp: ${{ .workflowInputs.timestamp }} - timezoneId: ${{ .workflowInputs.timezoneId }} - pattern: ${{ .workflowInputs.pattern }} - timestampUnit: ${{ .workflowInputs.timestampUnit }} - ``` - - ```json - mutation { - workflowAutomationStartWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { name: "from_epoch" } - workflowInputs: [ - {key: "timestamp", value: "1738236424003"} - {key: "timestampUnit", value: "MILLISECONDS"} - {key: "pattern", value: "yyyy-mm-dd HH:SS"} - {key: "timezoneId", value: "Asia/Kolkata"} - ] - ) { - runId - } - } - ``` - - ```json - { - "date": "2025-01-30", - "time": "16:57:04.003" - "datetime": "2025-01-30 16:00", - "timezone": { - "abbreviation": "IST", - "id": "Asia/Kolkata" - } - } - ``` -
- - - - - - - - - Esta ação é usada para transformar vários tipos de entrada (JSON, mapa) em um formato CSV. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo - - Descrição -
- **dados** - - Obrigatório - - qualquer - - Uma sequência de caracteres que representa dados a serem transformados em CSV, normalmente uma string JSON ou um mapa. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Opcionalidade - - Tipo de dados - - Descrição -
- **arquivo CSV** - - Obrigatório - - corda - - Representação em formato CSV dos dados recebidos. -
- - - - - - - - - - - - - - - - - - - - - - -
- Exemplo - - Entrada de fluxo de trabalho - - Saídas -
- ```json - name: nrqltocsv - - steps: - - name: queryForLog - type: action - action: newrelic.nrql.query - version: 1 - inputs: - accountIds: ['${{ .workflowInputs.accountId }}'] - query: ${{ .workflowInputs.nrql }} - - - name: csv1 - type: action - action: utils.transform.toCSV - version: 1 - inputs: - data: ${{ .steps.queryForLog.outputs.results | tostring }} - ``` - - ```json - mutation { - startWorkflowRun( - scope: { type: ACCOUNT id: "12345678" } - definition: { - name: "nrqltocsv", - } - workflowInputs: [ - {key: "accountId" value: "12345678"} - {key: "nrql" value: "FROM TransactionError SELECT error.message, error.class, transactionName, request.uri, query WHERE appName like 'my-app-1%' AND error.expected IS FALSE SINCE 1 hour ago LIMIT 50"} - ] - ) - { runId } - } - ``` - -
- - - - - - - - - Gere um UUID V4 compatível com a RFC. - - - - - Entradas - - - - Saídas - - - - Exemplo - - - - - - - - - - - - - - - - - - - - - - -
- Entrada - - Opcionalidade - - Tipo de dados - - Descrição -
- - - - -
- - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Tipo de dados - - Descrição -
- **uuid** - - corda - -
- - - - - - - - - - - - - - - - - - - - - -
- Exemplo - - Entrada de fluxo de trabalho - - Saídas -
- - - nome: gerarUUID
passos: - - * nome: gerarUUID tipo: ação ação: utils.uuid.generate versão: 1 - 		- ```json - { - "uuid": "c76bd606-5eaa-42bb-a847-4221fb49f83c", - } - ``` -
- - - - - \ No newline at end of file diff --git a/src/nav/workflow-automation.yml b/src/nav/workflow-automation.yml index 61a0640c6c4..c78ec835758 100644 --- a/src/nav/workflow-automation.yml +++ b/src/nav/workflow-automation.yml @@ -8,6 +8,8 @@ pages: pages: - title: Set up AWS credentials path: /docs/workflow-automation/setup-and-configuration/set-up-aws-credentials + - title: Deploy AWS infrastructure with CloudFormation + path: /docs/workflow-automation/setup-and-configuration/deploy-aws-infrastructure-cloudformation - title: Create destinations and notifications path: /docs/workflow-automation/setup-and-configuration/create-destinations - title: Actions catalog @@ -15,18 +17,73 @@ pages: pages: - title: Actions catalog overview path: /docs/workflow-automation/setup-and-configuration/actions-catalog/actions-catalog + - title: Auth actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/auth + pages: + - title: JWT Create action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/auth/auth-jwt-create - title: AWS actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws + pages: + - title: AWS CloudWatch actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-cloudwatch + - title: AWS EC2 actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-ec2 + - title: AWS Execute API actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-execute-api + - title: AWS Lambda actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-lambda + - title: AWS S3 actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-s3 + - title: AWS SNS actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sns + - title: AWS SQS actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-sqs + - title: AWS Systems Manager actions + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/aws/aws-systemsmanager - title: HTTP actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/http + pages: + - title: HTTP GET action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-get + - title: HTTP PUT action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-put + - title: HTTP POST action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-post + - title: HTTP DELETE action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/http/http-delete - title: New Relic actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/new-relic + pages: + - title: New Relic Ingest action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-ingest + - title: New Relic NerdGraph action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nerdgraph + - title: New Relic Notification action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-notification + - title: New Relic NRDB action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/newrelic/newrelic-nrdb - title: Communication actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/communication + pages: + - title: Slack Chat action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/slack/slack-chat - title: PagerDuty actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty + pages: + - title: PagerDuty Incident action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/pagerduty/pagerduty-incident - title: Other actions path: /docs/workflow-automation/setup-and-configuration/actions-catalog/others + pages: + - title: Script Run action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/utils/script-run + - title: DateTime action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-datetime + - title: Transform action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-transform + - title: UUID action + path: /docs/workflow-automation/setup-and-configuration/actions-catalog/utils/utils-uuid - title: Create a workflow automation path: /docs/workflow-automation/create-a-workflow-automation pages: diff --git a/static/images/python-script.webp b/static/images/python-script.webp new file mode 100644 index 00000000000..53a3f0e7361 Binary files /dev/null and b/static/images/python-script.webp differ