https://linen.dev logo
Join Slack
Powered by
Hey guys, is there some way to avoid having the po...
# singer-taps
m
Hey guys, is there some way to avoid having the postgres tap print every record in the DB into the logs?
v
By default that doesn't happen already, so you'll need to share your meltano.yml here
m
Im doing a load from a postgres tap to a postgres target and the logs have every record being loaded
Does this help? (Sorry for the pic using slack on my phone)
v
From all of that I wouldn't expect anything to be "printed" every run. Maybe someone tweaked and added log's I'd run 
meltano install --clean
just to be safe and run it again. If it's still happening if you could copy your 
meltano.yml
file (full content) and post some example logs
m
I do a clean install every time I run it, I have a very basic logging.yaml file as well
IMG_20241125_100419.jpg
v
please go on your computer and paste the yaml in instead of these pictures
root level:debug is your issue
put info in there and you'll probably be good
m
The logs with the DB records are level info
v
They aren't, try it please!
m
It says in the logs 
"level": info
is that wrong?
Here is an example log:
Copy code
{ consumer: false, producer: true, string_id: tap-sage-db, cmd_type: elb, run_id: string-here, job_name: string, stdio: stdout, name: tap-sage-db, event: DATABASE_RECORD_HERE, level: info, timestamp: datetime }
e
Hi @Matthew Podolak. You probably want something like what's described in https://github.com/meltano/meltano/issues/8760.
🙌 1
m
I'll try that out, thank you 🙌
np 1
2 Views
Open in Slack
PreviousNext
Powered by