Open Danouchka opened 1 year ago
cc @pmeresanu85 @lalit-satapathy @ManojS-shetty
Pinging @elastic/elastic-agent (Team:Elastic-Agent)
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
. Thank you for your contribution!
Currently A named instance can be running on a machine and the 'Microsoft SQL Server' integration connecting to localhost: instance port, or the machine ip: instance port. (We are not talking here about the instance vip:instance port)
Issue If the sql instance goes down, because it was moved to the other machine of the sql cluster, then the integration, actually elastic-agent, will fire a lot of errors (and possibly stops collecting logs ...). As it is not an error actually, this failover should be detected and message turned into WARNING or INFO level , not ERROR and message fired a few times. (this does not prevent the integration from trying to reconnect regularly to the instance until it comes back to the machine)
Thanks