Production Availability (Service Dashboard)
Location: Open the Service Dashboard. The Overview is displayed by default.
This widget shows the availability of this service and its underlying infrastructure over the selected time interval. Toggle between the chart view and the data view using the symbol in the bottom right corner.
Availability is measured over complete months, which is reflected in the time intervals for all availability chart and data views. For example, if you select a time interval of 6 months on Monday May 6th, 2014, the Production Availability chart and data views display availability for six complete months: November, December, January, February, March, and April, as well as the availability to May 1st to 5th, 2014.
Chart View: The chart view shows both overall availability and infrastructure availability for this service over selected the time interval. Availability is displayed as a continuous horizontal green bar, where:
Overall availability reflects the percentage of time that the service was operating as expected.
Infrastructure availability shows the percentage of time that the underlying facility, network, and hardware components in all environments associated with this service were operating as expected.
Any unplanned complete outages (if any) - that is, any unscheduled intervals when the service was completely unavailable and Oracle was responsible for restoring service - are displayed as red bars.
To be classified as complete unplanned infrastructure outage, the root cause must be identified in the security, network, OS, or hardware category. Planned outages, such as for routine maintenance, and service interruptions, where the service was partially available, are not included in availability calculations.
Data View: The data view production availability for this service over the selected time interval:
| Field | Description |
|---|---|
| Total Unplanned Outage Time | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Customer Outage | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and when your organization was responsible for service restoration. |
| Oracle Outage | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Total Unplanned Outage Count | Number of times unplanned outages occurred in this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Average Time to Restore for Each Unplanned Outage | Average time, to the nearest hour and minute, to restore the environment following an outage. |
| Total Infrastructure Outage Time | Total unplanned outage time (to the nearest hour and minute) for this environment, when the infrastructure was completely unavailable owing to a facility, network, or hardware cause and when Oracle was responsible for service restoration. |
| Total Infrastructure Outage Count | Number of times unplanned infrastructure outages occurred in this environment, when the infrastructure was completely unavailable and Oracle was responsible for service restoration. |
Production Availability by Environment (Customer Dashboard)
Location: Open the Customer Dashboard. The Overview is displayed by default.
This widget shows the availability of this environment and its underlying infrastructure over the selected time interval. Tap the chart icon in the bottom right corner of the widget to open the data view in expanded mode.
Availability is measured over complete months, which is reflected in the time intervals for all availability chart and data views. For example, if you select a time interval of 6 months on Monday May 6th, 2014, the Production Availability by Environment chart and data views display availability for six complete months: November, December, January, February, March, and April, as well as the availability to May 1st to 5th, 2014.
Chart View: The chart view shows both overall availability and infrastructure availability for this environment over selected the time interval. Availability is displayed as a continuous horizontal green bar, where:
Overall availability reflects the percentage of time that the environment was operating as expected.
Infrastructure availability shows the percentage of time that the underlying facility, network, and hardware components in the environment were operating as expected.
Unplanned complete outages - that is, any unscheduled intervals when the service was completely unavailable and Oracle was responsible for restoring service - are displayed as red bars.
To be classified as complete unplanned infrastructure outage, the root cause must be identified in the security, network, OS, or hardware category. Planned outages, such as for routine maintenance, and service interruptions, where the environment was partially available, are not included in availability calculations.
Data View: The data view shows production outages, if any, for this environment over the selected time interval:
| Field | Description |
|---|---|
| Infrastructure Outage Time | Total unplanned outage time (to the nearest hour and minute) for this environment, when the infrastructure was completely unavailable owing to a facility, network, or hardware cause and Oracle was responsible for service restoration. |
| Total Unplanned Outage Time | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Customer Outage | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and when your organization was responsible for service restoration. |
| Oracle Outage | Total unplanned outage time (to the nearest hour and minute) for this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Total Unplanned Outage Count | Number of times unplanned outages occurred in this environment, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Average Time to Restore for Each Unplanned Outage | Average time, to the nearest hour and minute, to restore the environment following an outage. |
Production Availability by Service (Customer Dashboard)
Location: Open the Customer Dashboard. The Overview is displayed by default.
This widget shows the availability of all your organization's individual Managed Cloud Services and their underlying infrastructure over the selected time interval. Tap the chart icon in the bottom right corner of the widget to open the data view in expanded mode.
Availability is measured over complete months, which is reflected in the time intervals for all availability chart and data views. For example, if you select a time interval of 6 months on Monday May 6th, 2014, the Production Availability by Service chart and data views display availability for six complete months: November, December, January, February, March, and April, as well as the availability to May 1st to 5th, 2014.
Chart View: The chart view shows both overall availability and infrastructure availability for this service over selected the time interval. Availability is displayed as a continuous horizontal green bar, where:
Overall availability reflects the percentage of time that all your organization's live, production Oracle Managed Cloud Services were operating as expected and accessible by end users.
Infrastructure availability shows the percentage of time that the underlying facility, network, and hardware components associated with your organization's production Managed Cloud Services environments were operating as expected.
Unplanned complete outages - that is, any unscheduled intervals when your organization's services were completely unavailable and Oracle was responsible for restoring service - are displayed as red bars.
To be classified as complete unplanned infrastructure outage, the root cause must be identified in the security, network, OS, or hardware category. Planned outages, such as for routine maintenance, and service interruptions, where the service was partially available, are not included in availability calculations.
Data View: The data view shows production outages, if any, for all your organization's live, production Managed Cloud Services over the selected time interval:
| Field | Description |
|---|---|
| Infrastructure Outage Time | Total unplanned outage time (to the nearest hour and minute) for all your organization's Managed Cloud Services, when the infrastructure was completely unavailable owing to a facility, network, or hardware cause and Oracle was responsible for service restoration. |
| Total Unplanned Outage Time | Total unplanned outage time (to the nearest hour and minute) for all your organization's Managed Cloud Services, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Customer Outage | Total unplanned outage time (to the nearest hour and minute) for all your organization's Managed Cloud Services, when the service or infrastructure was completely unavailable and when your organization was responsible for service restoration. |
| Oracle Outage | Total unplanned outage time (to the nearest hour and minute) for all your organization's Managed Cloud Services, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Total Unplanned Outage Count | Number of times unplanned outages occurred in any of your organization's Managed Cloud Services, when the service or infrastructure was completely unavailable and Oracle was responsible for service restoration. |
| Average Time to Restore for Each Unplanned Outage | Average time, to the nearest hour and minute, to restore all services following an outage. |
| Infrastructure Outage Time | Total unplanned outage time (to the nearest hour and minute) for all your organization's Managed Cloud Services, when the infrastructure was completely unavailable owing to a facility, network, or hardware cause and Oracle was responsible for service restoration. |
Recent Storage Activity (Landing Pad)
Location: On the landing pad, which is the Oracle Pulse home screen.
This tile shows the percentage change in storage activity since the date displayed. An increase of 5% or more in storage usage over one week is considered significant. If your storage usage increases by more than 5% in one week, Oracle recommends that you contact your Oracle service delivery manager (SDM) to discuss the increase.
Recommendations (Customer Dashboard)
Location: On the Customer Dashboard, tap Recommendations.
The Recommendations option shows actions that you can choose to take to improve performance, security, or other aspects of a service or environment. Drawn directly from a Managed Cloud Service repository of optimal configurations, recommendations are generated as part of periodic maintenance on environments.
Types of recommendations:
Current Recommendations - These recommendations have been approved by a planner and presented to you in an RFC. If approved, the RFC will be applied to the named environment.
Implemented Recommendations - These recommendations have been applied to the named environment.
Rejected Recommendations - These recommendations have been presented in RFCs but have been rejected and therefore were not applied to the named environment.
Recommendations (Service Dashboard)
Location: On the Service Dashboard, tap Recommendations.
Recommendations are actions that you can choose to take to improve performance, security, or other aspects of a service environment. Drawn directly from a Managed Cloud Service repository of optimal configurations, recommendations are generated as part of periodic maintenance on environments.
Types of recommendations:
Current Recommendations - These recommendations have been approved by a planner and presented to you in an RFC. If approved, the RFC will be applied to the service instance.
Implemented Recommendations - These recommendations have been applied to the service environment.
Rejected Recommendations - These recommendations have been presented in RFCs but have been rejected and therefore were not applied to the service environment.
Recommendations (Environment Dashboard)
Location: On the Environment Dashboard, tap Recommendations.
Recommendations are actions that you can choose to take to improve performance, security, or other aspects of a service environment. Drawn directly from a Managed Cloud Service repository of optimal configurations, recommendations are generated as part of periodic maintenance on environments.
Types of recommendations:
Current Recommendations - These recommendations have been approved by a planner and presented to you in an RFC. If approved, the RFC will be applied to the service environment.
Implemented Recommendations - These recommendations have been applied to the service environment.
Rejected Recommendations - These recommendations have been presented in RFCs but have been rejected and therefore were not applied to the service environment.
Location: On the Service Dashboard, tap Refreshes.
The Refresh chart and table show the following information over the selected time interval.
Consumed Entitled Refreshes shows the number of refreshes used for environments associated with this service, from your refresh entitlement in the time interval selected. Your refresh entitlement includes your refresh allowance for implementation and production phases. It also includes any additional refreshes that you have purchased. This information is calculated and maintained automatically. If there are any discrepancies, contact your Oracle service delivery manager (SDM).
Consumed Purchased Refreshes shows the number of additional purchased refreshes used for environments associated with this service, in the time interval selected.
Overage shows the number of refreshes, if any, that used for environments associated with this service, in excess of your entitled and purchased refreshes.
Service Transactions (Customer Dashboard)
Location: Open the Customer Dashboard. The Overview is displayed by default.
This widget shows a summary of all monitored transactions for all your organization's Managed Cloud Services, grouped by service. Tap the Transactions option on the navigation bar to see the full transactions table.
Transaction response times gives a sense of the performance of your services and environments and can indicate potential or actual issues. Your Oracle Service Delivery Manager (SDM) can work with you to identify these transactions and set up monitoring.
Note:
Where Business Transaction Monitoring (BTM) has been implemented, the Service Transactions widget displays populated transactions reports.If BTM has not been implemented, the transaction widgets will show empty chart and data views.
You cannot flip the Service Transactions widget.
One or more beacons measures the response time of each monitored transaction. You can view the last time data was collected from the beacon(s) and compare the current value with the 30 day average.
Each transaction record shows:
| Field | Description |
|---|---|
| Transaction Name | Name of the transaction being monitored |
| Collection Point | Hostname of the system from which data is collected as part of monitoring |
| Last Collection | Time of the last data collection from the collection point(s) |
| 30 Day Average | Average transaction time over the last 30 days |
| Threshold | Minimum acceptable performance level for this transaction |
Service Transactions (Environment Dashboard)
Location: Open the Environment Dashboard. The Overview is displayed by default.
This widget shows records of all monitored transactions for the selected environment. Tap the Transactions option on the navigation bar to see the full transactions table for this environment.
Transaction response times give a sense of the performance of your services and environments and can indicate potential or actual issues. Your Oracle Service Delivery Manager (SDM) can work with you to identify these transactions and set up monitoring.
Note:
Where Business Transaction Monitoring (BTM) has been implemented, the Environment Transactions widget displays populated transactions reports.If BTM has not been implemented, the Transactions option and widget are hidden.
You cannot flip the Environment Transactions widget.
One or more beacons measure the response time of each monitored transaction. You can view the last time data was collected from the beacon(s) and compare the current value with the 30 day average.
Each transaction record shows:
| Field | Description |
|---|---|
| Transaction Name | Name of the transaction being monitored |
| Collection Point | Hostname of the system from which data is collected as part of monitoring |
| Last Collection | Time of the last data collection from the collection point(s) |
| 30 Day Average | Average transaction time over the last 30 days |
| Threshold | Minimum acceptable performance level for this transaction |
Service Transactions (Service Dashboard)
Location: Open the Service Dashboard. The Overview is displayed by default.
This widget shows records of all monitored transactions for the selected service. Tap the Transactions option on the navigation bar to see the full transactions table for this service.
Transaction response times give a sense of the performance of your services and environments and can indicate potential or actual issues. Your Oracle Service Delivery Manager (SDM) can work with you to identify these transactions and set up monitoring.
Note:
Where Business Transaction Monitoring (BTM) has been implemented, the Service Transactions widget displays populated transactions reports.If BTM has not been implemented, the Transactions option and widget are hidden.
You cannot flip the Service Transactions widget.
One or more beacons measure the response time of each monitored transaction. You can view the last time data was collected from the beacon(s) and compare the current value with the 30 day average.
Each transaction record shows:
| Field | Description |
|---|---|
| Transaction Name | Name of the transaction being monitored |
| Collection Point | Hostname of the system from which data is collected as part of monitoring |
| Last Collection | Time of the last data collection from the collection point(s) |
| 30 Day Average | Average transaction time over the last 30 days |
| Threshold | Minimum acceptable performance level for this transaction |
Severity 1 Changes (Landing Pad)
Location: On the landing pad, which is the Oracle Pulse home screen.
This tile displays all open Severity 1 changes - that is, requests for change (RFCs) - created on production instances up to the date and time listed. Severity 1 indicates a complete loss of service for mission critical operations where work cannot reasonably continue
Tap the tile to see the following figures for each environment (labeled 'instance') and associated environment alias (labeled 'instance ID'):
Sev 1 RFCs - The number of open Severity 1 RFCs for the instance.
RFCs Awaiting Customer - The number of open RFCs awaiting your input or approval to progress.
Note:
If your My Oracle Support (MOS) user account does not have privileges to view RFCs, this tile is hidden.Severity 1 Incidents (Landing Pad)
Location: On the landing pad, which is the Oracle Pulse home screen.
This tile displays all open Severity 1 incidents - that is, service requests (SRs) - created on production instances up to the date and time listed. Severity 1 indicates a complete loss of service for mission critical operations where work cannot reasonably continue.
Tap the tile to see the following figures for each environment (labeled 'instance') and associated environment alias (labeled 'instance ID'):
Sev 1 Incidents - The number of open Severity 1 SRs created for the environment.
EM Generated - The number of SRs automatically generated by Oracle Enterprise Manager (EM).
BTM Failures - Where business transaction monitoring (BTM) has been implemented, the number of monitored transactions that have exceeded the performance threshold.
Awaiting Customer - The number of SRs awaiting your action as a customer, that is, requiring your input or approval to progress.
Note:
If your My Oracle Support (MOS) user account does not have privileges to view SRs, this tile is hidden.Storage Usage (Service Dashboard)
Location: Open the Service Dashboard. The Overview is displayed by default
This widget shows the storage used by each environment for the selected service. Your storage entitlement is usually allocated as needed across all environments. The Storage Usage chart can be useful in identifying environments that are consuming a disproportionate amount of storage.
Chart View: The chart view shows the entitlement, the total usage for all services and instances, and the storage usage for the selected service.
Data View: The data view lists the storage used by each environment as well as the category and subcategory.
Storage Usage (Environment Dashboard)
Location: Open the Environment Dashboard. The Overview is displayed by default
This widget shows the total storage used by this environment over the selected time interval.
Chart View: The chart view plots storage usage for this environment, compared with current entitlement and overall service storage.
Data View: The data view shows a breakdown by environment, category and subcategory of storage usage over the selected time interval.
Storage Usage by Service (Customer Dashboard)
Location: On the Customer Dashboard, tap Storage.
This widget shows the percentage of storage used by each of your organization's Managed Cloud Services. Your storage entitlement is usually allocated as needed across all services. The Storage Usage chart can be useful in identifying services that are consuming a disproportionate amount of storage.
Chart View: The chart view shows a breakdown of storage usage by service, as a percentage of total storage usage, for all your organization's Managed Cloud Services.
Data View: The data view lists all your organization's Managed Cloud Services. It displays the number of environments for each service, the total storage used by the environment, and the percentage of total storage that the service uses, as well as the category and subcategory.
Storage Usage versus Entitlement (Customer Dashboard)
Location: On the Customer Dashboard, tap Storage.
This widget shows overall storage usage for all your organization's Managed Cloud Services compared with your current entitlement, over the selected time interval.
Chart View: The chart view shows overall storage usage for all your organization's Managed Cloud Services compared with your current entitlement, over the selected time interval.
Data View: The data view provides detailed information about the total storage usage for each service, showing storage used per associated environment, category, and subcategory, for all your organization's Managed Cloud Services.
Storage Utilization versus Entitlement (Landing Pad)
Location: On the landing pad, which is the Oracle Pulse home screen.
This tile compares the amount of storage used by all your Managed Cloud Services with your purchased entitlement, on the last collection date. Your storage entitlement is usually allocated as needed across all services. This tile can be useful in identifying services that are consuming a disproportionate amount of storage.
Tap the tile to see the data view, listing the amount of storage used, in Gigabytes, and percentage of total storage used by each service.
Transaction Performance (Landing Pad)
Location: On the landing pad, which is the Oracle Pulse home screen.
This tile shows the number of transactions exceeding the threshold at the latest collection date and time. A transaction is a sequence of operations that is monitored as a single unit. Comparing transaction response times with the threshold value gives a sense of services' performance. If one or more transactions exceed the threshold, this can indicate potential or actual issues with the associated service.
Note:
Where business transaction monitoring has not been implemented, this tile is hidden.