Openstack Monitoring FAQs

Openstack Monitoring FAQs

How OpenStack is monitored in APM?

In Applications Manager, RESI API is used as mode of monitoring for OpenStack. Below APIs are used to monitor OpenStack and its resources:

Are there any prerequisites needed for monitoring OpenStack in Applications Manager?

  1. If user credential used while adding OpenStack monitor is an administrative user,, then by default 'policy defaults' will allow access to all the APIs.
  2. If the user is not an administrator, then access to the above mentioned APIs should be given in the respective service's policy file for the user.

How can I give access to APIs via policy file?

  1. Each OpenStack service defines the access policies for its resources in an associated policy file. To know more about policies, refer here.
  2. There are two types of policy configuration files: policy.json & policy.yaml.
  3. Each service has its own policy file and API permission for a user should be specified in the file (Sample can be seen below).
  4. However, in the latest release after Queens, there will be no more configurations by default.
    1. You have to manually create the file.
    2. By default, administrative users will have all the permissions.

How can I configure policy file for each service?

As mentioned above, each service has its own policy configuration file. To know more about configuring policy for users to give access to APIs, refer below:
  1. To give access to Authentication API, refer the policy configuration of Keystone service.
  2. To give access to Cinder API, refer the policy configuration of Cinder service.
  3. To give access to Glance API, refer the policy configuration of Glance service.
  4. To give access to Hypervisor (Nova) API, refer the policy configuration of Nova service.
  5. To give access to Neutron API, refer the policy configuration of Neutron service.
  6. To give access to Nova API, refer the policy configuration of Nova service.

What are the details needed to monitor OpenStack?

The following values are needed to monitor OpenStack in Applications Manager:
  • Base Authentication URL
  • Tenant Name
  • Username and Password
  • Project-scoped Token (If applicable)

                  New to ADSelfService Plus?

                    • Related Articles

                    • FAQs related to Windows Service monitoring

                      After installing APM Insight Windows service monitoring agent , if you don't see data in the Applications Manager console, or if you are unable to add monitors, follow the steps given below to troubleshoot. If few monitors are not getting added Check ...
                    • Monitoring HAProxy - Configuring the HAProxy Stats page

                      To monitor a HAProxy instance: Open the 'stats' port for collecting the metrics. To enable metrics collection, add the following content at the bottom of the file /etc/haproxy/haproxy.cfg: listen stats :9000 mode http stats enable stats hide-version ...
                    • Siebel CRM Monitoring FAQs

                      Prerequisites : To Monitor Siebel server, follow the step given below: Copy the "APMSiebelCommands.txt" file from the directory "AppManager_Home/working/resource/" and paste it under "Siebel Installation directory/siebsrvr/" directory and try to add ...
                    • End User Monitoring (EUM) - Frequently asked questions

                      How to access EUM Agent Settings page? Unable to Login End User Monitoring Agent? EUM Agent not mapped to Applications Manager. What should I do? How to Change Applications Manager hostname and port in EUM Agent for login? How to change AppManager ...
                    • User Privilege for DamengDB Monitoring

                      To effectively monitor DamengDB in Applications Manager, the Monitor user must be granted the Data Viewer privilege. To grant this privilege to the newly created user, please follow the steps given below: Connect to your DamengDB instance using a ...