Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug related to trigger #62258

Open
wxyvk opened this issue Apr 2, 2020 · 3 comments
Open

Bug related to trigger #62258

wxyvk opened this issue Apr 2, 2020 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@wxyvk
Copy link

wxyvk commented Apr 2, 2020

**Kibana version:7.1.1

Elasticsearch version:

Server OS version:

**Browser version:80.0

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug: Hello I am new to Kibana, and I apologize if I sound naive. I am trying to create a trigger in Kibana, which is available under the alert section and every time I set the threshold condition above 10,>> click on update, the trigger condition resets to a default 10000 count, and i am not sure why. Can anyone help me?

@liza-mae liza-mae added Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Apr 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@jloleysens
Copy link
Contributor

jloleysens commented Apr 3, 2020

Hi @wxyvk !

I am sorry to hear that you are struggling. In order to assist you, it would be great to get the following information:

  1. Is the issue happening as you are typing in a threshold value [EDIT](and clicking outside of the text field) or is the error happening after you are saving the watch?
  2. Are there any errors in the browser console?
  3. If possible, could you do a screen capture of the steps you are taking? It will definitely speed things along if we can see what is happening on your side 🙂 .

@wxyvk
Copy link
Author

wxyvk commented Apr 3, 2020

Thank you for the quick turnaround!

  1. The issue is happening after I hit the update button. Once I go to trigger> edit the threshold value (from default condition-->above 10000) to new condition( above 1). Then I hit on update button. And click on the trigger again to check if the new condition was saved or not. It shows me default trigger condition. I have tried deleting, adding new trigger. Deleting the monitor by itself and adding a new trigger but it still gives me that error.
  2. I tried in different browsers, I still get the same error

Screen Shot 2020-04-03 at 8 48 13 AM

Screen Shot 2020-04-03 at 8 48 23 AM

Screen Shot 2020-04-03 at 8 48 34 AM

Screen Shot 2020-04-03 at 8 48 54 AM

Let me know if you. need anything else from me.
Thankyou so much for your help

@cjcenizal cjcenizal added the bug Fixes for quality problems that affect the customer experience label May 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

5 participants