Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

Monitoring the tenant


While the tenant Overview page in the Tenant Management Console gives you a view of the tenant as a whole, the tenant log lets you monitor tenant and namespace activity on a more detailed level. The log records tenant and namespace events such as:

Tenant Management Console logins

Namespace creations

Tenant and namespace configuration changes

Creations, modifications, and deletions of retention classes

Privileged delete operations

Warnings about used storage approaching the hard quota

Each recorded entry about an event is called a message. The tenant log contains all the messages written to it since the tenant was created.

The Tenant Management Console provides several views of the log, as outlined in the table below.

View

Shows

More information

Tenant-level all events

All log messages recorded for the tenant and its namespaces

Viewing the complete tenant event log

Tenant-level major events

A subset of the log messages in the tenant-level all-events view

Major tenant events

Tenant-level security events

Only log messages about attempts to log into the Tenant Management Console with an invalid username

Viewing the tenant security log

Tenant-level compliance events

All log messages about events that require the compliance role across all the tenant's namespaces

Viewing the tenant compliance log

Namespace-level all events

All log messages for a given namespace

Viewing the complete namespace event log

Namespace-level major events

A subset of the log messages in the namespace-level all-events view

Major namespace events

Namespace-level compliance events

All log messages about events that require the compliance role for a given namespace

Viewing the namespace compliance log

In addition to these views of the log, HCP gives you the option of sending log messages to syslog servers, SNMP managers, and/or specified email addresses. For more information on this, see:

Enabling syslog logging

Enabling SNMP logging

Configuring email notification

For information on the messages that can appear in the tenant log and how to respond to them, see Tenant log messages.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Tenant log messages


The tenant log contains messages about events that happen at the tenant and namespace levels. The table in this appendix lists the messages HCP can write to the tenant log. The messages are listed in order by event ID.

For each message, the table shows:

The message ID

The short form of the message, which identifies the event to which the message applies

An explanation of the message

The action, if any, you should take in response to the message

The message severity

For more information on the system log, see Monitoring the tenant.

ID

Event

Explanation

Action

Severity

2005

HCP found an unavailable object

HCP could not repair an object because the object was unavailable.

Contact your HCP system administrator.

Warning

2006

HCP found an irreparable object

HCP found a broken object it could not repair.

Contact your HCP system administrator.

Error

2028

HCP found an irreparable object

HCP was unable to repair the object. The repair may be retried at a later time.

Contact your HCP system administrator.

Error

2044

HCP found an unavailable object

HCP could not repair an object because the object was unavailable.

Contact your HCP system administrator.

Warning

2046

HCP found an irreparable object

HCP found a broken object it could not repair.

Contact your HCP system administrator.

Error

2070

Object has been shredded

An object was shredded.

No action is required.

Notice

2087

Disposition service stopped: run complete

The disposition service finished successfully.

No action is required.

Notice

2088

Disposition service stopped without finishing

The disposition service stopped without completing its run. The service will resume at some point in the future.

No action is required.

Warning

2089

Disposition service stopped: run complete

The disposition service finished successfully.

No action is required.

Notice

2090

Disposition service stopped without finishing

The disposition service stopped without completing its run. The service will resume at some point in the future.

No action is required.

Warning

2092

Disposition service stopped without finishing

The disposition service stopped without completing its run. The service will resume at some point in the future.

No action is required.

Notice

2093

Disposition service stopped without finishing

The disposition service stopped without completing its run. The service will resume at some point in the future.

No action is required.

Notice

2154

Additional namespaces included in tenant replication

The indicated namespaces were selected to be included in replication of the tenant.

No action is required.

Notice

2155

One or more namespaces removed from tenant replication

The indicated namespaces were removed from replication of the tenant.

No action is required.

Notice

2156

Replication automatically paused for this tenant

Replication of the tenant was automatically paused for the indicated reason.

If the cause is one or more namespace name collisions, rename each indicated namespace. If the cause is that the replica does not support the DPL of one or more namespaces, lower the DPL of each indicated namespace. Alternatively, in either case, you can deselect the namespace from being replicated. After you make the necessary changes, notify your HCP system administrator that the problem has been resolved.

