Skip to main content
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.

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.

Before you begin

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.

Procedure

  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 All Events.

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.

Before you begin

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

Procedure

  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 Security Events.

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.

Before you begin

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

Procedure

  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 Compliance Events.

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:
    • For 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.
    • For system-initiated events, the username is [internal].
    • For 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:
    • Notice

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

      Examples are:

      • Namespace created
      • Privileged delete requested
    • Warning

      The event is out of the ordinary and may require manual intervention.

      Examples are:

      • Namespace over soft quota
      • User account failed login
    • Error

      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

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 expand all. To hide all details, click 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 the next () or back () control, respectively.

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 Management Console and Tenant Management Console.

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.

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.

Before you begin

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

Procedure

  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 Update Settings.

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.

Before you begin

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

Procedure

  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 Update Settings.

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.

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

Enabling email notification

  1. (Optional) Test whether email notification is supported.

  2. Select Enable email notification.

  3. (Optional) Change the format of the email to be sent.

  4. Specify one or more recipients to receive email about log messages.

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.

Procedure

  1. On the Email page, click Test.

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

  3. Click Send.

Results

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.

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:

  • From

    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.

  • Subject

    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.

  • Body

    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.

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 list below lists the variables you can use in the email template.

  • $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)

Modify the email notification template

Modify the template HCP uses for email notification about log messages.

Procedure

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

  2. Click Preview to preview the sample email with the specified format in the Message Preview field.

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

Restoring the default template

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

  • From

    log@$location

  • Subject

    [$severity] $shortText

  • Body

    The following event occurred on $date: $fullText
    
    Reason:
    $reason
    
    Action:
    $action
    
    Details:
    User: $user
    Origin: $origin

Procedure

  1. On the Email page, click Reset.

  2. Click Preview to preview the sample email with the default format in the Message Preview field.

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

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:
    • Notice

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

    • Warning

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

    • Error

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

  • Whether to send email about general log messages (). 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 ().
  • Whether to send email about log messages with a type of compliance ().

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

Modifying rows in the recipients list

  1. Add a row.

    1. (Optional) In the Recipients field, type a comma-separated list of one or more well-formed email addresses.

    2. Click 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.
  2. Modify a row.

    1. (Optional) 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.
    2. (Optional) 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.
  3. To delete a row, click the delete control () for the row.

    The row turns red.
  4. Click Update Settings at the bottom of the page.

Monitoring and managing replication

The Replication page in the Tenant Management Console shows information about replication of the current tenant when both of these conditions are true:

  • The tenant is eligible for and currently selected for replication.
  • The HCP system is configured to show this information.

If the tenant is eligible for but not currently selected for replication, the page shows a replication status of Not Replicating.

You can use the statistics and graphs on the Replication page to monitor replication progress. You can also use the page to select and deselect namespaces to be replicated along with the tenant.

To display the Replication page, in the top-level menu of the Tenant Management Console, select Services Replication.

Roles: To view the Replication page, you need the monitor or administrator role. To select and deselect namespaces for replication, you need the administrator role.

Tenant-level view of replication

At the tenant level, the Replication page shows:

  • Only on an HCP system that’s sending data for the tenant to other systems, the approximate number of objects and parts of multipart objects currently waiting to be replicated in all namespaces owned by the tenant.
  • Only on an HCP system that’s sending data for the tenant to other systems, the approximate amount of data currently waiting to be replicated in all namespaces owned by the tenant, in bytes.
  • On an HCP system that’s sending data for the tenant to other systems or receiving data for the tenant from other systems, the current rate of replication activity, expressed as operations per second and as bytes per second. An operation is the replication of a single item, such as the creation of a new object, a metadata change, or a namespace configuration change.

    These rates are the sums of the corresponding rates for the tenant's namespaces.

  • A list of the namespaces selected for replication with the tenant. For each namespace, the list shows a progress bar that measures the up-to-date-as-of time for replication of that namespace, along with this time as a numeric value. The length of the progress bar represents 30 days, with the right end representing the current time.

    The up-to-date-as-of time is the difference between:

    • The time before which objects, object parts, metadata changes, and configuration changes are guaranteed to have been sent to other systems or received from other systems
    • The current time

Managing the namespace list

By default, the namespace list on the Replication page includes all the namespaces that are selected for replication. The namespaces are listed 20 at a time in ascending order by namespace name.

You can page through, sort, and filter the list of namespaces. The Replication page indicates which namespaces are shown out of the total number of namespaces in the current list.

Paging

You can change the number of namespaces shown at a time on the Replication page. To do this, in the Items per page field, select the number of namespaces you want. The options are 10, 20, and 50.

To page forward or backward through the namespace list, click the next () or back () control, respectively.

Procedure

  1. In the Page field, type the page number you want.

  2. Press Enter.

Sorting

You can sort the namespace list in ascending or descending order by namespace name. To sort the list, click the Name column heading. Each time you click the column heading, the sort order switches between ascending and descending.

Filtering

You can filter the namespace list by namespace name or tag. The filtered list includes only those namespaces with a name or tag, as applicable, that begins with or is the same as a specified text string.

Procedure

  1. In the field above the Name column, select Name to filter by name or Tag to filter by tag.

  2. In the next field, type the text string you want to use as a filter.

    This string can be up to 64 characters long, can contain any valid UTF-8 characters except commas (,), and is not case sensitive. White space is allowed.
  3. Click the find control ().

Next steps

To redisplay the entire list of namespaces after filtering it, click the clear filter control ().

Namespace-level view of replication

To view more detailed information about the replication of an individual namespace listed on the Replication page, click the namespace name. The panel that opens shows:

  • The date and time before which objects, parts of multipart objects, metadata changes, and configuration changes for the namespace are guaranteed to have been sent to other systems or received from other systems
  • A graph of the history of the up-to-date-as-of time for replication of the namespace
  • A graph of the history of the data transmission rate for replication of the namespace
  • A graph of the history of the operation rate for replication of the namespace

On an HCP system that’s sending data for the tenant to other systems, the panel also shows this information for the namespace:

  • The approximate number of objects and parts of multipart objects currently waiting to be replicated
  • The approximate amount of data currently waiting to be replicated

Up-to-date-as-of time

The Up to date as of section in the namespace replication panel contains a graph that shows the history of the up-to-date-as-of time for replication of the namespace. The section heading shows the current up-to-date-as-of time. If the graph is not currently visible, click Up to date as of to display it.

The x‑axis in this graph marks the passage of time. It shows 30 days (or fewer if replication has been occurring for less than 30 days). The y-axis marks the up-to-date-as-of time in days, hours, or minutes. As the up-to-date-as-of time varies, the measurement unit for the y-axis grows or shrinks as needed (for example, from days to hours to minutes). The lower the up-to-date-as-of time, the closer replication is to being synchronized with current namespace activity.

Data transmission rate

The Transfer Rate section in the namespace replication panel contains a graph that shows the history of the rate of replication data transmissions for the namespace per second. The section heading shows the current data transmission rate. If the graph is not currently visible, click Transfer Rate to display it.

The x‑axis in this graph marks the passage of time. It shows 30 days (or fewer if replication or recovery has been occurring for less than 30 days). The y-axis marks the data transmission rate in KB, MB, or GB. As the transmission rate varies, the measurement unit for the y-axis grows or shrinks as needed (for example, from KB to MB to GB).

Operation rate

The Operations per Second section in the namespace replication panel contains a graph that shows the history of the rate of replication operations for the namespace per second. The section heading shows the current operation rate. If the graph is not currently visible, click Operations per Second to display it.

The x‑axis in this graph marks the passage of time. It shows 30 days (or fewer if replication or recovery has been occurring for less than 30 days). The y-axis marks the operation rate in tens, hundreds, or thousands. As the operation rate varies, the measurement unit on the y-axis grows or shrinks as needed (for example, from tens to hundreds to thousands).

Selecting or deselecting namespaces for replication

On the Replication page, at any time, you can change which namespaces are replicated with the tenant and, if allowed by the tenant configuration, specify whether those namespaces allow erasure coding. If you disable replication for a namespace that was already being replicated, replication of that namespace stops. If you subsequently enable replication for that namespace again, replication of the namespace starts again from where it stopped.

