Quietening down logs if I m mapping out to a lot of job have

Question

Quietening down logs if I m mapping out to a lot of job have a lot of params etc it can be difficult to follow logs Is there a way I can set logging such that I only see something if it s broken If I `export PREFECT LOGGING LEVEL=INFO` I see ```python3 tmp shell task py 2022 04 19 21 09 30+0100 INFO prefect FlowRunner | Beginning Flow run for My Flow 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | Task MyShellTask Starting task run 2022 04 19 21 09 30+0100 INFO prefect MyShellTask | lsto echo 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | Task MyShellTask Finished task run for task with final state Success 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | Task problem Starting task run 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | FAIL signal raised FAIL Oh no 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | Task problem Finished task run for task with final state Failed 2022 04 19 21 09 30+0100 INFO prefect FlowRunner | Flow run FAILED some reference tasks failed ``` If I ```export PREFECT LOGGING LEVEL=ERROR``` I see nothing Ideally I d like to only see messages about broken stuff Ideas

Nate · Answer

< Philip MacMenamin> if you re raising a caught exception as a `FAIL` signal in this case then its going to be `INFO` level as you can see in your logs ``` 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | FAIL signal raised FAIL Oh no ``` any unexpected errors should show up as `ERROR` level logs is that helpful

Philip MacMenamin · Answer

so I expected that but if I set `export PREFECT LOGGING LEVEL=ERROR` I see nothing WF runs out reports nothing at all

Anna Geller · Answer

based on this log the info that a flow run failed is still an INFO level log so that s expected ``` 2022 04 19 21 09 30+0100 INFO prefect FlowRunner | Flow run FAILED some reference tasks failed ``` this is much easier to configure in Prefect 2 0 perhaps a good reason to run your flow on 2 0 already check out <https discourse prefect io t how do i suppress created task run logs 750 7|this example>

Philip MacMenamin · Answer

< Anna Geller> I m not sure I m getting this I raised a signal FAIL in the task and this elicited ``` 2022 04 19 21 09 30+0100 INFO prefect TaskRunner | FAIL signal raised FAIL Oh no ``` Is is not expected behaviour that raising a FAIL would show up on an error level log

Anna Geller · Answer

nope this only means that the task run ends with a failed state the task runner log remains INFO Can you explain what problem do you try to solve here

Philip MacMenamin · Answer

Default settings generate a very large amount of logs along the lines of ``` 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task log Finished task run for task with final state Success 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task update adoc Starting task run 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task update adoc Finished task run for task with final state Mapped 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task update adoc 0 Starting task run 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task update adoc 0 Finished task run for task with final state Success 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command Starting task run 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command Finished task run for task with final state Mapped 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command 0 Starting task run 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command 0 Finished task run for task with final state Success 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task log Starting task run ``` which gets to be crippling if you re mapping over a lot of stuff I don t want to be told about all of this I just want to know if anything broke and ideally some kind of clue about what broke

Philip MacMenamin · Answer

I m not going to paste in an actual large log but if I m mapping to a couple of hundred items it becomes huge I m mapping to one in the above I don t want to be told about every event and every Success I d like some way to turn that down to help me keep logs at a size that I don t have to use grep etc to search them

Philip MacMenamin · Answer

Aside I tested ```from prefect import flow task from logging import getLogger logger = getLogger my logger logger setLevel INFO task def my task Hello from the task flow def my flow Hello from the flow my task my flow ``` running with `PREFECT LOGGING LEVEL=WARNING PREFECT LOGGING EXTRA LOGGERS=my logger python3 flow2 py` gives me ```Traceback most recent call last File flow2 py line 1 in lt module gt from prefect import flow task ImportError cannot import name flow from prefect home macmenaminpe local lib python3 8 site packages prefect init py ```

Philip MacMenamin · Answer

writing as ```cat flow py from prefect import Flow task from logging import getLogger logger = getLogger my logger logger setLevel INFO task def my task Hello from the task with Flow My Flow as f Hello from the flow my task f run ``` works but gives me ```$ PREFECT LOGGING LEVEL=WARNING PREFECT LOGGING EXTRA LOGGERS=my logger python3 flow py 2022 04 20 15 50 10+0100 INFO prefect FlowRunner | Beginning Flow run for My Flow 2022 04 20 15 50 10+0100 INFO prefect TaskRunner | Task my task Starting task run 2022 04 20 15 50 10+0100 INFO prefect TaskRunner | Task my task Finished task run for task with final state Success 2022 04 20 15 50 10+0100 INFO prefect FlowRunner | Flow run SUCCESS all reference tasks succeeded``` Ie same as previous too much logging

Philip MacMenamin · Answer

In the above case I m not even seeing Hello from the flow

Philip MacMenamin · Answer

```$ prefect version 1 2 0```

Nate · Answer

with regard to <https prefect community slack com archives CL09KU1K7 p1650466164692589 thread ts=1650399135 403099 amp cid=CL09KU1K7|this message> about the failed import that s because your prefect version is 1 2 but you re using the `prefect gt =2 0` syntax and imports which aren t valid for `prefect==1 x x`

Philip MacMenamin · Answer

right I suspected that was some versioning thing Thanks Nate

Anna Geller · Answer

gt I just want to know if anything broke and ideally some kind of clue about what broke The best way of solving that problem would be through state handlers or failure notifications that you could configure through Automation <https www prefect io blog orchestrating elt with prefect dbt cloud and snowflake part 3 |This blog post> discusses both

Philip MacMenamin · Answer

< Anna Geller> this might be nice for a more final version I m just going through stuff coding and trying to work out bugs Is this automation going to work on a locally hosted prefect server

Philip MacMenamin · Answer

So basically there isn t really a way of quietening down the logs I m hearing correct

Anna Geller · Answer

there is always a way to quiet down the logs you could e g use a log filter <https prefect community slack com archives C014Z8DPDSR p1650365258707909 thread ts=1650363875 537909 amp cid=C014Z8DPDSR> but I m not sure if getting rid of logs is the right strategy Logs are extremely helpful in troubleshooting I think you need them A better approach is to configure some hooks for failure notifications Automations are Cloud only but you could add a state handler on Server

Philip MacMenamin · Answer

Logs are very helpful in trouble shooting but if I have thousands of lines of logs and 99 999 of them say Success and buried in there there s something that s not working I d have thought there d be a simple way to surface this

Philip MacMenamin · Answer

As in if I explicitly raise a FAIL why is this not in a diff category Why is that grouped in with the thousands of Successes At the end of the day I ll have full logging but as I m writing stuff it s useful to run flows and see if there s anything wrong quickly

Philip MacMenamin · Answer

I mean I guess I can pipe everything through grep too but it just seems weird

Anna Geller · Answer

actually can you try running the same with the backend I think the actual error in your tasks will be displayed as ERROR level only the Flow and Task Runner are displayed as INFO

Philip MacMenamin · Answer

I m not following what do you mean by running it with the backend

Philip MacMenamin · Answer

registering it and running it through the web GUI

Anna Geller · Answer

yup exactly