Error

2157

Namespace replication collision detected

A namespace replication collision was detected, possibly requiring intervention from the tenant administrator.

If the cause is one or more namespace name collisions, rename each indicated namespace. If the cause is that the replica does not support the DPL of one or more namespaces, lower the DPL of each indicated namespace. Alternatively, in either case, you can deselect the namespace from being replicated. After you make the necessary changes, notify your HCP system administrator that the problem has been resolved.

Notice

2160

User account replicated with collisions

Either or both of two user accounts with the same user ID on a 4.x system were modified on that system, resulting in conflicting values for one or more properties. On replication to this system, the values for those properties were taken from the account with roles.

Ensure that the user account is configured correctly.

Warning

2343 Successfully added Service Principal Name to Active Directory HCP successfully added a Service Principal Name to Active Directory. No action is required. Notice
2345 Failed to add Service Principal Name to Active Directory HCP failed to add a Service Principal Name to Active Directory. Verify that the Service Principal Name was added to Active Directory. Warning
2347 An exception occurred while adding Service Principal Name to Active Directory HCP failed to add a Service Principal Name to Active Directory. Verify that the Service Principal Name was added to Active Directory. Warning

2351

Group account created

A user created a group account.

No action is required.

Notice

2353

Group account updated

A user updated a group account.

No action is required.

Notice

2355

Group account deleted

A user deleted a group account.

No action is required.

Notice

2396 Successfully removed Service Principal Name from the Active Directory Successfully removed Service Principal Name from the Active Directory. No action is required. Notice
2398 Failed to remove Service Principal Name from the Active Directory Failed to remove Service Principal Name from the Active Directory. Verify that Active Directory Service Principal Name is cleaned up. Warning

2613

HCP search facility index recovery started for namespace

A user reset HCP search facility indexing for a namespace.

If indexing was disabled for the namespace, reenable it to start rebuilding the HCP search facility index. (This also reenables metadata query engine indexing.)

Warning

2900

Privileged delete requested

A user requested a privileged delete operation.

No action is required.

Notice

2901

Privileged delete succeeded

A privileged delete operation succeeded.

No action is required.

Notice

2902

Privileged delete failed

A privileged delete operation failed.

No action is required.

Notice

2903

Retention class created

A user created a retention class.

No action is required.

Notice

2904

Retention class updated

A user updated a retention class.

No action is required.

Notice

2905

Retention class deleted

A user deleted a retention class.

No action is required.

Notice

2906

Retention mode set

The namespace retention mode has been changed.

No action is required.

Notice

2907

Privileged purge requested

A user requested a privileged purge operation.

No action is required.

Notice

2908

Privileged purge succeeded

A privileged purge operation succeeded.

No action is required.

Notice

2909

Privileged purge failed

A privileged purge operation failed.

No action is required.

Notice

2911 Retention class missing HCP system detected a missing retention class. Contact your HCP system administrator. Error

3004

Namespace created

A user created a namespace.

No action is required.

Notice

3005

Namespace updated

A user updated a namespace.

No action is required.

Notice

3006

Namespace deleted

A user deleted a namespace.

No action is required.

Notice

3011

User account created

A user created a user account.

No action is required.

Notice

3012

User account updated

A user updated a user account.

No action is required.

Notice

3013

User account deleted

A user deleted a user account.

No action is required.

Notice

3014

User account is disabled

A user tried to log in with a disabled user account.

Reenable the user account to allow the user to log in.

Warning

3015

User account disabled

A user account has been disabled.

No action is required.

Notice

3016

User account enabled

A user account has been enabled.

No action is required.

Notice

3017

User account password changed

A user changed the password for a user account.

No action is required.

Notice

3018

User account failed login

A user tried to log in with a username and password that are not valid for any user account.

Have the user log in with a username and password that are valid for a user account.

Warning

3019

Failed login to the Search Console

A user tried to log into the Search Console with a username and password that are not valid for any user account.

Have the user log into the Search Console with a username and password for that are valid for a user account.

