anchor.diff:      "timeout_h": 0
     },
     "org_id": 4242,
  -  "overall_state": "Alert",
  -  "overall_state_modified": "2019-11-21T18:57:35+00:00",
  +  "overall_state": "OK",
  +  "overall_state_modified": "2019-11-21T23:06:36+00:00",
     "query": "pct_change(avg(last_1h),last_1d):avg:datadog.nozzle.bbs.CrashedActualLRPs{deployment:<%= metron_agent_diego_deployment %>}.rollup(avg, 900) > 4.5",
     "tags": [
   
  
positive.code:     "renotify_interval": 0,
      "require_full_window": false,
      "silenced": {
      },
      "thresholds": {
        "critical": 4.5,
  
negative.code: {
    "created_at": 1493766436000,
    "deleted": null,
    "message": "## Description:\n  Number of Diego Crashed LRPs(long running processes) has increased significantly in the past day\n\n## Escalation Path:\n  Diego/Garden team\n\n## Causes:\n  Usually the Crashed LRPs are quite stable in the platform. If the count climbs unexpectedly, that may be an indication that some cells are in an abnormal state.\n\n## Potential Solutions:\nExplore why the number of LRP crashes increased.\n  - If this increase appears to be due natural application instance growth, mute this monitor for a day and confirm that it recovers tomorrow.\n  - Otherwise, consider escalating to the Diego team\n @slack-pws-notifications @slack-cf-diego",
    "multi": false,
    "name": "<%= environment %> Diego: number of crashed LRPs has increased significantly",
    "options": {
      "escalation_message": null,
      "include_tags": true,
  