John Mazzitelli

be able to deploy h-alerts in kubernetes via kubectl create -f (#454)

hawkular-alerts-k8s.yml

    • -0
    • +57
    /dist/hawkular-alerts-k8s.yml
fix docker push (#453)

tweak example triggers (#433)

example that shows alerts taking in data from multiple different sources

    • -0
    • +67
    /examples/multiple-sources/README.adoc
    • -0
    • +116
    /examples/multiple-sources/pom.xml
    • -0
    • +81
    /examples/multiple-sources/src/test/scripts/install.sh
    • -0
    • +194
    /examples/multiple-sources/src/test/scripts/store.py
the pie chart should only show non-resolved alerts just like the stacked bar charts. so only count alert that are not in the resolved state (i.e. open or acked)

fix graphs so they are not always recreated and "flashing" during updating

have a shared service for the filters so all pages can use the same settings (#417)

    • -13
    • +17
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -10
    • +0
    /ui/src/main/ui/src/alerts/alerts-service.js
    • -7
    • +7
    /ui/src/main/ui/src/alerts/alerts.html
    • -0
    • +22
    /ui/src/main/ui/src/app/services/filter-service.js
link to the alerts list from the dashboard - clicking the pie or the (#416)

cards takes you to the list with the filter set properly

    • -14
    • +4
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -0
    • +10
    /ui/src/main/ui/src/alerts/alerts-service.js
    • -3
    • +3
    /ui/src/main/ui/src/dashboard/dashboard.html
stub out the actual button onclick functions and only show the ones that make sense. (#411)

add new details composite expansion area leaving the notes to only show the notes (so now if you see "0 Notes" you know there is no data there).

    • -0
    • +16
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -9
    • +42
    /ui/src/main/ui/src/alerts/alerts.html
get the collapsible rows to work (#409)

    • -4
    • +57
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -1
    • +16
    /ui/src/main/ui/src/alerts/alerts-module.js
    • -60
    • +1
    /ui/src/main/ui/src/alerts/alerts.html
load alerts into scope for display in alerts list (#408)

    • -3
    • +29
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -83
    • +33
    /ui/src/main/ui/src/alerts/alerts.html
fix npe (#406)

generate alerts of different severities (#407)

    • -0
    • +51
    /examples/simple-generator/README.adoc
    • -0
    • +92
    /examples/simple-generator/pom.xml
    • -0
    • +64
    /examples/simple-generator/src/test/groovy/send_data.groovy
stub out alerts page and link on left menu (#405)

    • -0
    • +8
    /ui/src/main/ui/src/alerts/alerts-controller.js
    • -0
    • +2
    /ui/src/main/ui/src/alerts/alerts-module.js
    • -0
    • +15
    /ui/src/main/ui/src/alerts/alerts-service.js
    • -0
    • +358
    /ui/src/main/ui/src/alerts/alerts.html
explicitly set the version to avoid the ugly mvn warnings. (#402)

missing semis might be the cause of the travis errors. (#401)

dashboard with four cards and a stacked bar graph (#395)

* put the cards back - one row under the graphs.

* replace donut chart with stacked bar chart so you can see open/ack subcategorized by severity

* rearrange cards to reduce lots of empty space. the cards move below when you shrink the screen; move to the right when wide

    • -6
    • +32
    /ui/src/main/ui/src/dashboard/dashboard.html
show alert severity in a pie chart

    • -0
    • +3
    /ui/src/main/ui/src/dashboard/dashboard.html
Be able to start grunt server without starting up the browser window. (#389)

The default behavior is the same as always (browser starts up with "grunt server")

but if you pass in --nobrowser, it won't start the browser.

if the server is bound to some other non-localhost, non-8080 port, be able to tell examples where to send the data. (#386)

The default remains the same, so nothing changes if you just "mvn validate" but now

you can do this: "mvn validate -Dhost=192.168.1.100:8181" and it will work. You can also change the tenant

if you want via -Dtenant.

  1. … 8 more files in changeset.
Create a global app config object - for now store base URL information. (#384)

This means we no longer have to manually edit services js files if using

grunt or if the server is bound to some other IP/port that the grunt server is not.

    • -11
    • +4
    /ui/src/main/ui/src/actions/actions-service.js
    • -11
    • +4
    /ui/src/main/ui/src/triggers/triggers-service.js
There are times you have to clean out EVERYTHING that was generated. For example, Maybe to get back to a normal running state or you just want to remove everything not committed to git. This allows "grunt purge" to clean everything. *Note that "grunt clean" will not do this - so anyone performing a clean won't be surprised.* After a purge, you then must "npm install && bower install" to re-generate and build everything again. This is output in a log message to remind the user after they run this task. I found this was the only way to get the UI to work under some condition I found myself in.

add donut graph

    • -21
    • +8
    /ui/src/main/ui/src/dashboard/dashboard.html
clean the generated src/templates directory via grunt

fix the "console" option so it doesn't screw up the indexes of ispn on shutdown. This now puts the server in background just like start_alerting, but it also immediately tails the log file for you so it shows in the console, plus it adds a trap so when you control-c the stop_alerting is called and the server is shutdown normally.

comment out the backend-reindex property. in case it is needed this allows a person to just uncomment it and not have to remember what its name is

don't assume 127 IP

still trying to get dev environment configured properly - this is some cors properties that are needed

1. Get hawkular.sh to pass the correct sysprops so you can properly set the bind address and port (#365)

2. Change dashboard-service.js so you need only uncomment one line to change the IP (rather than change three lines total (comment 1, uncomment 2 and change one of them).

set default to 0.0.0.0 so a developer can run the server on a dev machine while accessing the server from another client machine.