APAC SD Team
Category
Data Sources
Product Version
8.0
Log event when data source connection attempts exceeded
Idea Logged
Related to this item: Never mark a data source as unavailable when volatile is enabled.
When we have configured volatile sources (or not) and trying to connect to a data source.. it will eventually give up (based on data source / volatile settings). However once this happens, we don't know.
E.g. If had a retry x 5 over 10mins.. after 10mins the report will simply stop trying to connect and fail to run.
We can see this in the source logs, but how can we track this via the event table for remediation . E.g. Attempt 5 of 5 failed. Giving up.
Can we please have a way to track this via the DB?
I like this idea 
Have logged this feature request on your behalf Manish.
Please let me know if you needed anything in the interim.
Regards,David
Have logged this feature request on your behalf Manish.
Please let me know if you needed anything in the interim.
Regards,David
In this case, you can try to use odbc connection and check if it helps.
In this case, you can try to use odbc connection and check if it helps.
This would be handy. Recently had issue with broadcasts failing with code REPORT_RUN_ERROR, which seems to be related to DB connections. Only evidence I found was that the Event.EventData duration was inline with volatile sources timeout/retries config (timeout x retries -1 = duration).
If this is timeout is occurring during report broadcasts I want to know how often its happening during other usage as it may explain sporadic performance issues with reports.
This would be handy. Recently had issue with broadcasts failing with code REPORT_RUN_ERROR, which seems to be related to DB connections. Only evidence I found was that the Event.EventData duration was inline with volatile sources timeout/retries config (timeout x retries -1 = duration).
If this is timeout is occurring during report broadcasts I want to know how often its happening during other usage as it may explain sporadic performance issues with reports.
Hi Nick,
I hope all is well,
I appreciate your use case in this scenario, with this I will make sure our development team are aware of this. If you require this to be escalated further, please let me know. I can reach out to your CSM to discuss further.
Regards,
Mark
Hi Nick,
I hope all is well,
I appreciate your use case in this scenario, with this I will make sure our development team are aware of this. If you require this to be escalated further, please let me know. I can reach out to your CSM to discuss further.
Regards,
Mark
Replies have been locked on this page!