Ticket 13426 - capture stdout and stderr path
Summary: capture stdout and stderr path
Status: RESOLVED WONTFIX
Alias: None
Product: Slurm
Classification: Unclassified
Component: Database (show other tickets)
Version: 21.08.4
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Director of Support
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2022-02-14 14:54 MST by HMS Research Computing
Modified: 2022-04-08 13:23 MDT (History)
1 user (show)

See Also:
Site: Harvard Medical School
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description HMS Research Computing 2022-02-14 14:54:25 MST 
Hello SchedMD,

As far as I can see the stdout and stderr paths are not captured in the slurmdb / sacct database.


Is there any future plan to add those two fields there?


and if not, how much it would be to sponsor this enhancement?


We are aware the information can be captured with ElasticSearch, but we were hoping to retire Elasticsearch since right now it is only used to look for those two paths.


Thank you,
Raffaele
Comment 2 Jess 2022-02-17 22:45:24 MST 
Hi Raffaele,

Thank you for your ping on this

I'm working to get the DEV SOW details to you shortly


-Jess