GuluStock and AutoServa · GuluStock and AutoServa: User Guide
The Data page in GuluStock shows the market data warehouse behind every scan, chart and backtest: which sources feed it, which Bursa Malaysia stocks and indices it holds, how complete each trading session is, and when it was last updated. It is used by clients who want to check that the numbers they read on the Analysis and Trades pages are traceable and up to date.
Four figures sit above the tabs, so they are always visible.
| Figure | What It Shows |
|---|---|
| Stocks | How many Bursa common stocks the warehouse holds (no ETFs or REITs) |
| Indices | How many Bursa indices it holds: the FBM KLCI, sector indices and portfolio indices |
| 1h Bars | How many one-hour price bars are stored, for how many stocks, and the date range they cover |
| DB Size | The total size of the warehouse in MB, and how many tables it spans |
| Tab | What It Shows |
|---|---|
| Coverage | What the warehouse holds, session by session (the default tab) |
| Sources | Each data feed, its vendor and what it supplies |
| Stocks | The stock universe broken down by Bursa listing board, with a count on the tab |
| Indices | Every Bursa index held, with its bar count and date range |
| Storage | The size of each part of the warehouse |
| Logs | When each kind of data was last written, updating live |
The Coverage tab is titled What The Server Holds, Session By Session. It is a grid: each column is one Bursa trading session, and each row is one stream of data.
The line beside the title shows the server clock in MYT, the last completed session, the size of the universe (how many stocks and indices), and how many sessions are shown, plus five planned future sessions.
Under it, a Status Brief paragraph sums up the grid in words: which sessions are done, which are still filling in, anything missing, and when today's data is due. It is written from the same boxes as the grid, so the two always agree.
| Row | What It Counts per Session |
|---|---|
| Stock Bars (1h) | How many stocks have one-hour price bars for that session, against the full universe |
| Server Pull Runs | How many successful data fetches ran for that session |
| Index Daily | How many indices have a daily close for that session, against all indices held |
| Gap Repairs | How many missing bars were backfilled for that session. Nothing To Repair is a good result here. |
At the right end of each data row, Next Pull gives the time window of the next scheduled update for that row and what it is, or shows running now while it runs. Hover the label to see every scheduled window for that row.
Below the data rows, a second group of rows shows whether each scheduled update step ran on each session. At the right end, Next Step shows the next step due and its time window.
| Step Row | What It Tracks |
|---|---|
| Midday Sync | The update during the lunch break on trading days |
| Post-Close Sync | The update after the market closes on trading days |
| Daily Bars Pull | The evening collection of daily price bars |
| Gap Repair Run | The overnight run that backfills any missing bars |
| State | Meaning |
|---|---|
| Complete | The session's data is in. Lighter to darker blue means 80% to 100% of the expected count. |
| Filling In | A recent session is still being completed. A session keeps filling for about three nights. |
| Partial | Older than three sessions and 40% to 80% complete |
| Thin | Under 40% complete |
| Missing | No data for that session |
| Not Pulled Yet (Today) | Today's data has not been collected yet |
| Planned | A future trading session |
| Nothing To Repair | No gaps needed backfilling for that session |
| Step Done | A pull step ran successfully |
| Degraded | A pull step ran but did not fully succeed |
| Failed | A pull step failed |
| Skipped | A pull step did not run for that session |
Hover any box for its exact count and percentage, for example the number of stocks with bars out of the expected total.
The Sources tab lists each feed the warehouse is built from, one row per feed.
| Column | What It Shows |
|---|---|
| # | Row number |
| Vendor | Who supplies the data, with a short note on how it is collected |
| Endpoint | The request type and the vendor address the data comes from |
| Description | What the feed supplies, such as the list of Bursa indices, daily index prices, stock details and listing boards, or live market data |
The FBM KLCI daily prices from these feeds are what the market regime is read from.
The Stocks tab breaks the stock universe down by Bursa listing board.
| Column | What It Shows |
|---|---|
| # | Row number |
| Market | The listing board, as recorded in the stock master list |
| Count | How many stocks are on that board |
| Share | That board's share of all stocks held, to one decimal place |
A Total row at the bottom adds up to 100%. Click a column header to sort.
The Indices tab lists every Bursa index the warehouse holds, including the FBM KLCI that drives the market regime.
| Column | What It Shows | Example |
|---|---|---|
| Code | The Bursa index code | 0200I is the FBM KLCI |
| Name | The full Bursa-published index name | FBM KLCI |
| Bars | How many daily price bars are stored for the index | |
| First | Date of the earliest stored bar | |
| Last | Date of the most recent stored bar |
The Storage tab shows how large each part of the warehouse is, with Table, Rows (the exact count of records) and Size (MB). The count on the tab is the number of tables. Use it to see how much history is held; it does not affect how you read any scan.
The Logs tab shows, for each kind of data, when it was last written to the server. The newest update is listed first.
| Column | What It Shows |
|---|---|
| Source | The kind of data: Stocks List, OHLCV 1-Hour, Indices List, OHLCV Index Daily, and Cron Ticks (TP/SL), which is the record of paper-trade stop and target checks |
| Rows | How many records are held |
| First | The oldest data point (a dash for lists that are not time series) |
| Latest | The newest data point |
| Last Server Update | When this data was last written to the server |
While the Logs tab is open and your browser window is visible, it refreshes every 10 seconds without reloading the page. A cell that changes flashes green briefly.
If a yellow banner says "These inventory numbers are stale", only the page's cached summary is late. The warehouse itself is fine. The summary strip, date ranges and the Indices and Storage tabs catch up the next time the summary is rebuilt.
If a banner says "The coverage grid could not be read", the grid failed to load for this visit. Reload the page later; if it keeps happening, tell the administrator.
Data for a session keeps filling for about three nights after it trades, so a recent session can show as Filling In, and today shows as Not Pulled Yet until its update runs.
No. The Data page is for reading only. Data collection and repair are handled by the GuluStock operator.
Bursa does not trade on weekends or exchange holidays, so there are no sessions for those days. An amber bar before a date marks a holiday closure.
It means that stream has no data for that session. The Gap Repair run backfills missing bars overnight where it can, and the Status Brief says when the next repair is due.
No. Complete data only means the inputs are in. A scan result is still research output, not advice, and every trading decision is yours.