Following are some basic functionalities that I have noticed are not working efficiently in the NPM log viewer
@aLTeReGo @jblankjblank
Hey There,
1.Time interval for search is defined by current view (Last hour, last ten minutes, etc.)
2. We recognize these limitations however there is a workaround. When full text is enabled (default & recommended), search has trouble with phrases having several token delimiters (e.g. space, equal sign, dot, …).
https://support.solarwinds.com/SuccessCenter/s/article/Enabling-full-text-search-limits-search-functionality-in-LM?language=en_US
So, in your example message above, your search string likely contains “DevIP<space>=<space>10.0.2.39”. In that case, search phrase must be modified to “DevIP=10.0.2.39” (no spaces around equal sign) if full text is enabled.
Hope this helps.
Hello @pravs88
I see the "full text search" option is only available with Log Analyzer?I have 1600+ nodes feeding my syslog database, so I have to pay $24k for LA1000 which limit up-to 1000 nodes to be able to partially search.So far, I'm not able to create views or reports using the "contains" boolean, reports and views list "yesterday's" entries timeout, and I've been getting out-of-memory errors when my main server and my database server have 128GB RAM each.
Legacy syslog client application used to work amazingly well, and it was included with the NPM license..