Welcome to the Forms Optel Dashboard (Operational Telemetry). This guide will help you understand and interpret all the data presented in the dashboard, enabling you to monitor your form's health and performance effectively.
- Getting Started
- Navigation
- Error Analysis Dashboard
- Performance Dashboard
- Other tabs (when enabled)
- Glossary
This dashboard provides hourly and daily insights (data is batched by hour/day from the RUM API, not streamed in real time) into how your web forms are performing for actual users visiting your website. Currently only the Error Analysis and Performance tabs are enabled. They cover:
- Errors: Resources that failed to load (images, scripts, stylesheets)
- Performance: How quickly your form becomes visible and usable to visitors
When enabled in future releases, Engagement (fills and clicks) and Resources (missing-resource focus) tabs will provide additional views.
- Select Date Range: Use the date picker at the top to choose a time period of 1 to 7 days (the dashboard enforces this limit).
- Search for URL: Use the "Search for URL" field to type or select the form page URL you want to monitor.
- Switch Tabs: Use the tabs to view different aspects of your form's health.
Before you select a URL, the message "Please select a URL to view dashboard" is shown. The app may display an Experimental ribbon in the header to indicate the dashboard is currently experimental.
The dashboard domain is editable from the UI:
- Enter a domain in the Domain input.
- Select Apply.
- The URL
domainparameter updates and the dashboard reloads data for that domain.
A domain key is resolved using the provided URL domainkey value (when present), otherwise the dashboard falls back to the token in localStorage (rum-bundler-token). If the domain/domainkey combination is invalid, the dashboard shows an "Invalid domain/domainkey combination" error and blocks data loading for that attempt.
Only two tabs are enabled in the UI today: Error Analysis and Performance. Use the tab buttons at the top to switch between them.
| Tab (enabled) | Purpose |
|---|---|
| Error Analysis | Monitor failed resource loads and missing files that could break your form |
| Performance | Track how quickly your form appears and becomes usable for visitors |
Engagement and Resources tabs are not yet enabled; they will be documented here when they are available.
The Error Analysis dashboard helps you identify and fix issues where resources (like images, scripts, or stylesheets) fail to load for your users.
Top filters: At the top of the tab, Device Type and Source dropdowns ("+ Add Device...", "+ Add Source...") let you narrow the data. Use Clear All to reset. Active choices appear as removable chips under the label Active Filters: (Active Status Filters: is a separate row used only in the Missing Resources panel below).
At the top of the Error Analysis dashboard, you'll find five key metric cards providing an overview of error status.
| Metric Card | What It Shows | How to Interpret |
|---|---|---|
| Total Errors | The cumulative count of all resource loading failures during the selected period | A higher number indicates more frequent problems. This should ideally be zero or very low. |
| Total Page Views | The number of times users loaded your form page | Provides context for other metrics. More views give you more reliable data. |
| Average Error Rate | The percentage calculated as: (Total Errors ÷ Total Page Views) × 100 | Under 1% = Good |
| Page Views with Missing Resources | Count of page loads where at least one resource failed | Shows real user impact. The subtext shows what percentage of all views were affected. |
| Unique Missing Resources | The number of distinct files/URLs that failed to load | A high number means many different things are broken; a low number with high errors means one resource is failing repeatedly. |
- Values displayed in red indicate concerning metrics requiring attention
- The percentage beneath "Page Views with Missing Resources" shows impact scope
Scenario: Total Page Views = 10,000 | Page Views with Missing Resources = 500 (5.0%)
Interpretation: 5% of your visitors experienced at least one missing resource. This means 1 in 20 users may have had a degraded experience.
This interactive line chart visualizes how error rates fluctuate over time, broken down by hour.
| Element | Description |
|---|---|
| X-Axis (Horizontal) | Time progression, with each point representing one hour |
| Y-Axis (Vertical) | Error rate expressed as a percentage (0% to maximum observed) |
| Line & Points | Connect hourly data points; each point is clickable for drill-down |
| Shaded Area | Filled area beneath the line showing error rate magnitude |
Points are color-coded based on error rate severity:
| Point Color | Error Rate | Severity Level |
|---|---|---|
| 🟢 Green | 0% | Excellent - No errors detected |
| 🟡 Yellow | Less than 1% | Minor - Acceptable range |
| 🟠 Orange | 1% to under 5% | Moderate - Investigate the cause |
| 🔴 Red | 5% and above | Critical - Immediate attention needed |
The chart background indicates time of day:
| Shading | Time Period | Typical Pattern |
|---|---|---|
| Light/White | Daytime (6 AM - 8 PM) | Usually higher traffic |
| Gray/Darker | Nighttime (8 PM - 6 AM) | Usually lower traffic |
A note below the chart shows your local timezone (e.g., "UTC+05:30") so you can correctly interpret the hour labels.
- Hover over any point to see a tooltip with:
- Error Rate percentage
- Total Errors count
- Total Page Views for that hour
- Click any point to open the Error Details Panel
| Pattern | Possible Cause | Recommended Action |
|---|---|---|
| Sudden spike at a specific hour | Deployment, server issue, or third-party outage | Check deployment logs for that time |
| Daily recurring spikes at same hour | Scheduled jobs, cache expiration, or maintenance | Review automated processes |
| Gradual increase over days | Growing infrastructure problem | Investigate server capacity and CDN health |
| Higher rates during peak hours | Server overload | Consider scaling resources |
When you click on a point in the Error Rate chart, a detailed breakdown panel slides into view.
- Click any point on the Error Rate Per Hour chart
- The panel appears below the chart with the header "Error Details for [Selected Hour]"
A scrollable list showing every unique error that occurred during the selected hour.
| Column | Description |
|---|---|
| Error Description | The source/target information identifying what failed (typically a URL or resource path) |
| Count | How many times this specific error occurred during the hour |
| Percentage | This error's share of total errors for the hour |
- Errors are sorted by frequency (most common at top)
- Higher percentages indicate the dominant issues to fix first
- The URL shown helps identify exactly which file failed
Click the "← Back to Overview" button in the panel header to collapse the details and return to the main view.
This pie chart appears within the Error Details Panel and shows which browsers, devices, and operating systems experienced errors.
A colorful pie chart breaking down errors by User Agent — the combination of browser type, version, device type, and operating system used by visitors.
| Element | Description |
|---|---|
| Pie Segments | Each colored segment represents a different user agent configuration |
| Legend (Right side) | Lists each user agent with its percentage of total errors |
| Hover Tooltip | Shows exact count and percentage for each segment |
The chart uses 12 distinct colors cycling through:
- Blue, Green, Amber, Red, Violet, Pink, Teal, Orange, Indigo, Lime, Cyan, Rose
| Observation | What It Means | Action |
|---|---|---|
| One segment dominates (>50%) | Errors are concentrated in specific browser/device | Investigate compatibility issues for that platform |
| Even distribution | Errors affect all users equally | Likely a server-side or universal resource issue |
| Mobile browsers dominate | Mobile-specific problem | Check responsive design and mobile resource loading |
| Older browser versions dominate | Legacy browser compatibility | Consider polyfills or graceful degradation |
Scenario: Chrome/Android = 45%, Safari/iOS = 35%, Firefox = 15%, Others = 5%
Interpretation: Mobile browsers (Chrome Android + Safari iOS = 80%) are experiencing most errors. This suggests a mobile-specific issue, possibly with resource paths or mobile-optimized assets.
Located at the bottom of the Error Analysis dashboard, this panel provides a comprehensive list of all resources (files) that failed to load.
Shows the title "Missing Resources (sorted by frequency)" indicating that the most problematic resources appear first.
The Status Code filter ("+ Add Status...") and Active Status Filters chips let you filter the missing-resources list by HTTP status (e.g. 404, 500).
Filter the list by resource type using checkboxes:
| Filter | File Types Included | When to Use |
|---|---|---|
| Image | PNG, JPG, JPEG, GIF, WebP, SVG, BMP, ICO, TIFF, AVIF | Finding broken images |
| JS | JS, MJS, CJS (labeled "JS" in the UI) | Finding script failures (critical for form function) |
| CSS | CSS | Finding stylesheet issues (affects appearance) |
| JSON | JSON | Finding data/configuration file issues |
| Others | All other file types | Fonts, videos, documents, etc. |
Each filter shows a count in parentheses: e.g., "Image (23)" means 23 image resources are missing.
A counter on the right shows: "X out of Y visible" indicating how many resources match your current filters.
Below the filters, a legend explains the color-coded severity. Note: Error Analysis uses High ≥ 40%, Medium 10–<40%, Low <10% of max frequency. The standalone Resources dashboard (when enabled) uses different thresholds: High ≥ 50%, Medium 20–<50%, Low <20%.
| Badge | Threshold (Error Analysis) | Meaning |
|---|---|---|
| 🔴 High | ≥ 40% of max frequency | Critical - Affects many page views |
| 🟡 Medium | ≥ 10% and < 40% of max | Important - Significant impact |
| ⚪ Low | < 10% of max | Minor - Limited impact |
| Column | What It Shows |
|---|---|
| Resource URL | Full file path that failed to load (monospace font for readability) |
| Rank | Position in the sorted list (#1 is most frequent) |
| Count | Number of page views affected by this missing resource |
| Percentage | Portion of total page views affected (e.g., "2.5%") |
| Background Color | Meaning |
|---|---|
| 🔴 Light Red | High frequency - Priority fix |
| 🟡 Light Yellow | Medium frequency - Should fix |
| White | Low frequency - Can defer |
When no resources are missing, you'll see:
✓ No missing resources detected! All resources loaded successfully.
This appears with a green background, indicating healthy status.
- Fix High (red) items first - They impact the most users
- Prioritize JavaScript/CSS over Images - Scripts affect functionality; images affect only appearance
- Check domain ownership - Your domain vs. third-party (you may not control third-party resources)
- Look for patterns - Multiple files from same path might indicate a folder/deployment issue
The Performance Dashboard helps you understand how quickly your form becomes visible and interactive for visitors.
Top filters: At the top of the tab, Device Type and Source dropdowns ("+ Add Device...", "+ Add Source...") let you narrow all data on the tab. Use Clear All to reset. Active choices appear as removable chips under the label Active Filters:.
Engagement Readiness Time (also called Form Visibility Time) measures the duration from when a user starts loading your page until your form block becomes visible on screen and ready for interaction. In the UI the main chart title may read "Form Block Load Time" — this is the same metric.
Think of it as: "How long do users wait before they can start filling out the form?"
Four key metrics: Total Views (with subtext "Views with form visibility time"), Fastest (Min), p50 (Median), and p75.
| Metric Card | What It Shows | How to Interpret |
|---|---|---|
| Total Views | Views with form visibility time | Context for load-time metrics |
| Fastest (Min) | The shortest load time recorded from any user | Best-case scenario; shows what's possible with fast connection/device |
| p50 (Median) | The middle value - 50% of users loaded faster, 50% slower | Your "typical" user experience - most important metric |
| p75 | 75% of users loaded faster than this time | Shows experience for slower users - important for inclusivity |
The p50 and p75 cards are interactive:
- Click p50 to view median values in the chart below
- Click p75 to view 75th percentile values in the chart below
- The active selection shows with a blue highlight
| Color | Time | Performance Rating |
|---|---|---|
| 🟢 Green | Under 1 second | Fast - Excellent |
| 🟡 Yellow/Amber | 1 to 2 seconds | Moderate - Acceptable |
| 🔴 Red | Over 2 seconds | Slow - Needs improvement |
| Percentile | Meaning | Why It Matters |
|---|---|---|
| p50 (Median) | Half your users load faster than this | Represents your "average" user; if this is good, most users are satisfied |
| p75 | Three-quarters of users load faster | Represents your slower users; ensures you're not leaving anyone behind |
Below the load-time stats, the Core Web Vitals section shows LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift), each with a subtext (e.g. "Largest Contentful Paint"). Values are classified (e.g. good / needs improvement / poor) by color to help you understand user experience quality.
An interactive line chart showing how form visibility times change throughout the day.
| Element | Description |
|---|---|
| X-Axis (Horizontal) | Time broken down by hour |
| Y-Axis (Vertical) | Load time in seconds (or milliseconds for fast loads) |
| Line | Shows either p50 or p75 values based on your selection above |
| Shaded Area | Filled area beneath the line |
Each point is colored based on performance:
| Point Color | Load Time | Performance Level |
|---|---|---|
| 🟢 Green | ≤ 1 second | Fast |
| 🟡 Yellow | 1-2 seconds | Moderate |
| 🟠 Orange | 2-3 seconds | Slow |
| 🔴 Red | > 3 seconds | Very Slow |
| Shading | Time Period |
|---|---|
| Light/White | Daytime hours (6 AM - 8 PM) |
| Gray/Darker | Nighttime hours (8 PM - 6 AM) |
Hover over any point to see:
- Selected percentile value (p50 or p75)
- Page Views count for that hour
- Minimum load time for that hour
- Click the p50 stat card above to view median times
- Click the p75 stat card above to view 75th percentile times
- The chart title updates to reflect your selection
| Pattern | Possible Cause | Action |
|---|---|---|
| Consistently high during business hours | Server overload from traffic | Scale resources or optimize caching |
| Spikes at specific times | Competing processes or deployments | Review server activity logs |
| Gradual increase over days | Growing payload or degrading infrastructure | Audit page weight and server health |
| Night times much faster than day | Traffic-dependent performance | Consider CDN or server upgrades |
A bar chart (histogram) showing the distribution of load times across all page views.
"Engagement Readiness Time (Form Visibility) Distribution"
The chart divides all recorded load times into five dynamic equal-width buckets derived from the min and max of the data (or custom thresholds when provided). The ranges are not fixed 0–10s, 10–20s, etc.; they depend on your data.
| Bar Position | Interpretation |
|---|---|
| Most bars on left side | Good! Most users experience fast loads |
| Bars evenly distributed | Mixed performance - some users fast, some slow |
| Most bars on right side | Concerning - many users experiencing slow loads |
| Tall single bar | Most users have similar experience (could be good or bad depending on position) |
Hover over any bar to see:
- Count of page views in that range
- Percentage of total views
- Exact time range
| Statistic | What It Shows |
|---|---|
| Total Views | Number of page loads measured |
| Min View Time | Fastest recorded load |
| Max View Time | Slowest recorded load |
| Mean (Average) | Arithmetic average of all load times |
| Median | Middle value (50% faster, 50% slower) |
| Relationship | Interpretation |
|---|---|
| Mean ≈ Median | Balanced distribution; no extreme outliers |
| Mean > Median | Some very slow loads are pulling average up; focus on outliers |
| Mean < Median | Some very fast loads exist; unusual pattern |
A section titled "By Source Over Time" with the description "Hourly trend per selected source(s)" shows a chart of form visibility time (p50 or p75) per hour for each selected traffic source. It uses the same Device Type and Source filters as the rest of the tab. The p50/p75 toggle in the summary cards above applies to this chart as well: click p50 or p75 to switch the percentile shown. Use this chart to compare load times across different referrers or campaign sources.
A detailed, sortable table showing how long individual resources take to load.
At the top of the table:
| Metric | What It Shows |
|---|---|
| Total Resources | Count of unique resource files tracked |
| Avg Load Time | Mean loading time across all resources |
| Slowest Resource (p95) | 95th percentile of slowest resource - worst-case scenario |
| Badge Color | Time Range | Classification |
|---|---|---|
| 🟢 Green (Fast) | < 250ms | Excellent |
| 🟡 Yellow (Moderate) | 250ms - 1s | Acceptable |
| 🔴 Red (Slow) | ≥ 1s | Needs optimization |
| Column | Description | Click to Sort |
|---|---|---|
| Resource URL | File path/address | Alphabetically |
| Min | Fastest recorded load for this resource | Fastest first/last |
| Median (p50) | Typical load time (50% faster than this) | By typical speed |
| p75 | 75% of loads are faster | By slower experience |
| p95 | 95% of loads are faster (near worst-case) | By worst-case |
| Mean | Average load time | By average speed |
| Count | How many times resource was loaded | By frequency |
Entire rows are highlighted based on mean loading time:
| Row Color | Meaning |
|---|---|
| 🟢 Light Green | Fast loading resource |
| 🟡 Light Yellow | Moderate loading resource |
| 🔴 Light Red | Slow loading resource |
Use the "Search resources..." search box to filter resources by URL. Useful for:
- Finding specific file types (e.g., search ".js")
- Finding resources from specific domains
- Locating a known problematic file
The table loads sorted by Mean, descending (slowest first) by default. Click any column header to sort:
- First click: Descending order (highest/slowest first)
- Second click: Ascending order (lowest/fastest first)
- Arrow indicator shows current sort direction
Focus on resources with:
- High count + slow time = Most user impact
- JavaScript/CSS = Critical for functionality
- Slow p95 but fast median = Occasional issues worth investigating
At the bottom of the Performance tab, the User Agent Distribution section has a Device Breakdown heading and a pie chart showing how page views (with form visibility time) are split by device type (e.g. Mobile: Android, Mobile: iOS, Desktop: Windows, Desktop: macOS). It respects the Device Type and Source filters. Use it to see which devices or browsers dominate your traffic and to spot device-specific performance patterns.
Engagement and Resources tabs are not yet enabled in the UI. When they are released:
- Engagement will show fill events (typing in fields) and click events, with summary stats and hourly charts.
- Resources will provide a standalone view of missing resources (similar to the Missing Resources panel in Error Analysis), with its own severity thresholds (50% / 20% for High / Medium).
This guide will be updated with full sections for those tabs when they are available.
| Term | Definition |
|---|---|
| Page View | A single instance of a user loading your form page |
| Error Rate | Percentage of page views that experienced one or more resource loading errors |
| Resource | Any file loaded by your webpage: images, scripts, stylesheets, fonts, data files, etc. |
| Missing Resource | A file that failed to load for a user (404 error, timeout, blocked, etc.) |
| p50 (Median) | The middle value when all measurements are sorted - 50% are faster, 50% are slower |
| p75 (75th Percentile) | 75% of measurements are faster than this value |
| p95 (95th Percentile) | 95% of measurements are faster; shows near-worst-case scenario |
| Mean (Average) | Sum of all values divided by the count of values |
| User Agent | Browser and device information (e.g., "Chrome 120 on Windows 11") |
| Engagement Readiness Time | Time until your form is visible and ready for user interaction |
| Fill Event | User typing/entering data into a form field |
| Click Event | User clicking on any form element |
| Optel (Operational Telemetry) | The product name and data source; operational telemetry for web forms (see AEM Live). |
| RUM (Real User Monitoring) | Collecting performance data from actual user visits, not simulated tests; the bundler API is the RUM data source. |
| CDN (Content Delivery Network) | Network of servers that deliver content to users from nearby locations |
| Facet | A dimension used to group and analyze data (e.g., by hour, by resource, by user agent) |
If you have questions about the dashboard or need assistance interpreting your data, please contact your account representative or support team.
Dashboard Version: 1.0