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

Smarts products: Definitions of threads seen in SM_Monitor outputs/logs (374448)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 8341Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Observed the following lines/threads from Smarts sm_monitor summary log:

InCharge Framework Current size 1
SM_ElementManager Current size 1
SubscriberFE-P-EAD-PLT-SAMN-01_NL-Driver-EventTimer Current size 1
uptime responder Current size 1
SubscriberFE-EventTimer Current size 1
Flow KeepAlives Current size 39
SubscriberFE-P-EAD-PLT-SAMN-02_NL-Driver-EventTimer Current size 1
SM_PropertyPoller Current size 1
ICS_ActionScheduler::ICS-ActionScheduler Current size 1070
SM_LicenseManager Current size 9
SubscriberFE-P-EAD-PRSN-SAMT_Event-Driver-EventTimer Current size 1

Do not know meaning of threads like InCharge Framework, SubscriberFE-P-EAD-PLT-SAMN-01_NL-Driver-EventTimer seen in Smarts sm_monitor summary log

Purpose

Provide definitions of threads seen in SM_Monitor outputs
What is the meaning of the lines/threads which are present in sm_monitor logs?

Resolution

The definitions of threads seen in SM_Monitor outputs as shown above are as follows:

1. InCharge Framework
A thread associated with a timed queue to provide general timing services to the server. Not related to processing external events received from the monitored domain. Users can ignore this thread.

2. SM_ElementManager
A thread associated with a timed queue to facilitate the function of periodically checking the active status of system components. Not related to processing external events received from the monitored domain. Users can ignore this thread.

3. SubscriberFE-P-EAD-PLT-SAMN-01_NL-Driver-EventTimer
This is the companion thread of the corresponding SubscriberFE's socket observer thread. It is also associated with a timed queue.
This thread is used by the corresponding SubscriberFE object to facilitate the implementation of some timing services, such as it can generate periodic timer events and inject the events into the notification data flow for the .asl script (executed on the event driver thread) to process.
Users can ignore this thread as well.
*For this particular thread, it is part of the thread group associated with a domain named as P-EAD-PLT-SAMN-01 (in relevance to the user scenario given).*

4. uptime responder
A thread associated with a timed queue to provide the "heartbeat" service to the server's client applications. Users can ignore this thread.

5. SubscriberFE-EventTimer
A thread with the same nature as (3) but associated with a subscriber front end with a default queue name. Can be ignored.

6. Flow KeepAlives
A thread created by TCP flow management function to facilitate the implementation of exchanging keepalive bits between the two end points of a TCP connection. Users can ignore the threads of this type.

7. SubscriberFE-P-EAD-PLT-SAMN-02_NL-Driver-EventTimer-
Please See (3).

8. SM_PropertyPoller
A thread used to facilitate the implementation of monitoring property changes of objects stored in repository. Users may see temporary queue accumulation of this thread from time to time when the server sees a burst changes of object properties. An accumulation of this queue may explain the temporary slowness of SAM. But in general, this queue should be able to clear itself in time.

9. ICS_ActionScheduler::ICS_ActionScheduler
A thread associated with a timed queue as well. The thread provides timing service to the SAM server to facilitate periodic automatic tasks - such as autoarchiving or acknowledgement or event state auto-clean up, etc. An accumulation of this queue may indicate the server is busy with automatic tasks created to continue processing received notifications at delayed time according to the policy configured for notification processing.

10. SM_LicenseManager
A thread dedicated to perform license related management tasks.

11. SubscriberFE-P-EAD-PRSN-SAMT_Event-Driver-EventTimer
Please See (3).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant