Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4net: How to Optimize Property based Search Tree Performance in Watch4net 6.6u1 and later? (517415)

Last Updated: 5/29/2020Categories: How toTotal Views: 2292Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

With the introduction of M&R 6.8u2, Watch4net frontend search has been replaced by property based search, which increases the performance
of the frontend search as compared with indexing based frontend search. The use case for searching is mostly to get to something we know, like a full device name and interface, so that should lead to 3-4 results max. Using search to get more than 10 results was not the end goal of search.
To ensure frontend search performs

1. Make sure the filter contains as the first variable : Variable is: APG:ALL

2. Change the display policy of both  device summaries  and  interface summaries  (each their two respective results) to  Always show the node  With the display policy set to "always show" search should not perform any checks and the results should be returned immediate or under 10 seconds (even with pagination set to 100), however, the drawback is that those nodes will always be visible, even if no results are available.

3. In some rare cases, there is a possibility customer may have modified the search to the point that frontend searches are still slow. In this case, you can use the attached search.xml template to make sure frontend search is not impacted by customizations.
To upload the search.template do the following:
1. Use the admin section of the frontend (/APG/admin/#), under the ReportPack section.
2. Choose the "Default ReportPack", and select the "Search" template. From there,
3. uploaded the attached file using the "Tree Template" menu. This will overwrite you current search tree.
4. From Edit mode, you can modify it, to fit your needs. Mostly to add your circuit properties to fit your needs, under the "Interface Summaries / Interface Summaries / device,part" report. You can modify the filter here, to add additional properties, separated by the "or ( | ) operator".

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Search template.xml

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant