surveilr_osquery_ms_node_uptime (table) Content

surveilr_osquery_ms_node_uptime (table) Schema


01JZ51EP3GV9MZ01C7ABR1A37Z	2025-07-02 12:17:54	demomini-ser5pro-01	10	11	48	8	906488
01JZ51EJ8GDCX2ACM53B37QN95	2025-07-02 11:10:05	prime.dcp.infra.nyc2.democorp.example	665	3	38	9	57469089
01JZ51EK33HAZCCC13HBGXVKD8	2025-07-02 12:18:10	DemoHW-Mini-R7-4800U-02	10	11	48	4	906484
01JZ51EHFPBK1DMNWQWXHB8K3Y	2025-07-02 12:17:16	demo-home.region1.demoorg.example	91	5	0	24	7880424
01JZ51EKWK72BRN2Q981QSBBF1	2025-07-02 12:17:38	demo-alpha101.democloud01.demoorg.example	23	7	56	42	2015802
01JZ51EGGZGS0APCXVN23YQ0BX	2025-07-02 11:08:32	ax161-production.demoorg.example	19	0	54	45	1644885

Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.

Error in query number 6:

Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:

            SELECT 'text' AS component,
                (SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
                                 ⬆️
                '(Page ' || $current_page || ' of ' || $total_pages || ') ' ||

Backtrace

sql parser error: Expected: ), found: $current_page at Line: 42, Column: 35

"console/content/table/surveilr_osquery_ms_node_uptime.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.

You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.