Warning

3020

Namespace over hard quota

The amount of storage used by the namespace exceeds the configured hard quota.

Delete some objects from the namespace or increase the hard quota.

Warning

3021

Namespace under hard quota

The amount of storage used by the namespace is under the configured hard quota

No action is required.

Warning

3022

Namespace over soft quota

The amount of storage used by the namespace exceeds the configured soft quota.

Consider deleting some objects from the namespace or increasing the hard quota for the namespace.

Warning

3023

Namespace under soft quota

The amount of storage used by the namespace is under the configured soft quota.

No action is required.

Warning

3024

Tenant over soft quota

The amount of storage used by all namespaces owned by the tenant exceeds the soft quota configured for the tenant.

Consider deleting some objects from the namespaces or requesting an increase in the hard quota for the tenant.

Warning

3025

Tenant under soft quota

The amount of storage used by all namespaces owned by the tenant is under the soft quota configured for the tenant.

No action is required.

Warning

3028

Failed user account login attempt

An attempt to log into a tenant failed because the user account could not be authenticated.

No action is required.

Warning

3032

Tenant at namespace quota

The number of namespaces is equal to the maximum allowed for this tenant.

No action is required.

Warning

3033

Tenant over namespace quota

The number of namespaces is greater than the maximum allowed for this tenant.

Either delete one or more namespaces or have your HCP system administrator increase the namespace quota.

Warning

3037

Username conflict

Multiple user accounts have the same username. All user accounts must have a unique username.

Rename one account or merge duplicate accounts together.

Warning

3508

HCP found an irreparable object

HCP found a broken object it could not repair.

Contact your HCP system administrator.

Error

3998

Search enabled or disabled

A user enabled or disabled search.

No action is required.

Notice

3999

Search indexing enabled or disabled

A user enabled or disabled search indexing.

No action is required.

Notice

4000

HCP search facility indexing failure

The HCP search facility encountered an object it could not index.

Contact your HCP system administrator.

Error

4002

User account created

A user created a user account.

No action is required.

Notice

4003

User account updated

A user updated a user account.

No action is required.

Notice

4004

User account deleted

A user deleted a user account.

No action is required.

Notice

4005

User authenticated

A user login to the Tenant Management Console was successfully authenticated.

No action is required.

Notice

4006

Authentication attempt by unknown user

A user tried to log in with an unknown username.

Have the user log in with a valid username and password.

Warning

4007

Account reenabled by timer

A disabled security user account has been automatically reenabled.

No action is required.

Notice

4008

Account is disabled

A user tried to log in with a disabled account.

Reenable the user account to allow the user to log in.

Warning

4009

Account has been inactive for too long

A user tried to log in with an account that was disabled due to inactivity.

Reenable the user account to allow the user to log in.

Warning

4010

Account does not include the required roles

A user tried to log in with an account that does not include a required role.

Update the account to include the required role to allow the user to log in.

Warning

4011

Password is invalid

A user tried to log in with an invalid password.

Have the user log in with a valid username and password.

Warning

4012

Remote authentication server error

The login for a remotely authenticated user failed due to an error communicating with a RADIUS server.

Contact your HCP system administrator.

Warning

4013

Password changed

A user changed the password for a user account.

No action is required.

Notice

4014

Account enabled

A user account has been enabled.

No action is required.

Notice

4015

Account disabled

A user account has been disabled.

No action is required.

Notice

4016

Account disabled due to too many failed logins

A user account has been automatically disabled due to too many failed login attempts.

Reenable the user account and have the user log in with a valid username and password.

Warning

4017

Account will be reenabled

A security user account will be reenabled automatically after a waiting period.

No action is required.

Notice

4018

User authenticated

A user login to the Search Console was successfully authenticated.

No action is required.

Notice

4019

Configuration changed

A user changed a configuration value of an HCP component.

No action is required.

Notice

4020

Configuration changed

A user changed a configuration value of an HCP component.

No action is required.

Notice

4021

Irreparable object acknowledged

A user acknowledged an irreparable object.

No action is required.

Warning

4022

