GeezerVison

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jul 6, 2026 10:16pm

PR Summary

Low Risk
Additive NerdGraph fields and response mapping only; no auth, request parameters, or existing output fields were removed or renamed.

Overview
Search Entities and Get Entity now return richer NerdGraph entity payloads: domain, reporting, alertSeverity, and tags (in addition to guid, name, and entityType). The tools’ GraphQL queries request those fields via AlertableEntity / AlertableEntityOutline fragments, and responses are shaped through a shared normalizeNewRelicEntity helper and updated NewRelicEntity types.

The New Relic block’s entities and entity output descriptions are updated so workflows document the expanded shape. Existing fields are unchanged; this is additive for consumers that only used the prior three fields.

^{Reviewed by Cursor Bugbot for commit 7729599. Configure here.}

Greptile Summary

This PR extends the New Relic integration by surfacing four additional entity fields (domain, reporting, alertSeverity, tags) across the get_entity and search_entities tools, and introduces a shared normalizeNewRelicEntity utility that consistently null-coalesces every field in a single place.

• Adds NewRelicRawEntity type and normalizeNewRelicEntity to utils.ts, replacing ad-hoc inline normalization with a single reusable function used by both tools.
• Updates both GraphQL queries to select the new fields (domain, reporting, ... on AlertableEntity/AlertableEntityOutline { alertSeverity }, tags { key values }), and updates output schemas and block descriptions accordingly.
• The change is purely additive: existing fields (guid, name, entityType) and their semantics are unchanged, and backward compatibility is maintained.

Confidence Score: 5/5

Safe to merge — changes are purely additive, all new fields are null-coalesced, and both tools now share the same normalization path.

The raw-entity passthrough concern raised in the previous review has been fully addressed: search_entities now maps every entity through normalizeNewRelicEntity before returning it, matching what get_entity already did. The new normalizeNewRelicEntity utility handles every nullable field consistently, the inline fragment names (AlertableEntityOutline vs AlertableEntity) are correct for their respective query contexts, and gqlString (backed by JSON.stringify) prevents GraphQL injection in the get_entity query. No existing fields or response shapes were changed.

No files require special attention.

Important Files Changed

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Caller
    participant Tool as get_entity / search_entities
    participant Utils as utils.ts
    participant NerdGraph as New Relic NerdGraph

    Caller->>Tool: invoke(params)
    Tool->>NerdGraph: POST /graphql (guid/query/cursor, new fields: domain, reporting, alertSeverity, tags)
    NerdGraph-->>Tool: "GraphQLResponse<RawEntity[]>"
    Tool->>Utils: parseNerdGraphResponse()
    Utils-->>Tool: typed payload
    Tool->>Utils: normalizeNewRelicEntity(rawEntity)
    Note over Utils: null-coalesces guid, name, entityType,<br/>domain, reporting, alertSeverity, tags
    Utils-->>Tool: NewRelicEntity (fully normalized)
    Tool-->>Caller: "{ success, output: { entity / entities } }"

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Caller
    participant Tool as get_entity / search_entities
    participant Utils as utils.ts
    participant NerdGraph as New Relic NerdGraph

    Caller->>Tool: invoke(params)
    Tool->>NerdGraph: POST /graphql (guid/query/cursor, new fields: domain, reporting, alertSeverity, tags)
    NerdGraph-->>Tool: "GraphQLResponse<RawEntity[]>"
    Tool->>Utils: parseNerdGraphResponse()
    Utils-->>Tool: typed payload
    Tool->>Utils: normalizeNewRelicEntity(rawEntity)
    Note over Utils: null-coalesces guid, name, entityType,<br/>domain, reporting, alertSeverity, tags
    Utils-->>Tool: NewRelicEntity (fully normalized)
    Tool-->>Caller: "{ success, output: { entity / entities } }"

_{Reviews (3): Last reviewed commit: "fix(new-relic): gate alertSeverity behin..." | Re-trigger Greptile}

Fixed — extracted a shared normalizeNewRelicEntity() helper in utils.ts and now use it in both get_entity.ts and search_entities.ts, so entities/tags/scalars are always normalized to the typed null/[] shape regardless of what NerdGraph omits. Pushed in bf5beaa.

@greptile review

@cursor review

Follow-up from an additional independent verification pass (re-checked every field against New Relic's live NerdGraph docs from scratch, including backwards-compat diffing against origin/staging): found that alertSeverity isn't a direct field on the Entity/EntityOutline types — it only exists on the AlertableEntity/AlertableEntityOutline sub-interfaces, so NerdGraph would reject both queries outright without an inline fragment. Fixed in 7729599: get_entity.ts now uses ... on AlertableEntity { alertSeverity }, search_entities.ts uses ... on AlertableEntityOutline { alertSeverity }. Everything else (domain/reporting/tags) is fine as direct fields per the docs.

@greptile review

@cursor review