Request to Statuspage.io API in order to notify Kibana users

[ryanholder]

The idea here is to make a request to the Statuspage.io API request using Angular $http and then display the retuned data as a notification in Kibana using the alertSrv service.

The Angular $http service will generate an HTTP request and return a promise allowing Kibana to continue functioning as normal while we wait for the results of the request to be returned.

[mrdavidlaing]

Grr - at the moment the "failure" above is to do with our CF cluster, not this project. I'm busy working on trying to stop deploys to apps.cityindex.logsearch.io failing intermittently

[mrdavidlaing]

@ryanholder - I've figured out how to build the statuspage.io proxy into the existing kibana3 hosting, as shown above by using an nginx proxy. One more thing to solve; configuring nginx to be able to proxy back to HTTPS endpoints; which I'll tackle tomorrow

[mrdavidlaing]

@ryanholder I've finally managed to get it deployed - http://kibana-pr17.apps.cityindex.logsearch.io/#/dashboard/elasticsearch/IP%20Diagnostics%20-%20LIVE

However, getting this deployed is going to have to happen after:

1. My customisations to the staticfile-buildpack after merged upstream
2. Our CF cluster stops being so temperamental - only 1 deploy is 3 is currently working.

[le-bott]

Test PASSed. Refer to this link for build results (access rights to CI server needed): http://jenkins.meta.logsearch.io/job/shared.releases.kibana-PRs/20/Test PASSed.

[mrdavidlaing]

@ryanholder I've fixed the CF cluster and the staticfile-buildpack, so these shouldn't block you getting this released

[le-bott]

Test FAILed. Refer to this link for build results (access rights to CI server needed): http://jenkins.meta.logsearch.io/job/shared.releases.kibana-PRs/21/

Build Log last 50 lines

[...truncated 56 lines...]
+ git config --global url.https://.insteadOf git://
+ npm install
npm WARN package.json grunt-contrib-htmlmin@0.1.3 No README data
npm WARN package.json rjs-build-analysis@0.0.3 No repository field.
npm WARN package.json expect.js@0.2.0 No repository field.
-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-npm WARN excluding symbolic link scratchy -> index.js
npm WARN excluding symbolic link scratchy -> index.js
-\|grunt-scratchy@0.5.0 node_modules/grunt-scratchy
└── scratchy@3.0.0-pre-milestone5 (underscore@1.5.2, mkdirp@0.3.5, underscore.string@2.3.3, optimist@0.6.1)
+ grunt build
Running "jshint:source" (jshint) task
Linting src/app/services/dashboard.js ...ERROR
[L156:C17] W015: Expected 'case' to have an indentation at 15 instead at 17.
                case 'partial_outage':
Linting src/app/services/dashboard.js ...ERROR
[L157:C19] W015: Expected 'alertParams' to have an indentation at 17 instead at 19.
                  alertParams = {
Linting src/app/services/dashboard.js ...ERROR
[L162:C19] W015: Expected 'break' to have an indentation at 17 instead at 19.
                  break;
Linting src/app/services/dashboard.js ...ERROR
[L163:C17] W015: Expected 'case' to have an indentation at 15 instead at 17.
                case 'major_outage':
Linting src/app/services/dashboard.js ...ERROR
[L164:C19] W015: Expected 'alertParams' to have an indentation at 17 instead at 19.
                  alertParams = {
Linting src/app/services/dashboard.js ...ERROR
[L169:C19] W015: Expected 'break' to have an indentation at 17 instead at 19.
                  break;
Linting src/app/services/dashboard.js ...ERROR
[L170:C17] W015: Expected 'default' to have an indentation at 15 instead at 17.
                default:
Linting src/app/services/dashboard.js ...ERROR
[L171:C19] W015: Expected 'alertParams' to have an indentation at 17 instead at 19.
                  alertParams = {
Linting src/app/services/dashboard.js ...ERROR
[L150:C58] W098: 'config' is defined but never used.
          .success(function(data, status, headers, config) {
Linting src/app/services/dashboard.js ...ERROR
[L150:C50] W098: 'headers' is defined but never used.
          .success(function(data, status, headers, config) {
Linting src/app/services/dashboard.js ...ERROR
[L150:C41] W098: 'status' is defined but never used.
          .success(function(data, status, headers, config) {

Warning: Task "jshint:source" failed. Use --force to continue.

Aborted due to warnings.
Build step 'Execute shell' marked build as failure

Test FAILed.

[le-bott]

Test PASSed. Refer to this link for build results (access rights to CI server needed): http://jenkins.meta.logsearch.io/job/shared.releases.kibana-PRs/22/Test PASSed.

[mrdavidlaing]

@ryanholder - I'm about to deploy a log parser change to cityindex.logsearch.io. During this deploy I'll flick cityindex.logsearch.io to various statuses so we can do a final test of http://kibana-pr17.apps.cityindex.logsearch.io/#/dashboard/elasticsearch/IP%20Diagnostics%20-%20LIVE prior to merging Agree?

[ryanholder]

@mrdavidlaing agreed

[mrdavidlaing]

Screencast of test against http://kibana-pr17.apps.cityindex.logsearch.io

[le-bott]

Test PASSed. Refer to this link for build results (access rights to CI server needed): http://jenkins.meta.logsearch.io/job/shared.releases.kibana-PRs/23/Test PASSed.

[ryanholder]

@mrdavidlaing we have a 5 min timeout and changes to the text in place. Any deploys planned to test against live ?

[mrdavidlaing]

@ryanholder, we don't have any planned deploys; however, I don't see any problem creating a "test incident" sometime today as part of a final "pre merge" test.

[le-bott]

Test PASSed. Refer to this link for build results (access rights to CI server needed): http://jenkins.meta.logsearch.io/job/shared.releases.kibana-PRs/25/Test PASSed.