When you reenable replication of a namespace that has already been replicated, all operations that occurred in that namespace while replication was not happening, including object deletions, are replicated to the other system. During this replication, conflicts can occur between changes made on different systems while the namespace was not being replicated.

If you disable replication for a namespace that has already been replicated and then delete the namespace on one or more systems, the namespace deletions are not replicated. If you then reenable replication for that namespace and the namespace still exists on one or more systems, the namespace is replicated back to the systems where you deleted it.

You can also enable or disable replication for a namespace and specify whether the namespace allows erasure coding on the namespace Replication panel.

Depending on the current status of replication, if the tenant is being replicated, you may not be able to disable replication for namespaces that are being replicated.

Allowing erasure coding for a namespace that has shredding enabled as the default for new objects can significantly increase the load on all systems in the replication topology.

ImportantDisabling replication for a namespace that has already been replicated may cause object data in that namespace to become inaccessible on one or more systems in the replication topology.

Procedure

  1. Click Namespace Selection for Replication.

    The Namespace Replication Selection section lists all the tenant's namespaces. For each namespace, the section shows whether the namespace is cloud optimized. The Namespace Replication Selection section has a column in which you can select or deselect namespaces for replication. If you can specify whether namespaces allow erasure coding, this section also has a column in which you can allow or disallow erasure coding for namespaces.
  2. In the Namespace Replication Selection section:

    • To enable or disable replication for a namespace, select or deselect the namespace in the Replication column.
    • To enable or disable replication for all namespaces at the same time, select or deselect the Replication column heading.

      When you deselect Replication for a namespace, Allow Erasure Coding is automatically deselected for that namespace.

    • To allow or disallow erasure coding for a namespace, select or deselect the namespace in the Allow Erasure Coding column. This option is available only for cloud-optimized namespaces.
    • To allow or disallow erasure coding for all cloud-optimized namespaces at the same time, select or deselect the Replication column heading.

      When you select Allow Erasure Coding for a namespace, Replication is automatically selected for that namespace.

      The Allow Erasure Coding column is present only if you're allowed to choose whether namespaces allow erasure coding.

  3. Click Update Namespaces.

Generating chargeback reports

You can generate chargeback reports from the Tenant Management Console. A chargeback report contains current and historical statistics about the tenant and its namespaces, broken out by hour.

Chargeback reports are a good source of information for namespace analysis, enabling you to adjust storage and bandwidth allocations based on usage patterns. These reports can also serve as input to billing systems that need to determine charges for capacity and bandwidth usage.

About chargeback reports

A chargeback report contains statistics for each namespace owned by the current tenant. It also contains aggregated namespace statistics for the tenant. For example, the total number of reads for the tenant during a given reporting interval is the total number of successful read operations that occurred during that interval in each of the tenant's namespaces.

When generated from the Tenant Management Console, chargeback reports are in CSV format. Each line in a report contains the values for one namespace or for the tenant during one instance of the reporting interval.

The lines in a chargeback report are ordered alphabetically by namespace name. The lines for the tenant are at the end of the report. Multiple lines for a namespace or the tenant are ordered in ascending chronological order.

Roles: To generate chargeback reports, you need the monitor or administrator role.

Types of chargeback reports

You use the Chargeback page in the Tenant Management Console to generate chargeback reports. From this page, you can generate an hourly, daily, or monthly report:

  • Hourly report

    Includes statistics for the most recent full hour, plus the statistics accumulated so far for the current hour. For example, if you request the report at 2:30:15 p.m., it will contain one set of statistics for the period of time between 1:00:00 p.m. and 1:59:59 p.m. and another set of statistics for the period of time between 2:00:00 p.m. and 2:30:15 p.m.

  • Daily report

    Includes statistics for the most recent full day, plus the statistics accumulated so far for the current day. For example, if you request the report at 2:30:15 p.m. on October 7th, it will contain 24 sets of statistics for the period of time between 00:00:00 and 23:59:59 on October 6th and 15 sets of statistics for the period of time between 00:00:00 and 2:30:15 p.m. on October 7th.

  • Monthly report

    Includes statistics for the past 30 days, plus the statistics accumulated so far for the current day. For example, if you request the report at 2:30:15 p.m. on October 7th, it will contain 24 sets of statistics for each of the past 30 days and 15 sets of statistics for the period of time between 00:00:00 and 2:30:15 p.m. on October 7th.