All irreparable objects acknowledged

A user acknowledged all irreparable objects.

No action is required.

Warning

4023

Unauthorized action

A user has requested an operation that is not authorized for the user account.

If the user should be allowed to perform this operation, add the required role to the user account.

Warning

4024

User account created

A user created a user account.

No action is required.

Notice

4025

User account updated

A user updated a user account.

No action is required.

Notice

4026

User account deleted

A user deleted a user account.

No action is required.

Notice

4027

User account is disabled

A user tried to log in with a disabled user account.

Reenable the user account to allow the user to log in.

Warning

4028

User account disabled due to too many failed logins

A user account has been automatically disabled due to too many failed login attempts.

Reenable the user account to allow the account user to log in.

Warning

4029

User account disabled

A user account has been disabled.

No action is required.

Notice

4030

User account password changed

A user changed the password for a user account.

No action is required.

Notice

4031

User accounts merged

A user merged multiple user accounts with the same username into a single account.

No action is required.

Notice

4100

Object replicated with collisions

An object being replicated conflicts with an existing object on the target system. The object has been stored in the .lost+found directory on the target system.

No action is required.

Warning

4101

Object did not replicate

An object was not replicated.

Contact your HCP system administrator.

Error

4102

Object did not replicate; will retry later

An object was not replicated. Replication of the object will be retried later.

Monitor the replica to see whether this object is eventually replicated. If the object does not replicate within one week, contact your HCP system administrator.

Warning

4114

Metadata query engine indexing failure

The metadata query engine encountered an object it could not index.

If this situation persists, contact your HCP system administrator.

Warning

4115

Metadata query engine checkpoint reset

A user reset the metadata query engine checkpoint for the indicated namespace.

No action is required.

Warning

4122

Failure adding namespace to the search index.

The HCP search facility could not create the index for a namespace because the system limit was reached.

No action is required. If this situation persists, contact your authorized service provider.

Warning

4123

Namespace was successfully added to index

Namespace was added to the index

No action is required.

Notice

4124

Content class created

A user created a content class.

No action is required.

Notice

4125

Content class updated

A user updated a content class.

No action is required.

Notice

4126

Content class deleted

A user deleted a content class.

No action is required.

Notice

4127

Namespaces associated with content class

A user associated namespaces with a content class.

No action is required.

Notice

4128

Content classes associated with namespace

A user associated content classes with a namespace.

No action is required.

Notice

4220

Namespace tags updated

A user updated the tags for a namespace.

No action is required.

Notice

4225

Namespace default settings updated

A user updated the namespace default settings.

No action is required.

Notice

 

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Viewing the complete tenant event log


The All Events panel on the Tenant Events page lists all messages recorded for the tenant and its namespaces. By default, the panel displays ten messages at a time in reverse chronological order.

RoleWebHelp.png

Roles: To view the tenant All Events panel, you need the monitor, administrator, security, or compliance role. However, only users with the compliance role can see messages about events that require the compliance role. Only users with the security role can see messages about attempts to log into the Tenant Management Console with an invalid username.

To display the All Events panel:

1.In the top-level menu of the Tenant Management Console, select Monitoring Tenant Events.

2.On the left side of the Tenant Events page, click on All Events.

For a description of the information provided by each log message, see Understanding log messages. For information on managing the message display, see Managing the message list.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Viewing the tenant security log


The Security Events panel on the Tenant Events page lists all messages about attempts to log into the Tenant Management Console with an invalid username. By default, the panel displays ten messages at a time in reverse chronological order.

RoleWebHelp.png

Roles: To view the tenant Security Events panel, you need the security role.

To display the Security Events panel:

1.In the top-level menu of the Tenant Management Console, select Monitoring Tenant Events.

2.On the left side of the Tenant Events page, click on Security Events.

For a description of the information provided by each log message, see Understanding log messages. For information on managing the message display, see Managing the message list.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Viewing the tenant compliance log


The Compliance Events panel on the Tenant Events page lists all messages about events that require the compliance role across all the tenant's namespaces. This includes all retention class activity and privileged delete operations. By default, the panel displays ten messages at a time in reverse chronological order.

