We have lots of releases that include remote unix script output. It would be very useful for us to be able to include this content in a search of the releases/archive.

Comments

  • To help us understand your needs better, could you describe the type of data you're looking for? Can it be categorized in any way and stored in dedicated columns?

    As an indirect alternative, you could explore exporting relevant log files that contain script execution details to tools like Elasticsearch or Splunk. These tools are specifically designed for efficient text searches. When exporting, be sure to include information that links the log entries to the script tasks you want to search. This approach provides search functionality outside our product but leverages the strengths of established tools.

  • We have Splunk for logs. Maybe if the script execution logs were output to the filesystem. Maybe they're in the docker container somewhere, but we'd need them to be exposed as a volume.

    There would also need to be a way to correlate these outputs back to the release/task that they came from. Right now, the script outputs, contain just the script output with a date/time as the file name. At least link comment to the task would probably suffice.