Group Policies provide centralized management and configuration of your Pulseway Agent configuration. Group Policies work on computer groups and they overwrite the configuration of all computers in the group.
Group Policies are commonly used in enterprise environments to quickly configure new computers and to ease the configuration update process. Once a Group Policy has been created, all computers will automatically update their configuration based on the policy overrides. Additionally, whenever a group policy gets changed, all computers in the group will receive the updated policy applying the new overrides immediately.
Managing Group Policies
Pulseway groups are created dynamically as a systems join them and they are automatically removed when the last system leaves the group. You can create/configure Pulseway Group Policies from the Pulseway WebApp -> Server Admin -> Policies tab.
Once you click on Create Policy, then you’ll be presented with a new screen in which you will be asked to specify the name for the policy and then configure all required options
Most policy settings have three states:
If a setting is Checked or Unchecked then the setting will be propagated to computers thus overwriting the locally configured value.
Leaving a setting as Undecided will not propagate any changes to the computers and the existing value on each computer will be used.
Note: Group policy changes are not reflected in the Pulseway Manager app. The Pulseway Manager app controls the local agent configuration; at runtime, in the Pulseway service, group policy settings will take override the local configuration.
Event log monitoring
Monitoring event logs for problems is an easy way to identify a problem before turns into something irreversible. In order to configure this you will need to open the Pulseway WebApp -> System -> Group Policies -> Notifications -> Event Log and simply add a new filter
Here is an example of a NIC event monitoring:
How to enable and configure the Syslog forwarding
Syslog is a standard for computer data logging. It separates the software that generates messages from the system that stores them and the software that reports and analyzes them.
You may choose to receive a status report containing one or more of the following:
Disk space usage
Logged in users count
Ping round trip time
Note: Pulseway notifications will be sent even if the Syslog server is inaccessible.
How to configure notification forwarding to PagerDuty
PagerDuty is an alarm aggregation and dispatching service for system administrators and support teams. It collects alerts from your monitoring tools, gives you an overall view of all of your monitoring alarms, and alerts an on duty engineer if there's a problem.
In order to be able to forward notifications to PagerDuty you must have a service key.
Steps on creating a PagerDuty service:
1. Log into your PagerDuty dashboard.
2. Click on Services tab.
3. From the right hand side of the screen click the “Add Service” button.
4. Enter a service name that is easy for you to recognize (I.e. Pulseway).
5 .Select an Escalation Policy that fits your needs.
6. Select “Generic API system” as Service Type.
7. Click on “Add Service” button at the bottom of the screen.
8. Copy the “Service API Key” value into Pulseway Manager.
How to configure notification forwarding to Zendesk
Zendesk is a SaaS suite that offers help desk ticketing, issue tracking, and customer service support.
Email: Email address you use to login to Zendesk console.
Authentication Type: Select Password if you wish to quickly get Zendesk forwarding or go to Zendesk and get your API Token.
From Name: Name of the ticket requester (Usually customer / company name).
From Email: Email of the ticket requester. All ticket updates will be sent to this address.
Notification Filter: You can select which notification priorities will be sent to Zendesk (Critical, Elevated, Normal or Low).
Getting a ZenDesk API Token:
Login to Zendesk console (usually companyname.zendesk.com).
Go to Settings (click the gear icon).
Look for Channels section and click on API.
Make sure that Token Access is enabled and copy your API Token then paste it into Pulseway Manager.
Assigning Group Policy to the group
In order to assign the group policy to the group of systems you will need open the Pulseway WebApp -> Server Admin -> Configuration -> expand the required Organization/Site/Group -> Overview -> Edit and assign the correct policy to the group. In this section there is the option to Choose Which antivirus application to use (Kaspersky or Webroot) and which Kaspersky policy to apply on this group to the group of systems and System patching policy. These policies will be applied on monitored systems automatically as soon as system is added into the group. Antivirus application will be installed automatically and if the system is offline, then Antivirus installation will be queued for that system and Antivirus will be installed as soon as that system comes online.
Note: The same policy can be assigned to multiple groups of systems. Also, you have the option to assign the same policy at the Organization or Site level, so it can be inherited by Sites or Groups of systems (you need to verify that the group policy will be inherited).
Removing Group Policy
If you would like to remove a Group Policy, then please open the Pulseway WebApp -> Server Admin -> Configuration -> expand the required Organization/Site/Group -> Overview -> Edit -> select the option [No Policy] and and save the changes.
Note: if one policy is removed, then other policies (Antivirus and Patch Management) will remain applied on that group of systems.