AppFabric SQL Monitoring Database Connected Connection Class

  • ID:  Microsoft.ApplicationServer.MonitoringStoreConnectedConnection
  • Description:  This class represents a connection between the event collection service and a monitoring database that has been verified via a SQL connection.
  • Class Hierarchy: 
    Object
    Configuration Item
    Logical Entity
    Local Application
    AppFabric SQL Database Connection
    AppFabric SQL Monitoring Database Connected Connection

  • Attributes:  Public, Hosted
Login
There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. This monitor periodically checks that a SQL monitoring database is accessible via a SQLConnection. If the database is not accessible then monitoring data might be getting lost on machines that are collecting events. In the unlikely event that an exception occurs while processing a particular event in the temporary (staging) table, the raw event is deposited into a failed staging table. The monitoring database logs administrative events in a table called the operations history table. This monitor checks that table for errors and surfaces them. This monitor checks to see if a SQL Instance Store is installed in the same database as the monitoring database artifacts. The AppFabric SQL monitoring database stores events in a temporary table and then periodically imports them into tables that are visible to external tools such as IIS Manager. If that table grows too large, it is most likely that your applications are emitting events at a rate that is faster than the import procedure can move them. This event indicates that a particular database connection threw an exception when trying to open a connection. This will usually be due to a misconfigured connection string, network connectivity issues, or security issues. This event indicates that a particular database connection threw an exception when trying to write events for an application. This will usually be due to a misconfigured connection string, network connectivity issues, or security issues. This event indicates that the Event Collection Service could not access the ETW APIs. This usually indicates that an unsupported or invalid Windows installation is present. Monitoring will not work if this problem occurs. This event indicates that the service could not open an ETW session. Monitoring will not work if this problem occurs. This event indicates that the Event Collection Service’s logon does not have sufficient permissions to perform a required ETW task. This event indicates that the service could not create an ETW session. Monitoring will not work if this problem occurs. This event indicates that there was a failure while retrying a write to a monitoring database. The event indicated how many, if any, events were lost due to the failure as well as the number of times a retry has occurred. This event indicates that an event has been collected, but no database connection has ever been established for the required destination. Since the connection was never established, the system will drop the event as opposed to buffering it and retrying. This event indicates that the Event Collector failed to add a particular event source (provider) to the current session. Monitoring will not work for the application(s) that are a part of this source. This event indicates that the Event Collection Service was unable to read a particular web.config file. This event indicates that the Event Collection Service encountered an exception at runtime while listening to ETW. If this happens, monitoring will not function. This event indicates that the Event Collector failed to add a particular event source (provider) to the current session. Monitoring will not work for the application(s) that are a part of this source. This monitor uses SCOM’s built in support for NT service monitoring to make sure the Event Collection Service is running. This event indicates that the Event Collection service failed to process an individual event. This should be very rare, but if you see it continuously there may be a problem. . This event indicates that the Event Collection Service could not unregister an event source (provider) from an ETW session. This event indicates that the event collection service encountered an unhandled exception that was unexpected. This event indicates that a particular IIS web.config file has enabled monitoring, and specifies a connection string reference. However, the referenced connection string could not be found. This event indicates that no event collector configuration was found for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. This event indicates that there was an exception while trying to read the event collector configuration for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. This event indicates that the event collection service was running successfully, but a configuration change was detected and there was an exception while trying to read the event collector configuration for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer> section of the machine’s root web.config file. The service will continue to run with the previous configuration. This event indicates that an invalid command line parameter was passed to the event collection service at startup. This will cause the service to fail and no monitoring will occur. This event indicates that multiple IIS Web Applications have configured monitoring at different levels, but use the same provider Id. This event indicates that a bulk copy plugin failed to load properly. These plugins allow the Event Collection Service to optimize its writes to a database. The system will now fall back to using ADO.NET batching which will result in lower performance. This event indicates that an event has been collected, but the buffers allocated to the destination have been filled. The event will be dropped. This usually occurs when the system is under very high stress. This class represents a connection between the event collection service and a monitoring database that has been verified via a SQL connection. This class represents a Windows NT Service that AppFabric installs. This service is responsible for collecting event data from WCF and WF services that are managed by AppFabric and sending that data to a monitoring database. This object represents an AppFabric SQL monitoring database. This database stores event data that has been collected from WCF and WF services that are managed by AppFabric.

Download diagram as a Visio file

Properties

Display Name Description
Asset Status Asset status
Connection String Hash (Key)  
Connection String Name  
Display Name Display name of the object.
Monitoring Store DB Identity  
Notes Notes
Object Status Object status
Provider  

Discovered By

Name Description
AppFabric Monitoring Database Discovery This discovery discovers connections to SQL monitoring databases that are currently in use by AppFabric managed applications on the machine. This is accomplished by reading application configuration files.

Relations

Health Source
NameClassType
Monitoring Database Connected Connections Reference Monitoring Databases AppFabric SQL Monitoring Database Connected Connection Reference
Owned By User Configuration Item Reference
Affects Customers Configuration Item Reference
Serviced By User Configuration Item Reference
Contains Configuration Item Configuration Item Membership
Is Related to Configuration Item Configuration Item Reference
Config Item References Location Configuration Item Reference
Entity Watched By Perspective Object Reference

Health Target
NameClassType
Event Collection Services Host Monitoring Database Connected Connections AppFabric SQL Monitoring Database Connected Connection Hosting
Monitoring Databases Contain Monitoring Database Connected Connections AppFabric SQL Monitoring Database Connected Connection Membership

Class Knowledgebase

Summary

This class represents a connection between the event collection service and a monitoring database that has been verified via a SQL connection.

External References
This class does not contain any external references.

See Also for Windows Server AppFabric Management Pack


Downloads for Windows Server AppFabric Management Pack