A.1 Tables and Views
The following tables and views are used in Telemetry Streaming.
Oracle DBA Views
The following views are accessible to users having the Oracle DBA role.
Table -1 TELEMETRY_DBA.TELEMETRY_WORKSPACES
Columns | Data Type | Description |
---|---|---|
|
NUMBER |
Workspace ID |
|
VARCHAR2(128) |
Name of the workspace |
|
VARCHAR2(128) |
Default tablespace of the workspace |
|
DATE |
Time at which this workspace was created |
Table -2 TELEMETRY_DBA.TELEMETRY_ADMINS
Columns | Data Type | Description |
---|---|---|
|
NUMBER |
Workspace ID |
|
VARCHAR2(128) |
The database user who is assigned as an ADMIN to the workspace ID |
|
NUMBER |
User ID of the |
|
DATE |
Time at which the user was assigned as an admin user |
Admin User Views
The following views are accessible to users with the workspace administrator role.
Table -3 TELEMETRY_DBA.TELEMETRY_WORKSPACE_USERS
Column | Data Type | Description |
---|---|---|
|
NUMBER |
This is an automatically generated unique ID for every workspace created |
|
VARCHAR2(128) |
Name of the workspace given at the time of creation |
|
VARCHAR2(128) |
The database user name of the user associated with this workspace |
|
VARCHAR2(128) |
'INGEST', 'QUERY' or 'INGEST|QUERY' are the valid values |
Table -4 TM$<workspace
name>.TELEMETRY_INGEST_STATS
Column | Data Type | Description |
---|---|---|
|
NUMBER |
The size of the ingest payload in bytes |
|
NUMBER |
Number of metrics ingested |
|
NUMBER |
Number of metrics rejected |
|
VARCHAR2(128) |
Username of the ingest user |
|
NUMBER |
Time taken for ingest in ms |
INGEST_METHOD |
VARCHAR2(200) |
(PLSQL or REST) |
INGEST_TIMESTAMP |
TIMESTAMP(6) |
The time of ingestion |
Table -5 TM$<workspace
name>.TELEMETRY_INGEST_DISCARDS
Column | Data Type | Description |
---|---|---|
|
VARCHAR2(512) |
The metric name |
|
VARCHAR2(4000) |
The metric tags |
|
NUMBER |
The metric value |
|
NUMBER |
Time in epoch |
|
NUMBER |
Epoch of ingest payload receive |
DISCARD_REASON |
VARCHAR2(500) |
Why was the ingest discarded? |
DISCARD_TIMESTAMP |
TIMESTAMP(6) |
The time at which the ingest was discarded |
Table -6 TM$<workspace
name>.TELEMETRY_QUERY_STATS
Column | Data Type | Description |
---|---|---|
|
VARCHAR2(200) |
(Instant, Range, Label, or Series) |
|
NUMBER |
The query start time in epoch |
|
NUMBER |
The query end time in epoch |
|
NUMBER |
The Step Size for range queries |
|
VARCHAR2(128) |
The username of the query user |
QUERY_DURATION_MILLISECONDS |
NUMBER |
The time taken for the ingest in ms |
QUERY_METHOD |
VARCHAR2(200) |
(PLSQL or REST) |
QUERY_TIMESTAMP |
TIMESTAMP(6) |
The time of the query |
Table -7 TM$<workspace
name>.TELEMETRY_ADMIN_LOG
Column | Data Type | Description |
---|---|---|
|
VARCHAR2(4000) |
Message Text |
|
TIMESTAMP(6) |
Th timestamp of the message |
Note:
Query stats are gathered and inserted into stats table through an autonomous transaction as a part of the query. As a result, there is a write operation into the database as a part of the query. This prevents PromQL queries to be executed from Read-only, standby databases.
Query User Views
The following views are accessible to users with the query user role.
Table -8 TM$<workspace
name>.TELEMETRY_METRICS
Column | Data Type | Description |
---|---|---|
|
VARCHAR2(512) |
The metric name part of the time series |
|
VARCHAR2(4000) |
The tags part of the time series in JSON format |
|
NUMBER |
The point-in-time value of the time series |
|
NUMBER |
The time in epoch |