The statistics reported for the current hour may not reflect some reads and writes that have already occurred during the hour. After the hour is past, however, the statistics reported for it are complete.

TipYou can use the HCP management API to generate chargeback reports that cover longer time periods and are in XML, JSON, or CSV format. This allows you to create applications that generate chargeback reports at regular intervals and feed those reports to a billing system. For information about using the management API to generate chargeback reports, see HCP Management API Reference.

Generating a chargeback report

Before you begin

To generate a chargeback report, you need the monitor or administrator role.

Procedure

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

  2. On the Chargeback page:

    As applicable:
    • Click Hourly Chargeback Report.
    • Click Daily Chargeback Report.
    • Click Monthly Chargeback Report.
  3. Select the browser-specific option for downloading the report.

Results

By default, the name of the downloaded report file is either Hourly-Chargeback-Report.csv, Daily-Chargeback-Report.csv, or Monthly-Chargeback-Report.csv, as applicable.

Chargeback statistics collection

Chargeback statistics either reflect a point in time or are dynamic. Point-in-time statistics are measurements taken at the end of a reporting interval, such as the used storage capacity for a namespace at the end of an hour. Dynamic statistics are measurements, such as the number of reads or writes to a namespace, that are accumulated over time.

HCP accumulates dynamic statistics on an hourly basis, starting at the beginning of each hour. So, for example, one statistic might represent the number of successful writes to a namespace that occurred between 11:00:00 and 11:59:59. Another might represent the number of successful writes to the same namespace that occurred between 12:00:00 and 12:59:59.

Chargeback report content

The first line of a chargeback report contains identifiers for the values in the subsequent lines. The list below describes each of these values.

  • bytesIn

    Type: Dynamic

    The total number of bytes successfully written to the given namespace or to any of the namespaces owned by the tenant during the reporting interval.

    The total number of bytes written includes all parts uploaded for multipart uploads regardless of whether the upload of the part has finished, the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload.

    If data was compressed before being transmitted, this is the number of bytes before compression.

  • bytesOut

    Type: Dynamic

    The total number of bytes read from the given namespace or from any of the namespaces owned by the tenant during the reporting interval.

    If data (including XML for directory listings) was compressed before being transmitted, this is the number of bytes before compression.

  • deleted

    One of:

    • true

      For a namespace only, the namespace was deleted after the statistics in the set were collected.

    • false

      The namespace or tenant currently exists.

    • included

      For a tenant only, the statistics in the set include values for one or more namespaces that were subsequently deleted.

  • deletes

    Type: Dynamic

    The total number of delete and purge operations successfully performed in the given namespace or in any of the namespaces owned by the tenant during the reporting interval.

    A delete of a multipart object counts as a single delete operation. The count of delete and purge operations does not include automatic deletions of replaced parts, parts of aborted multipart uploads, or unused parts of completed multipart uploads.

  • endTime

    The end time of the reporting interval for the set of statistics in the line, in the same format as is used for the startTime value.

  • ingestedVolume

    Type: Point in time

    The total size of the stored data and custom metadata, in bytes, before the data and custom metadata were added to the given namespace or to any of the namespaces owned by the tenant.

  • multipartObject Bytes

    Type: Point in time

    The total number of bytes of object data in all the parts of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.

  • multipartObject Parts

    Type: Point in time

    The total number of parts of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.

  • multipartObjects

    Type: Point in time

    The total number of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.

  • multipartUpload Bytes

    Type: Point in time

    The total number of bytes of object data in all the successfully uploaded parts of multipart uploads that are currently in progress in the given namespace or in all the namespaces owned by the tenant.

    This number does not include bytes of data in replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads.

  • multipartUpload Parts

    Type: Point in time

    The total number of successfully uploaded parts of multipart uploads that are currently in progress in the given namespace or in all the namespaces owned by the tenant.

    This number does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads.

  • multipartUploads

    Type: Point in time

    The total number of multipart uploads that are currently in progress in the given namespace or in all the namespaces owned by the tenant.

  • namespaceName

    The name of the namespace to which the set of statistics in the line applies.

    In lines that contain tenant statistics, this field has no value.

  • objectCount

    Type: Point in time

    The number of objects in the given namespace or in all the namespaces owned by the given tenant.

    Each version of an object counts as a separate object. The object count does not include object versions that are delete markers.

    Each multipart object counts as a single object. Objects that are in the process of being created by multipart uploads are not included in the object count.

  • reads

    Type: Dynamic

    The total number of read operations performed in the given namespace or in any of the namespaces owned by the given tenant during the reporting interval.

    A read of a multipart object counts as a single read operation.

  • startTime

    The start time of the reporting interval for the set of statistics in the line, in this format:

    yyyy-MM-dd hh:mm:ss

    hh is hours on a 24-hour clock.

    For example: 2010-10-07 14:00:00

  • storageCapacity Used

    Type: Point in time

    The total number of bytes occupied by stored data in the given namespace or in any of the namespaces owned by the given tenant. This includes object data, metadata, and any redundant data required to satisfy the applicable service plan.

    Used storage capacity includes storage occupied by the parts of in-progress multipart uploads that have already been written to HCP. Used storage does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads.

  • systemName

    The HCP domain name used for access to the content of namespaces owned by the given tenant

  • tenantName

    Either:

    • The name of the tenant that owns the namespace to which the set of statistics in the line applies
    • The name of the tenant to which the set of statistics in the line applies
  • valid

    The status of the set of statistics in the line. Possible values are:

    • true

      HCP successfully collected all statistics in the set.

    • false

      The statistics in the set do not reflect all the activity that occurred during the reporting interval. This may be due, for example, to a network failure or to other hardware issues.

  • writes

    Type: Dynamic

    The total number of write operations successfully performed in the given namespace or in any of the namespaces owned by the given tenant during the reporting interval.

    Each upload of a part for a multipart upload counts as a separate write operation. This applies even if the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload.

