Skip to content

Commit 0929c5e

Browse files
author
James Eichelbaum
authored
revert logs
1 parent 0c709fa commit 0929c5e

2 files changed

Lines changed: 89 additions & 50 deletions

File tree

dagster/assets/logs/dagster-plus.yaml

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,13 @@
11
id: dagster-plus
2-
# See app_id in your integration's manifest.json file to learn more:
3-
# https://docs.datadoghq.com/developers/integrations/check_references/#manifest-file
42
metric_id: dagster-plus
5-
# If for some reason id must be different than app_id, add the app_id in this field instead.
6-
# If id and app_id already match, this field can be left blank.
73
backend_only: false
84
facets:
95
- description: ""
106
facetType: list
117
groups:
128
- others
13-
name: dagster.event_type
14-
path: dagster.event_type
9+
name: dagster-plus.event_type
10+
path: dagster-plus.event_type
1511
source: log
1612
type: string
1713
pipeline:
@@ -22,7 +18,7 @@ pipeline:
2218
query: source:dagster-plus
2319
processors:
2420
- type: date-remapper
25-
name: Use the timestamp on the event as the date of the event.
21+
name: Define `timestamp` as the official date of the log
2622
enabled: true
2723
sources:
2824
- timestamp
@@ -44,22 +40,22 @@ pipeline:
4440
defaultLookup: info
4541
type: lookup-processor
4642
- type: status-remapper
47-
name: Use status field as the status of the event
43+
name: Define `status` as the official status of the log
4844
enabled: true
4945
sources:
5046
- status
5147
- type: attribute-remapper
52-
name: Nest event_type to dagster.event_type
48+
name: Map `event_type` to `dagster-plus.event_type`
5349
enabled: true
5450
sources:
5551
- event_type
5652
sourceType: attribute
57-
target: dagster.event_type
53+
target: dagster-plus.event_type
5854
targetType: attribute
5955
preserveSource: false
6056
overrideOnConflict: false
6157
- type: service-remapper
62-
name: Service Remapper
58+
name: Define `service` as the official service of the log
6359
enabled: true
6460
sources:
6561
- service
Lines changed: 82 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,83 @@
1-
id: dagster-plus
1+
id: "dagster-plus"
22
tests:
3-
- sample: >-
4-
{
5-
"run_id": "a3bcb088-1640-40dc-9701-4b554c0b9cac",
6-
"timestamp": "1747684829.8596163",
7-
"event_type": "STEP_WORKER_STARTED",
8-
"job_name": "diamond_asset_job",
9-
"message": "Executing step \"diamond_final_asset\" in subprocess.",
10-
"deployment": "prod",
11-
"service": "dagster-plus"
12-
}
13-
result: null
14-
- sample: >-
15-
{
16-
"run_id": "ff550567-4f6f-4aa0-a7b1-548d97a99170",
17-
"timestamp": "1747684973.981837",
18-
"event_type": "STEP_FAILURE",
19-
"job_name": "__ASSET_JOB",
20-
"message": "Execution of step \"dbt_non_partitioned_models\" failed.",
21-
"deployment": "prod",
22-
"service": "dagster-plus"
23-
}
24-
result: null
25-
- sample: >-
26-
{
27-
"run_id": "a3bcb088-1640-40dc-9701-4b554c0b9cac",
28-
"timestamp": "1747684824.7399628",
29-
"event_type": "ENGINE_EVENT",
30-
"job_name": "diamond_asset_job",
31-
"message": "Starting run metrics thread with container_metrics_enabled=True and python_metrics_enabled=False",
32-
"deployment": "prod",
33-
"service": "dagster-plus"
34-
}
35-
result: null
36-
37-
# The `result` field should be left blank to start. Once you submit your log asset files with
38-
# your integration pull-request in a Datadog GitHub repository, Datadog's validations will
39-
# run your raw logs against your pipeline and return the result. If the result output in the
40-
# validation is accurate, take the output and add it to the `result` field in your test YAML file.
3+
-
4+
sample: |-
5+
{
6+
"run_id" : "a3bcb088-1640-40dc-9701-4b554c0b9cac",
7+
"event_type" : "STEP_WORKER_STARTED",
8+
"job_name" : "diamond_asset_job",
9+
"service" : "dagster-plus",
10+
"message" : "Executing step \"diamond_final_asset\" in subprocess.",
11+
"timestamp" : "1747684829.8596163",
12+
"deployment" : "prod"
13+
}
14+
result:
15+
custom:
16+
dagster-plus:
17+
event_type: "STEP_WORKER_STARTED"
18+
deployment: "prod"
19+
job_name: "diamond_asset_job"
20+
run_id: "a3bcb088-1640-40dc-9701-4b554c0b9cac"
21+
service: "dagster-plus"
22+
status: "info"
23+
timestamp: "1747684829.8596163"
24+
message: "Executing step \"diamond_final_asset\" in subprocess."
25+
service: "dagster-plus"
26+
status: "info"
27+
tags:
28+
- "source:LOGS_SOURCE"
29+
timestamp: 1
30+
-
31+
sample: |-
32+
{
33+
"run_id" : "ff550567-4f6f-4aa0-a7b1-548d97a99170",
34+
"event_type" : "STEP_FAILURE",
35+
"job_name" : "__ASSET_JOB",
36+
"service" : "dagster-plus",
37+
"message" : "Execution of step \"dbt_non_partitioned_models\" failed.",
38+
"timestamp" : "1747684973.981837",
39+
"deployment" : "prod"
40+
}
41+
result:
42+
custom:
43+
dagster-plus:
44+
event_type: "STEP_FAILURE"
45+
deployment: "prod"
46+
job_name: "__ASSET_JOB"
47+
run_id: "ff550567-4f6f-4aa0-a7b1-548d97a99170"
48+
service: "dagster-plus"
49+
status: "error"
50+
timestamp: "1747684973.981837"
51+
message: "Execution of step \"dbt_non_partitioned_models\" failed."
52+
service: "dagster-plus"
53+
status: "error"
54+
tags:
55+
- "source:LOGS_SOURCE"
56+
timestamp: 1
57+
-
58+
sample: |-
59+
{
60+
"run_id" : "a3bcb088-1640-40dc-9701-4b554c0b9cac",
61+
"event_type" : "ENGINE_EVENT",
62+
"job_name" : "diamond_asset_job",
63+
"service" : "dagster-plus",
64+
"message" : "Starting run metrics thread with container_metrics_enabled=True and python_metrics_enabled=False",
65+
"timestamp" : "1747684824.7399628",
66+
"deployment" : "prod"
67+
}
68+
result:
69+
custom:
70+
dagster-plus:
71+
event_type: "ENGINE_EVENT"
72+
deployment: "prod"
73+
job_name: "diamond_asset_job"
74+
run_id: "a3bcb088-1640-40dc-9701-4b554c0b9cac"
75+
service: "dagster-plus"
76+
status: "info"
77+
timestamp: "1747684824.7399628"
78+
message: "Starting run metrics thread with container_metrics_enabled=True and python_metrics_enabled=False"
79+
service: "dagster-plus"
80+
status: "info"
81+
tags:
82+
- "source:LOGS_SOURCE"
83+
timestamp: 1

0 commit comments

Comments
 (0)