You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be the case that logs from the system under test are available in some external system, e.g.: splunk/datadog/aws/etc. It'd be nice if an execution report could offer a link to the related system logs for a given test.
This would have to be a customisable behaviour plugged into the Flocessor. We've just need an API to allow a flow's report data to be edited before it get written to storage. The behaviour would need access to message data (there might be a logging correlation token in a message header or something).
The behaviour could then insert a link to the logs into the flow motivation text.
The text was updated successfully, but these errors were encountered:
It might be the case that logs from the system under test are available in some external system, e.g.: splunk/datadog/aws/etc. It'd be nice if an execution report could offer a link to the related system logs for a given test.
This would have to be a customisable behaviour plugged into the
Flocessor
. We've just need an API to allow a flow's report data to be edited before it get written to storage. The behaviour would need access to message data (there might be a logging correlation token in a message header or something).The behaviour could then insert a link to the logs into the flow motivation text.
The text was updated successfully, but these errors were encountered: