RumataOverview
Chapter 1 of 10
Read your app’s activity, investigate issues, and explore detailed monitoring.
Before you start
- Access to the factory and the resources you want to inspect.
1. Open your application overview
- Open your factory workspace from Home.
- Switch to System Explorer and select Overview.
- Wait for the current sample to load. Read the application, database, and frontend status before interpreting the cards.
2. Understand At a glance
This is the everyday view of how your application is doing.
- Website traffic: requests made to the production website in the displayed period.
- Users / customers: a detected user or customer count when available.
- Automation runs: workflow executions in the displayed period.
- Automation reliability: successful versus failed executions.
- Business records: records stored by the application.
- Files stored: stored file size and storage areas.
3. Investigate anything that needs attention
- Read the status and review message below the cards.
- If an issue is listed, follow its available action to inspect the affected resource.
- Use Refresh when you need a new sample. Allow it to finish before comparing results.
- After resolving an issue, refresh and repeat the affected user task.
4. Explore detailed application insights
Want to understand more about how your application is performing? Rumata's Extended Overview gives you deeper insights into your website traffic, workflows, databases, and resource usage—all in one place.
Open the Extended Overview
- Go to System Explorer → Overview.
- Click Extend overview below the At a glance cards.
- Scroll through the available monitoring sections to explore your application's performance.
What can you monitor?
Frontend traffic
See how your live website is performing, including the number of requests, errors, average response times, and data transferred.
Workflow pulse
Understand how your automations are performing over time. Compare successful and failed executions, switch between Hourly and Daily views, and adjust the available time range.
Request origins
Explore where your application's requests are coming from using an interactive map and Top locations list. Select a country to inspect its activity, and use the map controls to zoom or reset the view.
Database performance
Review how your database is performing, including connections, cache efficiency, table scans, and other database health metrics.
Understand database performance metrics
Cache efficiency: How often requested data is served from memory instead of read from disk. Interpret it alongside workload and response times.
Dead rows: Older row versions left after updates or deletes. PostgreSQL normally reclaims them through vacuuming; a rising count alone does not establish a problem.
Scans: Sequential scans read through table rows; index scans use an index to find matching data. Sequential scans can be appropriate for small tables or queries that return many rows.
Connections: Database sessions currently in use. Compare connection activity with the displayed capacity and your application’s workload.
Workflow performance
Explore more detailed workflow statistics, including execution times, throughput, and response-time measurements such as median (p50) and tail latency (p95).
Understand workflow timing and throughput
Median (p50): Half of the measured requests finish at or below this time.
Tail latency (p95): 95% finish at or below this time; it helps you understand slower requests.
Throughput: The number of executions or requests processed over the displayed interval.
Execution time and response time describe different parts of a request. Compare matching time ranges and read the metric’s help text before drawing conclusions.
Database operations
Examine database activity and operational statistics to better understand how your application interacts with its data.
Interpret database activity counters
Reads, writes, scans, and row-operation counters describe database activity. Some counters accumulate since the statistics were reset, rather than covering the chart’s selected time range. Check whether a figure applies to this factory’s schema or the whole database. Compare samples over time; a large cumulative count by itself does not indicate a fault.
Capacity & recovery
Review available information about resource capacity and recovery to identify potential issues before they affect your application.
Understand capacity and recovery information
Compare current resource usage with the limits shown for your application. Recovery availability depends on your plan and the backup service’s verified archive. Read the available recovery window and timezone in Database → Operations before planning a recovery; a displayed recovery point does not mean a recovery has been performed.
File storage
Monitor your application's stored files and storage usage.
Understand the metrics
Some sections include advanced technical statistics, such as database cache efficiency, dead rows, or workflow latency.
Click the ? icon beside a metric to learn what it means and how to interpret it.
When you're finished, click Hide extended overview to return to the simpler dashboard.
5. Read statistics in context
Requests are not unique visitors or page views. A page can request multiple assets. Some database counters are cumulative since the statistics reset, some measures cover the whole database, and others cover this factory schema. Read the labels before comparing figures.