When adding hastic graph to dashboard in grafana - an error message appears, that HASTIC_SERVER_URL is not set.

Right now the user has to navigate to dashboard settings -> variables. Like this:

We should make the addition of this variable easier and more obvious to the user.
Maybe create a pop-up, that requests a port number as an input from the user. And it will automatically add this port to HASTIC_SERVER_URL variable in grafana.

There is no crosshair on graph hover
Guess it's related to this fix

The documentation should answer questions:

• What is hastic-graph-panel
• What is it different from basic graph-panel and how related to it
• How you can use hastic-panel and how features look like (screenshots)

We can't guarantee that user can install plugin from master branch
Let's make releases and instruction to install with wget <release_url>

I think when we collect bugreports from users if would be nice to have basic Info about hastic environement.

So I would get:

• hastic-panel version
• grafana version
• hastic-server version
• how hastic-server installed (docker / build) (maybe we should put it in our status on server)
• hastic server node version (maybe we should put it in our status on server)
• basic info about browser and os

@rozetko @sankerust review this please

Steps to reproduce:

• Create new analytic unit
• Wait for learning to finish
• Click "Label" button

Nothing happens
And if you open console - you would see this error

Let`s make first release and update docs accordingly.

We should add "info" icon with analytic unit id in tooltip

We should highlight the segments, that were used for the learning process "under the hood".

User feedback.

isBackendOk function, https://github.com/hastic/hastic-server/issues/66

We can make a folder with scripts where we create plugin release and upload it to github
https://github.com/grafana/grafana/tree/master/scripts

When we in mode "delete", when we can show "anti-segments" from server

I think we should render query if hastic-server is unavailable.
... and continue to work without it.

Steps to reproduce:

• Create analytic unit
• Delete it
• Create new analytic unit

Expected behaviour:

• New analytic unit would have the same color as the 1st one had

Actual behaviour:

• New analytic unit has next color from the palette

Since this plugin is based on https://github.com/CorpGlory/grafana-graph-panel, this problem with Singelstat and Chart panels affects it too

When running server from Docker - there is no git field in /status response
Thus, you got Cannot read property 'branch' of null error

I can try to do it myself but it will take much more time.

We need a proper documentation about how to install a plugin

Build failed for nodejs less than 6.14

Expected behaviour: build passed
Recieved:

➜  hastic-grafana-graph-panel git:(master) npm run build                                                                                                                 

> [email protected] build /home/jo/extra/hastic-grafana-graph-panel
> webpack --config build/webpack.prod.conf.js

/home/jo/extra/hastic-grafana-graph-panel/node_modules/webpack/bin/webpack.js:86
        let notify =
        ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)
    at startup (node.js:136:18)
    at node.js:966:3

npm ERR! Linux 4.15.0-33-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `webpack --config build/webpack.prod.conf.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] build script 'webpack --config build/webpack.prod.conf.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hastic-graph-panel package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack --config build/webpack.prod.conf.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs hastic-graph-panel
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls hastic-graph-panel
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/jo/extra/hastic-grafana-graph-panel/npm-debug.log

Steps to reproduce:
(nodejs less than 6.14)

cd hastic-grafana-graph-panel
npm run build    

When using webpack and doing npm run build i got this error.

I don`t like long name "General approach"
Lets short it!

Deleted segments should be shown only in deleting mode
They are shown always though

I am getting this error while trying to add a panel to the dashboard. The variable has already been configured. I downloaded the tar file and unzipped it in the right location. However, I am still unable to add the panel. I am using centos 7.4 and grafana 5.3.

I'm getting this unexpected error while adding an analytic unit. I'm using Grafana 5.3.1

When trying to manually change the color of an analytic unit - this error appears in console and color change doesnt happen.

Steps to reproduce:

• Create new analytic unit
• Click the color icon
• Click any color from the palette

    at t.onColorSelect (app.5372b9bbcb8c6d1c027e.js:19772)
    at t.setColor (ColorPickerPopover.tsx:37)
    at t.sampleColorSelected (ColorPickerPopover.tsx:42)
    at app.5372b9bbcb8c6d1c027e.js:19820
    at Object.u (react-dom.production.min.js:26)
    at Object.invokeGuardedCallback (react-dom.production.min.js:25)
    at Object.invokeGuardedCallbackAndCatchFirstError (react-dom.production.min.js:25)
    at p (react-dom.production.min.js:30)
    at v (react-dom.production.min.js:32)
    at b (react-dom.production.min.js:32)```

