This might be obvious to most but just used plugin inheritance to debug a target that was failing with production data on a specific stream. In 2 minutes I have a test going. 1.Change meltano config

- name: tap-name-debug
    inherit_from: tap-name
    select:
     - failingstream.*

2. run

meltano install

3. get my output to a file so I can replicate the issue locally and improve the target

meltano invoke tap-name-debug > debugoutput

@visch Did you know there's a

--select failingstream

property on

meltano elt

that can do that as well? 😄 You can also feed it into

meltano invoke

using

TAP_NAME__SELECT_FILTER='["failingstream"]'

Ahh even better! Thank you!

Sounds like an issue to clarify that is in order! @taylor Could be part of your Troubleshooting issue as well: https://gitlab.com/meltano/meltano/-/issues/2538

So much hidden goodness

Meltano has a large surface area and our documentation could use a lot of improvement, so don’t blame yourself for not knowing the hidden goodie bits 😅