Diagnostic Manager 5.0.1 - User Guide

NOTE: Metalogix Diagnostic Manager only sends an e-mail when an alert changes status, not when an alert remains in the same state.

Sender Address

The e-mail address that appears as the sender of the e-mail.

Reply-to Address

The e-mail address that appears as the reply-to address. All replies to the message are sent to the address you specify. You must specify a reply-to address to receive replies to the email.

Message Footer

Text that you want to appear in the footer of the e-mails  Metalogix Diagnostic Manager sends.  Metalogix Diagnostic Manager includes the text that you specify in every alert email that it sends.

SMTP Server Address

The name or Internet Protocol (IP) address of your SMTP mail server.

SMTP Server Port

The IP port that the SMTP mail server uses. (The default SMTP port is port 25.)

If you want Metalogix Diagnostic Manager to use SSL encryption to connect to the mail server, check Use an SSL encrypted connection.

SMTP Server required authentication

If your SMTP server requires authentication:

·check this box

AND

·specify a valid user name and password that Metalogix Diagnostic Manager can use to access the mail server.

NOTE: Metalogix Diagnostic Manager prompts you for the email address to which you want to send the test message.

NOTE: Metalogix Diagnostic Manager only generates SNMP traps in response to  Metalogix Diagnostic Manager alerts and does not act as an SNMP agent.

NOTE: The administrator of your SNMP management tool should be able to provide this information

SNMP Server Address

The IP Address or the name of the SNMP server to which generated traps should be sent.

Port

The Port on which the SNMP management software listens.

Community

The name of any SNMP community to use for the provider

NOTE: This feature is not available for SharePoint 2007 or Office 365 tenants.

Enable gathering of ULS data from SharePoint databases

When this box is checked, Metalogix Diagnostic Manager will be permitted to gather ULS data from SharePoint once the ULS Synchronization Schedule has been enabled and set.

Gather ULS log entries from SharePoint Database

How often the Collection Service should gather ULS log entries from SharePoint.

ULS log retention

The number of days Metalogix Diagnostic Manager should retain ULS log entries in the Repository database.

ULS Synchronization Schedule

Enables the SharePoint Timer Job Diagnostic Data Provider: Trace Log and overrides the schedule set in Central Administration for all monitored farms and servers.

Caution: If the Diagnostic Data Provider: Trace Log timer job has never been enabled in SharePoint or has not been run recently, the synchronization of what may be a significant amount of accumulated log data across multiple servers and/or farms is required.  Therefore, the time it takes to complete the initial synchronization may range from several minutes to several hours.  Subsequent synchronizations are performed incrementally, and therefore can be completed in much less time.

Minimum Log Level

The minimum level of severity for which Metalogix Diagnostic Manager will gather ULS log entries.  (That is, Metalogix Diagnostic Manager will gather only log entries that are of the severity you specified and higher.)

Click the icon to display the options from which to select.

See "Minimum Log Entry Level Values," following for descriptions and rankings of log entry severity levels.

High

General functional detail for the high priority events that happen in the environment. Examples include global configuration modifications, service start and stop, timer jobs completed, and so on.

Critical

Events that demand the immediate attention of the system administrator. They are generally directed at the global (system-wide) level, such as System or Application. They can also be used to indicate that an application or system has failed or stopped responding.

Error

Events that indicate problems, but in a category that does not require immediate attention.

Medium/Warning

Events that provide forewarning of potential problems.  Although not a response to an actual error, a warning indicates that a component or application is not in an ideal state and that some further actions could result in a critical error.

Unexpected

A logic check failed that is not typical, or the message returns an unexpected error code.  These generally represent code bugs that should be investigated and fixed.

Monitorable

Traces that indicate a problem, but do not need immediate investigation. The intent is to collect data and analyze it over time, looking for problem trends.

Information

Events that pass noncritical information to the administrator, similar to a note that says: "For your information."

Verbose

Verbose status, such as progress or success messages.

VerboseEx

Useful for traces that are likely to be high volume, especially information that is not needed for all debugging scenarios. Examples of situations where you should use the VerboseEx setting are method entry and exit events, tracing in loops, or to relay information that is not useful to developers outside your team.

NOTE: The disabling of ULS data gathering by Metalogix Diagnostic Manager does not disable—nor does it change the current schedule of—the Diagnostic Data Provider: Trace Log timer job in SharePoint.  If you want to disable the timer job itself, you can do so via SharePoint Central Administration.