New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Augment session events with cluster name #4994
Conversation
70809cb
to
e1eb68b
Compare
lib/events/events.proto
Outdated
@@ -61,6 +61,9 @@ message ServerMetadata { | |||
// session occurred on. | |||
map<string, string> ServerLabels = 5 | |||
[ (gogoproto.nullable) = false, (gogoproto.jsontag) = "server_labels,omitempty" ]; | |||
|
|||
// ClusterName identifies the originating teleport cluster | |||
string ClusterName = 6 [ (gogoproto.jsontag) = "cluster_name" ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be in just Metadata
?
aren't all events cluster-specific?
lib/srv/exec.go
Outdated
@@ -60,6 +60,8 @@ type ExecResult struct { | |||
|
|||
// Exec executes an "exec" request. | |||
type Exec interface { | |||
fmt.Stringer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to add it in the interface
as long as remoteExec
implements fmt.Stringer
, printing it with %v
should pick it up
e1eb68b
to
fe7f582
Compare
We've a customer that's current aggregating all logs into Splunk for SIEM usage. Would we be able to backport this into 5.1 |
@benarent Sure I can submit a backport. |
Fix local etcd backend tests (backport of #4986).
This PR augments session events with a cluster name.
Fixes #3751.