Salesforce System Overview Test

Salesforce is a multi-tenant system, where resources are shared across organizations. To ensure that no organization monopolizes these resources, Salesforce enforces strict limits on the usage of the resources. Here are some of the key resources on which Salesforce imposes usage restrictions:

• Custom objects: These are objects that are created by users in a Salesforce organization and those installed from packages.

• API: These are API calls made to the organization.

• Rules: Workflow lets you automate standard internal procedures and processes to save time across a Salesforce organization. A workflow rule is the main container for a set of workflow instructions. These instructions can always be summed up in an if/then statement.

• Apex triggers: Apex is a strongly typed, object-oriented programming language that allows developers to execute flow and transaction control statements on the Salesforce Platform server, in conjunction with calls to the API. Apex triggers enable you to perform custom actions before or after changes to Salesforce records, such as insertions, updates, or deletions.

• Apex classes: An Apex class is a template or blueprint from which Apex objects are created. Classes consist of other classes, user-defined methods, variables, exception types, and static initialization code.

• Code: This is the total number of characters in your Apex triggers and Apex classes (excluding comments, test methods, and @isTest annotated classes).

The Salesforce System Overview test monitors how the target Salesforce organization uses the aforesaid resources, and alerts administrators if the limits are about to be reached. This way, administrators can determine if an organization is attempting to utilize more resources than it is permitted to. In the process, administrators can also figure out whether they need to regulate usage so that it falls within the limits, or to expand the limits based on the usage.

Target of the test : A Salesforce organization

Agent deploying the test : A remote agent.

Outputs of the test : One set of results for the Salesforce organization being monitored

Configurable parameters for the test

Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Email	This test needs to login to the target Salesforce organization as a user with Administrative rights, in order to run API commands on it and pull metrics. To facilitate this connection, specify the email ID of the Administrator of the Salesforce organization here.
Password	Specify the password of the Administrator here.
Confirm Password	Confirm the administrator password by retyping here.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Custom objects	Indicates the number of custom objects currently used.	Number
Total custom objects	Indicates the maximum number of custom objects that can be created	Number	By comparing the value of this measure with that of the Custom objects measure, administrators can figure out how many more objects can be created before the limit is reached.
Custom object usage	Indicates the percentage usage of custom objects.	Percent	The value of this measure is computed using the formula: (Custom objects / Total custom objects)*100 If the value of this measure grows close to 100%, it implies that the limit is about to be reached.
Custom settings	Indicates the number of custom settings in use.	Number
API request	Indicates the number of API calls made to the target organization.	Number
Total API request	Indicates the maximum number of API calls that can be made to the organization.	Number
API usage	Indicates what percentage of the API calls limit is currently in use.	Percent	The value of this measure is computed using the formula: (API request/ Total API request)*100 If the value of this measure grows close to 100%, it implies that the limit is about to be reached. When an organization exceeds this limit, all users in the organization will be temporarily blocked from making additional calls. Calls are blocked until usage for the preceding 24 hours drops below the limit. To know which user made the maximum number of API requests to the organization and when, use the detailed diagnosis of this measure.
Rules	Indicates the number of workflow rules in use.	Number
Total rules	Indicates the maximum number of workflow rules that can be configured in the organization.	Number
Rules usage	Indicates what fraction of the rules limit is currently in use.	Percent	The value of this measure is computed using the formula: (Rules/ Total rules)*100 If the value of this measure grows close to 100%, it implies that the limit is about to be reached. To make sure that necessary workflow rules can be created without any interruption, administrators need to remove those rules that are seldom used, thus making room for new, useful ones.
Apex triggers	Indicates the number of apex triggers currently in use.	Number
Apex classes	Indicates the number if apex classes currently in use.	Number
Code used	Indicates the number of characters used in code.	Number
Total code used	Indicates the maximum number of characters that can be used in code.	Number
Code used	Indicates what percentage of the prescribed character limit is currently used in code.	Percent	The value of this measure is computed using the formula: (Code used/ Total code used)*100 If the value of this measure grows close to 100%, it implies that the limit is about to be reached.