-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Shell script and powershell connector for watcher alerts #105381
Comments
@marcelvarallo-leidos By "connector" do mean a new type of Watcher action? If so, then I believe you're requesting an Elasticsearch enhancement. |
Apologies, I use several versions of Elasticsearch and it appears I got a little confused. In the Alerts and Actions section, there's a tab to create new Connectors and contains items like webhook, email, jira etc. That's the area I was thinking of. But a watcher action would be good too :) |
If we had this feature, I could create a diagnostic index and then use this alert action to (for example) call nslookup/tracert/whatever diagnostic tool needs to be run when the Alert happens and output the response to a file which filebeat scoops into that index so I can check what was happening elsewhere when this happened. |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
cc @arisonl |
This would be so helpful +1 |
Describe the feature:
A powershell and Shell/bash script connector for watcher alerts
Describe a specific use case for the feature:
In the event of certain alerts, trigger a shell script or powershell command parsing in detail from the alert.
I currently have an intermittent issue with one of my servers and I'd like to run a diagnostic script when it happens but it disappears before I notice and can run the script.
The text was updated successfully, but these errors were encountered: