Wildcard searchable logs broken on OC200

Wildcard searchable logs broken on OC200

Wildcard searchable logs broken on OC200
Wildcard searchable logs broken on OC200
2024-09-30 13:44:39 - last edited 2024-10-09 15:34:49
Tags: #Logs #wildcard
Model: OC200  
Hardware Version: V2
Firmware Version: 5.14.26.23

Changes to the latest controller FW seem to have added drop-down TYPE criteria to search with, but has removed or broken most wildcard search capability.  OC200 v2 5.14.26.23 with ER7206 v1 1.4.1 gateway.  Seems we are forced to select a TYPE of message, then only search hits within that TYPE will display.  This makes troubleshooting much more difficult when trying to retrace a client's experience with the logged contents.  

 

Here is the result of a search for client APHYBRID8y1MMIw without any TYPE selection...  

 

Contrary to the above results, the client does exist in the logs.  Only IP address seems to remain functioning as a wildcard search criteria.  Client name, MAC, AP, or any other BLUE attributes are no longer searchable.  Note the various TYPE of activity found in this sample search by CONTENT being IP ADDRESS of the client.    Client APHYBRID8y1MMIw has IP: 192.168.0.73.  Searching under the IP does yield the following sample of results... 

 

This issue doesn't exist on another system running ER7212PC v1.0 with 5.14.0.34, where the older LOG structure remains and the wildcard search is intact.

 

 

While the log search capability is being evolved, the ability to wildcard on the blue log parameters must remain as a basic troubleshooting capability.

 

Thank you!  

  0      
  0      
#1
Options
1 Accepted Solution
Re:Wildcard searchable logs broken on OC200-Solution
2024-10-09 09:26:12 - last edited 2024-10-09 15:34:49

Hi  @RF_Dude 

 

The request can be achieved by the following steps:

 

 

With the above config, you will be able to search the logs according to the client name.

 

Recommended Solution
  0  
  0  
#3
Options
3 Reply
Re:Wildcard searchable logs broken on OC200
2024-10-02 00:54:42

Hi  @RF_Dude 

 

Hello, thank you for posting on the TP-Link community, and we certainly appreciate all your feedback and feature requests here. While we don't have any specific details that I can share around if the feature can come to the controller, or when it might, I'll make sure to log this feature request and pass it along to the team.
Feel free to let us know of any other feature requests you may have, we’d be happy to send them up for you.

  0  
  0  
#2
Options
Re:Wildcard searchable logs broken on OC200-Solution
2024-10-09 09:26:12 - last edited 2024-10-09 15:34:49

Hi  @RF_Dude 

 

The request can be achieved by the following steps:

 

 

With the above config, you will be able to search the logs according to the client name.

 

Recommended Solution
  0  
  0  
#3
Options
Re:Wildcard searchable logs broken on OC200
2024-10-09 15:34:13

  @Vincent-TP Thanks for this tip.  It isn't straightforward, and is an extra step.  

 

I confirmed that it works in your new controller release.  The previous Wildcard search (Type, Level, or Content) has been replaced with displayed COLUMN specific search.  Since default column displays are minimal for a narrower screen, additional columns to be included in the search require deliberate action to select via checkbox.  I guess there was a need to restrict search to a column for a faster user experience?  Or to allow for culling to a TYPE of error/warning/status?  

 

  1. In the right side ACTION three dots, change from default columns to either ALL or reduce to CUSTOM columns with checkboxed searchable columns.  
  2. Clicking on EXPAND, the search form is revealed. 
  3. Any info in any search box can cull the data out of the displayed columns.    Columns not displayed are not considered.  

 

This does work.  An extra step is required.  Not as intuitive as the previous method.  Thank you Vincent for the assistance.  

 

RF Dude 

  1  
  1  
#4
Options

Information

Helpful: 0

Views: 232

Replies: 3

Tags

Logs
wildcard
Related Articles