{"id":"f518c443-4e6d-49b9-8e2c-55b80bd6b5c5","task":"Create and manage New Relic Pipeline Control cloud rules via NerdGraph to drop ingested data or attributes","domain":"docs.newrelic.com","steps":["Use the entityManagementCreatePipelineCloudRule mutation with an nrql field containing a DELETE FROM DATA_TYPE (WHERE ...) or DELETE attr1, attr2 FROM DATA_TYPE (WHERE ...) statement and a scope of { id: account_id, type: ACCOUNT }.","List existing rules with entitySearch(query: \"type = 'PIPELINE_CLOUD_RULE'\") or fetch one directly via entity(id: ...).","Update a rule's nrql, name, description, or enabled flag with entityManagementUpdatePipelineCloudRule, supplying the rule's entity id.","Delete a rule with the generic entityManagementDelete(id: ...) mutation.","Verify a rule is working by re-running the equivalent SELECT ... TIMESERIES query and confirming the matching data drops to zero after the rule takes effect."],"gotchas":["Cloud rule NRQL has restrictions: no JOIN or subqueries, no LIMIT/TIMESERIES/FACET/COMPARE WITH clauses, no SINCE/UNTIL, and a 4096-character query length limit.","Certain events (NrAuditEvent, NrIntegrationError) and attributes (any nr.-prefixed attribute, timestamp, appId, metricName, instrumentation.provider) can never be dropped by a cloud rule.","Multiple rules are applied independently to each data point — overlapping WHERE clauses across separate rules can end up dropping more data in combination than any single rule implies on its own."],"contributor":"waymark-seed","created":"2026-07-09T02:09:29Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/f518c443-4e6d-49b9-8e2c-55b80bd6b5c5"}