Sample chargeback report

Here's an example of a daily chargeback report, where the report was requested for February 17, 2017, through February 18, 2017. The report shows statistics for the europe tenant, which owns the finance and hr namespaces. The report is shown as it would appear in a spreadsheet.

systemNametenantNamenamespaceNamestartTimeendTimeobjectCountIngestedVolumestorageCapacityUsedbytesInbytesOutreadswritesdeletesmultipartObjectsmultipartObjectPartsmultipartObjectBytesmultipartUploadsmultipartUploadPartsmultipartUploadBytesdeletedvalid
hcp.example.comeuropefinance2/17/2017 0:00:002/17/2017 23:59:5961342437211342709761239862638756111002793213889000FALSETRUE
hcp.example.comeuropefinance2/18/2017 0:00:002/18/2017 23:59:59151864967471865482245225302600120311132662065000FALSETRUE
hcp.example.comeuropehr2/17/2017 0:00:002/17/2017 23:59:5979609368962150496093680070000000FALSETRUE
hcp.example.comeuropehr2/18/2017 0:00:002/18/2017 23:59:59151970738719730432100980190080000000FALSETRUE
hcp.example.comeurope 2/17/2017 0:00:002/17/2017 23:59:59131438530891438924801335956318756111702793213889000FALSETRUE
hcp.example.comeurope 2/18/2017 0:00:002/18/2017 23:59:59302062041342062786566235104500200311132662065000FALSETRUE

Chargeback page graphs

The Chargeback page contains four graphs. These graphs show information about the usage of the tenant's namespaces during the past 30 days (or since HCP was installed if that was less than 30 days ago).

The graphs are:

  • Writes (bytes)

    Shows the number of bytes of data written to the tenant's namespaces.

    The number of bytes written includes all parts written for multipart uploads regardless of whether the upload of the part has finished, the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload.

  • Writes (operations)

    Shows the number of successful write operations that targeted the tenant's namespaces.

    Each write of a part for a multipart upload counts as a separate write operation. This applies even if the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload.

  • Reads (bytes)

    Shows the number of bytes of data read from the tenant's namespaces.

  • Reads (operations)

    Shows the number of read operations that targeted the tenant's namespaces.

    A read of a multipart object counts as a single read operation.

 

  • Was this article helpful?