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
I searched in the Concourse source code but could not find the origin.
I found that the logger used by Concourse, lager, has a feature called Session(), but as I understand it, is a false positive.
I found function func (b *build) LagerData() lager.Data in file atc/db/build.go and I was excited for a moment, but it does not add a "session" field.
I found something in the Concourse code related to a session with the database, but there also I could not find any place where the "session" field is added to lager.
I found that the SSH server implementation used by Concourse has the notion of a session hash, but here also I think it is a false positive.
I noticed that, given a build_id, the session string has the same prefix but the length is different over the various events logged.
I also noticed that the session field repeats itself after a few days, so to me it might encode somehow a network connection plus something else that makes it slightly more unique...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
the majority of
concourse web
logs have a"session"
field. For example:I searched in the Concourse source code but could not find the origin.
I found that the logger used by Concourse,
lager
, has a feature calledSession()
, but as I understand it, is a false positive.I found function
func (b *build) LagerData() lager.Data
in fileatc/db/build.go
and I was excited for a moment, but it does not add a"session"
field.I found something in the Concourse code related to a session with the database, but there also I could not find any place where the
"session"
field is added to lager.I found that the SSH server implementation used by Concourse has the notion of a session hash, but here also I think it is a false positive.
I noticed that, given a
build_id
, thesession
string has the same prefix but the length is different over the various events logged.I also noticed that the session field repeats itself after a few days, so to me it might encode somehow a network connection plus something else that makes it slightly more unique...
Any hints ? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions