People you won't believe but i solve problem through chat GPT it says when in elastic-agent configuration fleet:enabled: true it overrides all inputs so the configuration must be done in ESET integration in Kibana so here is a screen shot of integration configuration:
As you see ssl config is in Custom TCP Options and the error disappeared making elastic-agent status HEATHY.
Thaks for your help that was really productive to me to know a little more about Elastic/Kibana