Elastic connector

Running a test on the Elastic connector has always returned one result for me, so that doesn't seem like anything is wrong. There should be a "Logs" tab in the connector settings. Enable the logs, set the log level to Info, and see what happens as the connector runs.

But the connector doesn't run automatically

And the first problem is that the one result it returns me when I "run connector once" is repeating itself, instead of going 1 by one through all alerts found. (Here you can see that I ran it twice, and the same alert was considered, although it found 2.

View files in slack

@honeybadger633 , not sure about why no alerts are ingested when you run the connector.. Could you try to re-create the connector?
Do you have any other connector installed and producing alerts?
Did this same connector work in the past for you?

As for the test results only showing the same alert, I am not familiar with Elastic connector's code, but generally speaking, the test function is for connectivity and does not retain any 'memory' or 'state'. So every time you run it you get a 'fresh' run for the connector, which means it will get the same alert, provided its still in the timeframe.

I tried re-creating the connector, as well as using both the available integrations for elastic, the test works but it won't work by itself once turned on.
Is there anything else that needs to be done so it starts pulling in data?

Thanks for the clarification regarding the "run once" aspect.

Also, is there any way I can set the connector's "Max Days Backwards" to less than 24 hours?

I can only use whole numbers, even negative numbers, such as -1 days, but not .2 or .3

But the connector doesn't run automatically

And the first problem is that the one result it returns me when I "run connector once" is repeating itself, instead of going 1 by one through all alerts found. (Here you can see that I ran it twice, and the same alert was considered, although it found 2.

View files in slack