Skip to content

Add “Query Logs” Action to New Relic Component #16968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

edward-rosado
Copy link

@edward-rosado edward-rosado commented Jun 4, 2025

Add “Query Logs” Action to New Relic Component

Overview

This PR introduces a new Query Logs action to the New Relic component, enabling users to query logs from New Relic using NRQL (New Relic Query Language). This action allows for advanced log analysis and monitoring workflows directly within Pipedream.

What’s Included

  • New Action:
    • components/new_relic/actions/query-logs/query-logs.mjs
    • ES module action that leverages the New Relic GraphQL API to run NRQL queries against logs.
  • Documentation Update:
    • Expanded README.md to document the new action, its usage, and example use cases.

Usage

  • Inputs:

    • Account ID: The New Relic account to query.
    • NRQL Query: The NRQL query to run (e.g., SELECT * FROM Log WHERE message LIKE '%error%' LIMIT 10).
  • Output:

    • Returns the results of the NRQL query, which can be used in subsequent workflow steps.

Example Use Case

  • Search for error patterns or specific events in New Relic logs and trigger downstream actions or notifications in your workflow.

Motivation

This addition expands the observability and automation capabilities of the New Relic component, making it easier for users to monitor, analyze, and respond to log data within their Pipedream workflows.

Summary by CodeRabbit

  • New Features

    • Introduced a "Query Logs" action for New Relic, allowing users to fetch and analyze log data using NRQL queries.
  • Documentation

    • Expanded the New Relic component README with details and usage examples for the new "Query Logs" action, including required inputs, best practices, and example use cases.

Copy link

vercel bot commented Jun 4, 2025

@edward-rosado is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Jun 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jun 4, 2025 8:23pm

Copy link
Contributor

coderabbitai bot commented Jun 4, 2025

Walkthrough

A new "Query Logs" action was added to the New Relic component, enabling users to execute NRQL queries for log data retrieval and analysis. The README was updated to document this new action, including its usage, required inputs, example scenarios for log analysis and alerting.

Changes

File(s) Change Summary
components/new_relic/actions/query-logs/query-logs.mjs Added a new action to query logs from New Relic using NRQL via a GraphQL API call with pagination support.
components/new_relic/README.md Expanded documentation to describe the new "Query Logs" action, its inputs, example use cases, and usage.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Workflow
    participant QueryLogsAction
    participant NewRelicAPI

    User->>Workflow: Triggers workflow with Query Logs action
    Workflow->>QueryLogsAction: Passes app instance, accountId, and NRQL query
    QueryLogsAction->>NewRelicAPI: Sends GraphQL POST with NRQL query and accountId
    NewRelicAPI-->>QueryLogsAction: Returns query results (with pagination)
    QueryLogsAction->>NewRelicAPI: Requests next page if nextCursor present
    QueryLogsAction-->>Workflow: Returns aggregated results and summary
    Workflow-->>User: Provides log query results
Loading

Poem

In the warren of logs, a rabbit peers,
Querying New Relic without any fears.
With NRQL in paw, it hops through the night,
Fetching log tales, errors in sight.
Now, with new docs and actions to show—
The burrow’s insights continue to grow! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/new_relic/actions/query-logs/query-logs.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@adolfo-pd adolfo-pd added the User submitted Submitted by a user label Jun 4, 2025
@pipedream-component-development
Copy link
Collaborator

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

@pipedream-component-development
Copy link
Collaborator

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Nitpick comments (2)
components/new_relic/actions/query-logs/query-logs.mjs (1)

40-41: Improve return value structure.

The current implementation returns the entire GraphQL response, but it would be more useful to return just the query results with better structure.

-        $.export("$summary", `Queried logs with NRQL: ${this.nrql}`);
-        return response.data;
+        const results = response.data.data.actor.account.nrql.results;
+        $.export("$summary", `Queried logs with NRQL: ${this.nrql} - Found ${results?.length || 0} results`);
+        return {
+            query: this.nrql,
+            accountId: this.accountId,
+            results: results,
+            metadata: {
+                executedAt: new Date().toISOString(),
+                resultCount: results?.length || 0
+            }
+        };
components/new_relic/README.md (1)

18-19: Enhance the log analysis example with more practical scenarios.

The current example is good, but could benefit from additional real-world use cases.

