Can you render html in dagster logs

Question

George Pearse · Answer

Open issue here <https github com dagster io dagster issues 3416>

George Pearse · Answer

All I was actually specifically after currently was url rendering which I see I can do with ``` op def emit metadata context df yield AssetMaterialization asset key= my dataset metadata= my text label hello dashboard url MetadataValue url <http mycoolsite com my dashboard> num rows 0 ``` Cheers for that

George Pearse · Answer

And possible that `MarkdownMetadataValue` will support everything else I d want

Zach · Answer

I d still like a better way for emitting formatted metadata to dagster logs without it being tied to an AssetMaterialization I recently started using `context instance report engine event `for this but it feels a bit dirty

George Pearse · Answer

I was thinking the same I thought this had been implemented but I m currently struggling to re find it

George Pearse · Answer

< Zach> how do you then feed in the metadata dict I want to adopt your hacky fix for the time being

Zach · Answer

let me know if you do find it that d be really nice

Zach · Answer

this is how I ve been doing it ```context instance report engine event message= Launched ECS Task pipeline run=context pipeline run engine event data=EngineEventData MetadataEntry cloudwatch url description= entry data=MetadataValue url task cloudwatch url MetadataEntry task arn description= entry data=MetadataValue text task task arn ```

George Pearse · Answer

This might be what we want

Zach · Answer

oh sweet thanks will try that out

George Pearse · Answer

Sorry doesn t seem to be what we re after ```Runs Assets Status Workspace Jobs and pipelines maintain cxr lake pipeline Legacy update dataset permissions research and development 47292e08 Failure Run of update dataset permissions d5ccb193 View tags and config Debug file Hide not started steps Re execute All 0 5s1 0s1 5s2 0s2 5s3 0s3 5s4 0s4 5s5 0s5 5s run update dataset permissions pipe Hide unselected steps Not executed 0 No steps are waiting to execute Executing 0 No steps are executing Errored 1 run update dataset permissions pipe 1 481s Succeeded 0 debug info warning error critical event Copy URL OP EVENT TYPE INFO TIMESTAMP run update datas rmissions pipe ENGINE EVENT Starting initialization of resources io manager pg handler 18 14 38 352 run update datas rmissions pipe ENGINE EVENT Finished initialization of resources io manager pg handler io manager PickledObjectFilesystemIOManager io manager init time 0 63ms pg handler PostgresHandler pg handler init time 0 12ms 18 14 38 366 run update datas rmissions pipe LOGS CAPTURED Started capturing logs for step run update dataset permissions pipe captured logs View stdout stderr 18 14 38 445 run update datas rmissions pipe STEP START Started execution of step run update dataset permissions pipe 18 14 38 465 run update datas rmissions pipe STEP FAILURE dagster core errors DagsterExecutionStepExecutionError Error occurred while executing op run update dataset permissions pipe The above exception was caused by the following exception KeyError test name Stack Trace File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan utils py line 47 in solid execution error boundary yield File opt dagster behold pipelines lib python3 7 site packages dagster utils init py line 398 in iterate with context next output = next iterator File opt dagster pipelines research and development update dataset permissions py line 67 in run update dataset permissions pipe test name File opt dagster behold pipelines lib python3 7 site packages dagster core execution context compute py line 355 in add output metadata metadata=metadata output name=output name mapping key=mapping key File opt dagster behold pipelines lib python3 7 site packages dagster core execution context system py line 546 in add output metadata output def = self solid def output def named output name File opt dagster behold pipelines lib python3 7 site packages dagster core definitions node definition py line 124 in output def named return self output dict name 18 14 39 946 View full message ENGINE EVENT Multiprocess executor parent process exiting after 4 83s pid 3612383 pid 3612383 18 14 40 527 RUN FAILURE Execution of run for update dataset permissions failed Steps failed run update dataset permissions pipe 18 14 40 552 ENGINE EVENT Process for run exited pid 3612383 18 14 40 591 Error dagster core errors DagsterExecutionStepExecutionError Error occurred while executing op run update dataset permissions pipe File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan execute plan py line 232 in dagster event sequence for step for step event in check generator step events File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan execute step py line 343 in core dagster event sequence for step step output error checked user event sequence step context user event sequence File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan execute step py line 69 in step output error checked user event sequence for user event in user event sequence File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan compute py line 169 in execute core compute for step output in yield compute results step context inputs compute fn File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan compute py line 146 in yield compute results user event generator File opt dagster behold pipelines lib python3 7 site packages dagster utils init py line 400 in iterate with context return File home dagster anaconda3 lib python3 7 contextlib py line 130 in exit self gen throw type value traceback File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan utils py line 78 in solid execution error boundary from e The above exception was caused by the following exception KeyError test name File opt dagster behold pipelines lib python3 7 site packages dagster core execution plan utils py line 47 in solid execution error boundary yield File opt dagster behold pipelines lib python3 7 site packages dagster utils init py line 398 in iterate with context next output = next iterator File opt dagster pipelines research and development update dataset permissions py line 67 in run update dataset permissions pipe test name File opt dagster behold pipelines lib python3 7 site packages dagster core execution context compute py line 355 in add output metadata metadata=metadata output name=output name mapping key=mapping key File opt dagster behold pipelines lib python3 7 site packages dagster core execution context system py line 546 in add output metadata output def = self solid def output def named output name File opt dagster behold pipelines lib python3 7 site packages dagster core definitions node definition py line 124 in output def named return self output dict name ```

George Pearse · Answer

Think you have to add the name of an existing asset to use it Or something like that

Zach · Answer

oh this might be specifically for adding metadata to an output so you d have to reference an output key dang

George Pearse · Answer

< Zach> is EngineEventData a custom class can t find a way to import it

Zach · Answer

it s in `dagster core events`