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
Currently we have no way to ship ad-hoc command to the log aggregator
/api/v2/ad_hoc_commands/
When a user executes an ad-hoc command, a single activity_stream event is sent representing the creation of the command but no other information is. None of the 'ad_hoc command events' available in the Tower API are sent.
SUMMARY
The text was updated successfully, but these errors were encountered:
I have confirmed that when setting up external logging (I used loggly), and sending job_events, that ad_hoc commands end up showing up in external logger.
ISSUE TYPE
Currently we have no way to ship ad-hoc command to the log aggregator
/api/v2/ad_hoc_commands/
When a user executes an ad-hoc command, a single activity_stream event is sent representing the creation of the command but no other information is. None of the 'ad_hoc command events' available in the Tower API are sent.
SUMMARY
The text was updated successfully, but these errors were encountered: