About Wssecure application monitor
Practices, see Monitoring and diagnostic best practices for Azure Service Fabric.For a tutorial that shows how to view Service Fabric events and health reports, query the EventStore APIs, and monitor performance counters, see Tutorial: Monitor a Service Fabric cluster in Azure.To learn how to configure Azure Monitor logs to monitor your Windows containers orchestrated on Service Fabric, see Tutorial: Monitor Windows containers on Service Fabric using Azure Monitor logs.Service Fabric ExplorerService Fabric Explorer, a desktop application for Windows, macOS, and Linux, is an open-source tool for inspecting and managing Azure Service Fabric clusters. To enable automation, every action that can be taken through Service Fabric Explorer can also be done through PowerShell or a REST API.Application monitoringApplication monitoring tracks how features and components of your application are being used. You want to monitor your applications to make sure issues that impact users are caught. The responsibility of application monitoring is on the users developing an application and its services since it is unique to the business logic of your application. Monitoring your applications can be useful in the following scenarios:How much traffic is my application experiencing? - Do you need to scale your services to meet user demands or address a potential bottleneck in your application?Are my service-to-service calls successful and tracked?What actions are taken by the users of my application? - Collecting telemetry can guide future feature development and better diagnostics for application errorsIs my application throwing unhandled exceptions?What is happening within the services running inside my containers?The great thing about application monitoring is that developers can use whatever tools and framework they'd like since it lives within the context of your application! You can learn more about the Azure solution for application monitoring with Azure Monitor Application Insights in Event analysis with Application Insights.We also have a tutorial
Key features of the Wssecure application monitor that are enabled through these drivers include:
- Use SAM application monitor templates and application monitors
- NTP Monitor - Application Monitor Templates - Server Application
- Postfix - Application Monitor Templates - Server Application Monitor
- Application Pool monitoring - Forum - Server Application Monitor
- GIS - Application Monitor Templates - Server Application Monitor
- Solaris - Application Monitor Templates - Server Application Monitor
- Application Monitor License - Forum - Server Application Monitor
SAM includes predefined component monitors, comprised of code and scripts, that you can use to assess the status and performance of applications, services, processes, and event on nodes throughout your environment. SAM application monitor templates are collections of component monitors that you can assign to nodes as "application monitors" that are also called "applications." A single component monitor can be used on its own and applied to a node in an application monitor, or it can be used in multiple templates. For example, the HTTPS Monitor is included in the following templates: AppInsight for IIS HTTPS Monitor SolarWinds Platform server - Main Polling Engine For a quick overview, watch Common SAM template elements (6:34). Note the following details about SAM component monitors: Some component monitors have specific port requirements, as detailed in the SAM Application Monitor Template Reference. WinRM is the default transport method used to fetch data for WMI-based component monitors. Some component monitors can use SolarWinds Platform agents to collect data. Some component monitors do not support polling via SolarWinds Platform Remote Collectors (ORCs). To display the component monitors included in a template: Navigate to Settings > All Settings > SAM Settings >Manage Templates. On the Manage Application Templates page, click the Application Monitor Templates tab. Select an existing template and click Edit. The following example shows some of the component monitors in the AppInsight for Active Directory template: Component monitor types Component monitors that share similar characteristics are categorized by a component monitor type. The following example shows three different types included in the Active Directory 2016 Services and Counters template: Performance Counter Monitor, Windows Service Monitor, and Window Event Log Monitor To learn more about individual component monitor types, see the SAM Application Monitor Template Reference. For database values assigned to component monitor types that you can use to configure alerts, see Component monitor properties for alerts. Component monitor fetching methods For many component monitors, you can configure the preferred fetching method used to gather data from target nodes. SAM automatically switches to a fallback method to collect data if the first method fails, and then