RoleWebHelp.png

Roles: To view the tenant Compliance Events panel, you need the compliance role.

To display the Compliance Events panel:

1.In the top-level menu of the Tenant Management Console, select Monitoring Tenant Events.

2.On the left side of the Tenant Events page, click on Compliance Events.

For a description of the information provided by each log message, see Understanding log messages. For information on managing the message display, see Managing the message list.

For information on retention classes, see Working with retention classes. For information on privileged delete, see Using privileged delete.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Understanding log messages


Each message displayed in a view of the tenant log includes this information about an event:

The username of the event initiator:

oFor user-initiated events, this is the username currently associated with the user account used by the user who initiated the event. These considerations apply:

For an HCP user account, if the account has been deleted, the username is followed by the letter D in parentheses.

For an AD user account, if the account has been deleted or if HCP currently cannot contact AD, the username for the message is blank.

oFor system-initiated events, the username is [internal].

oFor events initiated by HCP service or support personnel by means other than the Tenant Management Console, the username is [service].

Additionally, when the tenant is being replicated, messages for events initiated by a user who accessed the Tenant Management Console directly from the HCP System Management Console have a username of [remote admin] in the log messages on systems to which the tenant is replicated.

The severity of the event. Possible values are:

oNotice — The event is normal and requires no special action. Events of this severity are informational only. Examples are:

Namespace created

Privileged delete requested

oWarning — The event is out of the ordinary and may require manual intervention. Examples are:

Namespace over soft quota

User account failed login

oError — The event is serious and most likely requires manual intervention. Examples are:

HCP found an irreparable object

Object did not replicate

The date and time at which the event occurred, shown in the time zone of the HCP system.

A short description of the event.

To view more details about an event, click anywhere in the row containing the event message. To hide the details, click again in the row.

The details displayed for an event are:

The user ID of the event initiator

For user-initiated events, the port through which HCP received the event request

For user initiated events, the IP address from which the event request was sent

The message ID

The full text of the event message

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Managing the message list


You can take the following actions in any of the views of the tenant log:

To display details for all the listed events, click on expand all. To hide all details, click on collapse all.

To view a different number of messages per page, select the number you want in the Items per page field.

To page forward or backward, click on the next ( PageForward.png ) or back ( PageBack.png ) control, respectively.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Viewing the Active Directory log


The Active Directory log lists the unassigned Service Principal Names of the tenant. If there are no SPNs or the system is not set to warn you about missing SPNs, the log states that the system is properly configured. If the tenant is missing an SPN, then it is listed here. This page is only visible if AD is enabled on both the System and Tenant Management Console.

RoleWebHelp.png

Roles: To view the Active Directory log, you need the monitor, administrator, and security roles.

To display the Active Directory Status panel, in the top-level menu of the Tenant Management Console, select Security Active Directory.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Enabling syslog logging


An HCP system can be configured to send system-level log messages to one or more specified syslog servers. You can choose to also send tenant log messages to those servers. The system-level configuration determines whether compliance and security messages are sent along with the other tenant log messages.

You use the Syslog page in the Tenant Management Console to enable or disable sending tenant log messages to the syslog servers. To display this page, in the top-level menu of the Tenant Management Console, select Monitoring Syslog.

RoleWebHelp.png

Roles: To view the Syslog page, you need the monitor or administrator role. To enable or disable syslog logging, you need the administrator role.

To enable or disable the logging of tenant log messages to syslog servers:

1.On the Syslog page, select (to enable) or deselect (to disable) Enable syslog logging.

If the HCP system is not configured for syslog logging, selecting this option has no effect.

2.Click on Update Settings.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Enabling SNMP logging


An HCP system can be configured to send system-level log messages to one or more specified SNMP managers. You can choose to also send tenant log messages to those managers. The system-level configuration determines whether compliance and security messages are sent along with the other tenant log messages.

You use the SNMP page in the Tenant Management Console to enable or disable sending tenant log messages to the SNMP managers. To display this page, in the top-level menu of the Tenant Management Console, select Monitoring SNMP.

