Ticket 13426

Summary:	capture stdout and stderr path
Product:	Slurm	Reporter:	HMS Research Computing <rc>
Component:	Database	Assignee:	Director of Support <support>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	4 - Minor Issue
Priority:	---	CC:	jess
Version:	21.08.4
Hardware:	Linux
OS:	Linux
See Also:	https://bugs.schedmd.com/show_bug.cgi?id=6886
Site:	Harvard Medical School	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	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:	---

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