This plugin provides a way for the PSM customers to use PSM plugins written in Ruby in AppOptics (including their own custom plugins). If PSM customers migrate to AppOptics, they will no longer have access to the PSM UI or PSM’s remote configuration. In this case, customers can still use PSM’s Ruby plugins, but they need to place those files on their servers themselves manually or via configuration management of choice (Ansible, Salt, etc).
This plugin is currently available for x86_64 Linux platforms.
psm plugin is included with the SolarWinds Snap Agent by default. It’s an adapter for Ruby plugins written originally for PSM/Scout.
If you are a Scout client willing to migrate to AppOptics, please use the dedicated tool: https://github.com/pingdomserver/scout-ao
This plugin requires that Ruby is available and Scout is installed but inactive on the target host.
Normally you won't need to change anything here, the migration script does all the necessary setup.
If you wish to change the collector plugin settings, edit its configuration file
## Most probably you won't need to change those fields and may safely rely on the defaults
## For detailed configuration documentation please refer to https://server-monitor.readme.io/docs/agent
ruby_pathis optional and defaults to the First
agent_ruby_binis optional and defaults to
/usr/share/scout/ruby/scout-client. It is an installation path of scout-client.
plugin_directoryis optional and defaults to
/opt/SolarWinds/Snap/bin/psm. It is a path to where the PSM plugins .rb files were downloaded (along with the corresponding .yaml files holding particular configs).
agent_data_fileis optional and defaults to
For more detailed configuration documentation please refer to scoutd docs
If you wish to change the collector task settings, edit its configuration file
interval: "0 * * * * *"
# Don't change
# Currently filtering is not supported for psm collector
## Suggested tags:
# roles: db
# environment: production
# hostname: localhost
- plugin_name: publisher-appoptics
To make changes happen, restart the agent:
$ sudo service swisnapd restart
Unless you already did so, enable the PSM plugin in the AppOptics UI:
On the Integrations Page you will see the PSM plugin available. If you do not see the plugin, see Troubleshooting Linux.
Metrics will appear as
As each customer has his/her own tailored set fo plugins, there’s no predefined default dashboard for this integration.
Each metric is annotated with the following tags:
|hostname||Name of the host on which scout was running (used for host identification by the PSM API).|
|environment||Annotation used in PSM for configuring different notifications for eg. production and staging servers. See the environments page in the PSM/Scout docs for more|
|roles||Annotation used in PSM that let configuring servers in bulk. Servers could belong to many roles. See the roles page in the PSM/Scout docs for more|
|local_filename||Name of the .rb file that reported metric|
|origin||Origin of the plugin (eg. ‘local')|
|plugin_id||Identificator of the original PSM/Scout plugin.|
When the APM Integrated Experience is enabled, AppOptics shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate AppOptics and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.