RoleWebHelp.png

Roles: To view the SNMP page, you need the monitor or administrator role. To enable or disable SNMP logging, you need the administrator role.

To enable or disable the logging of tenant log messages to SNMP managers:

1.On the SNMP page, select (to enable) or deselect (to disable) Enable SNMP logging.

If the HCP system is not configured for SNMP logging, selecting this option has no effect.

2.Click on Update Settings.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Configuring email notification


HCP can be configured at the system level to support the use of email to notify recipients about messages added to the system-level log. If the HCP system supports email notification, you can configure HCP to send email about tenant log messages to recipients that you specify.

You can configure each email recipient to receive notification of only selected messages based on the message importance, severity, and type. Important messages are those that appear in the Tenant Management Console. Message severity levels are notice, warning, and error. Message types are general, security, and compliance. In all cases, HCP makes a best effort to send the applicable email in a timely manner.

Recipients are added to the blind carbon copy (bcc) list for each email, so the recipients of an email are not visible to one another. The To list remains empty.

You can configure the content of the email that HCP sends. For example, you could choose to have HCP send the full text, severity, and date and time, and node number for each log message. Or, if you’re concerned about exposing system tenant and namespace information in what is by nature an insecure medium, you could format the email to say only that a log message was recorded.

HCP writes messages to the tenant log about email that the email server fails to accept. The messages about failed email are not sent to email recipients.

You use the Email page in the Tenant Management Console to enable and configure email notification. To display this page, in the top-level menu of the Tenant Management Console, select Monitoring Email.

RoleWebHelp.png

Roles: To view the Email page, you need the monitor or administrator role. To configure email notification, you need the administrator role.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Enabling email notification


To have HCP send email about log messages, on the Email page:

1.Optionally, test whether email notification is supported. For instructions on this, see “Testing email notification” below.

2.Select Enable email notification.

3.Optionally, change the format of the email to be sent. For instructions on this, see Constructing the email message template.

4.Specify one or more recipients to receive email about log messages. For instructions on this, see Specifying email recipients.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Testing email notification


HCP email notification works only if the HCP system has been configured to enable support for this feature. At any time, you can test the HCP system to determine whether it has been configured to support email notification.

Testing support for email notification causes HCP to send an email to an address that you specify. This email comes from the email address specified in the From field in the Message Settings section on the Email page. The email subject is “Test email from HCP.”

To test whether email notification is supported, on the Email page:

1.Click on Test.

2.In the Test Email Notification window, type the email address to which you want HCP to send the test email.

3.Click on Send.

If support for email notification is not configured at the system level, the Tenant Management Console displays an error message. If the Console displays a success message but the email does not arrive, ensure that you’ve correctly specified the email address to which you want the email sent. If the email still doesn’t arrive, contact your HCP system administrator for help.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Constructing the email message template


The content of the email messages HCP sends is determined by the message template specified in the Message Settings section on the Email page. You can modify this template at any time. The Message Preview section shows a sample email that uses the current template.

The email template has three fields, each of which can be filled in with any combination of plain text and email template variables:

The From field specifies the content of the email From line. This field must have a value. That value must have the form of a valid email address.

Some email servers require that the value in the From line be an email address that is already known to the server.

The Subject field specifies the content of the email Subject line. This field must have a value.

For the email template subject, plain text can include spaces but not line breaks or tabs.

The Body field specifies the body of the email. This field is optional.

For the email template body, plain text can include spaces and line breaks but not tabs. The character sequence consisting of a backslash (\) followed by a lowercase n creates a line break.

To modify the template HCP uses for email notification about log messages, on the Email page:

1.In the From, Subject, and Body fields in the Message Settings section, specify the values that you want to use.

2.Optionally, click on Preview to preview the sample email with the specified format in the Message Preview field.

3.Click on Update Settings at the bottom of the page.

Email template variables

The values you specify in the From, Subject, and Body fields in the email template can include variables that correspond to the information available for each log message (for example, the severity of the event that triggered the message or the short description of the event). When sending email, HCP replaces the variables in the email message with the applicable information.

