Solution to count and monitor log events in CTA

• Adopting OpenTelemetry can be a risk (vs the option of creating our own mechanism).
• In addition, we may not need all the complexity that it provides.
• Task 1: Select 1 or 2 use cases.
• Task 2: Check which infrastructure would need to be used.
• Task 3: Experiment and prototype on a separate branch. Have a POC.

Allow VO override for repack

• We will call the new column IS_REPACK_VO.

Review error messages for prepare abort

• We need to find ways to improve our error messages returned with query prepare.

Tasks:

• Add new fields to the file xattrs that help improving the "error_text" message in the query prepare command (For example "[123456789.00][cta-taped] trigger workflow - synchronous workflow failed"). Examples:
  • Timestamp
  • Message type
  • Message origin (cta-taped, cta-frontend, EOS, ...)
  • Etc...
• Check existing xattrs.
• Review default "error_text" messages filed by EOS. Check if they are adjusted to each specific scenario.
• Review mechanism that passes messages from CTA to EOS (&mgm.errmsg= field).

Unify permission configuration across different CTA tools

• Needs more investigation.