surveilr_osquery_ms_node_interface_address (table) Content

surveilr_osquery_ms_node_interface_address (table) Schema

Start Row: 0
Rows per Page: 50
Total Rows: 4
Current Page: 1
Total Pages: 1


01JZ51EHFPBK1DMNWQWXHB8K3Y	2025-07-02 12:00:46	demo-home.region1.demoorg.example	10.13.0.7	0a:1d:04:29:8c:f2
01JZ51EK33HAZCCC13HBGXVKD8	2025-07-02 12:01:13	DemoHW-Mini-R7-4800U-02	192.168.2.36	a8:a1:59:57:b8:f9
01JZ51EP3GV9MZ01C7ABR1A37Z	2025-07-02 12:06:43	demomini-ser5pro-01	192.168.2.46	b0:41:6f:14:84:31
01JZ51EJ8GDCX2ACM53B37QN95		prime.dcp.infra.nyc2.democorp.example	10.13.0.6	96:a1:3c:f1:d4:bc

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_interface_address.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'.