search

elastic / integrations

Elastic Integrations
https://www.elastic.co/integrations
Other
201 stars 433 forks source link

entityanalytics_{okta,entra_id} - Add request tracer config option for 8.15 #10498

Closed andrewkroh closed 1 month ago

andrewkroh commented 3 months ago

The entityanalytics input will have support for request tracing in 8.15.0. The entityanalytics Entra ID and Okta integrations need a configuration toggle to enable the tracing.

Related issues

elasticmachine commented 3 months ago

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

efd6 commented 2 months ago

I have a change for the okta integration but the entra_id integration panics when the request tracer is turned on. I'm investigating, but it looks like the fetcher is being passed a nil context and so the ctx.Done() call here is panicking.

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x55dd0cbd0d1e]
goroutine 238 [running]:
github.com/elastic/go-concert/ctxtool.(*cancelContext).Done(0x0?)
    <autogenerated>:1 +0x1e
github.com/elastic/beats/v7/x-pack/filebeat/input/entityanalytics/provider/azuread/fetcher/graph.requestTrace.func1()
    github.com/elastic/beats/v7/x-pack/filebeat/input/entityanalytics/provider/azuread/fetcher/graph/graph.go:448 +0x25
created by github.com/elastic/beats/v7/x-pack/filebeat/input/entityanalytics/provider/azuread/fetcher/graph.requestTrace in goroutine 170
    github.com/elastic/beats/v7/x-pack/filebeat/input/entityanalytics/provider/azuread/fetcher/graph/graph.go:446 +0x385