Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
andrewkroh opened this issue Jul 15, 2024 · 2 comments · Fixed by #10765
Closed

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

andrewkroh opened this issue Jul 15, 2024 · 2 comments · Fixed by #10765
Assignees
@efd6
Labels
8.15 candidate enhancement New feature or request Integration:entityanalytics_entra_id Microsoft Entra ID Entity Analytics Integration:entityanalytics_okta Okta Entity Analytics Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]

Comments

@andrewkroh
Copy link
Member

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
@andrewkroh andrewkroh added enhancement New feature or request Integration:entityanalytics_entra_id Microsoft Entra ID Entity Analytics Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations] 8.15 candidate Integration:entityanalytics_okta Okta Entity Analytics labels Jul 15, 2024
@elasticmachine
Copy link

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

@efd6 efd6 self-assigned this Aug 12, 2024
@efd6 efd6 mentioned this issue Aug 12, 2024
Merged
4 tasks
@efd6
Copy link
Contributor

efd6 commented Aug 12, 2024 •
edited
Loading

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

This was referenced Aug 12, 2024
Merged
Merged
@mergify mergify bot mentioned this issue Aug 13, 2024
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@efd6 efd6

Labels
8.15 candidate enhancement New feature or request Integration:entityanalytics_entra_id Microsoft Entra ID Entity Analytics Integration:entityanalytics_okta Okta Entity Analytics Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

entityanalytics_entra_id: add support for request trace logging efd6/integrations
3 participants
@andrewkroh @elasticmachine @efd6