Monitoring Accounts
- 30 Jul 2025
- 2 Minutes to read
- Print
- PDF
Monitoring Accounts
- Updated on 30 Jul 2025
- 2 Minutes to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Monitoring Accounts are the user accounts who have administrative rights to access the Windows Server. You can configure Monitoring Accounts for users for a specific Department.
Configure Monitoring Account
To configure Monitoring Account, perform the following steps:
Select Admin > Advanced > Discovery & Monitoring > Monitoring Account.
Figure: Monitoring Account
On the Monitoring Account page, click Add New on the right-side panel.
Select the Department and type in the new Monitoring Account details. For more information about the field on the Monitoring Account Details page, see Field Description below.
Figure: Monitoring Accounts Details Page
Field Description
The following table describes the fields on the Monitoring Account page:
Fields | Description |
Details | |
Used For | Select the protocol used for monitoring. Note: Under the Used For drop-down field, select LDAP drop-down list and configure the Domain, User Name, Password, Re-enter Password, IPAddress, LDAP Path, and Active fields. After the LDAP configurations are set, the configured LDAP path is available for selection on the DISCOVERY page under the LDAP Path field while configuring the Discovery using Type as Active Directory. |
Domain | Type in the domain name to which the user belongs. |
User Name | Type in the user name of the User to whom you want to provide the administrative rights to access the Windows server machines. |
Password | Type in the password. |
Re-enter Password | Re-enter the password. |
AWS Account Name | Specify the unique name for the AWS Account. After the configuration, you can view this to filter the Dashboards on the AWS CloudWatch Dashboard page. Note: This field displays only when you select the Used For field value as AWS from the drop-down list. |
Access Key | Specify the access key that is used to authenticate the AWS CloudWatch Dashboard. Note: This field displays only when you select the Used For field value as AWS from the drop-down list. |
Secret Key | Specify the Secret Key that is used to authenticate the AWS CloudWatch Dashboard. Note: This field displays only when you select the Used For field value as AWS from the drop-down list. |
Re-enter Secret key | Re-enter the secret key. Note: This field displays only when you select the Used For field value as AWS from the drop-down list. |
Description | Type in a brief description about the user or the purpose of adding Monitoring Account or any warning message. For example, you can create a user to access data from a group of critical servers, you can add a message like “Do not delete this user name”. |
Is Sudo | This check box should be selected only for the Sudo accounts. If selected for an account, which is not Sudo, the discovery results may not be as expected. For more information, refer to How to Enable Sudo Access. |
Active | Indicates the status set for the Monitoring Account.
|
Click Submit. A new Monitoring Account is configured.
Actions
This section explains all the icons displayed on the right-side panel of the Monitoring Account page.
Filters
Click the Filters icon to select a value for the Used For list. Click Submit.
Figure: FILTERS pop-up page
Show List
Click Show List to display the LIST table showing all the Monitoring Accounts configured in the SUMMIT application for the selected Department.
Figure: Monitoring Account List Page
To edit a Monitoring Account configuration, click User Name. Make appropriate changes and click SUBMIT.
Note
When the Monitoring Accounts are displayed under the LIST table, the Add New action is displayed on the right-side panel. Click Add New to configure a new Monitoring Account.
Change History
Click the Change History icon to view the change history details of the Monitoring Account.
Figure: Change History
Was this article helpful?