Hi Jonathan, thanks for writing in! We'll get this into our backlog. 

Could you describe in a bit more detail what you're solving for? Would having an account-wide external logging service handle what you're looking for, or is having an external service configured on a destination-by-destination basis the only ideal outcome? 

Thank you!

Jimmy

Hi Jimmy,

I am working with Jonathan on the same project and we desire to have this configurable per connector due to our connectors syncing data from various AWS regions. We want to use CloudWatch to filter on the "status" log event so we can determine when a connector has finished syncing successfully. This will result in a Lamda function being run, which puts a new message on an SQS queue with the connector's details. We are doing this so we can orchestrate the connection sync end with a follow-up Matillion transformation job.

Regards,

Colin

Hi,

I'd like to plus one this. Right now, nothing related to logging is accessible via the REST API, which makes it unusable for us.

Though as Jimmy mentions, being able to configure the external logging service on an account-wide basis would also solve our problem.

Jillian Kozyra Jonathan Kolar, I'm wondering if you've been able to play around with our log connector. It can be configured at the account level to deliver logs directly to your destination.

@... while the logs connector is helpful, being able to have all of our logs from different services aggregated in the logstream would be more valuable. This would enable us to easily leverage Google Cloud's Logs-based Metrics. Currently, Fivetran is the only one of our services that is missing, and it's quite a critical dependency for us.