Access different reports via the main tabs.

Within each report, navigate pages via the left and right arrows at the bottom of the dashboard.

Drill through by right-clicking on screen.

Health – Platform Costs

• A retrospective look back on Total Infrastructure Costs, broken down by component
• Enables users to view the split of costs per component for the nominated time period
• Provides visibility at a per week/per month grouping
• Enables comparison of costs
• Values are taken from Azure Portal

Used for: Steer co, weekly tracking, internal & external stand ups. Analysis and recommendations made by Solution Architect and Delivery Lead as a result

Health – SQL Metrics

• A retrospective look back on Storage Consumption in GB by Database along with Compute Utilisation (Cores) by Database
• Enables users to view the split of average storage consumption per week or month comparative to the storage allocation, plus Compute Utilisation (Cores) compared to the limit
• Provides visibility at a per week per month grouping
• Enables comparison of Average Storage Consumption and Average Compute used
• Values are taken from SQL DB Audit Logs

Used for: Steer co, weekly tracking, internal & external stand ups. Analysis and recommendations made by Solution Architect and Delivery Lead as a result

Usage – Power BI

• A retrospective look back on number of unique Power Bi Users and total usage by report
• Enables users to view the split of unique users and views, plus total usage per report
• Provides visibility at a per day grouping
• Enables comparison o usage across published reports and unique users
• Values are taken from Power BI Audit Logs

Used for: Steer co, weekly tracking, internal & external stand ups. Analysis and recommendations made by Solution Architect and Delivery Lead as a result

Usage – SQL

• A retrospective look back on Unique Platform users and number of activities performed
• Enables users to view the split per day and per user
• Provides visibility at a per week/per month grouping
• Enables comparison of access count and users, along with summary of total activities by user
• Values are taken from SQL DB Audit Logs

Used for: Steer co, weekly tracking, internal & external stand ups. Analysis and recommendations made by Solution Architect and Delivery Lead as a result

Usage – Databricks

• A retrospective look back on Unique Platform users and number of activities performed
• Enables users to view the split per day and per user
• Provides visibility at a per week/per month grouping
• Enables comparison of access count and users, along with summary of total activities by user
• Values are taken from Databricks Audit Logs/Unity Audit Logs if available

Report overview

As part of monitoring Platform Health, this report provides an overview of:

1. Health – Platform Costs – Track costs to ensure there are no surprises and determine whether all components of the platform are generating positive ROI
2. Health – SQL Metrics –
   
   • Storage Consumption – Databases can perform slowly if they are not properly set up to meet the demand in terms of storage. Poor database performance can manifest itself in other aspects of the platform e.g. slowing down pipelines or slow reports. On the other hand if we are steadily using less than 20 % of the storage, we can reconsider the storage space needed.
   • Compute – Similar to storage, the utilization of compute power can have a direct impact on database performance in terms of query speed or any other data extraction/ingestion. It is important to track and compare compute power allocated vs average compute utilization to ensure we have the right configuration for our needs
3. Usage – Usage logs are key to understand the adoption of the assets and tie them back to the discussion of value/cost

Data availability

The report always shows the latest available data at the time this report is refreshed.

Data sources

• Azure portal exports for costs
• Azure portal SQL DB Diagnostic logs
• Azure Portal SQL and Databricks audit log exports
• Power BI Usage metrics report

How to run this report

This report refreshes daily automatically to pick up the latest information. The following parameters will have to be configured for the first time the report is scheduled.

SQL Sever – SQL Server name for eg : ignite-dev-sal-srv.database.windows.net

SQL Database – SQL Database name for eg: IgniteSQLDB01

Project Name – Name of the client

Key definitions

• Average Storage Used: The amount of storage consumed by the given database at the timestamp in GB.
• Average Platform Activity By Week: Average of all activities by week on the platform for specific date interval.
• Average CPU Consumption: The amount of compute power consumed by the given b at the timestamp
• Cost: Costs related to the given time period for a given Infrastructure component
• Compute Limit: The amount of compute power allocated to a given db. For eg: CPU, DUs
• Databricks Tables Accessed Count: The number of times a table is accessed for specific date interval.
• Platform Activity: A table shows the count of all activities on the platform by each user for a specific date interval.
• Usage Trend: A line chart shows number of views for each report for a specific date interval.
• Storage Limit: The amount of storage allocated to a given db in GB
• Total Unique Platform Users: Distinct users for specific date interval.
• Unique Power BI Users: Distinct users for a specific data interval

Delivery & Activity

• A retrospective look back on activities & what has been delivered.
• Enables users to view the split of effort across new development vs platform management & a breakdown per card type.
• Provides ability to view at a per week/per month grouping.
• Tables enable comparison of estimated vs actual time spent & epic status.
• Values are taken from kanban board & can be utilised for all project types, plus includes service desk cards & time spent.

Used for: Steer co, weekly time tracking, internal & external stand ups. Analysis & recommendations made by Delivery Lead as a result.

Platform Management

• Summarised view of service desk, applicable only to platform manage & grow accounts.
• Summarised view of incidents and service desk cards raised as a result of platform monitoring and requests submitted.
• Enables visibility of trends per “component” based on cards raised.

Used for: Steerco, weekly time tracking, internal & external stand ups Analysis & recommendations made by Solution architect & Delivery Lead as a result.

Plan – Epic Prioritisation

• Forward view of the kanban board.
• Order of epics is as per epic order.
• Enables forward planning & prioritisation based on data included in epics & associated cards in the backlog.
• Times are reported based on estimated vs actual & estimated time remaining within associated cards.

Used for: Steerco, weekly time tracking, internal & external stand ups. Analysis & recommendations made by Delivery Lead as a result.

Effort Breakdown

• Primarily used to support invoicing & share breakdown of effort allocation across a 2 week invoicing period (nominated time frame)

Used for: Invoicing, internal & external stand ups.

Report Overview

The DataPulse reporting tool provides a comprehensive overview of the projects within the portfolio, their progress, resource allocation, risks, and overall performance. It also provides a summary of the current status of each card in a project, including key milestones, timelines, and progress achieved. This helps stakeholders understand the overall progress and identify any epics that may require additional attention or support.

Data availability

The report always shows the latest available card details at the time this report is refreshed.

How to run this report

This report refreshes automatically daily, picking up the latest information. It is not necessary to enter or change any parameters.

Key Definitions

• Actual Effort (hrs) – actual hours to complete (per card)
• Business Priority – prioritisation level assigned to an epic
• Deadline – due date for epic completion
• Date Prioritised – date epic was prioritised by steerco
• Epic Name – name of epic
• Epic Type – type of epic
• Est. Value – estimated value in dollars produced by an epic
• Est. Effort (hrs) – estimated hours to complete (per card)
• Est. Effort Remaining (hrs) – the remaining effort for cards that are “in progress” or “not started” by subtracting the sum of actual effort from the sum of estimated effort, but returns 0 if the actual effort is greater than or equal to the estimated effort
• Open Tickets Pending Resolution – open service tickets with type incident or service request
• Open Problem Tickets – open service tickets with type problem
• % Hours Completed – actual effort divided by the sum of actual effort and remaining effort expressed as a percentage
• % Hours Remaining – remaining effort divided by the sum of actual effort and remaining effort expressed as a percentage
• Project Code – unique identifier for specific project associated with an epic
• Status – epic status
• Tickets Opened – open service tickets with type incident, service request or problem
• Tickets Resolved – resolved service tickets with type incident, service request or problem
• Total Cards – sum total of all cards associated with an epic
• Value Drive – key objective of an epic