The video at the bottom of the Resolution field will cover How to create SQL Performance Investigator agents for monitoring and focus on adding the Performance Investigator extension after the agent connection details has been setup.
Applicable for both Simple and Advance types of discovery methods.
This video is applicable for Foglight 5.6.11, 5.7.1, and 5.7.5.
This video at the bottom of the Resolution field will cover How to create SQL Performance Investigator agents for monitoring and focus on adding the Performance Investigator extension after the agent connection details has been setup.
Applicable for both Simple and Advance types of discovery methods.
The setup has some minimum requirements for database and os connections. Review the prerequisites and requirements as a setup reference; also consult the foglight documentation guides mentioned below
Please review the Foglight for SQL Server Permissions Guide, Hardware Sizing Guide and Users Guide for additional requirements.
1. To add Agents, log into the Foglight web console with your foglight user. Click on Databases to access the databases dashboard.
2. Click on Monitor and select SQL Server, the Monitor SQL Server Instance setup GUI should display in a simple mode format requesting the needed setup configurations for creating a single instance. A similar screen exists in the Advance mode at the set credentials step within the Edit Credentials dialogue box to add the SQL PI extension, using the discover multiple SQL Server instances link located under Monitor SQL Server Instance to create multiple SQL Performance Investigator agents in a setting.
3. Under SQL Server Connection, The Agent Manger Host field specifies the agent manager selected to use to discover the instance. The host shown in blue is usually defaulted based on the least amount of instances already deployed against. Also helps with load balancing and sizing that effects performance. Click the host to change Agent Manager Host if desired, another optioned screen shows the current agent managers and the number of agents deployed against it. You have a choice of selecting a new agent manager or continuing on with the default host. Remember the host should meet the system requirements and supported number of deployed agents.
4. The information Little i is helpful explaining the login configurations use of each section
5. Next Section, The Connection Details is where to specify the name of the SQL Server Instance to monitor. To monitor a default instance, only input the host name in the server field. For named instance, use the host name\instance format. In a clustered environment, insert the virtual host name of the SQL Server host
6. SQL Server Default port is 1433. If no port is specified, the wizard will use the port provided by the SQL Browser service, in which case this service must be started.
7. Next there are two methods for login connections, one is to specify login credentials section by either configuring manually using windows or SQL Server authentication both available in the dropdown. The same connecting methods when accessing the SQL Server Management studio. So if the provided user can connect via the SQL Server Management Studio it should be able to establish login through this wizard.
If Windows Authentication is selected to login into the instance, in one configuration this authentication will allow to connect to the instance as well as login to the OS to gather OS metrics if enable. Enter the user name in the domain\username format level
If SQL Server authentication is selected configure database connectivity using a database user and password. The OS credentials for configuring OS metrics are suggested separately under the Monitoring Extension/Operating System section. Click on the red Missing Credentials and complete the OS login setup in accordance to the information provided, consult the little i. There is also an option to select stored credentials from a lockbox if it exists, ideal for domain users accessing.
8. The second one is Log in to SQL Server using Windows Authentication and the Windows account that is running Foglight (SYSTEM), means if a local Foglight agent manager installed on the SQL Server host, it will adopt those credentials
9. Choose the desired authentication
10. Note the current sensitivity level for this instance is usually Normal. This alarm level is adjustable by clicking on the level (Normal). There is a sensitivity control definition for each level of choice, Essential, Normal, Tuning, and Performance
11. Accept or defined a new Alarm Sensitivity level
12. Under the monitoring extension section is where to add Extension features such as SQLPI
13. Click on Click for Licensing Information link before adding the Performance Investigator extension to become familiar with the SQLPI features and how to obtain the add-on-license if it hasn’t been done.
14. To add the SQLPI extension Check the box next to SQL PI and another container pops up showing a pick list of Agent managers reporting into the FMS that are possible candidates for Performance Investigator Repository hosts. Included are the agent managers names and the corresponding OS’s and If there are preexisting PI repository from another instance creation on that agent manager indicated by a check mark, which is also available to add the agent to that existing repository. Take heed of the noting necessary recommendations and Hardware sizing reference link. Consequently the PI repository can support up to 100 instances with the proper resource sizing.
15. Select a qualified Agent manager and click apply. The process will verify the system requirements, if the agent manager selected fails to meet the requirements another informing box will pop up indicating with some options.
16. Click monitor configuration starts. The setting up txt may indicate PI repository creation if the agent manager host selected did not have an existing PI repository. If the selected Agent manager host did have an existing PI repository, the setup text may not mention the PI repository, instead in the background link the agent to the chosen Agent Manager’s existing SQLPI repository.
Once completed, the initialized successfully monitoring popup is indicated. There is a choice of adding another database in which will take you back to the setup screen or click close.
The new agent is now created and viewable in the database dashboards. There is also an entry in the databases SQLPI dashboard. The monitor status also shows PI is enabled. After a couple of collection intervals the dashboards should become fully populated with associated metrics
This video will cover How to create SQL Performance Investigator agents for monitoring and focus on adding the Performance Investigator extension after the agent connection details has been setup.