<commit_before>{
  "created_at": 1497567450000,
  "deleted": null,
  "message": "## Description:\nCF Push SLI has reported failure several times within the last ten minutes.\n\nhttps://concourse.lakitu.cf-app.com/teams/main/pipelines/cron:cron/jobs/cf-sli-test-<%= environment %>\n\nThis probably means that the app is failing to stage or start successfully. It could also mean that the CF CLI is failing to communicate with the CF at some point. CF Push is takes about a dozen HTTP calls and involves most CF components.\n\n <%= cloudops_pagerduty %>   \n\n## Escalation Path:\n  CAPI, Diego \n\n## Possible Causes:\nLast updated July 3 2017\n\n### Bundler failure\nWe think we fixed this by vendoring dependencies correctly, but maybe we're wrong! If so, please write & prioritize a chore to convert this app to Go or Java, because we really want this test to be insulated from network failures.\n\n###Diego cell is unhealthy\nSaw a flurry of staging failures July 3 2017. A cell became unhealthy and then was presumably fixed by a Bosh scan-and-fix. Eric thinks ClamAV is likely implicated.\n\n###CAPI can't find Diego BBS during MySQL deploys\nThis can be checked quickly by looking for deploy alerts in the #cf-diego channel. Locket has a known issue during MySQL deploys. The Diego team is investigating and fixing.\n\n### Dependency for the CC stats endpoint is failing\nWe've seen push failures when CAPI couldn't contact Doppler nodes successfully. The CAPI team is aware of this and should be working on failing more gracefully in this case. Though if it appears that this has happened again we should follow up with them.\n\n### Other possibilities\nThe basic dependency list for Push\nUAA (and its database)\nS3 blob store\nCC and CCDB\nDiego staging cell\nDiego BBS\nRouter\nDoppler (hopefully by the time you're reading this, this is out of date)\n\n## Potential Solutions:\n\n##Feedback:\n Have feedback for this alert? [File an issue](https://github.com/pivotal-cf/datadog-config/issues/new)",
  "multi": false,
  "name": "<%= environment %> CF: SLI is lower than 100% in the last 10 minutes.",
  "options": {
    "escalation_message": "",
    "include_tags": false,
    "locked": false,
    "new_host_delay": 300,
    "no_data_timeframe": 10,
    "notify_audit": false,
    "notify_no_data": false,
    "renotify_interval": 0,
    "require_full_window": true,
    "silenced": {
    },
    "thresholds": {
      "critical": 0.95
    },
    "timeout_h": 0
  },
  "org_id": 4242,
  "overall_state": "OK",
  "overall_state_modified": "2017-07-16T16:34:10.299287+00:00",
  "query": "max(last_30m):avg:pws.cf_sli.app_start_status{deployment:<%= deployment %>} < 0.95",
  "tags": [
    null
  ],
  "type": "metric alert"
}<commit_msg>Update datadog config for sli test alert<commit_after>{
  "created_at": 1497567450000,
  "deleted": null,
  "message": "## Description:\nCF Push SLI has reported failure several times within the last ten minutes.\n\nhttps://concourse.lakitu.cf-app.com/teams/main/pipelines/cf:cf-sli/jobs/cf-sli-ruby\n\nThis probably means that the app is failing to stage or start successfully. It could also mean that the CF CLI is failing to communicate with the CF at some point. CF Push is takes about a dozen HTTP calls and involves most CF components.\n\n <%= cloudops_pagerduty %>   \n\n## Escalation Path:\n  CAPI, Diego \n\n## Possible Causes:\nLast updated July 3 2017\n\n### Bundler failure\nWe think we fixed this by vendoring dependencies correctly, but maybe we're wrong! If so, please write & prioritize a chore to convert this app to Go or Java, because we really want this test to be insulated from network failures.\n\n###Diego cell is unhealthy\nSaw a flurry of staging failures July 3 2017. A cell became unhealthy and then was presumably fixed by a Bosh scan-and-fix. Eric thinks ClamAV is likely implicated.\n\n###CAPI can't find Diego BBS during MySQL deploys\nThis can be checked quickly by looking for deploy alerts in the #cf-diego channel. Locket has a known issue during MySQL deploys. The Diego team is investigating and fixing.\n\n### Dependency for the CC stats endpoint is failing\nWe've seen push failures when CAPI couldn't contact Doppler nodes successfully. The CAPI team is aware of this and should be working on failing more gracefully in this case. Though if it appears that this has happened again we should follow up with them.\n\n### Other possibilities\nThe basic dependency list for Push\nUAA (and its database)\nS3 blob store\nCC and CCDB\nDiego staging cell\nDiego BBS\nRouter\nDoppler (hopefully by the time you're reading this, this is out of date)\n\n## Potential Solutions:\n\n##Feedback:\n Have feedback for this alert? [File an issue](https://github.com/pivotal-cf/datadog-config/issues/new)",
  "multi": false,
  "name": "<%= environment %> CF: SLI is lower than 100% in the last 10 minutes.",
  "options": {
    "escalation_message": "",
    "include_tags": false,
    "locked": false,
    "new_host_delay": 300,
    "no_data_timeframe": 10,
    "notify_audit": false,
    "notify_no_data": false,
    "renotify_interval": 0,
    "require_full_window": true,
    "silenced": {
    },
    "thresholds": {
      "critical": 0.95
    },
    "timeout_h": 0
  },
  "org_id": 4242,
  "overall_state": "OK",
  "overall_state_modified": "2017-07-16T16:34:10.299287+00:00",
  "query": "max(last_30m):avg:pws.cf_sli.app_start_status{deployment:<%= deployment %>,!java_buildpack} < 0.95",
  "tags": [
    null
  ],
  "type": "metric alert"
}
{'fraction_non_alphanumeric': 0.10903483309143687, 'fraction_numerical': 0.026124818577648767, 'mean_word_length': 4.166822867853796, 'pattern_counts': {'":': 50, '<': 12, '<?xml version=': 0, '>': 10, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '113272', 'n_tokens_mistral': 1861, 'n_tokens_neox': 1669, 'n_words': 661}