JSON Data Points¶
The following table shows the data points that are available to use when you create a web request action for a defined rule. These data points can be included in the JSON payload using the format:
Data points table¶
Note
Timestamps display in the UI as Mmm DD, YYYY hh:mm:ss AM/PM in the
user's browser timezone. All system timestamps adhere to the ISO 8601 format
YYYY-MM-DDTHH:mm:ss.sssZ. Observability assumes UTC when no timezone is specified.
| Namespace | Data point | Description | Format |
|---|---|---|---|
| company | ui_url | Domain of your Observability UI. | |
| component | id | The component base ID, inferred from the component key. | |
| component | key | The component key. | |
| component | name | The component name. | |
| event | id | Identifier in the database for an event. | |
| event | external_url | The URL in an external tool with more details about the event. | |
| event | log_level | Level, or severity, of the log message. Possible values: error, warning, info. | |
| event | message | Text string of a log message related to a component (optionally, a task). See Message Log event. | |
| event | metric_key | User-defined key identifying the metric. See Metric Log event. | |
| event | metric_value | Value of the metric. | |
| event | event_timestamp | When the event occurred in ISO format. | ISO 8601 |
| event | event_timestamp_formatted | When the event occurred, formatted for readability. | Month DD, YYYY at 10:10 AM (UTC) |
| event | received_timestamp | When the event was received in ISO format. | ISO 8601 |
| event | received_timestamp_formatted | When the event was received, formatted for readability | Month DD, YYYY at 10:10 AM (UTC) |
| pipeline | name | The batch pipeline name. | |
| project | id | The ID of the project. This string can be found in the URL after /project/. |
|
| project | name | The name of the project. | |
| run | id | The ID of the run, inferred from the run key and pipeline ID. | |
| run | key | The run key. | |
| run | status | The run status, as appears in the database. | |
| run | start_time | When the run started, in ISO format. | ISO 8601 |
| run | start_time_formatted | When the run started, formatted for readability. | Month DD, YYYY at 10:10 AM (UTC) |
| run | end_time | When the run ended, in ISO format. | ISO 8601 |
| run | end_time_formatted | When the run ended, formatted for readability. | Month DD, YYYY at 10:10 AM (UTC) |
| run_task | id | The ID of the pipeline run that an event is associated with, inferred from the task key and run ID. | |
| run_task | status | The run task status, as listed in the database. | |
| run_task | start_time | When the run task started, in ISO format. | ISO 8601 |
| run_task | start_time_formatted | When the run task started, formatted for readability. | Month DD, YYYY at 10:10 AM (UTC) |
| run_task | end_time | When the run task ended, in ISO format. | ISO 8601 |
| run_task | end_time_formatted | When the run task ended, formatted for clarity. | Month DD, YYYY at 10:10 AM (UTC) |
| task | id | The ID of a task, inferred from the key. | |
| task | key | The task key. | |
| task | name | The task name. |