- **Log Analysis and Alerting**: Use the Query Logs action to search for error patterns or specific events in your New Relic logs. For example, you can run an NRQL query like `SELECT * FROM Log WHERE message LIKE '%error%' LIMIT 10` to find recent error logs and trigger downstream actions or notifications.
+ **Log Analysis and Alerting**: Use the Query Logs action to search for error patterns or specific events in your New Relic logs. Examples include:
+   - Finding recent errors: `SELECT * FROM Log WHERE message LIKE '%error%' LIMIT 10`
+   - Monitoring failed logins: `SELECT * FROM Log WHERE message LIKE '%authentication failed%' SINCE 1 hour ago`
+   - Tracking performance issues: `SELECT * FROM Log WHERE duration > 5000 SINCE 30 minutes ago LIMIT 20`
+   These queries can trigger downstream actions like Slack notifications, PagerDuty alerts, or automatic scaling decisions.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06adeff and 0ca86c5.

📒 Files selected for processing (2)
  • components/new_relic/README.md (1 hunks)
  • components/new_relic/actions/query-logs/query-logs.mjs (1 hunks)
🔇 Additional comments (1)
components/new_relic/README.md (1)

5-9: LGTM! Well-structured documentation.

The new "Available Actions" section clearly documents both existing and new actions with helpful descriptions.

@edward-rosado edward-rosado force-pushed the feature/query-logs-action branch from 8a8dd8b to 0ca86c5 Compare June 4, 2025 19:57
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
components/new_relic/actions/query-logs/query-logs.mjs (1)

31-34: Add missing description for Account ID prop.

The accountId prop lacks a description, which was identified in past review comments. This affects usability and documentation completeness.

Apply this diff to add the missing description:

 accountId: {
     type: "string",
     label: "Account ID",
+    description: "Your New Relic account ID (numeric)",
 },
🧹 Nitpick comments (1)
components/new_relic/actions/query-logs/query-logs.mjs (1)

7-21: Enhance NRQL validation and add JSDoc documentation.

The helper functions provide basic security measures but could be improved:

  1. The sanitization regex could be more comprehensive to handle additional injection vectors
  2. The functions lack JSDoc documentation for better maintainability

Apply this diff to enhance the validation and add documentation:

+/**
+ * Sanitizes NRQL query by removing potentially dangerous characters
+ * @param {string} nrql - The NRQL query to sanitize
+ * @returns {string} - The sanitized NRQL query
+ */
 function sanitizeNrql(nrql) {
-    // Remove dangerous characters and trim whitespace
-    return nrql.replace(/[;`$\\]/g, "").trim();
+    // Remove dangerous characters including quotes, semicolons, and trim whitespace
+    return nrql.replace(/[;`$\\'"/]/g, "").trim();
 }

+/**
+ * Validates if the NRQL query meets basic security and format requirements
+ * @param {string} nrql - The NRQL query to validate
+ * @returns {boolean} - True if valid, false otherwise
+ */
 function isValidNrql(nrql) {
     // Basic validation: must start with SELECT, not empty, and not contain forbidden patterns
-    const forbidden = /[;`$\\]/;
+    const forbidden = /[;`$\\'"/]/;
     return (
         typeof nrql === "string" &&
         nrql.trim().length > 0 &&
         /^SELECT\s+/i.test(nrql.trim()) &&
         !forbidden.test(nrql)
     );
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4828494 and 22a11b1.

📒 Files selected for processing (2)
  • components/new_relic/README.md (1 hunks)
  • components/new_relic/actions/query-logs/query-logs.mjs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/new_relic/README.md
🔇 Additional comments (1)
components/new_relic/actions/query-logs/query-logs.mjs (1)

41-102: LGTM! Comprehensive implementation addressing security and functionality concerns.

The run method successfully addresses all major concerns from past reviews:

Security: Uses GraphQL variables instead of string interpolation
Validation: Validates both Account ID and NRQL input
Error Handling: Comprehensive try-catch with specific error messages
Pagination: Properly implements cursor-based pagination
Response Validation: Validates GraphQL response structure

The implementation demonstrates robust error handling, proper data sanitization, and follows GraphQL best practices. The pagination logic correctly accumulates results across multiple API calls.

@edward-rosado edward-rosado changed the title Add Query Logs action and update documentation for New Relic componen… Add “Query Logs” Action to New Relic Component Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User submitted Submitted by a user
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants