What is the difference between xpack.security.http.ssl.verification_mode and xpack.http.ssl.verification_mode

Elastic Stack Elasticsearch
1

I want to know what is the difference between xpack.security.http.ssl.verification_mode: certificate and xpack.http.ssl.verification_mode: certificate

Also, can I use both setting at same time...?

Thank you..!
Hiruni

2

Hi @hiruni.insyncit.net,
Here's what I found with links to the respective documenation.

The first one configures http ssl verification at the cluster level.

Configures http ssl verfication for watcher.

Yes, you can, but if you aren't currently using watcher you probably don't need to.

2 Likes
3

Hi Andrew,

Thank you for the reply.
I'm trying to configure watcher in my cluster.

I configured xpack settings and email server settings in the elasticsearch.yml file as follows:
image

Then I create a watcher on Kibana. as mention in watcher

Watcher is working when I execute it using Kibana Dev-tool but it's not automatically working on scheduled time.
What can I do for this issue to automate the watcher at the scheduled time...?
Do I need to do any additional work to automate watcher in the cluster...?

Thank you...!
Hiruni

4

Try using the Simulate tab when building a watcher. I've found that very helpful to debug what issues are happening. If the query is working as expected in dev tools that is a good sign though, so sounds like you are close.

5

Hi Andrew,

Thank you for the reply.

image
image960×364 11.7 KB

I'm getting this on Simulate tab.
Thank you...!
Hiruni

6

If editing an existing watcher you might notice that any password fields are redacted when viewing the watcher. To simulate you'll need to put in the password to the right field, and then try to run the simulation again.

1 Like
7

Hi Andrew,
I gave password as input, but still I'm getting same error.

I tried this command.
POST _watcher/watch/error_report/_execute
{
"trigger_data" : {
"triggered_time" : "now",
"scheduled_time" : "now"
},

"ignore_condition" : true,
"action_modes" : {
"my-action" : "simulate"
},
"record_execution" : true
}

This command works fine.
Thank you...!
Hiruni

8

Interesting, glad the command you just put is working fine.

1 Like
9

Hi Andrew,

But the watcher is not firing at the scheduled time. Still, I have the same problem. The above post command didn't show any errors.

So, how can we verify this watcher has registered on the trigger engine or not...?

Thank you...!
Hiruni

10

Oh ok I understand now. What version are you on? Are you running the above command from dev tools? If you are I'd recommend using the watcher ui in kibana instead.

11

Hi Andrew,

Thank you for the reply.
I'm using 8.1.2 version.
Yes...I run above command on dev-tool.

I will try watcher UI.
Thank you for your reply.

Thank you..!
Hiruni

12

Ok, nice. I bet once you have the watcher visible in kibana's UI that it will start running on a schedule. I like to start with whatever default elastic provides when setting up an advanced watch. That will make sure you schedule is all setup (but you can always change it later as well).

Good luck!

13

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.