To include a variable in the email template, you specify the variable name preceded by the dollar sign ($). A dollar sign followed by anything other than a variable name is displayed as a dollar sign in the email HCP sends.

The table below lists the variables you can use in the email template.

Variable Description
$action The action to take in response to the message
$date The date and time at which the event occurred (for example, Wed Feb 8 2012 3:15:57 PM EST)
$fullText The full text of the message
$id The message ID
$location The fully qualified name of the HCP system on which the event occurred (for example, hcp-ma.example.com)
$origin For user-initiated events, the IP address from which the event request was sent and the port through which HCP received the event request, separated by a colon (for example, 192.168.152.181:8000)
$reason The reason why HCP issued the message
$scope Either Tenant or Namespace
$severity The severity of the event that triggered the message
$shortText A brief description of the event that triggered the message
$type The type of message (General, Security, or Compliance), preceded by Important and a comma if the message is important (for example, Important, Security)
$user The user ID and username of the event initiator (for example, 105ff38f-4770-4f98-b5b3-8371ab0af359 lgreen)

For more information on log messages, see Understanding log messages and Tenant log messages.

Restoring the default template

The table below shows the format of the default email template.

Field Default value
From log@$location
Subject [$severity] $shortText
Body

The following event occurred on $date: $fullText

Reason:
$reason

Action:
$action

Details:
User: $user
Origin: $origin

To change the email template back to the default, on the Email page:

1.Click on Reset.

2.Optionally, click on Preview to preview the sample email with the default format in the Message Preview field.

3.Click on Update Settings at the bottom of the page.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Specifying email recipients


You use the Recipients section on the Email page to specify the email addresses to which HCP sends email about log messages. HCP sends email as blind carbon copies, so email recipients are not visible to one another.

Each row in the Recipients section contains one or more email addresses and indicates which messages are sent to those addresses. The section can have at most 25 rows.

Because each row in the Recipients section can contain multiple email addresses, you can specify a total of more than 25 addresses in this section. However, HCP sends each email only to an arbitrary 25 of the addresses that are supposed to receive the email. For example, if 34 email addresses are supposed to receive email about log messages that are important and have a severity level of error and a type of general, HCP sends such email only to 25 of those addresses.

You can add, modify, and delete rows in the Recipients section at any time.

Understanding the recipients list

Each row in the Recipients section specifies:

One or more email addresses.

Whether to send email only about important log messages (Major) to the specified email addresses or to send email about all log messages (All).

The severity of the log messages about which to send email:

oNotice tells HCP to send email about log messages with a severity level of notice, warning, or error.

oWarning tells HCP to send email about log messages with a severity level of warning or error.

oError tells HCP to send email only about log messages with a severity level of error.

Whether to send email about general log messages ( AdministratorRoleSymbol.gif ). General log messages are all messages that do not have a type of security or compliance.

Whether to send email about log messages with a type of security ( SecurityRoleSymbol.gif ).

Whether to send email about log messages with a type of compliance ( ComplianceRoleSymbol.gif ).

Email recipients receive email only about log messages that have all the selected properties.

Adding, modifying, and deleting rows in the recipients list

To add, modify, and/or delete rows in the recipients list, on the Email page:

1.Take one or more of these actions:

oTo add a row:

1.Optionally, in the Recipients field, type a comma-separated list of one or more well-formed email addresses.

2.Click on Add.

A new row appears in the recipients list with importance set to Major, severity set to Error, and only general selected as the type. The row is highlighted in green.

To remove the new row, click on the delete control ( DeleteControl.png ) for the row.

oTo modify a row:

Optionally, in the Address field, type additional well-formed email addresses and/or modify or delete existing addresses. This field must contain at least one well-formed email address and no incorrectly formed addresses.

Optionally, change the properties based on which HCP sends email to the specified addresses.

If you deselect all the types, no email is sent to the specified addresses.

oTo delete a row, click on the delete control ( DeleteControl.png ) for the row.

The row turns red. To undo the deletion, click again on the delete control.

2.Click on Update Settings at the bottom of the page.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.