endpoint and specifically the code that does the host querying? I think I might be looking for something like
based off what I've read in
? Seems like there could be some sort of bug in play and want to understand what exactly is happening here.
- where it's doing something like
, where the
MATCH(host_name) AGAINST('h*' IN BOOLEAN MODE)
is the user supplied portion of text. Running that query manually, it mimics the incorrect/missing results I see in the UI. So not entirely what is going wrong with my SQL table/database. I assume the full text index being used for the search is somehow incorrect, but my SQL knowledge is pretty limited.
is set to 3 and
is set to 4. In addition, the
can not be used as a token, so when I have systems named something like
, there aren't any tokens available that can be searched on and so searches fail. (Side note, typing
into the select hosts dropdown, results in a 500 error and a SQL error returned) This was also effecting the ability to search with some IP addresses, especially if your hosts use only 2 digits or less in each octet. End result, I modified
to 1 and rebuilt the FULLTEXT index on the hosts table. This results in getting the appropriate results back for all of my hosts.