This one for server:
https://github.com/hastic/hastic-server/issues/16

Deleting any analytic units only deletes the first analytic unit in column.
Steps to reproduce:

• Create 2 or more analytic units
• Click delete button on any analytic unit except for the first one

As you can see on the screenshots - deleting AnalyticUnitName7 removed AnalyticUnitName1.

Probably related to:
https://github.com/hastic/hastic-server/issues/42

P.s. no errors in console

I want to send labels during learning. I think that hastic-server should handle this.

• User makes query
• User label patterns
• User change query

AND WHAT? Now everything is broke. We show wrong patterns and analytics doesn`t know what data which should be analysed changed.

Steps:

• Click "Add Analytic Unit"
• Change name of new Analytic Unit
• Click on button "Add Analytic Unit"

it will drop value in name of new Analytic Unit in input form.
I think it is unexpected behavior.

When you open panel editor and have no datasource in metrics - you got "Datasource not found" error

We cannot get any datasource's type from ds-request-response
e.g. there is no such field in Prometheus
We should get datasource type from Grafana API right before sending request to hastic-server
The same bug as CorpGlory/grafana-data-exporter-panel#14

Want to regulate confidence threshold

I see this error when just load hastic panel in my Grafana instance. I need to check version

I want to see it as a warning

Based on https://github.com/hastic/hastic-server/issues/21

I am getting error : TypeError: Cannot read property 'type' of undefined when trying to make a simple elasticseaarch query

We should add some sort of help section to panel, that would help the user to choose appropriate analytics for his/her needs.

It should include description and examples of all of the available detection patterns.

User feedback.

Just jest with ts. And test #29

When 2 or more anomalies are using the same name the color choice starts to work wierd.

It only changes color for the last created anomaly with the same name. And it is not possible to change colors for anomalies with same name, that were created previously.
bug or feature?

test:

• Create 2 or more anomalies with same name.
• Try to change the color for the last with same name (works OK)
• Now try to change the color for the first (changes color for the last only)

Adjust color choosing script?
Check anomaly name fields and restrict user from creating same names?

If you've deleted a segment and then changed your mind - you can't undelete it
Should be possible to delete deleted segments

P.S. it's not even supported by server yet

When hastic-server is down, panel would start to show "Unexpected error" trying to get new chunk of data

There is a nice way to make you panel public: http://docs.grafana.org/reference/sharing/
I think we can`t do something like this with hastic-panel yet

@amper43 @rozetko do we need this?

Would nice to have if you create patterns, than colors would be different.
Its like when we create new metrics in graphs

When in some time range you have multiple anomalies - all range is labeled as anomaly, even places without them

Based on https://github.com/hastic/hastic-server/issues/22

We keep in readme it

We need to store everything connected to analytics (analytic units, segments) on the server. While in panel itself we shouldn't store any data, only take it from the server.
The problem is when a user deletes segments and did NOT save the dashboard - he expects, that they will stay displayed.

In grafana 5.1.4 hastic graph is rendered OK.
In grafana 5.2.1 hastic graph is not rendered at all.

Steps to reproduce:

• Use grafana version 5.2.1
• Create a dashboard with hastic graph panel

Expected behaviour (grafana version 5.1.4)

Grafana 5.2.1 behaviour:

And console output:

TypeError: Cannot read property 'min' of undefined
    at s (ticks.ts:123)
    at updateLegendValues (graph_renderer.ts:829)
    at GraphRenderer../graph_renderer.ts.GraphRenderer.render (graph_renderer.ts:207)
    at GraphCtrl../module.ts.GraphCtrl.onRender (module.ts:393)
    at o.emit (index.js:150)
    at e.emit (emitter.ts:11)
    at GraphCtrl.t.render (panel_ctrl.ts:245)
    at solo_panel_ctrl.ts:32
    at angular.js:20440
    at i (angular.js:6362)

• add analyticsReady field
• make fields wider
  

P.S. Grafana version is not displayed in 5.3.1