-
Re: What are the things that Solarwinds cannot do?
dhanson Apr 15, 2015 12:56 PM (in response to peradojr)2 of 2 people found this helpfulTo be perfectly honest, this list is going to be short. There's enough flexibility to the Orion platform where you can do pretty much anything you want if you have the time/patience/knowledge to do it. At this point, most of what SolarWinds can't do is either subtle or cosmetic.If you want, check the Feature Requests pages for each module you are interested in. This would be a great place to see what SolarWinds can't do yet. Here's the link for NPM's, and these pages exist for each module: Network Performance Monitor Feature Requests
Here's a few of the things that I'd like to see:
1. Better event correlation. Right now, groups and dependencies aren't that great. What I've seen of 11.5's dynamic dependency generation leaves much to be desired. Ultimately, we need a correlation step or tagging system that can reduce the amount of noise that comes from a single outage. Right now, if you lose a core device that is a single point of failure, you'll still get alerts from all of its dependencies, and each of the affected nodes might alert in all ways possible (e.g. "node down" alert, "packet loss" alert, "neighbor down" alert) . If you have a larger environment, and a lot of attributes you want to alert on, this could become an unreasonable amount of noise. I have a very small implementation, and I can get between 30-300 e-mails for a single core device going down.
2. This idea: If...Then...Else statements for Alert Manager. The concept is easy, the logic is well known and popular, and common to multiple programming languages. I understand this would be a pain to merge with SQL in a way that could dynamically populate SQL queries with each alert, which is likely why this hasn't gained traction on the SolarWinds side, but it would make alert creation significantly easier to understand and design. Even for incredibly complex alerts. Right now, the alert logic takes some getting used to, but once you get the idea, it's relatively easy to manage for simple alerts, and you can create custom SQL alerts if the rules you want to place aren't available through the standard logic...which has lead to me learning SQL, in addition to my other languages, out of necessity, and solely for SolarWinds.
3. SolarWinds really has two alerting features: poll-based and traps. Poll-based is really good and can track nearly anything, but suffers from its alert creation logic (hence #2 above) and has the same weaknesses of any polling engine: latency/delay on the poll rate. For those occasions where you need the alert immediately when the situation occurs, then the trap handler is used. These two systems are not natively integrated. What this means is: if a condition exists on a device that results in a trap, AND you have an alert configured that checks against the same conditions, you could potentially receive 2 alerts for the exact same event. So now you're stuck with the decision of alerting on that event solely by polling or trapping, or accepting the fact that you'll get double notifications (or more). I believe there should be a way to relate incoming traps with configured poll-based alerts, but as it stands right now, there is no relationship between these two features, so you basically have to choose one or the other. Sure, you could write some script that triggers when a trap comes in that prevents (or triggers) an event to artificially create a relationship between them, but this is something that we shouldn't have to do, and should be built into the system.
4. (as of 11.0.1) Custom Query Resources are SWQL only.
Some of the perks:
1. Thwack. There are a lot of good people here, who will happily help you resolve whatever disadvantage you come across, and at worst, if the functionality you want just isn't there, you can make a Feature Request to potentially get what you want in a later release.
2. Although I may trash on the idea that I had to learn SQL, and this language serves me no other purpose, it provides a flexibility that is hard to disagree with. If I want to see the current status of all devices that use 3 unique Universal Device Pollers (UnDP's), then I can create a SQL query that will dynamically populate that based on a wide range of additional criteria, and set up a Custom Query Resource that displays that where ever I'd like. I can then create a regular report on the status of these UnDP's, graph them, and alert on them based on their unique values. Between alert generation, reporting and custom resources, SQL is the key to unlocking most of SolarWinds' potential.
3. For all of the issues I listed above, there are workarounds. That's the thing about SolarWinds. It will do whatever you want it to do, you just have to have the vision (and time) to bend it to your will. If you are looking for an out-of-the-box solution, SolarWinds can do that, too, but to really unlock its full potential, you just have to really play with it. When your Custom Summary Report displays a high-level view of your network availability, prediction of future utilization figures and provides recommendations on hardware updates for End of Support devices on a weekly/monthly/annual basis, and it delivered this automagically to your boss, there's a sense of accomplishment that will wash over you while you sit with your feet up watching Orion do your job for you.
Good luck!
-
Re: What are the things that Solarwinds cannot do?
alexslvApr 16, 2015 10:34 AM (in response to dhanson)
4 of 4 people found this helpful1. Solution: Automatic Dependencies Based On Custom Properties (Node Location)
2. +1 vote from me on the idea, although I am already triggering actions dynamically (sending emails to the right team) based on custom properties with the help of SQL macros in TO/CC fields
3. I agree, although this does not answers the original question - it is a nice to have feature, but it does not limit monitoring capabilities a dime
4. Same as #3 ... so what? You can use report written in SQL in Report-Writer to display as resources on pages. Alternatively, you can also build custom tables based on SQL queries for on page resources
-
Re: What are the things that Solarwinds cannot do?
dhanson Apr 16, 2015 11:09 AM (in response to alexslv)1 of 1 people found this helpfulHi Alex,
In general, Perk #3 applies to all of the items I mentioned. There's always something you can do to make it work, regardless of the issue you're facing. The problems with SolarWinds at this point are the complexity of the workarounds.
1. This was our alternative, and what we have implemented. Like I said in the perks #3, there's always a workaround.
2. I manipulated the trigger logic to work for me, and the rest are custom SQL alerts. Some of my more complex alerts could be simplified a great deal if this were to be implemented.
3. His initial question was what can't SolarWinds do, and right now, it can't natively integrate polling and traps. You're right, it doesn't limit capabilities at all, but it does affect your "noise" level, which is a problem with all NMS solutions. I believe this user is asking about this because he's scoping out different NMS solutions, and is asking about PRO/CONs for SolarWinds.
4. Yeah, this one was definitely a "so what?" item. Again, Perk #3: there's always a workaround, and you just described several of them. Perhaps I should've just left this one off. It's more of a pet peeve than a true problem. =)
Hope this makes sense.
-
-
-
Re: What are the things that Solarwinds cannot do?
daveb7114 Apr 15, 2015 2:52 PM (in response to peradojr)Peradojr,
Please elaborate on what you would LIKE to be able to do and it will be easier for someone to respond to each aspect. I have been using Solarwinds for about 5 years now and as previously commented above, it can span a wide range of capability. Please respond with some specifics and we can go from there.
Thanks!
Dave Burton
Loop1 Systems
-
Re: What are the things that Solarwinds cannot do?
Craig NorborgApr 16, 2015 10:05 AM (in response to peradojr)
1 of 1 people found this helpfulAs of yet I have not been able to get it to get me a breakfast burrito (with or without green chile), or a soda...
It doesn't cook bacon...
I've never seen it catch a train or a plane...
It doesn't monitor children for you...
To the best of my knowledge, it's unable to send back nearly indestructable robots in time to aid it in taking over the world by killing Sarah Connor...
-
Re: What are the things that Solarwinds cannot do?
zackmApr 20, 2015 8:04 AM (in response to Craig Norborg)
Why on earth would anyone want a breakfast burrito WITHOUT green chile?!?!?!
What is this anarchy?
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 22, 2015 12:12 PM (in response to Craig Norborg)
If you do some training at Loop1 Systems they will get the Breakfast Taco and Green Sauce for you (for some reason they get red sauce too, i think this is for the Gringo's).
Per the Monitoring Children, i think the issue is the Bio-integration with the Hardware health monitoring, but for now you can just use ICMP.
*You should be able to PING if you set said child's wireless device to a static IP when on the home wireless. Alert when pings respond and when they stop responding.
& We still have time to figure out this time travel thing...
-
Re: What are the things that Solarwinds cannot do?
robertcbrowningOct 21, 2016 2:56 AM (in response to cahunt)
I'm still worried about pinging children around the ear. They call it abuse in the UK.
-
-
Re: What are the things that Solarwinds cannot do?
jkrenzien Oct 20, 2016 9:57 AM (in response to Craig Norborg)None of this is the fault of SolarWinds, but the systems you are trying to control. If you have a machine that breakfast burritos and bacon and an wireless blood sugar monitor it sure could get that made for you. You could also have it control the emergency plan catching systems and potentially shutdown or redirect trains if you put your mind to it. As for children, wirelessly monitor vitals, GPS, noise. Yes you would need something to interrupt it before SolarWinds could handle it, but it is not impossible. You fix the time travel thing and I will work up a system to figure out and send snmp traps with where and when to send the robots. All of it require scripting and some invention, but none of it would be a limitation of SolarWinds...
Darn it now I want to work on the child monitor that would be awesome to have!
-
Re: What are the things that Solarwinds cannot do?
HerrDoktor Oct 22, 2016 3:03 AM (in response to Craig Norborg)Monitoring the kids seems to be one of the best ideas I have ever seen on Thwack
-
Re: What are the things that Solarwinds cannot do?
RichardLettsNov 3, 2016 10:27 AM (in response to Craig Norborg)
Whenever someone says something is impossible in Orion, I think how it might be achieved, which sometimes ends up a little Heath Robinson
To monitor children using Solarwinds Orion:
1. get yourself a Raspberry Pi with a Camera wireless card
2. setup motion detection and image capture software
3. when motion is detected, send a syslog or trap to Orion (see my posts on how to raise alerts from Traps or Syslog messages)
Optionally (if you have more than one child)
- ask your vet to embed a pat-tracker chip in your children
- Connect a pet-chip reader to your RaspPi so the trap/syslog message can include a child-identifer.
Here is an example for cat monitoring that could be extended: Catcierge by JoakimSoderberg
Optionally (if you have more tuits)
- identify regions of the kitchen (fridge, cookie jar, etc) and extend the syslog message to indicate the infraction
Note: this idea is untested due to lack of children -- perhaps adatole could demonstrate this on a SolarWinds Lab episode.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 3, 2016 11:00 AM (in response to RichardLetts)
-
Re: What are the things that Solarwinds cannot do?
ken_cohen Nov 3, 2016 10:29 AM (in response to Craig Norborg)I tried to install SNMP in my children so SolarWinds could monitor them. For some reason they objected...
-
Re: What are the things that Solarwinds cannot do?
cahuntJan 31, 2017 11:29 AM (in response to ken_cohen)
SNMP is not a default protocol for humons under 21, upload the protocol constraints and details to said persons flash, import into the start up config and reboot.
-
-
-
Re: What are the things that Solarwinds cannot do?
alexslvApr 16, 2015 10:12 AM (in response to peradojr)
SolarWinds is a platform, it is not a tool. Whatever is possible or not possible depends solely on you - your creativity and your willingness to come up with solution no matter what.
... Is there anything you cannot fry in frying pan?
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 22, 2015 12:14 PM (in response to alexslv)
another frying pan of equal or larger size may be an issue.. then again, just cook your bacon in the larger pan so you can make more bacon.
- then monitor with the SW Sandvich Monitor.
-
Re: What are the things that Solarwinds cannot do?
alexslvApr 22, 2015 12:57 PM (in response to cahunt)
lol you can always chop-chop-chop
-
Re: What are the things that Solarwinds cannot do?
goodzhere Apr 22, 2015 2:04 PM (in response to alexslv)I agree and I might add that it is a constantly growing platform. If the capability is not available, it is up to us (Thwack and SolarWinds customers) to voice the limitation or feature request. SolarWinds doesn't know what we want or need without us voicing it and they have given us Thwack as a means to do so. I have seen many additions from Thwack, customer feedback, research, and end-user experience sessions. And for the most part, SolarWinds does something that most competitors don't do...they listen to their customers!
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 22, 2015 1:52 PM (in response to alexslv)
-
-
-
-
Re: What are the things that Solarwinds cannot do?
wlmorris Apr 16, 2015 10:26 AM (in response to peradojr)If it cooked bacon, I would install it at home as well as at work.
-
Re: What are the things that Solarwinds cannot do?
rschroederNov 2, 2016 9:32 AM (in response to wlmorris)
It would be easy to configure NCM to cook bacon--and eggs! All it need do is send a CLI instruction to apply power to the appropriate interface through a relay or IC.
For example, where Dick Van **** energies the relay at 1:32 here: Chitty Chitty Bang Bang - You Two (HD) - YouTube That could be NCM doing the work for you.
Of course, you're responsible for the Rube Goldberg device that handles the physical side. But it would be Orion cooking the bacon!
-
Re: What are the things that Solarwinds cannot do?
ecklerwr1Nov 2, 2016 10:12 AM (in response to rschroeder)
Actually patrick.hubbard did a geek lab on some stuff he built with a raspberry pi he was remote controlling!
-
-
-
Re: What are the things that Solarwinds cannot do?
michael.kentApr 17, 2015 5:27 AM (in response to peradojr)
We've found it cannot replace the need to have a competent Networking person to understand what it all does. Despite what management think.
As people have said the Platform will do almost all you'd need. You need to put the effort in to achieve it though. Thwack will help with this.
-
Re: What are the things that Solarwinds cannot do?
alexslvApr 17, 2015 5:42 AM (in response to michael.kent)
bang on!
-
-
Re: What are the things that Solarwinds cannot do?
orioncrack Apr 19, 2015 11:08 PM (in response to peradojr)Here is my list of various application events and objects that SolarWinds does not alert on out of the box completely, or without alert trigger customization. Some may poke holes in this list. Bring it on.
This is not to say, it cannot do any of these. But merely, at this moment, I get all of these with a competing product out of the box wityh easy overrides and customiztion. SolarWinds falls way short compared to this list and the manner of deployment for a large Microsoft centroic shop. People will say what about AppInsight? AppInsight doesn't do any of this out of the box.
Many of these rules and monuitors I cannot live without. To reverse engineer and deploy all of these rules and monitors with overrides with SolarWinds would be a nearly impossible, and admittedly monumnetal task.
Microsoft.SQLServer.2012.Database.Configuration.AutoClose
Microsoft.SQLServer.2012.Database.Configuration.AutoCreateStat
Microsoft.SQLServer.2012.Database.Configuration.AutoShrink
Microsoft.SQLServer.2012.Database.Configuration.AutoUpdateStatAsync
Microsoft.SQLServer.2012.Database.Configuration.AutoUpdateSet
Microsoft.SQLServer.2012.AlwaysOn.DbrDataSynchronizationState
Microsoft.SQLServer.2012.AlwaysOn.DbrJoinState
Microsoft.SQLServer.2012.AlwaysOn.DbrSuspendState
Microsoft.SQLServer.2012.AlwaysOn.AutomaticFailoverReadiness
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupErrorPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupWarningPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupOnline
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaIsConnected
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaDataSynchronizationHealth
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaErrorPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaWarningPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaIsJoined
Microsoft.SQLServer.2012.AlwaysOn.RoleOfAvailabilityReplicaIsHealthy
Microsoft.SQLServer.2012.AlwaysOn.AllAvailabilityReplicasAreConnected
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicasSynchronizing
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicaRoleState
Microsoft.SQLServer.2012.DBEngine.BlockedSPIDsMonitor
Microsoft.SQLServer.2012.Database.DBBackupStatusMonitor
Microsoft.SQLServer.2012.DBErrorUserPolicyStateMonitor
Microsoft.SQLServer.2012.DBWarningUserPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.DatabaseReplicaErrorPolicyStateMonitor
Microsoft.SQLServer.2012.AlwaysOn.DatabaseReplicaWarningPolicyStateMonitor
Microsoft.SQLServer.2012.Database.DBStatusMonitor
Microsoft.SQLServer.2012.Database.Configuration.DBChaining
Microsoft.SQLServer.2012.Monitoring.DBFileSpaceMonitor
Microsoft.SQLServer.2012.Database.LogShippingDestinationMonitor
Microsoft.SQLServer.2012.Database.Configuration.TornPageDetection
Microsoft.SQLServer.2012.Database.Configuration.RecoveryModel
Microsoft.SQLServer.2012.DBEngine.Configuration.ServicePackLevel
Microsoft.SQLServer.2012.DBEngine.Configuration.SPNStatusMonitor
Microsoft.SQLServer.2012.Database.LogShippingSourceMonitor
Microsoft.SQLServer.2012.Agent.ServiceMonitor
Microsoft.SQLServer.2012.AnalysisServices.ServiceMonitor
Microsoft.SQLServer.2012.DBEngine.FullTextSearchServiceMonitor
Microsoft.SQLServer.2012.IntegrationServices.ServiceMonitor
Microsoft.SQLServer.2012.ReportingServices.ServiceMonitor
Microsoft.SQLServer.2012.DBEngine.UserConnectionsBaselineMonitor
Microsoft.SQLServer.2012.AlwaysOn.AvailabilityReplicasSynchronizationState
Microsoft.SQLServer.2012.Database.Configuration.TrustWorthy
Microsoft.SQLServer.2012.AlwaysOn.ClusterStateMonitor
Microsoft.Windows.InternetInformationServices.6.2.ApplicationPool.ApplicationPoolStatusCheck.Monitor
Microsoft.Windows.InternetInformationServices.6.2.Application.pool.disabled.due.to.WAS.request.failure.Monitor
Microsoft.Windows.InternetInformationServices.6.2.Application.Pool.disabled.due.to.worker.process.failure.Monitor
Microsoft.Windows.InternetInformationServices.6.2.The.identity.of.the.application.pool.is.invalid.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.WAS.Failed.To.Process.ConfigurationRequest.For.WebSite.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.Failed.To.Initialize.Logging.For.WebSite.Monitor
Microsoft.Windows.InternetInformationServices.6.2.FTPServer.NTService.CheckServiceState.Monitor
Microsoft.Windows.InternetInformationServices.6.2.FTPSite.FTPSiteStatusCheck.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.HTTP.Listening.To.Too.Many.Ports.Monitor
Microsoft.Windows.InternetInformationServices.6.2.ServerRole.NTService.CheckServiceState.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.RootApplicationDefined.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.InvalidBindings.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.InvalidURL.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.IP.Address.Not.In.HTTP.Sys.IP.Listen.List.Monitor
Microsoft.Windows.InternetInformationServices.6.2.ApplicationPool.MemoryLeak.Monitor
Microsoft.Windows.InternetInformationServices.6.2.LegacySMTPServer.NTService.CheckServiceState.Monitor
Microsoft.Windows.InternetInformationServices.6.2.LegacySMTPVirtualServer.SMTPVirtualServerStatusCheck.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WAS.has.encountered.an.error.during.the.SID.mapping.for.the.application.pool.Monitor
Microsoft.Windows.InternetInformationServices.6.2.RemoteAdmin.NTService.CheckServiceState.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.WebSiteStatusCheck.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.DuplicateBinding.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.InvalidApplicationPool.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.WAS.Did.Not.Create.Site.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebSite.WAS.did.not.process.changes.that.affect.the.web.site.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WAS.NTService.CheckServiceState.Monitor
Microsoft.Windows.InternetInformationServices.6.2.WebServer.NTService.CheckServiceState.Monitor
AD_Essential_Services_Running_2.Monitor
AD_Essential_Services_Running_1.Monitor
AD_Client_Connectivity.Monitor
AD_Client_GC_Availability.Monitor
AD_Client_PDC_Response.Monitor
AD_Client_Serverless_Bind.Monitor
AD_Database_and_Log_DBSpace.Monitor
AD_Database_and_Log_DB.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.GCSearchTime.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.LastBindMonitor.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.LostObjectCount.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.OpMasterDomainNamingLastBind.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.OpMasterInfrastructureLastBind.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.OpMasterPDCLastBind.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.OpMasterRIDLastBind.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.OpMasterSchemaLastBind.Monitor
AD_DNS_Verification.Monitor
AD_General_Response.Monitor
AD_Global_Catalog_Search_Response.Monitor
AD_Database_and_Log_LogSpace.Monitor
AD_Database_and_Log_LOG.Monitor
AD_Op_Master_Response.Monitor
AD_CPU_Overload.Monitor
AD_Replication_Monitoring.Monitor
AD_Replication_Partner_Count.Monitor
AD_Replication_Partner_Op_Master_Consistency.Monitor
Microsoft.Windows.Server.2008.AD.DomainController.TimeSkew.Monitor
AD_Monitor_Trusts.Monitor
AD_Validate_Server_Trust_Event.Monitor
AD_ADWS_Service.Monitor
Microsoft.Windows.Server.2008.AD.ConnectionObject.Monitor
Microsoft.Windows.Server.2008.AD.EssentialService.DCLocator.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.DFS.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.DFSR.ServiceCheck
Microsoft.Windows.Server.2008.AD.DC.NtFrs.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.ISM.ServiceCheck
Microsoft.Windows.Server.2008.AD.DC.KDC.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.KDC.ServiceCheck
Microsoft.Windows.Server.2008.AD.DC.Netlogon.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.NetLogon.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.NTDS.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.NTFRS.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.SysVol.ServiceCheck
Microsoft.Windows.Server.2008.AD.DC.W32Time.ServiceCheck
Microsoft.Windows.Server.2008.AD.EssentialService.W32Time.ServiceCheck
A_problem_has_been_detected_with_the_trust_relationship_between_two_domains
AD_Replication_Monitoring_A_problem_has_been_detected_with_the_trust_relationship_between_two_domains
Active_Directory_cannot_replicate_configuration_and_schema_information_5_Rule
AD_Replication_Partner_Op_Master_Consistency_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Replication_Partner_Op_Master_Consistency_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Replication_Partner_Op_Master_Consistency_Pass_through_1
AD_Replication_Partner_Op_Master_Consistency_Pass_through_2
Miscellaneous_UserEnv_Errors_5_Rule
Miscellaneous_KDC_Errors_5_Rule
Miscellaneous_NetLogon_Errors_1_Rule
Miscellaneous_SAM_Errors_5_Rule
Session_setup_failed_because_no_trust_account_exists___Script___AD_Validate_Server_Trust_Event_5_Rule
Machine_Account_Authentication_Failure_1_Rule
The_default_NTFS_security_settings_have_not_been_applied_to_Active_Directory_folders_5_Rule
Thread_in_directory_is_waiting_for_remote_procedure_call_5_Rule
Two_replication_partners_have_an_inconsistent_view_of_the_FSMO_role_holders
A_certificate_was_not_authenticated_because_the_computer_it_came_from_is_not_a_domain_controller_5_Rule
A_dll_cannot_be_loaded_because_the_software_was_incorrectly_installed_5_Rule
A_DNS_server_used_by_this_server_for_name_resolution_did_not_respond_1_Rule
A_domain_controller_has_an_extremely_high_number_of_replication_partners
A_domain_controller_has_an_unusually_high_number_of_replication_partners
A_domain_controller_made_a_replication_request_for_a_writable_directory_partition_that_has_been_denied_by_the_local_domain_controller_5_Rule
A_GPO_extension_was_not_applied_because_the_registry_extension_failed_5_Rule
A_Group_Policy_object_cannot_be_found_in_Active_Directory_5_Rule
A_Group_Policy_Object_has_not_been_processed_because_the_filter_check_could_not_be_performed_5_Rule
A_Group_Policy_Object_is_corrupt._5_Rule
A_journal_wrap_error_has_occurred_on_the_Sysvol_5_Rule
A_lingering_object_has_been_detected.__Replication_has_been_blocked._5_Rule
A_replication_island_has_been_detected_Replication_will_not_occur_across_the_enterprise
A_resource_record_for_the_computer_name_of_the_DC_is_not_registered_1_Rule
A_RSoP__Resultant_Set_of_Policies__error_occurred_5_Rule
A_schema_collision_occurred_while_replicating_a_class_definition_5_Rule
A_schema_collision_occurred_while_replicating_attribute_definitions_5_Rule
A_user_from_a_different_forest_logged_onto_this_machine._Group_policy_processing_has_been_effected._5_Rule
A_well_known_account_has_been_recreated_because_it_did_not_exist_5_Rule
A_well_known_group_has_been_recreated_because_it_did_not_exist_5_Rule
Account_Changes_Report_Available_5_Rule
Account_creation_will_fail_on_this_domain_controller_until_the_account_identifier_pool_is_obtained_5_Rule
Account_Name_Not_Unique_5_Rule
Accounts_with_the_same_SID_have_been_detected___one_has_been_deleted_5_Rule
Active_Directory_cannot_allocate_a_new_domain_controller_GUID_5_Rule
Active_Directory_cannot_be_initialized_5_Rule
Active_Directory_cannot_boot_normally_because_the_database_was_in_an_incorrect_state_5_Rule
Active_Directory_cannot_change_the_state_of_the_database_during_a_backup_operation_5_Rule
Active_Directory_cannot_construct_a_mutual_authentication_Service_Principal_Name_5_Rule
Active_Directory_cannot_create_a_new_security_descriptor_5_Rule
Active_Directory_cannot_create_the_default_security_descriptor_for_an_application_directory_partition_5_Rule
Active_Directory_cannot_delete_the_access_control_entry__ACE__for_the_domain_Domain_Controllers_security_group_on_a_newly_created_application_directory_partition_5_Rule
Active_Directory_cannot_delete_the_key_New_Database_GUID_during_the_restore_recovery_process_5_Rule
Active_Directory_cannot_find_any_RPC_protocol_sequences_installed_5_Rule
Active_Directory_cannot_function_normally_5_Rule
Active_Directory_cannot_perform_an_authenticated_RPC_call_to_another_DC_because_the_SPN_for_the_destination_DC_is_not_registered_on_the_KDC_5_Rule
Active_Directory_cannot_rebuild_the_following_number_of_indices_and_has_failed_5_Rule
Active_Directory_cannot_set_the_replication_consistency_registry_key_5_Rule
Active_Directory_cannot_update_object_due_to_insufficient_memory_5_Rule
Active_Directory_cannot_update_the_functional_level_on_the_NTDS_Settings_object_for_the_local_domain_controller_5_Rule
Active_Directory_cannot_validate_the_functional_level_of_the_domain_controller_5_Rule
Active_Directory_cannot_write_a_new_security_descriptor_for_object_5_Rule
Active_Directory_encountered_a_replication_error.__Replication_will_be_delayed._5_Rule
Active_Directory_has_failed_to_upgrade_a_critical_index_as_part_of_initialization_5_Rule
Active_Directory_shadow_copy_restore_was_unsuccessful.__The_contents_of_Active_Directory_are_unpredictable._5_Rule
Microsoft.Windows.Server.2008.AD.DomainController.DRAOutboundBytesTotal.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAInboundBytesComp.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAIntersiteInBytes.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAInboundBytes.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAInboundBytesNotComp.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAInboundBytesTotal.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAIntersiteOutBytes.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAOutboundBytesComp.Collection
Microsoft.Windows.Server.2008.AD.DomainController.DRAOutboundBytesNotComp.Collection
AD_ADWS_Service_Script_Based_Test_Failed_to_Complete
AD_cannot_allocate_memory_5_Rule
AD_cannot_find_the_NTDS_object_for_this_domain_controller_5_Rule
AD_cannot_find_the_partition_container_5_Rule
AD_cannot_release_memory_5_Rule
AD_cannot_update_object_because_the_disk_containing_the_database_is_full_5_Rule
AD_cannot_update_the_object_5_Rule
AD_Client_Connectivity_3.PerformanceCollection
AD_Client_Connectivity_2.PerformanceCollection
AD_Client_Connectivity_1.PerformanceCollection
AD_Client_Connectivity_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Client_Connectivity_AD_Client_Side_Script_Parameters_are_configured_incorrectly
AD_Client_Connectivity_Pass_through1
AD_Client_Connectivity_Pass_through2
AD_Client_Connectivity_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Client_GC_Availability_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Client_GC_Availability_AD_Client_Side_Script_Parameters_are_configured_incorrectly
AD_Client_GC_Availability_Pass_through
AD_Client_GC_Availability.PerformanceCollection
AD_Client_GC_Availability_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Client_Pack_DC_discovery_encountered_an_error_some_machines_will_not_be_monitored_by_the_client_pack
AD_Client_PDC_Response_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Client_PDC_Response_AD_Client_Side_Script_Parameters_are_configured_incorrectly
AD_Client_PDC_Response_1.PerformanceCollection
AD_Client_PDC_Response_Pass_through_1
AD_Client_PDC_Response_Pass_through_2
AD_Client_PDC_Response_2.PerformanceCollection
AD_Client_PDC_Response_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Client_Serverless_Bind_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Client_Serverless_Bind_AD_Client_Side_Script_Parameters_are_configured_incorrectly
AD_Client_Serverless_Bind_Pass_through_1
AD_Client_Serverless_Bind_Pass_through_2
AD_Client_Serverless_Bind_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Client_Update_DCs
AD_Client_Update_DCs_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Client_Update_DCs_AD_Client_Side_Script_Parameters_are_configured_incorrectly
AD_Client_Update_DCs_Pass_through_1
AD_Client_Update_DCs_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_configuration_information_is_missing_from_the_registry_5_Rule
AD_CPU_Overload_Pass_through_1
AD_CPU_Overload_Script_Based_Test_Failed_to_Complete
AD_CPU_Overload_Script_Parameters_are_configured_incorrectly
AD_Database_and_Log_Pass_through_1
AD_Database_and_Log_Script_Based_Test_Failed_to_Complete
AD_Database_and_Log_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Database_and_Log_1.PerformanceCollection
AD_database_is_corrupt_5_Rule
AD_Database_and_Log_2.PerformanceCollection
AD_DC_Demoted
AD_DC_Demoted_Pass_through_1
AD_DC_Demoted_Script_Based_Test_Failed_to_Complete
AD_DNS_Verification_Script_Based_Test_Failed_to_Complete
AD_DNS_Verification_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_General_Response_Pass_through
AD_General_Response.PerformanceCollection
AD_General_Response_Script_Based_Test_Failed_to_Complete
AD_General_Response_Script_Parameters_are_configured_incorrectly
AD_General_Response_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Global_Catalog_Search_Response_Pass_through_1
AD_Global_Catalog_Search_Response_Pass_through_2
AD_Global_Catalog_Search_Response_Script_Parameters_are_configured_incorrectly
AD_Global_Catalog_Search_Response_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Global_Catalog_Search_Response.PerformanceCollection
AD_internal_error__reinstall_server_5_Rule
AD_Database_and_Log_3.PerformanceCollection
AD_Database_and_Log_4.PerformanceCollection
AD_Lost_And_Found_Object_Count_Pass_through_1
AD_Lost_And_Found_Object_Count_Pass_through_2
AD_Lost_And_Found_Object_Count_Script_Based_Test_Failed_to_Complete
AD_Lost_And_Found_Object_Count_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Monitor_Trusts_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Monitor_Trusts_Pass_through_1
AD_Monitor_Trusts_Pass_through_2
AD_Monitor_Trusts_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Op_Master_Response_4.PerformanceCollection
AD_Op_Master_Response_3.PerformanceCollection
AD_Op_Master_Response_6.PerformanceCollection
AD_Op_Master_Response_5.PerformanceCollection
AD_Op_Master_Response_2.PerformanceCollection
AD_Op_Master_Response_1.PerformanceCollection
AD_Op_Master_Response_Script_Parameters_are_configured_incorrectly
AD_Op_Master_Response_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Op_Master_Response_8.PerformanceCollection
AD_Op_Master_Response_7.PerformanceCollection
AD_Op_Master_Response_10.PerformanceCollection
AD_Op_Master_Response_9.PerformanceCollection
Active_Directory_Latency_Alert_Rule_For_Windows2008
Active_Directory_Latency_Alert_Rule_For_Windows2003
Active_Directory_Latency_Alert_Rule_For_Windows2000
AD_Replication_Monitoring_Access_Denied
AD_Replication_Monitoring_Pass_through
AD_Replication_Monitoring.Helper1
AD_Replication_Monitoring.Helper2
AD_Replication_Monitoring_Script_Based_Test_Failed_to_Complete
AD_Replication_Monitoring_Script_Parameters_are_configured_incorrectly
AD_Replication_Monitoring_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Replication_Monitoring_Time_skew_detected
AD_Replication_Partner_Count_Script_Based_Test_Failed_to_Complete
AD_Replication_Partner_Count_Script_Parameters_are_configured_incorrectly
AD_Replication_Partner_Count_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Replication_Monitoring.PerformanceCollection_1
AD_Replication_Monitoring.PerformanceCollection_4
AD_Replication_Monitoring.PerformanceCollection_3
AD_Replication_Monitoring.PerformanceCollection_2
AD_Server_Moved_Site_AD_Client_Side_Script_Based_Test_Failed_to_Complete
AD_Server_Moved_Site_Pass_through_1
AD_Server_Moved_Site_Pass_through_2
AD_Server_Moved_Site
AD_Server_Moved_Site_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_Validate_Server_Trust_Event_Script_Based_Test_Failed_to_Complete
AD_Validate_Server_Trust_Event_The_AD_Management_Pack_does_not_support_the_agentless_management_mode
AD_MOM_Agent_Proxy_is_not_enabled
All_replication_partners_failed_to_synchronize
An_account_cannot_be_added_to_the_group_5_Rule
An_account_name_collision_occurred___this_may_result_in_authentication_failures_5_Rule
An_attempt_to_check_whether_group_caching_is_enabled_has_failed_5_Rule
An_attempt_to_set_the_time_was_aborted_due_to_the_offset_being_too_large_5_Rule
An_attempt_to_update_user_credentials_failed_5_Rule
An_error_occurred_while_granting_rights_to_the_Domain_Administrators_group_5_Rule
An_internal_AD_error_occurred_5_Rule
An_Intersite_Messaging_Service_request_to_modify_an_LDAP_object_failed_5_Rule
An_object_cannot_inherit_a_security_identifier__SID__from_another_object_5_Rule
An_object_has_been_duplicated_during_a_cross_domain_move_5_Rule
Attempts_to_backup_or_restore_Active_Directory_have_failed_or_will_fail_5_Rule
Attempts_to_update_Active_Directory_are_failing_5_Rule
Cannot_access_the_registry_policy_file_5_Rule
Cannot_delete_a_registry_value_5_Rule
Cannot_process_client_side_group_policy_extension_5_Rule
Cannot_read_the_GPO_history_5_Rule
Certificate_for_intersite_replication_was_rejected_5_Rule
Change_Password_on_KRBTGT_Account_Failed_5_Rule
Classes_from_COM.DLL_not_registered_5_Rule
Collection_Rule_for_No_DC_GC_in_Site_events_5_Rule
Collection_rule_for_the_Replication_Collisions_Report_5_Rule
Collection_rule_for_the_Replication_Failures_Report_5_Rule
Contacting_the_Domain_Naming_FSMO_Role_Holder_has_completed_successfully
Contacting_the_Infrastructure_FSMO_Role_Holder_has_completed_successfully
Contacting_the_PDC_FSMO_Role_Holder_has_completed_successfully
Contacting_the_RID_Master_FSMO_Role_Holder_has_completed_successfully
Contacting_the_Schema_Master_FSMO_Role_Holder_has_completed_successfully
Corrupt_Credentials_5_Rule
Could_not_determine_the_FSMO_role_holder
Cross_domain_Group_Policy_processing_has_been_aborted_because_the_other_domain_cannot_be_reached_5_Rule
DC_2000_has_failed_to_synchronize_with_its_replication_partner
DC_2003_has_failed_to_synchronize_with_its_replication_partner
DC_2008_has_failed_to_synchronize_with_its_replication_partner
DC_is_both_a_Global_Catalog_and_the_Infrastructure_Update_master_5_Rule
Direct_replication_cannot_occur_as_configured_5_Rule
DNS_registrations_of_essential_Domain_controller_records_is_failing_1_Rule
Domain_Operation_Mode_has_been_changed_to_Native_Mode_5_Rule
Duplicate_account_names_were_detected___one_account_has_been_renamed_5_Rule
Duplicate_moved_object_detected_5_Rule
Duplicate_User_Principal_Names_have_been_detected_5_Rule
Failed_to_ping_or_bind_to_the_Domain_Naming_Master_FSMO_role_holder
Failed_to_ping_or_bind_to_the_Infrastructure_Master_FSMO_role_holder
Failed_to_ping_or_bind_to_the_PDC_FSMO_role_holder
Failed_to_ping_or_bind_to_the_RID_Master_FSMO_role_holder
Failed_to_ping_or_bind_to_the_Schema_Master_FSMO_role_holder
Format_of_schedule_object_attribute_unrecognized_5_Rule
FRS_has_not_replicated_one_or_more_files_in_the_Sysvol_to_other_domain_controllers_5_Rule
FRS_is_scanning_the_system_volume_before_sharing_it_5_Rule
Group_Cache_Refresh_cannot_obtain_a_connection_schedule_to_it_s_preferred_site_5_Rule
Group_Cache_Refresh_cannot_schedule_an_update_5_Rule
Group_Cache_Refresh_found_a_GC_in_a_non_optimal_site_5_Rule
Group_Cache_Refresh_has_reached_the_user_limit_for_this_domain_controller_5_Rule
Group_policy_processing_aborted___cannot_connect_to_the_Directory_Service_5_Rule
Group_policy_processing_aborted___cannot_determine_site_5_Rule
Group_policy_processing_aborted___reboot_this_machine_5_Rule
Group_policy_processing_aborted___the_search_for_the_root_AD_object_failed_5_Rule
Group_Policy_processing_aborted_because_a_filter_check_for_the_GPO_failed_5_Rule
Group_Policy_processing_aborted_because_the_common_name_for_the_GPO_cannot_be_accessed_5_Rule
Group_policy_processing_aborted_because_the_GPO_does_not_have_a_version_number_5_Rule
Group_Policy_processing_has_been_aborted__in_planning_mode__because_the_user_computer_does_not_have_access_to_a_required_object_5_Rule
Group_Policy_processing_has_been_aborted_because_an_invalid_class_of_object_was_discovered_5_Rule
Group_Policy_processing_has_been_aborted_because_GPO_lists_cannot_be_set_up_5_Rule
Group_Policy_processing_has_been_aborted_because_of_an_invalid_access_configuration_5_Rule
Group_Policy_processing_has_been_aborted_because_the_extensions_from_the_registry_cannot_be_read_5_Rule
Group_Policy_processing_has_been_aborted_because_the_file_gpt.ini_cannot_be_accessed_5_Rule
Group_Policy_processing_has_been_aborted_because_the_GPLink_property_of_an_object_cannot_be_accessed_5_Rule
Group_Policy_processing_has_been_aborted_because_the_GPO_does_not_have_a_functionality_version_number_5_Rule
Group_Policy_processing_has_been_aborted_because_the_user_does_not_have_access_to_an_object_5_Rule
Group_Policy_processing_was_aborted_because_a_security_check_failed_5_Rule
Group_Policy_processing_was_aborted_because_historical_data_cannot_be_moved_from_the_users_old_SID_to_their_new_one_5_Rule
Group_Policy_processing_was_aborted_because_security_cannot_be_set_on_Group_Policy_events_5_Rule
Group_Policy_processing_was_aborted_because_the_refresh_timer_cannot_be_set_5_Rule
Group_Policy_processing_was_aborted_because_the_search_for_objects_cannot_be_completed_5_Rule
Group_Policy_processing_was_aborted_because_the_security_ID_of_the_user_cannot_be_obtained_5_Rule
Group_Policy_processing_was_aborted_because_the_users_security_ID_cannot_be_written_to_the_registry_5_Rule
Group_Refresh_updates_are_falling_behind_5_Rule
Initial_replication_after_domain_controller_promotion_has_not_completed
Internal_async_schema_cache_update_failed_5_Rule
Inter_Site_Messaging__ISM__Service_SMTP_Transport_plug_in_has_determined_that_one_or_more_classes_from_CDO_library_are_not_registered_as_expected_5_Rule
Inter_Site_Messaging__ISM__Service_SMTP_Transport_plug_in_has_encountered_an_unexpected_error_from_CDO_library_5_Rule
Inter_Site_Messaging_Service_SMTP_Transport_plug_in_failed_to_add_SMTP_routing_domain_5_Rule
Inter_Site_Messaging_Service_SMTP_Transport_plug_in_failed_to_bind_the_event_sink_ismsink.dll_to_the_SMTP_Service_5_Rule
Inter_Site_Messaging_Service_SMTP_Transport_plug_in_failed_to_read_the_SMTP_mail_message_5_Rule
Inter_Site_Messaging_Service_SMTP_Transport_plug_in_failed_to_register_the_event_sink_ismsink.dll_5_Rule
Intersite_Messaging_Service_SMTP_Transport_received_a_delivery_failure_5_Rule
Invalid_Forwarded_AS_Request_5_Rule
Invalid_object_class_5_Rule
Invalid_Policy_Data_5_Rule
Invalid_Script_Parameter_Configuration
Invalid_site_link_definition_will_be_ignored_5_Rule
ISM_cannot_receive_messages_5_Rule
ISM_Request_Failure_5_Rule
ISM_transport_has_been_shut_down_5_Rule
KCC_cannot_compute_a_replication_path_5_Rule
KCC_cannot_configure_replication_topology_due_to_ISM_failure_5_Rule
KCC_failed_to_initialize_5_Rule
KCC_failed_to_stop_5_Rule
KCC_failed_to_update_replication_topology_5_Rule
KCC_is_ignoring_a_replication_path_because_non_intersecting_schedules_are_preventing_replication_along_that_path_5_Rule
LDAP_agent_cannot_open_security_provider_5_Rule
Local_cleanup_failed_on_cross_domain_move_5_Rule
Local_group_policy_is_disabled_5_Rule
Loopback_processing_has_been_disabled_5_Rule
AD_CPU_Overload.PerformanceCollection
Machine_account_policy_failure___Active_Directory_GPO_lookup_failure_5_Rule
Machine_account_policy_failure___Security_Configuration_Engine_error_occurred_5_Rule
Manual_deregistration_of_some_DNS_records_is_required_5_Rule
Memory_Allocation_Error___the_system_may_be_overloaded_5_Rule
Memory_cannot_be_allocated_5_Rule
Missing_X.509_Domain_Controller_certificate_5_Rule
Name_conflict_detected_while_replicating_partition_5_Rule
No_changes_detected_in_the_list_of_GPOs_5_Rule
No_input_provider_to_sync_time_5_Rule
No_Key_to_Generate_Kerberos_Ticket_5_Rule
No_suitable_domain_controller_is_available_for_authentication_in_this_domain_5_Rule
None_of_the_preferred_bridgehead_servers_can_replicate_the_directory_partition_5_Rule
One_or_more_domain_controllers_may_not_be_replicating_For_2000
One_or_more_domain_controllers_may_not_be_replicating_For_2003
One_or_more_domain_controllers_may_not_be_replicating_For_2008
One_or_more_of_the_DC_Locator_DNS_records_are_not_registered_1_Rule
PAC_Verification_Failure_5_Rule
Policy_Update_Failure_5_Rule
Replication_error_5_Rule
Replication_has_been_aborted_5_Rule
Replication_has_been_stopped_with_a_source__5_Rule
Report_Collection___Machine_Account_Authentication_Failures_5_Rule
Schedule_attribute_of_siteLink_object_is_invalid_5_Rule
Schema_cache_load_failed_to_convert_the_string_default_SD_on_class_schema_object_5_Rule
Schema_cache_load_failed_to_inherit_all_attributes_for_the_class_5_Rule
Security_Descriptor_Propagator_has_been_terminated_with_error_5_Rule
Setting_the_administrators_password_failed.__It_has_been_reset_to_blank._5_Rule
Site_has_no_NTDS_Site_Settings_object_5_Rule
Site_link_was_not_found_5_Rule
The_account_identifier_pool_for_this_domain_controller_cannot_be_updated_5_Rule
The_Active_Directory_database_is_corrupt_5_Rule
The_AD_replication_process_is_unable_to_continue_5_Rule
The_attempt_to_change_the_directory_partition_name_to_a_name_that_is_not_conflicting_failed_5_Rule
The_attempt_to_discover_the_tombstone_lifetime_from_the_domain_failed_5_Rule
The_attempt_to_move_a_child_object_to_a_container_failed_5_Rule
The_behavior_version_of_the_dsa_object_is_higher_than_the_behavior_version_of_this_OS_5_Rule
The_computer_cannot_function_properly_for_authentication_purposes_5_Rule
The_computer_didnt_have_sufficient_rights_to_perform_the_secure_dynamic_update_1_Rule
The_computer_name_cannot_be_mapped_to_an_object_in_Active_Directory___this_may_result_in_authentication_failures_5_Rule
The_computer_s_domain__1_is_unavailable.___2_.__5_Rule
The_connection_object_translation_task_in_the_consistency_checker_is__disabled_5_Rule
The_DC_was_unable_to_obtain_the_next_account_identifier_5_Rule
The_deleted_list_for_an_extension_cannot_be_obtained_5_Rule
The_directory_forest_behavior_version_and_or_domain_behavior_version_are_changed_to_values_incompatible_with_this_version_of_Windows_5_Rule
The_directory_partition_cannot_be_replicated_over_a_specified_transport_because_none_of_the_domain_controllers_support_the_transport_5_Rule
The_DNS_server_with_which_this_DC_will_register_does_not_support_1_Rule
The_domain_behavior_version_or_the_forest_behavior_version_is_incompatible_with_this_version_of_Windows_5_Rule
The_Domain_Changes_report_has_data_available_5_Rule
The_domain_controller_failed_to_obtain_a_new_account_identifier_pool_5_Rule
The_Domain_Controller_has_been_started_5_Rule
The_Domain_Controller_has_been_stopped_5_Rule
The_Domain_Controller_has_shutdown_unexpectedly_5_Rule
The_domain_controller_is_booting_to_directory_services_restore_mode_5_Rule
The_DS_Service_Configuration_object_is_not_found.__You_will_not_be_able_to_set_service_parameters._5_Rule
The_GPO_cannot_be_processed_because_it_was_created_by_an_old_version_of_the_GPO_editor_5_Rule
The_group_caching_option_has_now_been_properly_updated_5_Rule
The_Group_Policy_client_side_extension_failed_to_execute_5_Rule
The_Inter_Site_Messaging_Service_cannot_allocate__memory_5_Rule
The_Inter_Site_Messaging_Service_cannot_perform_a_requested_LDAP_bind_operation_5_Rule
The_Inter_Site_Messaging_Service_encountered_a_malformed__transport_distinguished_name_5_Rule
The_Inter_Site_Messaging_Service_encountered_an_error_while__attempting_to_start_the_Service_Control_Dispatcher_5_Rule
The_Inter_Site_Messaging_Service_failed_to_create_an_event_5_Rule
The_Inter_Site_Messaging_Service_failed_to_initialize_5_Rule
The_Inter_Site_Messaging_Service_failed_to_start_5_Rule
The_Inter_Site_Messaging_Service_failed_to_start_the_RPC_server_5_Rule
The_Intersite_Messaging_service_failed_to_start_the_RPC_server_because_it_was_unable_to_register_authentication_information._5_Rule
The_Inter_Site_Messaging_Service_failed_to_wait_for_a_message_5_Rule
The_Inter_Site_Messaging_Service_requested_to_abandon_an_LDAP_notification_message_5_Rule
The_Inter_Site_Messaging_Service_SMTP_Transport_plug_in_failed_to_remove__SMTP_routing_domain_5_Rule
The_Knowledge_Consistency_Checker__KCC__cannot_run_successfully.__Replication_may_be_affected_5_Rule
The_Knowledge_Consistency_Checker__KCC__detected_an_incompatible_up_to_dateness_vector_format_5_Rule
The_list_of_GPOs_for_this_user_or_computer_has_changed_5_Rule
The_local_domain_controller_has_attempted_to_replicate_an_object_which_is_not_present_because_it_may_have_been_deleted_and_already_garbage_collected_5_Rule
The_local_domain_controller_has_denied_a_replication_attempt_on_a_directory_partition.__This_may_pose_a_security_risk_5_Rule
The_machine_account_cannot_be_found_5_Rule
The_NetLogon_service_on_remote_machines_will_not_be_able_to_connect_to_this_DC_over_TCP_IP_resulting_in_authentication_failure_5_Rule
The_non_domain_naming_context_has_no_security_descriptor_reference_domain_5_Rule
The_number_of_Group_Policies_has_exceeded_the_maximum_limit_5_Rule
The_object_does_not_exist_in_Active_Directory_5_Rule
The_PDC_Emulator_cannot_be_contacted
The_PDC_Emulator_has_been_contacted_successfully
The_registry_key_cannot_be_created_5_Rule
The_registry_policy_file_could_not_be_accessed_during_application_of_machine_policy_5_Rule
The_registry_value_cannot_be_set_5_Rule
The_script_cannot_locate_the_server_or_its_site_in_Active_Directory
The_search_for_objects_in_the_schema_directory_partition_failed_5_Rule
The_security_descriptor_propagation_task_encountered_an_error_5_Rule
The_server_has_moved_between_sites
The_Services_container_has_more_than_one_object_of_class_msExchConfigurationContainer_as_an_immediate_child_5_Rule
The_site_cannot_be_found_5_Rule
The_site_contains_one_or_more_domain_controllers_but_is_not_connected_by_any_site_links_5_Rule
The_site_name_cannot_be_queried_for_5_Rule
The_SMTP_domain_administrative_namespace_is_not_available_at_this_time_5_Rule
The_system_clock_has_not_been_synchronized_for_some_time_5_Rule
The_system_failed_to_promote_this_server_into_a_Global_Catalog_5_Rule
The_task_that_monitors_Active_Directory_for_changes_in_the_Inter_Site_Transport_objects_failed_to_start_5_Rule
The_user_or_computer_does_not_have_access_to_a_GPO_5_Rule
The_user_or_computer_does_not_pass_the_filter_check_to_the_GPO_5_Rule
The_WMI_service_is_disabled.__A_Group_Policy_object_has_not_been_processed_5_Rule
There_are_no_domain_based_Group_Policy_objects_for_this_user_computer._5_Rule
There_are_not_enough_GCs_available
This_domain_controller_failed_to_register_as__and_will_not_advertise_as__a_global_catalog_5_Rule
This_domain_controller_has_been_promoted_to_PDC_5_Rule
This_domain_controller_will_not_start_up_because_its_machine_account_has_been_deleted_5_Rule
This_server_cannot_process_the_replication_request_5_Rule
This_server_is_no_longer_a_domain_controller_5_Rule
This_source_server_failed_to_add_schema_information_for_the_mail_replication_request_5_Rule
This_source_server_failed_to_generate_the_changes_5_Rule
Transport_initialization_failure_5_Rule
Trusted_Domain_List_Update_Failure_5_Rule
Unable_to_establish_connection_with_any_Global_Catalog_s__5_Rule
Unable_to_establish_connection_with_server_5_Rule
Unable_to_open_performance_counters_5_Rule
Unable_to_set_privileges_necessary_for_security_checks_5_Rule
Unexpected_Error_applying_group_policy_to_machine_account_5_Rule
Unexpected_SAM_Failure_5_Rule
Windows_cannot_access_information_in_the_registry_5_Rule
Windows_cannot_determine_the_role_of_this_computer._5_Rule
Windows_cannot_determine_the_user_or_computer_name._5_Rule
Windows_cannot_load_extension_5_Rule
Windows_cannot_obtain_the_domain_controller_name_for_your_computer_network._5_Rule
Windows_cannot_read_the_history_of_GPOs_from_the_registry._5_Rule
Windows_Directory_Service__Active_Directory__cannot_be_initialized_5_Rule
Windows_Directory_Service__Active_Directory__exception_5_Rule
Windows_is_setting_a_registry_value_5_Rule
WMI_Replication_Provider_is_not_installed_Replication_cannot_be_monitored_fully
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMCU_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.CannotConnectActiveDirectory
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToConnectADForLongTime
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.DomainControllerCanNotFinishReplica
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_REPORT_CONNECTION_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_REPORT_SECURITY_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.TCP_SESSIONS_EXCEEDING_AVG_BWLIMIT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.UDP_SESSIONS_EXCEEDING_AVG_BWLIMIT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.TCP_SESSIONS_EXCEEDING_PEAK_BWLIMIT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.UDP_SESSIONS_EXCEEDING_PEAK_BWLIMIT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_AddTenantAndSyndicatorLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ABHandler.ABSHTTPHANDLER_E_SERVICE_FAILED_START
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.DLExpansion.PERF_ABSWeb_AverageAbsSearchRequestProcessingTime
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.DLExpansion.PERF_ABSWeb_AbsFailedSearchRequestsPerSec
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.ABSWEBSVC_DATABASE_VERSION_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.ABSWEBSVC_E_WEB_SERVICE_FAILED_TO_INIT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.ABSWEBSVC_E_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABS.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABS.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABS.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.USER_COUNT_MISMATCH
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABWQ.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABWQ.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ABWQ.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_PRESENCE_WATCHER_NOT_FOUND
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_CANT_SUBSCRIBE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.TCP_ALLOCATE_PORT_LIMIT_EXCEEDED_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.UDP_ALLOCATE_PORT_LIMIT_EXCEEDED_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.RTCHOST_E_APPDOMAIN_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.IIS.ApplicationPool.StatusCheck.Monitor
Microsoft.LS.2013.Monitoring.IIS.Application.pool.disabled.due.to.WAS.request.failure.Monitor
Microsoft.LS.2013.Monitoring.IIS.Application.Pool.disabled.due.to.worker.process.failure.Monitor
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_ARCHIVED_QUEUE_ITEMS_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_NumberOfProcessingFailedSessions
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.CannotFindArchivingStore
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ACP.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ACP.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ACP.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_NO_MUSIC_FILES
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVConference.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVConference.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVConference.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVEdgeConnectivity.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVEdgeConnectivity.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.AVEdgeConnectivity.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.TCP_AUTHENTICATION_FAILURES_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.UDP_AUTHENTICATION_FAILURES_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Reach.WEBRELAY_DC_FAILED_MTLS_AUTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AutodiscoverService.AUTODISCOVER_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_AVERAGE_HOLDING_TIME
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_PROTO_AVERAGE_INCOMING_MESSAGE_LIFETIME
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_DB_REGIST_BAD_DB_VERSION
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVAuthEdge.PERF_MRASRequests_NUM_BAD_REQUESTS_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PDP.PERF_MRASRequests_NUM_BAD_REQUESTS_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BIDataCollectorService.BIDATACOLLECTOR_E_SERVICE_FAILED_START
Microsoft.LS.2013.Monitoring.Internal.Health.CallReliabilityAndMediaQuality.DiscoveryRunner
Microsoft.LS.2013.Monitoring.Internal.Health.CDR.CDRRunner
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_CANNOT_START_CONVERSATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.MCUINFRA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.MCUINFRA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVAuthEdge.MRAS_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.MCUINFRA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVEdge.MR_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSFileTransfer.FTA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.MCUINFRA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.MCUINFRA_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.LogRetentionCertificateAboutToExpireError
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.MRASPDP_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.PDP_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.CertificateAboutToExpireError
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Reach.WEBRELAY_ERROR_CERTIFICATE_ABOUT_TO_EXPIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.MCUINFRA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.MCUINFRA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVAuthEdge.MRAS_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.MCUINFRA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVEdge.MR_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSFileTransfer.FTA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.MCUINFRA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.MCUINFRA_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.LogRetentionCertificateExpired
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.MRASPDP_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.PDP_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.CertificateExpired
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Reach.WEBRELAY_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_E_CERTIFICATE_NOT_FOUND
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_APP_CERT_CONFIG_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.CAHandler.FAILED_TO_FIND_REGISTRAR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.CAHandler.NO_UPRP_RESPONSE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAHandler.CERT_PROV_APPDOMAIN_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FAILED_TO_CONNECT_TO_XDS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FAILED_TO_INITIALIZE_SCHEDULED_TASK
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_SCHEDULED_TASK_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_E_CERTIFICATESCHANGEDPROCESSING_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_CHECK_MCU_AVAILABILITY_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_W_MEETING_ID_QUERY_MAINTENANCE_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_W_MEETING_ID_QUERY_MAINTENANCE_FAILED_LOCAL
Microsoft.LS.2013.Url.BasePage.StatusCodeMonitor
Microsoft.LS.2013.Url.BasePage.ErrorCodeFailureMonitor
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PDP.PERF_PDPTURN_CLIENT_AUTHTIMEOUT_FAILURES_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EVENT_CLVFILTER_UNABLE_TO_LOAD_SETTINGS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.CannotFindClusterPolicy
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_HOSTING_ERROR_WHEN_BINDING_TO_SERVICE_PORT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_NO_PROVISIONING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_NO_PROVISIONING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_NO_PROVISIONING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_HOSTING_UNHANDLED_EXCEPTION_PLATFORM_THREADPOOL
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_FOCUS_NO_SIMPLE_URI_CONFIGURED
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.JoinLauncher.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.JoinLauncher.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.JoinLauncher.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_ERROR_DATACONF_JOURNAL_CORRUPTED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_DATACONF_EXPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_DATACONF_IMPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_FAILED_CONFIG_CHANGE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_CMS_EXPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_CMS_IMPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIP_E_STACK_TRANSPORT_FAILED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_FAILED_TO_CONNECT_TO_FABRIC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.HostedMigrationService.HOSTEDMIGRATION_NO_EXTERNAL_HOSTINGPROVIDER
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PDP.PERF_PDPTURN_FIRSTPACKET_TIMEOUTS_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.LYSS_GENERATE_LEGACY_CONTACT_LIST_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebConfEdge.PERF_DP_NET_SERVER_CONNECTIONS_CURRENT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.RGS.PERF_ACD_MM_CURRENT_NUM_CALLS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_ARCHIVING_FOLDER_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_ARCHIVING_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_ARCH_E_DB_UNACQUIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_ARCH_E_BAD_DB_VERSION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_CDR_E_DB_UNACQUIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_CDR_E_BAD_DB_VERSION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Lyss.UDC_EXCHARCH_E_BIG_FILE
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Lyss.UDC_EXCHARCH_W_UNABLE_TO_DELIVER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_QOE_E_DB_UNACQUIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.DATACOLLECTION_QOE_E_BAD_DB_VERSION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Lyss.UDC_SESSION_W_UNABLE_TO_ENQUEUE_DATA
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.DataConference.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.DataConference.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.DataConference.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSMaster.MASTER_E_FAILED_TO_ACQUIRE_BACKEND
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FAILED_TO_ACQUIRE_BACKEND
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_DBACCESS_QUEUE_DEPTH
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_DBACCESS_QUEUE_LATENCY
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_DBACCESS_SPROC_LATENCY
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.CannotFindDbStore
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_DB_SPACE_USED_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_DeleteSyndicatorsLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.UpdateServer.DEVICEUPDATER_INITIALIZATION_FAILED
Microsoft.LS.2013.Monitoring.Internal.Health.DiscoveryRunner
Microsoft.LS.2013.Monitoring.UnitMonitor.ManualResetEvent.Common.Disk.Corrupted
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Common.Disk.Full
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.InvalidDomainControllerConfiguration
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_LegalIntercept_EMAIL_SENDING_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_LegalIntercept_SEND_EMAIL_LATENCY
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.DataConf.PERF_DATAMCU_CONFERENCE_MCUHT_SESSION_QUEUES_STATE
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ExUMConnectivity.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ExUMConnectivity.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.ExUMConnectivity.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_W_MEETING_ID_DELETE_MAINTENANCE_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_DEACTIVATE_CONFERENCES_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MAINTAIN_CONFERENCE_PARTICIPANTS_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MAINTAIN_CONFERENCE_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.DLExpansion.PERF_DlxWeb_AverageValidRequestProcessingTime
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.DLExpansion.PERF_DlxWeb_SoapExceptionsPerSec
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.DLX_E_WEB_SERVICE_FAILED_TO_INIT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_EP_EXTERNALFQDN_MISMATCH
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ABHandler.PERF_ABSFiles_AbsFailedRequestsPerSec
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_UCS_MIGRATION_FAILURE_WITH_MALFORMED_ADDNEWIMCONTACTTOGROUPRESPONSE_REASON_COUNT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_LYSS_API_TOTAL_NUMBER_OF_FAILED_CONTACT_NOTIFICATION_GET_IM_ITEM_LIST_CALLS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Reach.PERF_WEBRELAYWebRelay_FailedDataCollaborationAuthenticationRequestPerSecond
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.StoreWeb.PERF_STOREWEB_StoreWeb_FailedNotifications
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.CPS.PERF_CPS_Planning_TOTAL_FAILED_PARK_REQUESTS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.CPS.PERF_CPS_Planning_TOTAL_FAILED_PARK_REQUEST_NO_ORBIT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.StoreWeb.PERF_STOREWEB_StoreWeb_FailedRequests
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.StoreWeb.PERF_STOREWEB_StoreWeb_FailedStorageServiceClientCalls
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMCU_E_BRIDGE_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMCU_E_ACP_NOT_REACHABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfPublicationFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.CPS.PERF_CPS_Planning_TOTAL_FAILED_FALLBACKS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_UCS_FAILED_UCS_SUBSCIPTION_COUNT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.CannotAccessLegalInterceptFileStore
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.CannotAccessLogRetentionFileStore
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSFileTransfer.FTA_E_ALL_FILE_TRANSFER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSMaster.MASTER_E_ALL_FILE_TRANSFER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FILE_TRANSFER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PresenceFocus.ES_E_REG_BACKEND_FAILED_TO_ACQUIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.XmppFederationProxy.XMPPTGWPX_E_NO_GATEWAY_CONNECTIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_ConferenceSessionQueryLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_ConferenceMessageQueryLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_P2PMessageQueryLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_P2PSessionQueryLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_NumberOfFailedGetLogUploadUrls
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_GetLogUploadUrlsLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_GetNextPageLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_ADGetNextPageLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.NoGlobalContainer
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Common.Process.ProcessorTime
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.McxService.PERF_McxWeb_CurrentlyActiveSessionsWithPresenceSubscriptions
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.HostedMigrationService.HostedUserMigration_NUMBER_OF_SYNC_TO_AD_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.HostedMigrationService.HostedUserMigration_NUMBER_OF_COM_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.HostedMigrationService.HostedUserMigration_NUMBER_OF_UNEXPECTED_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.HostedMigrationService.HOSTEDMIGRATION_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AutodiscoverService.AUTODISCOVER_NO_HOSTING_PROVIDER_FOUND
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PersistentChat.PERF_CHAT_PROTOCOL_INBOUND_QUEUE_SIZE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.GroupIM.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.GroupIM.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.GroupIM.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.IM.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.IM.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.IM.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_EP_INTERNALFQDN_MISMATCH
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PDP.PDP_IPADDRESS_NOT_CONFIGURED_IN_NCS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lwa.JOINLAUNCHER_INITIALIZATION_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PersistentChat.PERF_CHAT_PROTOCOL_LAST_MESSAGE_WAIT_TIME
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.MRASPDP_LISTEN_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVAuthEdge.MRAS_LISTEN_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_E_INITIALIZATION_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_E_LISSETTINGS_CHANGENOTIFICATIONPROCESSING_EXCEPTION
Microsoft.LS.2013.QoE.Metric.AudioQuality.AVConf.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.InterRegion.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.InterUserSite.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.Subnet.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.IntraUserSite.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.GatewayClient.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.GatewayMS.UnitMonitor
Microsoft.LS.2013.QoE.Metric.AudioQuality.MediationServer.UnitMonitor
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.BIDataCollectorService.RtcBIDataCollector
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.LegalInterceptService.RTCLISVC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.AppDomainException
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.LogRetentionService.RTCLRSVC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.LogRetentionAppDomainException
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.ProvisionService.RtcProv
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.AppDomainUnhandledException
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_APNS_PROXY_FAILED_AUTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_NOT_HEALTHY
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_APNS_PROXY_SERVICE_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_MPNS_PROXY_SERVICE_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_MPNS_PROXY_FAILED_AUTH
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PNCH.PnchService
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_POSSIBLE_OFFENSIVE_DOMAIN_ALERT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_CONFIGURATION_CHANGENOTIFICATIONPROCESSING_REQUIRESRESTART
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_STARTUP_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PNCH.PNCH_ERROR_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PhoneConf.RTCACPMCU
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_APPSHARING_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.AppSharingConf.RTCASMCU
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_AUDIO_VIDEO_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.AVAuthEdge.RTCMRAUTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMcu_FAILED_TO_SEND_FOCUS_NOTIFICATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMcu_MCUINFRA_FAILED_TO_UPDATE_MCU_HEALTH
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVConf.PERF_PLANNING_NUM_CONFERENCE_PROCESSING_DELAYS
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.AVConf.RTCAVMCU
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_MEDIA_QUALITY_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_AVMCU_SIP_LISTENING_PORT_CHANGED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_OCS_SIP_PROXY_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_SERVICE_FAILED_START
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_MRAS_REQUEST_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_E_CAS_UNREACHABLE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVConf.AVMCU_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.AVEdge.RTCMEDIARELAY
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.BackupService.LYNCBACKUP
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PDP.RTCPDPAUTH
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PDP.RTCPDPCORE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_E_MRAS_AUTHENTICATION_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_E_MRAS_RESOURCE_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CPS.RTCCPS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.ClsAgent.RTCCLSAGT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_MRAS_AUTHENTICATION_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_MRAS_RESOURCE_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CAS.RTCCAS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_CONNECTION_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_TLS_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_MRAS_AUTHENTICATION_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_MRAS_RESOURCE_FAILED_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CAA.RTCCAA
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_CONNECTION_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_TLS_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CMSFileTransfer.FTA
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.AccessEdge.RTCSRV
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.Registrar.RTCSRV
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_CHAT_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.IMConf.RTCIMMCU
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CMSMaster.MASTER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.DATABASE_UNREACHABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.MediationServer.RTCMEDSRV
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PersistentChatCompliance.RTCCHATCOMPL
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.PersistentChat.RTCCHAT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_PHONE_CONF_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.CMSReplicator.REPLICA
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.RGS.RTCRGS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_MEETING_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.WebConfEdge.RTCDATAPROXY
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MCUFactory.MCUFACTORY_DATA_CONF_MODALITY_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.DataConf.RTCDATAMCU
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.XmppFederation.RTCXMPPTGW
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.XmppFederationProxy.RTCXMPPTGWPX
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Reach.WEBRELAY_DC_FAILED_GET_MTLS_CERT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Reach.WEBRELAY_DC_FAILED_LISTEN_PORT
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.RemotePowerShell.REMOTEPS_CANNOT_FIND_MANAGEMENT_STORE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_ERROR_WHEN_BINDING_TO_WCF_PORT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AppSharingConf.PERF_ASMCUMCUHT_MCUHT_HEALTH_STATE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.IMConf.PERF_IMMCU_MCUHT_MCUHT_HEALTH_STATE
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.MCXP2PIM.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.MCXP2PIM.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.MCXP2PIM.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_MEDIA_ENDPOINT_REGISTRATION_FAIL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_CORRUPT_MEDIAFILE_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_CONFIGURATION_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_INTERNAL_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_MRAS_INTERACTION_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_PROXY_PEER_CALL_COMPLETION_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_PROXY_PEER_CONNECTIVITY_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_TRUNKING_PEER_CALL_COMPLETION_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_MAJOR_TRUNKING_PEER_CONNECTIVITY_FAILURE_ALARM
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_EPMESSAGE_E_MSG_DOMAIN_UNKNOWN_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PersistentChatCompliance.GC_COMPLIANCE_ADAPTER_STOPPED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PersistentChatCompliance.GC_COMPLIANCE_MGCCOMP_DATABASE_CONNECTION_LOST
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PersistentChatCompliance.GC_COMPLIANCE_MGC_DATABASE_CONNECTION_LOST
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PersistentChat.E_OCS_CONNECTION_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PersistentChat.GC_MGC_DATABASE_CONNECTION_LOST
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PersistentChat.GC_COMPLIANCE_LOGGING_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PersistentChat.E_OCS_MTLS_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PersistentChat.E_OCS_TRUST_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToConnectMSODSForLongTime
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToConnectPICServiceForLongTime
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_MCXCONFIGURATION_CHANGENOTIFICATIONPROCESSING_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_INITIALIZATION_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.TenantAdmin.LocpCertificateExpired
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfCookiePersistenceFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Reach.PERF_WEBRELAYWebRelay_DataCollaborationServerConnectionFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVConf.PERF_MSipConnections_NumberOfDNSResolutionFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfSyncToADFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfContactProvisionFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_QOE_REPORTS_DROPPED_DB_INSERTION_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_QOE_REPORTS_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfTenantProvisionFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_NumberOfUserProvisionFailures
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToConnectO365UpgradeServiceForLongTime
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_OAUTH_CERTIFICATE_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AutodiscoverService.AUTODISCOVER_OAUTH_NOT_CONFIGURED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_OAUTH_CONFIGURATION_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Lyss.LYSS_OAUTH_ISSUER_CONFIGURATION_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_OAUTH_STS_CONFIGURATION_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.OUTBOUNDROUTING_CALL_FAILED_NO_GATEWAY
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.OUTBOUNDROUTING_REGEX_REPLACE_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.OR_UNKNOWN_USAGE_IN_UCPOLICY
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EVENT_OUTBOUNDROUTING_EXCEPTION_REQUEST
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EVENT_OUTBOUNDROUTING_EXCEPTION_RESPONSE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OUTBOUNDROUTING_ALL_GATEWAYS_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OR_APP_DISABLED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OUTBOUNDROUTING_CALLPARK_INVALID_SERVICEID
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OUTBOUNDROUTING_CALLPARK_SETTINGS_LOAD_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OR_DATA_LOAD_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OR_DATA_LOAD_PARTIAL_SUCCESS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OUTBOUNDROUTING_GATEWAYS_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.OUTBOUNDROUTING_TRUNK_CONFIGURATION_LOAD_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.TCP_PACKETS_DROPPED_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AVEdge.UDP_PACKETS_DROPPED_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.P2PAV.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.P2PAV.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.P2PAV.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PersistentChat.PERF_CHAT_PROTOCOL_MESSAGES_UCMA_QUEUE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PersistentChat.PERF_CHAT_PROCESSING_OUT_SERVER_QUEUE_SIZE
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PersistentChatMessage.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PersistentChatMessage.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PersistentChatMessage.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.CAA.PERF_CAAPlanning_ApplicationEndpointCreationFailure
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_RP_SUBSCRIBE_POLLINGSUBSCRIBE_DB_THROTTLED_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PresenceFocus.PERF_RP_SUBSCRIBE_POLLINGSUBSCRIBE_QUERY_THROTTLED_SEC
Microsoft.LS.2013.Monitoring.Internal.Health.PoolWatcherDiscovery
Microsoft.LS.2013.Monitoring.Internal.Main.STRunner
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_OEF_RESTRICTED_PEERS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_OEF_MAXCONTACTS_PEERS
Microsoft.LS.2013.Monitoring.IIS.ApplicationPool.MemoryLeak.Monitor
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MAINTAIN_BATCHINSERTPRESENCEPOLICY_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Presence.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Presence.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Presence.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAA.CAA_E_PRIVATE_CONTACT_OBJECT_MISSING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CAS.CAS_E_PRIVATE_CONTACT_OBJECT_MISSING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_E_FAIL_CREATE_STACK
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.XmppFederation.XMPPTGW_E_NO_EDGE_CONNECTIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PSTN.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PSTN.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.PSTN.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MAINTAIN_TIMEBOUNDPUBS_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_PNS_PROXY_SERVICE_UNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.RemotePowerShell.REMOTEPS_CANNOT_READ_RBAC_ROLES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_NumberOfPermanentlyFailedSessions
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PresenceFocus.ES_E_AGGREGATIONSCRIPTREGISTRATION_TIMEDOUT
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_MAINTAIN_CLUSTER_MIGRATION_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_DISCONNECTED_FROM_FABRIC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_POOL_FAIL_BACK_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_POOL_FAIL_OVER_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EVENT_SERVICE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_FABRIC_PLACEMENT_WRITE_QUORUM_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_FABRIC_PLACEMENT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_FAILED_TO_CONNECT_TO_FABRIC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_NCS_CHANGE_PROCESSING_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_MAINTAIN_NOTIFY_USC_DOWN_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Registration.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Registration.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.Registration.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_NOTIFYPIPE_SYNC_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_NOTIFYPIPE_HEALING_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_DKM_ERROR_DURING_CMS_CERTITICATE_REPLICATION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_CONFIGURATION_ERROR_DURING_CMS_CERTITICATE_REPLICATION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_CERTIFICATE_ERROR_DURING_CMS_CERTITICATE_REPLICATION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSMaster.MASTER_E_REPLICATION_NOT_UPTODATE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FAILED_TO_INITIALIZE_SERVICEHOST
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_SERVICEHOST_STOPPED_INVALIDPORT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_SERVICEHOST_FAULTED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DLExpansion.ABSWEBSVC_COMPONENT_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_LegalIntercept_MAX_RETRIED_SESSIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MCU_ROLLOVER_TASK_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.NoRootOU
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EVENT_REPLICATIONAPP_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMcu_MCUINFRA_FAILED_TO_UPDATE_MCU_HEALTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMcu_FAILED_TO_SEND_FOCUS_NOTIFICATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMCU_E_SIP_FAILED_FOCUS_CONNECTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMCU_E_SIP_FAILED_FOCUS_CONNECTION_TLS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMcu_FAILED_TO_SEND_FOCUS_NOTIFICATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMCU_E_MRAS_REQUEST_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMcu_MCUINFRA_FAILED_TO_UPDATE_MCU_HEALTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMCU_E_SERVICE_FAILED_TO_START
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AppSharingConf.ASMCU_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ClsAgent.CLSAGENT_E_UNABLE_TO_DELETE_ETL_FILE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ClsAgent.CLSAGENT_E_TRACING_STOPPED_NO_SPACE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ClsAgent.CLSAGENT_E_SERVICE_FAILED_START
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_FOCUSCERT_INVALID
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_ALL_DATAPROXY_CONNECTION_LOST
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.DataMcu_MCUINFRA_FAILED_TO_UPDATE_MCU_HEALTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.DataMcu_FAILED_TO_SEND_FOCUS_NOTIFICATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_ALL_WEBPROXY_CONNECTION_LOST
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_FILESTORE_FULL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_FOCUSADAPTER_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_WAC_W14_INTEROP_FAIL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_WAC_DISCOVERY_FAIL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_TICKET_SERVICE_FAIL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_UNHANDLEDEXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.IMMcu_MCUINFRA_FAILED_TO_UPDATE_MCU_HEALTH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.IMMcu_FAILED_TO_SEND_FOCUS_NOTIFICATIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.IMMCU_E_FAILED_CONNECT_TO_FE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.IMMCU_E_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.MRASPDP_UNEXPECTED_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.PDP_UNEXPECTED_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.ProvDbFailedToAcquire
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.ProvDbRegsitBadDBVersion
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_NumberOfSendingFailedEmails
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_SendEmailLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.PDP.PERF_PDPTURN_SERVER_AUTHTIMEOUT_FAILURES_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_HOSTING_INVALID_POOL_CONFIG
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.ErrorInConfigStoreChangeEvent
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.ConfigStoreChangeEventError
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FatalErrorInConfigStoreChangeEvent
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LegalInterceptService.ErrorServiceDefinitionRemoved
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LogRetentionService.RemovedServiceDefinition
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PhoneConf.ACPMCU_E_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVAuthEdge.MRAS_ERROR_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVEdge.MR_ERROR_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_SERVICE_DEFINITION_REMOVED_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.DataConf.EVENT_DATAMCU_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.IMConf.IMMCU_E_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.MediationServer.MEDIATIONSERVER_ERROR_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.PDP.PDP_ERROR_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.ServiceDefinitionRemovedError
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.APIEM_E_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebConfEdge.DPROXY_EVENT_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_E_SERVICE_DEFINITION_REMOVED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_SERVICE_ENDPOINT_REGISTRATION_FAIL
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AVAuthEdge.MRAS_UNEXPECTED_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_LegalIntercept_PROCESSING_FAILED_SESSIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Reach.PERF_WEBRELAYWebRelay_SipConnectionFailuresPerSecond
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_SIP_LISTENING_PORT_NOT_PRESENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.APIEM_E_CRITICAL_APP_NOT_RUNNING
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_AUTH_SYSTEM_ERRORS_SEC
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.SIP_E_EVENT_AUTH_AUTHORITYUNAVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_THROTTLE_AVERAGE_HOLDING_TIME
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_PROTO_AVERAGE_INCOMING_MESSAGE_LIFETIME
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_PEER_AVERAGE_SEND_QUEUE_DELAY
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_PEER_AVERAGE_SEND_QUEUE_DELAY
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.AccessEdge.SIPPROXY_EVENT_CRYPT_REFERRER_DATE_SKEWED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIP_E_STACK_TRANSPORT_FAILED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_EVENT_POOL_SERVICES_DOWN
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_EVENT_POOLFQDN_MISMATCH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_EVENT_SERVERFQDN_MISMATCH
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_EVENT_DHCP_SERVER_START_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.AccessEdge.SIPPROXY_EVENT_DNS_SRV_CACHE_OVERFLOW
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_RESPONSES_LOCAL_INTERNAL_SERVER_ERROR_RESPONSES
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.AccessEdge.SIP_W_FLAT_FILE_LOG_SECURITY_ALERT
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.SIP_W_FLAT_FILE_LOG_SECURITY_ALERT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_E_FAIL_CREATE_STACK
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_AUTH_SA
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIP_E_STACK_TRANSPORT_CERT_EXPIRED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIP_E_STACK_TRANSPORT_CERT_NOT_FOUND_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIP_E_STACK_DEFAULT_OUTGOING_CERT_EXPIRED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_EVENT_ROUTINGVAL_ERROR_HEADER
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.SIPPROXY_E_OUTBOUND_TLS_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_E_BAD_CERT_CONFIGURED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.SIPPROXY_E_DEFAULT_OUTGOING_CERT_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.SIP_E_EVENT_AUTH_NTLMTIMEOUT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToConnectDNSServiceForLongTime
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CPS.CPS_SQL_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_ENQUEUE_MESSAGES_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_EXECUTE_CMD_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_DELETE_BLOB_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_GET_BLOB_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_NOTIFICATION_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_PUT_BLOB_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.StoreWeb.STOREWEB_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MAINTAIN_SUBSCRIPTION_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_CC_CALL_DECLINED_BECAUSE_OF_HIGH_LOAD
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_CC_CALL_DECLINED_BECAUSE_OF_MEMORY_PRESSURE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.ProvisionService.FailedToUpgradeTenant
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PDP.PDP_MACHINE_DISCONNECTED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PDP.PDP_MACHINE_DISCONNECTED_STALE_CREDS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIP_E_STACK_TRANSPORT_CERT_EXPIRED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIP_E_STACK_TRANSPORT_CERT_NOT_FOUND_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_PRESENCEPOLICIES_EXCEEDED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIP_E_STACK_DEFAULT_OUTGOING_CERT_EXPIRED_EVENT
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_DCReplicaLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_GetChangesLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PublishLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_ContactProvisionLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_TenantProvisionLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_UserProvisionLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_SaveLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_ROUTINGVAL_ERROR_HEADER
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.AVEdge.SYSTEM_LOW_ON_MEMORY
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Reach.PERF_WEBRELAYWebRelay_ClientDataCollaborationConnectionsClosedByThrottlingPerSecond
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.IMConf.PERF_IMMCU_ImMcu_ThrottledSipConnections
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Reach.WEBRELAY_DC_SERVER_CONN_CLOSED_THROTTLING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSFileTransfer.FTA_E_FAILED_TO_CREATE_TOPOLOGY_WATCHER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSMaster.MASTER_E_FAILED_TO_CREATE_TOPOLOGY_WATCHER
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_FAILED_TO_READ_TOPOLOGY
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_ASYNCTASK_UNHANDLED_EXCEPTIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_ASYNCTASK_STOP_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_EXCHARCH_SESSION_DROPPED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_LYSS_EWS_AUTODISCOVER_ERRORS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_EXCHARCH_IO_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_EWS_SUBSCRIPTIONS_ERRORED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_LYSS_FABRIC_UNHANDLED_EXCEPTIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_LYSS_DB_OPERATION_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_SPROC_EXECUTION_TIME_OUTS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_CURRENT_NUMBER_OF_LYSS_STALE_QUEUE_ITEMS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebScheduler.PERF_WEBSCHEDULERWebScheduler_FailedAbwqLookups
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Reach.PERF_WEBRELAYWebRelay_QueuedBytesForDataCollaborationServerConnections
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebScheduler.PERF_WEBSCHEDULERWebScheduler_FailedRequests
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_LYSS_OAUTH_AUTHENTICATION_FAILURES
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_OAUTH_STS_REQUESTS_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_LYSS_UNEXPECTED_EXCEPTIONS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_DATACOLLECTION_EXCHARCH_DEAD_LETTERS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Lyss.PERF_LYSS_API_TOTAL_NUMBER_OF_UNHEALTHY_ADAPTORS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.TXSVC_APP_DISABLED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.TXSVC_CALLPARK_SETTINGS_LOAD_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.TXSVC_TRANSLATION_RESULT_INVALID
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.TXSVC_TRANSLATION_TOO_LONG
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.TXSVC_MULTIPLE_LOCATION_PROFILE_UNKNOWN
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.PresenceFocus.ES_E_MIGRATE_CONTACTS_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.UcwaService.UCWA_ERROR_INITIALIZATION_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UDC_AGENT_W_EXCEPTION_PROCESSING_REQUEST
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UDC_AGENT_W_EXCEPTION_PROCESSING_RESPONSE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.UDC_AGENT_E_UNABLE_TO_CONNECT_IPC_QUEUE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_UDC_LYSS_IO_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_UDC_MESSAGE_DROPPED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UDC_AGENT_E_IM_BLOCKED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.UDC_AGENT_E_FAILED_TO_START
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UDC_AGENT_W_UNABLE_TO_ENQUEUE_DATA
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_E_BAD_CERT_CONFIGURED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_EP_EXTERNAL_CERT_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.AccessEdge.SIPPROXY_EVENT_EP_INTERNAL_CERT_ERROR
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_NumberOfUnexpectedExceptions
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_NumberOfUnexpectedExceptions
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Lyss.LYSS_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSFileTransfer.FTA_E_APPDOMAIN_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSMaster.MASTER_E_APPDOMAIN_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.CMSReplicator.REPLICA_E_APPDOMAIN_UNHANDLED_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.UnifiedContactStore.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.UnifiedContactStore.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.UnifiedContactStore.Perf
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_ProcessedLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_NumberOfSessionsPurgingFailedPurged
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LegalInterceptService.LegalIntercept_PurgeableLatency
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_NumberOfFailedUploadActivityLog
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.LogRetentionService.LogRetention_UploadActivityLogLatency
Microsoft.LS.2013.Url.Internal.Health.Discovery
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_USERSTORE_EXPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.BackupService.BACKUP_USERSTORE_IMPORT_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_USER_SERVICE_NOT_AVAILABLE
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_INIT_HTTP_NO_OUTGOING_CERT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_INIT_HTTP_INVALID_OUTGOING_CERT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_E_REG_BACKEND_FAILED_TO_ACQUIRE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_QUEUE_DEPTH
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_QUEUE_LATENCY
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_MAINTAIN_ENDPOINT_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_HTTP_POST_NEW_RECEIVE_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_HTTP_MESSAGE_SEND_SYNC_TIMEDOUT
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_W_SERVER_LOCAL_STORE_UNAVAILABLE_STARTUP_PENDING
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.ES_W_SERVER_REQUIRED_CONFIG_REPLICATION_PENDING
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.ES_E_UPDATE_ESSETTINGS_SPROC_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UPIN_FOUND_TEMPORARILY_LOCKED_USERS
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.UPIN_FOUND_PERMANENTLY_LOCKED_USERS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EXUMROUTING_APPLICATION_DISABLED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EXUM_HOST_AUTHORIZATION_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.Registrar.EXUM_INCOMPLETE_VOICEMAIL_CONFIGURATION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EXUM_UNKNOWN_DIALPLAN
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EXUM_INCOMPLETE_HOSTED_VOICEMAIL_CONFIGURATION
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EXUM_NO_HOSTED_VOICEMAIL_POLICY
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EXUM_DIALPLAN_FAILURE
Microsoft.LS.2013.Monitoring.UnitMonitor.TimerResetEvent.Registrar.EXUM_TOO_MANY_303
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebConfEdge.DPROXY_EVENT_SYSTEM_THROTTLING_ON
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebInfra.PERF_WEBAUTH_REQUESTS_IN_PROCESSING_TOTAL
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebInfra.PERF_WEBAUTH_UNAUTH_REQUESTS_IN_PROCESSING
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebInfra.PERF_WEBAUTH_PROXY_REQUESTS_INPROGRESS
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebInfra.PERF_WEBAUTH_REQUESTS_FAILED_APP_THROTTLE
Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.WebInfra.PERF_WEBAUTH_PROXY_REQUESTS_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebInfra.WEBINFRA_CANNOT_FETCH_ISSUER_KEYS
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebInfra.WEBINFRA_COMMUNICATION_FAILURE_TO_NEXT_HOP
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebScheduler.WEBSCHEDULER_ERROR_CERTIFICATE_EXPIRED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.WebScheduler.WEBSCHEDULER_INITIALIZATION_FAILED
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.McxService.MCX_ERROR_WSSETTINGS_CHANGENOTIFICATIONPROCESSING_EXCEPTION
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.LIService.LIS_E_WSSETTINGS_CHANGENOTIFICATIONPROCESSING_EXCEPTION
Microsoft.LS.2013.Monitoring.IIS.WebSite.StatusCheck.Monitor
Microsoft.LS.2013.Monitoring.UnitMonitor.PairedEvent.RGS.ACD_MMS_NO_DATAMODEL
Microsoft.LS.2013.Monitoring.UnitMonitor.NTService.WebServices.w3svc
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.XmppIM.Avail
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.XmppIM.Internal
Microsoft.LS.2013.Monitoring.UnitMonitor.SyntheticTransaction.XmppIM.Perf
Microsoft.Office.Sharepoint.Server.Net_CLR_Data_Sql_Client_Connections
Microsoft.Office.Sharepoint.Server.Net_CLR_Data_Sql_client_Failed_connections
Microsoft.Office.Sharepoint.Server.Net_CLR_Memory_Percentage_Time_in_GC
Microsoft.Office.Sharepoint.Server.Net_CLR_Memory_Bytes
Microsoft.Office.Sharepoint.Server.Net_CLR_Memory_Large_Objects
Microsoft.Office.Sharepoint.Server.NET_CLR_Object_Finalization_Survivors
Microsoft.Office.Sharepoint.Server.A_Content_Query_Web_Part_failed_to_return_content
Microsoft.Office.Sharepoint.Server.A_form_templates_business_logic_caused_an_OutOfMemory_exception
Microsoft.Office.Sharepoint.Server.A_runtime_exception_occurred_in_the_Business_Data_Catalog_database_adapter
Microsoft.Office.Sharepoint.Server.A_runtime_exception_occurred_in_the_Business_Data_Catalog_Web_service_adapter
Microsoft.Office.Sharepoint.Server.A_site_copy_operation_has_failed_leaving_the_site_structure_in_an_unusual_state
Microsoft.Office.Sharepoint.Server.A_site_deletion_operation_has_failed_leaving_the_site_structure_in_an_unusual_state
Microsoft.Office.Sharepoint.Server.A_site_move_operation_has_failed_leaving_the_site_structure_in_an_unusual_state
Microsoft.Office.Sharepoint.Server.Administration_site_for_the_Shared_Service_Provider_is_missing
Microsoft.Office.Sharepoint.Server.ASP_Compiled_Templates_Cached
Microsoft.Office.Sharepoint.Server.ASP_Current_Templates_Cache
Microsoft.Office.Sharepoint.Server.ASP.NET_Applications
Microsoft.Office.Sharepoint.Server.ASP.NET_Worker_Process_Restart
Microsoft.Office.Sharepoint.Server.Audience_Compilation_failed
Microsoft.Office.Sharepoint.Server.Availabilty_of_Memory_in_Bytes
Microsoft.Office.Sharepoint.Server.Business_Data_Catalog_Web_Service_Adapter_transport_error
Microsoft.Office.Sharepoint.Server.Cache_Bytes
Microsoft.Office.Sharepoint.Server.Cache_Faults_Per_Sec
Microsoft.Office.Sharepoint.Server.Cannot_initialize_disk_based_cache_because_the_specified_location_is_inaccessable
Microsoft.Office.Sharepoint.Server.Committed_Memory_in_Use
Microsoft.Office.Sharepoint.Server.Content_Database_Synchronization_failed
Microsoft.Office.Sharepoint.Server.Content_deployment_job_could_not_contact_the_destination_server
Microsoft.Office.Sharepoint.Server.Context_Switches_Per_Sec
Microsoft.Office.Sharepoint.Server.Could_not_parse_the_regular_expression_for_disk_based_cache
Microsoft.Office.Sharepoint.Server.CPU_Total_Processor_Time
Microsoft.Office.Sharepoint.Server.Crawl_failed_because_no_contact_e_mail_is_set
Microsoft.Office.Sharepoint.Server.Crawler_cannot_read_from_registry
Microsoft.Office.Sharepoint.Server.Crawler_exception
Microsoft.Office.Sharepoint.Server.Database_out_of_space
Microsoft.Office.Sharepoint.Server.Disk_Block_Read_Size
Microsoft.Office.Sharepoint.Server.Disk_Block_Write_Size
Microsoft.Office.Sharepoint.Server.Disk_Request_Read_Count
Microsoft.Office.Sharepoint.Server.Disk_Request_Read_Size
Microsoft.Office.Sharepoint.Server.Disk_Request_Write_Count
Microsoft.Office.Sharepoint.Server.Disk_Request_Write_Size
Microsoft.Office.Sharepoint.Server.Disk_Usage_Disk_Time
Microsoft.Office.Sharepoint.Server.Document_converter_failed_to_create_an_HTML_page
Microsoft.Office.Sharepoint.Server.Document_converter_was_unable_to_send_confirmation_email
Microsoft.Office.Sharepoint.Server.Enabling_features_failed_on_some_sites
Microsoft.Office.Sharepoint.Server.Enabling_features_on_existing_sites_failed
Microsoft.Office.Sharepoint.Server.Encountered_errors_while_indexing_anchor_text
Microsoft.Office.Sharepoint.Server.Error_adding_enterprise_application_definition
Microsoft.Office.Sharepoint.Server.Error_backing_up_registry_to_Shared_Services_Provider_database
Microsoft.Office.Sharepoint.Server.Error_communicating_with_Excel_Calculation_Services
Microsoft.Office.Sharepoint.Server.Error_deleting_enterprise_application_definition
Microsoft.Office.Sharepoint.Server.Error_retreiving_credentials
Microsoft.Office.Sharepoint.Server.Error_retreiving_cryptographic_sign
Microsoft.Office.Sharepoint.Server.Excel_Calculation_Services_is_not_running_locally
Microsoft.Office.Sharepoint.Server.Excel_Calculation_Services_not_available
Microsoft.Office.Sharepoint.Server.Exception_occurred_during_Business_Data_Catalog_Web_service_proxy_generation
Microsoft.Office.Sharepoint.Server.Exception_occurred_in_the_Business_Data_Catalog_database_adapter_connection
Microsoft.Office.Sharepoint.Server.Exception_occurred_while_processing_an_InfoPath_form_template_request
Microsoft.Office.Sharepoint.Server.Failed_to_connect_to_parent_server_farm
Microsoft.Office.Sharepoint.Server.Failed_to_load_index
Microsoft.Office.Sharepoint.Server.Failed_to_load_protocol_handler
Microsoft.Office.Sharepoint.Server.Failed_to_load_Single_Sign_On_configuration_settings
Microsoft.Office.Sharepoint.Server.Failed_to_load_word_breaker
Microsoft.Office.Sharepoint.Server.Failure_to_commit_to_SQL
Microsoft.Office.Sharepoint.Server.Idle_Time_of_Logical_Disk
Microsoft.Office.Sharepoint.Server.IIS_Start_Command
Microsoft.Office.Sharepoint.Server.IIS_Stop_Command
Microsoft.Office.Sharepoint.Server.Index_is_corrupt
Microsoft.Office.Sharepoint.Server.InfoPath_form_templates_have_conflicting_business_logic_assembly_identities
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_business_logic_attempted_to_store_a_nonserializable_object
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_business_logic_exceeded_the_maximum_limit_of_operations
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_business_logic_exception_occurred_while_loading_a_form_template
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_calculations_exceeded_the_maximum_limit
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_cannot_find_or_load_ifsFileNames.xml
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_event_counter_mismatch
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_failed_to_load_a_form_template
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_found_an_unexpected_session_state_version
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_postback_failure
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_rules_exceeded_the_maximum_limit
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_user_has_exceeded_the_maximum_number_of_actions_per_postback
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_user_has_exceeded_the_maximum_session_state_size
Microsoft.Office.Sharepoint.Server.InfoPath_Forms_Services_was_running_business_logic_when_ASP.NET_request_timed_out
Microsoft.Office.Sharepoint.Server.Instance_of_search_could_not_be_initialized
Microsoft.Office.Sharepoint.Server.Insufficient_disk_space
Microsoft.Office.Sharepoint.Server.Internal_plug_in_error
Microsoft.Office.Sharepoint.Server.Internal_Single_Sign_On_service_error
Microsoft.Office.Sharepoint.Server.Invalid_File_Access_method_configured
Microsoft.Office.Sharepoint.Server.Invalid_SessionID_in_the_request
Microsoft.Office.Sharepoint.Server.IView_runtime_error
Microsoft.Office.Sharepoint.Server.Locale_ID_has_changed
Microsoft.Office.Sharepoint.Server.Master_merge_error
Microsoft.Office.Sharepoint.Server.Maximum_memory_configured_for_Excel_Calculation_Services_has_been_exceeded
Microsoft.Office.Sharepoint.Server.Membership_Import_failed
Microsoft.Office.Sharepoint.Server.Memory_Pages_Per_Second
Microsoft.Office.Sharepoint.Server.Memory_Allocation_Failed
Microsoft.Office.Sharepoint.Server.Microsoft_Single_Sign_On_service_failed_to_start
Microsoft.Office.Sharepoint.Server.Microsoft_Single_Sign_On_service_failed_to_stop
Microsoft.Office.Sharepoint.Server.My_Site_Creation_failure
Microsoft.Office.Sharepoint.Server.Network_Interface_Bytes_Sent
Microsoft.Office.Sharepoint.Server.Network_Interface_Bytes_Received
Microsoft.Office.Sharepoint.Server.Network_Interface_Total_Bytes
Microsoft.Office.Sharepoint.Server.Network_Queue_Length
Microsoft.Office.Sharepoint.Server.Page_Faults_Per_Second
Microsoft.Office.Sharepoint.Server.Paging_File
Microsoft.Office.Sharepoint.Server.Performance_Measuring__ASP.NET_Cache__Hit_ratio
Microsoft.Office.Sharepoint.Server.Performance_Measuring__ASP.NET_Cache___size
Microsoft.Office.Sharepoint.Server.Performance_Measuring__Disk_Based_Cache__Size
Microsoft.Office.Sharepoint.Server.Performance_Measuring__Object_Cache__Cache_flushes
Microsoft.Office.Sharepoint.Server.Performance_Measuring__Object_Cache__Cache_hits_sec
Microsoft.Office.Sharepoint.Server.Performance_Measuring__Object_Cache__Hit_ratio
Microsoft.Office.Sharepoint.Server.Performance_Measuring__Object_Cache___Size
Microsoft.Office.Sharepoint.Server.Plug_in_failed_to_connect_to_SQL_Server
Microsoft.Office.Sharepoint.Server.Process_W3WP_Handle_Count
Microsoft.Office.Sharepoint.Server.Process_W3WP_Private_Bytes
Microsoft.Office.Sharepoint.Server.Process_W3WP_Processor_Time
Microsoft.Office.Sharepoint.Server.Process_W3WP_Working_Set
Microsoft.Office.Sharepoint.Server.Process_Sql_Server_Private_Bytes
Microsoft.Office.Sharepoint.Server.Process_Sql_Server_Processor_Time
Microsoft.Office.Sharepoint.Server.Process_Sql_Server_Working_Set
Microsoft.Office.Sharepoint.Server.Processor_Interrupts_Per_Sec
Microsoft.Office.Sharepoint.Server.Processor_Privileged_Time
Microsoft.Office.Sharepoint.Server.Processor_Queue_Length
Microsoft.Office.Sharepoint.Server.Processor_User_Time
Microsoft.Office.Sharepoint.Server.Profile_Import_Failed
Microsoft.Office.Sharepoint.Server.Propagation_failed_to_communicate_with_a_query_server
Microsoft.Office.Sharepoint.Server.Propagation_of_the_content_index_paused_because_of_a_lagging_query_server
Microsoft.Office.Sharepoint.Server.Publication_of_ranking_information_failed
Microsoft.Office.Sharepoint.Server.Query_server_removed_from_rotation
Microsoft.Office.Sharepoint.Server.Recycle_Application_Pool
Microsoft.Office.Sharepoint.Server.Remote_Procedure_Call_service_failed_to_start
Microsoft.Office.Sharepoint.Server.Remote_Procedure_Call_service_failed_to_stop
Microsoft.Office.Sharepoint.Server.Search_Number_of_queries_towards_an_index
Microsoft.Office.Sharepoint.Server.Search_Query_Rate
Microsoft.Office.Sharepoint.Server.Search_Succeeded_Queries
Microsoft.Office.Sharepoint.Server.Search_Total_Number_of_Documents
Microsoft.Office.Sharepoint.Server.Shared_Services_Provider_provisioning_failed
Microsoft.Office.Sharepoint.Server.Shared_Services_Provider_synchronization_failed
Microsoft.Office.Sharepoint.Server.Single_Sign_On_audit_failure
Microsoft.Office.Sharepoint.Server.Single_Sign_On_failure
Microsoft.Office.Sharepoint.Server.Site_Directory_scan_job_failed
Microsoft.Office.Sharepoint.Server.Site_Synch_failed
Microsoft.Office.Sharepoint.Server.Spelling_checker_failed_to_load
Microsoft.Office.Sharepoint.Server.SQL_Server_Database_Error
Microsoft.Office.Sharepoint.Server.SSL_is_required_but_is_not_configured
Microsoft.Office.Sharepoint.Server.Sweep_Synch_failed
Microsoft.Office.Sharepoint.Server.Synch_Job_Scheduler_failed
Microsoft.Office.Sharepoint.Server.The_connection_to_the_destination_server_timed_out_while_transporting_the_deployment_package_created_by_the_content_deployment_job
Microsoft.Office.Sharepoint.Server.The_connection_to_the_destination_server_was_lost_while_transporting_the_deployment_package_created_by_the_content_deployment_job
Microsoft.Office.Sharepoint.Server.The_content_deployment_job_failed_on_the_destination_server_during_the_import_phase
Microsoft.Office.Sharepoint.Server.The_content_deployment_job_failed_on_the_source_server_during_the_export_phase
Microsoft.Office.Sharepoint.Server.The_disk_based_cache_exceeded_the_specified_limit
Microsoft.Office.Sharepoint.Server.The_Document_Conversions_Launcher_Service_failed_to_start
Microsoft.Office.Sharepoint.Server.The_Document_Conversions_Load_Balancer_Service_failed_to_start
Microsoft.Office.Sharepoint.Server.The_last_query_server_was_removed_from_rotation
Microsoft.Office.Sharepoint.Server.The_launcher_cannot_register_with_the_load_balancer
Microsoft.Office.Sharepoint.Server.The_launcher_lacks_permissions_to_write_to_disk
Microsoft.Office.Sharepoint.Server.The_location_specified_for_the_disk_based_cache_is_no_longer_accessible
Microsoft.Office.Sharepoint.Server.The_Microsoft_Single_Sign_on_Service_State
Microsoft.Office.Sharepoint.Server.The_object_cache_exceeded_its_maximum_assigned_size
Microsoft.Office.Sharepoint.Server.The_Office_Document_Conversions_Launcher_Service_state
Microsoft.Office.Sharepoint.Server.The_Office_Document_Conversions_Load_Balancer_Service_State
Microsoft.Office.Sharepoint.Server.The_Office_SharePoint_Server_Search_State
Microsoft.Office.Sharepoint.Server.The_Page_Editing_toolbar_detected_missing_or_corrupted_configuration_files_in_the_Master_Page_Gallery
Microsoft.Office.Sharepoint.Server.Unable_to_delegate_credentials
-
Re: What are the things that Solarwinds cannot do?
rharland2012Apr 20, 2015 7:53 AM (in response to orioncrack)
There's this thing called an attachment....
I get it, though....this post would lack some of the gravity without the mile o' text.
-
Re: What are the things that Solarwinds cannot do?
orioncrack Apr 20, 2015 7:57 AM (in response to rharland2012)The effect would have been much less dramatic indeed. The irony is it could have been twice as long so I picked out the essentials.
-
Re: What are the things that Solarwinds cannot do?
rharland2012Apr 20, 2015 9:44 AM (in response to orioncrack)
I applaud your restraint!
-
Re: What are the things that Solarwinds cannot do?
designerfxOct 21, 2016 9:35 AM (in response to orioncrack)
If you're monitoring all of that in SCOM then you aren't monitoring that in SCOM. Plenty of those are things that in most environments aren't even a concern. Seeing this many things pasted from scom makes me wonder if you've read the mp guides properly, because this is easily too much.
-
Re: What are the things that Solarwinds cannot do?
orioncrack Oct 21, 2016 12:48 PM (in response to designerfx)The simple fact that SolarWinds does not autodiscover and maintain my fixed disk inventory for me makes it a totally substandard product for server monitoring compared to scom. But again, as I have mentioned before most of the people that trash scom don't understand these concepts and don't understand the automation that scom provides out of the box which would take an extraordinary amount of time to replicate in SAM. All good though. I just got SolarWinds another $60,000 order from another client of mine. SolarWinds does many things well. But the lack of key automated components is truly a shame. I monitor 10 companies with SolarWinds and 15 with scom. I see on a daily basis how much better of a job scom does for servers. Last week a Solar client had a huge outage because a volume label changed in a disk and Solar doesn't manage that change. To me and my Solar client - this fact is unconscionable for a monitoring solution. But 99.999999999999% of the people that buy Solar have no clue about this kind of horrible deficiency and the others. And no one here really has any argument of why the lack of automated discovery is a positive thing. It drives me nuts how and great and how **** poor Solar is at the same time. Scom has its own troubles. But for servers, it's a no brainer that scom does a better job all around. The Cisco VPN template that I deployed yesterday from ater blew my mind. Solar does things well indeed. But I just can't accept it's terrible faults for servers. People that truly use scom know what I'm talking about.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 1, 2016 9:54 AM (in response to orioncrack)
1 of 2 people found this helpfulI just clicked on your name orioncrack and got some very interesting insights about your last posts...
Quotes (just a few of them below):
"SCOM does it brilliantly. I can export Excel sheets of all of my..."
"The simple fact that SolarWinds does not autodiscover and maintain my fixed disk inventory for me makes it a totally substandard product for server monitoring compared to scom ..."
"You could reverse engineer SCOM's built-in event log rules and create your own event log template with SAM. Here are the SQL error events that SCOM alerts on automatically out of the box: ..."
"Easily done with SCOM. I can generate spreadsheets "
"Well.....I manage 12 different SCOM environments for several companies with..."
Besides, there is not a single helpful comment out there and all you are doing just bumping up little problems and issue here and there.
I would recommend to ban you from this forum. I have no issues with SCOM at all - it is just another tool and some may prefer it over to SolarWinds - good for them. I respect Microsoft same as I respect SolarWinds, but your choice of strategy is just downright wrong!
-
Re: What are the things that Solarwinds cannot do?
orioncrack Nov 1, 2016 1:02 PM (in response to alexslv)Alex,
Why mad bro?
My choice of strategy? Please elaborate? Are you talking about strategy for server monitoring or strategy for getting rid of all of this unused Halloween candy?
I love SolarWinds. I just love SCOM 100x more for servers for the reasons you list above with my quotes. They are all 100% truth. We can agree to disagree. I'm not going to go Trump on you and demand the Ban Hanmer.
-
-
-
-
-
-
Re: What are the things that Solarwinds cannot do?
johnny ringo Apr 20, 2015 11:35 AM (in response to orioncrack)Just curious, what is the tool name?
-
Re: What are the things that Solarwinds cannot do?
goodzhere Apr 22, 2015 1:56 PM (in response to johnny ringo)I am sure he is talking about SCOM. Seems like I have seen comments like this before. And he actually is right to some degree, but I also know that it is a Microsoft product, it has been around since like around 2000, it is expensive, but it still has it's limitations. Especially, since all servers are not Microsoft and all databases aren't SQL. SAM on the other hand, does have the capability and can do ALL of this, even if it isn't right out of the box. SAM has only been around since around 2008 and has been increasing in capability. AppInsight is relatively new. It is getting there. As more people give input as what is needed, the product will continue to grow. I would guess that new features are based on request, time lines, and the amount of customer need.
-
Re: What are the things that Solarwinds cannot do?
designerfxOct 23, 2016 6:05 AM (in response to goodzhere)
I've worked with SCOM and every so often I see him post something about how SCOM is better. I have to say as someone who has done full on SCOM and full on Solarwinds admin that you need multiple teams of people who are full on MS techs to handle SCOM successfully and even then SCOM is laughable when it comes to network hardware and non-windows OS handling.
Also, nothing he's listing in SCOM is out of the box. Everything in SCOM has to be configured and you have to look through the management pack guides to understand - which requires both a highly experienced person with SCOM *and* the people experienced with the MS product you're monitoring with SCOM.
Can you use SCOM for MS products? Yes. Can you use SCOM correctly for MS products? No. I say this with 100% confidence as someone who received SCOM admin training and can spin up SCOM instances without any issues. Ask MS themselves and they will start suggesting other tools like one they hilariously also call application insights: Kevin Greene IT Blog: Application Insights Deep Dive Part 1 - Getting Started . Also, good luck even with 'premiere' MS support - I find I get better support out of engineers sometimes and other times it's nothing. Thwack actually has use.
-
Re: What are the things that Solarwinds cannot do?
bobmarley Oct 21, 2016 11:58 AM (in response to designerfx)1 of 1 people found this helpful
-
-
-
-
Re: What are the things that Solarwinds cannot do?
alexslvApr 21, 2015 5:17 AM (in response to orioncrack)
1 of 1 people found this helpfulwhat is this "copy-paste" stuff from? scom? why would you do that? are you working for marketing department at Microsoft?
If I will copy-paste everything SolarWinds can - you would not have enough RAM to load on your desktop... At a quick glance - all this CAN be monitored using custom apps and templates.
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 22, 2015 3:16 PM (in response to orioncrack)
a lot of these look like individual components that I would find within the composed APM Template ... or in which case where the windows or proper server template did not cover a few said resources or processes in monitoring - I would customize the template
Then with the updated / Addendum template I would figure out why I had to adjust it, note what was changed for what reason/service and after a week of watching for any issues I would re post the adjusted template with explanation to thwack! for anyone else trying to work through my experience.
then some of these appear to be conditions that would have me looking for a new server (or at least SharePoint Admin)
Microsoft.Office.Sharepoint.Server.The_launcher_lacks_permissions_to_write_to_disk ??? Can you say check box ???
-
Re: What are the things that Solarwinds cannot do?
bobmarley Oct 21, 2016 10:02 AM (in response to orioncrack)How many routers and switches can you monitor with 'said product?'
-
Re: What are the things that Solarwinds cannot do?
ecklerwr1Nov 2, 2016 10:14 AM (in response to orioncrack)
Did you know you can load some monitoring scripts from other monitoring products into SAM?
-
-
Re: What are the things that Solarwinds cannot do?
rscreed92 Apr 20, 2015 3:09 PM (in response to peradojr)It is still weak on the wireless. It has potential, but is weak.
I also would love to see better "un-manage" functionality, like allowing multiple outages to be scheduled at the first of the week for 1 device. It also would be great to have an alert suppression allowing us to monitor the exact outage and not the 6 hour window provided by ISP without any information.
-
Re: What are the things that Solarwinds cannot do?
planglois Apr 21, 2015 1:30 PM (in response to peradojr)Just have a look at the feature request here on thwack to see what's missing to the users eye
-
Re: What are the things that Solarwinds cannot do?
superfly99Apr 21, 2015 8:19 PM (in response to peradojr)
It doesn't make coffee.
But as far as networking monitoring goes, it does everything I need it to do plus it's super easy to use.
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 22, 2015 4:08 PM (in response to superfly99)
If your Coffee Maker is snmp write capable - IT COULD!
RFC 2324
-
Re: What are the things that Solarwinds cannot do?
RichardLettsApr 22, 2015 7:36 PM (in response to cahunt)
if you have NCM it only needs to accept SSH connections and you could invoke a script against it.
if it has a SOAP/REST interface then an empty-pot trap could invoke the make-another-pot service (http post is in the alert manager)
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Oct 21, 2016 11:17 PM (in response to RichardLetts)Yes Ncm can accept to only SSH to run script, but if the situation can occur where SSH connection has been blocked (By acl or by any reason) then how we can run script, then solarwinds should vote for this to NCM accept the snmp to run script,
Because I tried but did not get option over there to run script by SNMP in NCM
(If I am doing wrong please advise too)
-
Re: What are the things that Solarwinds cannot do?
rschroederNov 1, 2016 4:29 PM (in response to krishna mishra)
If ACLs deny access from NPM, then you need to explain to your Security team why your NPM addresses must exempted from those ACL's.
Changes made via snmp RW privileges can be challenging to troubleshoot and track, compared to using SSH.
You might consider only giving your Orion products Read-Only access through snmp, and then use TACACS and AD to give an Orion service account RW access via SSH-V2, and relaxing the ACL's accordingly.
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 2, 2016 5:57 AM (in response to rschroeder)yes we are using the R/w snmp string, but the point is whenever acl blocked to login by ssh account then we should run script to break the acl, but NCM have not feature to run the script snmp (have only option like ssh), and if i am using engineer tool then we can do it.
-
Re: What are the things that Solarwinds cannot do?
rschroederNov 2, 2016 9:36 AM (in response to krishna mishra)
I feel your solution of scripting a method of breaking the ACL isn't a best practice. My team's preferred method is to correctly write the ACL to allow Orion to do its job, and to not give Orion RW permission via snmp at all.
-
-
-
-
-
Re: What are the things that Solarwinds cannot do?
superfly99Apr 23, 2015 12:23 AM (in response to cahunt)
Hmmm I'm not convinced of RFC2324. It's dated 1st April 1998
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 23, 2015 9:14 AM (in response to superfly99)
IT's an April Fools Day RFC...there is a followup regarding Tea brewing a few years after on April 1st - i forget the actual rfc on that one.
-
Re: What are the things that Solarwinds cannot do?
planglois Apr 23, 2015 10:46 AM (in response to cahunt)Here you go: https://tools.ietf.org/html/rfc7168
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 23, 2015 11:35 AM (in response to planglois)
I knew it was in the 7000 range, just was lazy and didn't feel typing that into google. Nice!
who adds Milk to Tea? sheesh..
addition-type = ( "*"
| milk-type
| syrup-type
| sweetener-type
| spice-type
| alcohol-type
| sugar-type
) *( ";" parameter )
sugar-type = ( "Sugar" | "Xylitol" | "Stevia" )
-
Re: What are the things that Solarwinds cannot do?
superfly99Apr 27, 2015 12:05 AM (in response to cahunt)
The better question is "who drinks tea??"
-
Re: What are the things that Solarwinds cannot do?
rharland2012Apr 27, 2015 8:04 AM (in response to superfly99)
Grownups.
-
Re: What are the things that Solarwinds cannot do?
maria.bungau Apr 29, 2015 9:39 AM (in response to rharland2012)Who are these...Grownups?
-
Re: What are the things that Solarwinds cannot do?
wlmorris Apr 29, 2015 9:52 AM (in response to maria.bungau)They are like us but worried, often irritated, and rarely laugh. Nothing to strive for.
-
Re: What are the things that Solarwinds cannot do?
rharland2012Apr 29, 2015 10:01 AM (in response to maria.bungau)
Characterized by their fondness for tea, frowning, and constantly hassling all of the fun people, grownups are a rapidly-growing minority that really can *** everyone else out.
-
-
-
Re: What are the things that Solarwinds cannot do?
cahuntApr 27, 2015 9:40 AM (in response to superfly99)
I call it an Arnold Palmer... it's not all Tea.
-
-
-
-
-
-
-
-
Re: What are the things that Solarwinds cannot do?
joepoutre Nov 6, 2015 9:05 AM (in response to peradojr)Reporting is neither intuitive nor easy. We have requirements to generate performance analysis across groups of devices, identify the "noisiest" interfaces, and a variety of other reports. Some of these are ad hoc, others are meant to be emailed every day, so we can't build a whole new page.
In building reports we should have the ability to dynamically point-and-click to choose what devices and components are included in reports, rather than having to choose them one at at time using wildcarded filters.
It is building ad hoc reports correlating multiple devices that aren't grouped yet have interdependencies where this would help.
It would also help to have reports where one can adjust the time parameters, such as creating a report of errors and discards on a set of devices, then being able to adjust what time frame is covered in a dynamic way.
Thank you,
Joe Poutre
BNP Paribas
(If this is all possible as the app is currently built, someone should point me to the right training and documentation.)
-
Re: What are the things that Solarwinds cannot do?
Andre Thompson Oct 19, 2016 11:24 AM (in response to peradojr)Hi
I use Solarwinds primarily for Network Monitoring.
What I notice for newer Cisco switches with the updated Cisco OID, Solarwinds cannot recognize it.
Also there is very little discovery support for IPv6. You have to manually add the IPv6 addresses of all the switches you want to manage.
It does not use CDP or LLDP.
- Andre
-
Re: What are the things that Solarwinds cannot do?
d09hOct 20, 2016 11:20 AM (in response to peradojr)
Show (out of the box) where polling is failing. Suppose SNMP credentials change on one or more devices. Not knowing they've changed, you don't update SolarWinds. When you later seek our interface info/ CPU info/ whatever, you find blank graphs. I know there are some homebrew SQL and SWQL queries and reports shared among users of the forum, but I'm referring to a central/ integrated into the product way of knowing that right now there are 13 devices on your network that you can only get ICMP up/down status due to SNMP connectivity failing. Your interfaces and CPU could be maxed, but you would be blissfully unaware. Alerts may not be getting triggered. You find out the hard way.
-
Re: What are the things that Solarwinds cannot do?
rschroederOct 20, 2016 12:05 PM (in response to d09h)
It's easy to show where polling is failing by creating a couple of standard jobs to run nightly. One is the config backup task, the other is the inventory task.
If administrative access is denied or fails due to credentials changing, you'll get a report that shows which devices failed to backup.
If SNMP strings change, then the inventory management task will fail and you'll receive an e-mail listing which devices failed to be inventoried. Those are the ones with changed snmp strings, likely.
Not too bad a challenge to overcome.
-
Re: What are the things that Solarwinds cannot do?
d09hOct 21, 2016 7:38 AM (in response to rschroeder)
I agree it can be done. In the way mentioned, it seems to require NCM (users probably don't put servers in NCM though, if they bought it for configuration management functionality and not to help detect broken SNMP connectivity, or for that matter if they didn't buy licenses with this use case in mind). But a user who only needs NPM (or can only afford NPM)...what's he supposed to do? It would be great if there was a banner across every screen--click here for nodes that you aren't getting statistics from. Baked into the product from day one. (OK, I would probably get mad that it was taking up space, but I would be thankful when I found the ones not being monitored successfully.)
-
Re: What are the things that Solarwinds cannot do?
designerfxOct 21, 2016 1:27 PM (in response to d09h)
Uh, if you only care that SNMP works - require polling via SNMP (which is an option). Suddenly, SNMP fails and node is down. Problem solved?
-
Re: What are the things that Solarwinds cannot do?
d09hNov 1, 2016 12:00 PM (in response to designerfx)
Not at all. End users would (correctly) tell me the tool was broken since they could log in to the devices. I would get called in to work to fix the broken tool. And the issue would creep with more devices becoming stale. Issue exacerbated any time a router deployed doing routing correctly but SNMP incorrectly.
-
Re: What are the things that Solarwinds cannot do?
designerfxNov 1, 2016 12:39 PM (in response to d09h)
1 of 1 people found this helpfulWell, there are other ways that exist within NPM to solve that particular problem - if you look at hardware health on your routers it's going to show undefined/unknown when SNMP fails even if you can still ping em. That's out of the box, assuming you're using brands that they support hardware health on. So alert on unknown hardware health, and you know what suddenly had SNMP fail. It depends on what you're doing with the tools and what the users are doing.
-
Re: What are the things that Solarwinds cannot do?
rschroederNov 2, 2016 9:41 AM (in response to designerfx)
I use this exact method of discovering where things have fallen through the cracks. Often I find that team members may add devices to the network, and add them to NPM, but not add them in with snmp settings, and not add them into NCM.
My front page of NPM shows all Undefined devices NPM is aware of, and that's an easy list to review for correct SW configuration/deployment.
Even better, it's an indicator of recently-added devices that have a high probability of not been added to our custom NCM daily, weekly, or monthly jobs.
-
Re: What are the things that Solarwinds cannot do?
d09hDec 6, 2016 7:58 AM (in response to rschroeder)
So perhaps for noobs and anyone else unaware...NPM product should indicate at least on a Node Details page, and ideally in a very 'in your face' way elsewhere (banners), no stats available on these devices...click here for more. In enterprise environments with multiple shifts and other teams allowed to add devices (and other teams who change devices but don't circle back to SolarWinds functionality afterward), the administrator wouldn't have to deduce/ investigate as much. He probably still should review custom property assignments. I know one thing constantly cropping up for me was IOS changes on Cisco devices, or deployment of a replacement for a device taken off the network. From that point on, SNMP might be failing. I believe certain devices (McAfee email gateways) always showed me unknown hardware status...perhaps due to system MIB not responding. So the unknown status for devices across the enterprise would always show some unknowns, and wouldn't look different other than perhaps the number of them increasing. Still a stretch compared to blatantly showing admins that their reports/ alerts/ ability to show SNMP data was broken for the following few dozen devices.
-
Re: What are the things that Solarwinds cannot do?
rschroederJan 31, 2017 3:38 PM (in response to d09h)
2 of 2 people found this helpfulLeverage the existing Hardware Health Overview view by adding it to the top of your Orion Summary Home page. It's a great way to see a graphic of those devices whose snmp is misconfigured or has failed--they'll be Gray/Undefined.
This does not require NCM, by the way . . . Happiness!
From the above view, you can click on any part of the pie that isn't green and get a list of devices in Warning, Critical, or Undefined state. Or you can just click on Undefined and go straight to the list of devices that have failed snmp and begin troubleshooting and testing and correcting them.
For this, you don't need NCM. But you should have it. It's saved the day for me several times, enabling me to quickly identify which configuration lines have changed, what they were before the change, what they are after the change, and that lets me revert the problem lines quickly.
If you have no budget for NCM, to back to Management and make a persuasive case for how correct Network Management is an income-provider instead of a liability. I created a paper describing how to accomplish that, if you're interested in pursuing the valiant cause of proving NCM (or any other product) is actually an asset instead of a liability:
A Stratagem For Obtaining Funding For Your Projects
Once you have NCM, run a nightly Inventory of all devices via NCM; any that fail are either totally unavailable, or have misconfigured snmp settings in them or in NPM/NCM. That Job generates an e-mailed report every day, and the failed devices are right at the top, easy to find.
If having a reliable network is important to Management, one that's up 99.999% of the time (or better), NCM is an important ingredient for that tasty recipe!
-
Re: What are the things that Solarwinds cannot do?
designerfxJan 31, 2017 11:06 PM (in response to rschroeder)
I can vouch for that rschroeder is right on, NCM is a pretty crucial tool for network management if you have routers and switches. How much of it you use is to be determined, but it's very useful.
-
-
Re: What are the things that Solarwinds cannot do?
robertcbrowningFeb 1, 2017 11:07 AM (in response to d09h)
I run a daily report of volumes that are unresponsive.
If there's one or two it might be that volume labels were changed & Orion not updated.
But a great byproduct of this is if ALL the volumes of a server are unresponsive it either means that the SNMP service has died or, even worse, the server has hung and no services are running properly.
It's amazing how often an early morning restart can fix a hung Win2k box There's not many left and they keep saying that they'll be swapped out soon, but in the meantime - - --
Re: What are the things that Solarwinds cannot do?
d09hFeb 1, 2017 12:30 PM (in response to robertcbrowning)
That's a pretty good workaround for lack of something built-in.
Duct tape could keep me attached to my seat in a car crash, but it's not the most elegant solution (believe Mythbusters did this...).
This should not be construed as a criticism of the workaround, but rather a criticism of the need. If hardware health or unresponsive volumes are among the best ways (or if SQL/ SWQL queries are best), fine...so be it. Have a native resource available from day one that shows this. Prominently. If nothing else, put it in Manage Nodes...under a category 'Polling for metrics but no metrics available' (or whatever wording makes sense...'check SNMP/ WMI' perhaps?).
This is a recommendation to SolarWinds the company and not to the admins who use workarounds.
-
Re: What are the things that Solarwinds cannot do?
rschroederFeb 1, 2017 10:23 PM (in response to d09h)
Do you ever use Quality Of Experience to show services that are slow or that have failed? It's free with NPM, and you could set it to alert you anytime any servers or service's speeds exceed your thresholds.
Not bad, for a built-in solution that isn't just a work-around for exactly what you want.
-
Re: What are the things that Solarwinds cannot do?
d09hFeb 7, 2017 7:40 AM (in response to rschroeder)
Haven't, but will look into it. Thanks.
-
-
-
-
-
-
-
-
-
-
-
-
Re: What are the things that Solarwinds cannot do?
chadsikorra Oct 20, 2016 2:24 PM (in response to peradojr)The single most annoying missing feature to me is more flexibility around scheduled maintenance windows and alerting. Right now I have resorted to a custom Powershell script that uses the SolarWinds API, custom properties, and a rigid WSUS group naming scheme to make sure things don't get alerted when they have monthly maintenance. The solution is less than ideal. The concept of maintenance windows and suppressing alerts during them should be a baked in feature by now.
The only other disadvantage I've noticed is not having much flexibility in how a node is determined to be up/down. Compared to many other monitoring solutions that allow you to define a script, or just about any method you want, to determine if a host is up/down SolarWinds could use some improvements here. Currently it
's SNMP, agent port, or ping.
-
Re: What are the things that Solarwinds cannot do?
rschroederFeb 1, 2017 7:57 AM (in response to chadsikorra)
It seems you might be missing some other options--ping, snmp, and agent port aren't the only ways to get alerts when something's down. Have you tried using Quality Of Experience metrics and alerting on them when they go exceed a threshold? QoE is included with NPM, and if you're using WMI to monitor servers, you can see and alert on a lot of variables.
I monitor a number of Windows and SQL and Citrix servers; it's easy to see which ones have issues, which apps are out of spec. Just alert on those that exceed your preferred thresholds and you've got a fine "to do" list:
-
-
Re: What are the things that Solarwinds cannot do?
d09hOct 21, 2016 8:47 AM (in response to peradojr)
SolarWinds is relatively lacking when it comes to llamas. WinAmp set the standard: Winamp whips llama - YouTube
-
Re: What are the things that Solarwinds cannot do?
nickzourdosOct 21, 2016 1:25 PM (in response to peradojr)
SAM doesn't return the expiration date for more than one certificate unless you use AppInsight for IIS. This is a problem because not all certificates are used in IIS... some are installed in other applications on the server. It would be nice to be able to see all certificates in the store and their expiration dates.
-
Re: What are the things that Solarwinds cannot do?
Andre Thompson Nov 1, 2016 8:38 AM (in response to peradojr)Another item that Solarwinds cannot do easily is items from a page cannot be exported to CSV format.
For example if you need to export the list of Managed nodes to CSV for management reporting you cannot do that.
You can only export to pdf.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 1, 2016 9:30 AM (in response to Andre Thompson)
2 of 2 people found this helpfulYou can ... easily! You just need to create report for it with any columns you wish and then export the result of the report output into Excel/CSV. You can start with default "Inventory Report" to get your initial base line and fine-tune it to your liking
-
Re: What are the things that Solarwinds cannot do?
designerfxNov 1, 2016 2:22 PM (in response to Andre Thompson)
2 of 2 people found this helpfulExport to PDF is the only *visible* option if it's a classic report as far as what options you can see andrethompson . If you create a web-based report, it'll show "export to CSV" in the corner. Or, you can even take the classic report from report writer and copy the sql into the web report if you want management to see the "Export as spreadsheet" options.
In both instances you can actually get an excel if you add &dataformat=xls (or csv if I recall correctly) to the end of the URL for a classic report. So example when the URL says Orion/Report.aspx?ReportID=(ID) add &dataformat=xls . Or you can go the alexslv approach as well.
-
Re: What are the things that Solarwinds cannot do?
ecklerwr1Nov 2, 2016 10:16 AM (in response to designerfx)
I do exactly this too designerfx I add the &dataformat=xls oprion so some consumers of data only need click link and get a direct downloaded excel spreadsheet for further manipulation... it works great!
-
-
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 2, 2016 6:00 AM (in response to peradojr)-
Re: What are the things that Solarwinds cannot do?
robertcbrowningNov 2, 2016 7:44 AM (in response to krishna mishra)
If you have your servers grouped, in the Manage Nodes & Group By view you can expand the multiple interfaces & volumes of these nodes and mark a selection of volumes or nodes for deletion at one go.
Or have I misunderstood?
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 2, 2016 8:05 AM (in response to robertcbrowning)but if i am saying volume name - xyx-123, where is mounted in the infra's node, then we should use the sql query to find the same volume, and in second point if i would like remove the same volume from multiple node, then again use the sql query to delete, but it is part of risk.
That's why i am recommending the same volume management feature should be there.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 2, 2016 8:20 AM (in response to krishna mishra)
I would agree. Although this is kind of "Nodes" management page, not Volumes, but if Interfaces are listed, why not Volumes then. +1 from me
-
-
-
-
Re: What are the things that Solarwinds cannot do?
ecklerwr1Nov 2, 2016 10:36 AM (in response to peradojr)
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 3, 2016 3:12 AM (in response to peradojr)Alert Acknowledged report is not working based on trigger alert, which is very important report it helps we can come on result how many alert are being acknowledged or not, so based on we can do alert optimization and take an step for alert automation.
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 4, 2016 7:26 AM (in response to krishna mishra)Any one can help to make the important report, which is should be based on Event (trigger alert) and who and when acknowledge the alert.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 4, 2016 1:04 PM (in response to krishna mishra)
1 of 1 people found this helpfulPlease post a separate thread as a question and explain in details what you need. Please also pay particular attention into WHY you are doing this - request from boss, some other particular need, etc. Pretty much anything can be done in multiple different ways - knowing what you are trying to solve will help. Besides... new thread is definitely way to go for this. Feel free to mention me - I will pick this up next week
-
-
-
Re: What are the things that Solarwinds cannot do?
bsciencefiction.tvNov 3, 2016 8:03 AM (in response to peradojr)
Conditionals in alerts (If...Then...Else statements for Alert Manager )
Flexibility with Scheduled Task Monitoring
Automatically identify neighbors and automatically create dependencies. This is one I bring up at every UX. When we used to have Spectrum and added a node, it automatically located neighbors up and down stream to create dependencies. Ie, If I added a router at a location, it automatically saw the switch and server and then created dependencies accordingly.
Report creation is cumbersome and sometimes very trial and error.
Granular Node Management Rights. This is another one that I really do not understand. A lot like Windows versus Unix, the fact that Solarwinds does not allow you to grant or deny specific rights amazes me. Basically either you can do everything or nothing.
Other than that, excellent product with responsive support.
-
Re: What are the things that Solarwinds cannot do?
d09hFeb 1, 2017 12:37 PM (in response to bsciencefiction.tv)
Granular node management would be potentially helpful when gone for the night/ for the weekend. Someone who wouldn't normally have node management permissions could be allowed to add node/ unmanage/ delete note / some of these/ all of these.
-
-
Re: What are the things that Solarwinds cannot do?
krishna mishra Nov 4, 2016 7:24 AM (in response to peradojr)Yes i am agree, Solarwinds can do everything but need patient and knowledge to implement the same, but some time reporting feature in not fruitful, If Solarwinds start focus too on reporting then i can also bed no one can stand against the solarwinds
please keep it up and try to resolve all reporting issue.
-
Re: What are the things that Solarwinds cannot do?
lynchnigel Nov 7, 2016 5:19 AM (in response to peradojr)We use Orion for most things NPM,NCM, SRM,DPA,SAM,NTA,IVIM,UD,QOE
But I was wondering (and to try convert our DB's) what it is like for deep monitoring of databases? Does it allow you to dig deep into it - a question for the DB's out there using Orion and which product.
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 7, 2016 5:39 AM (in response to lynchnigel)
2 of 2 people found this helpfulAs far as I know SolarWinds has two ways of monitoring DBs - one is with SQL AppInsight (which requires 50 licenses of SAM per instance) and another one is more deeper and dedicated products DPA (interestingly you have also mentioned it as well)
I guess if you give your DBAs below links to play with - they will get an idea themselves if it is worthwhile their time and your investment
SQL AppInsight:
http://oriondemo.solarwinds.com/Orion/APM/Summary.aspx?viewid=202
DPA:
-
Re: What are the things that Solarwinds cannot do?
lynchnigel Nov 10, 2016 1:13 AM (in response to alexslv)Thanks very much, I will send them the links, I'm sure they have had a look before but its worth them having another look as Orion changes over time and just gets better
We do have SAM and looking through Orion, we haven't actually got DPA licenced - we had the trial and obviously still thinks it is still there for some reason?
-
Re: What are the things that Solarwinds cannot do?
alexslvNov 10, 2016 4:11 AM (in response to lynchnigel)
Check The Lab - you may want to pin this for 16th of November in your calendar :
-
-
-