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

Watcher UI: Comment field is never filled up, should be removed? #24001

Open
spinscale opened this issue Oct 15, 2018 · 2 comments
Open

Watcher UI: Comment field is never filled up, should be removed? #24001

spinscale opened this issue Oct 15, 2018 · 2 comments

Comments

@spinscale
Copy link
Contributor

Kibana version: 6.4.2
Elasticsearch version: 6.4.2

image

As seen in the above UI the Comment column is never filled up. I think the field value should not be a comment, but rather a watch status state, however even that is blank despite watches being fired.

Is this somehow a condition that I misread and is only set in certain conditions? If not, we should either show the right value or remove the column.

@ghost
Copy link

ghost commented Nov 1, 2018

It would be nice to have a text field that can be filled with the description of the watch.

@nhowe91
Copy link

nhowe91 commented Dec 4, 2018

Hey @spinscale, I was looking around at this just now (was seeing if maybe we could set it via a transform script) but it looks like it the comment field is a constant set in code. For us, it mostly appears when actions are being throttled.

It is referenced here. I put a picture below showing it on some watchers we have set up

image

I believe the status page takes the comment from the latest watch history item, it would be awesome if it could be manually set though and expanded upon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants