-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] Okta module mapping issue for 'okta.target' #24354
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Mar 4, 2021
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Mar 4, 2021
This could be as simple as changing the field type from |
Changing the mapping to
and returned
which was successful as there are 3 okta docs and only 2 matched which whats was expected. |
This was referenced Mar 18, 2021
6 tasks
andrewkroh
changed the title
Field not parsing correctly
[Filebeat] Okta module mapping issue for 'okta.target'
Oct 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parse the field "okta.target" with filebeat module
Right now, all other fields are parsed correctly. But for "okta.target" field, that still shows up as JSON and there are 4 sub-fields that you can't parse normally with mappings. Working with support to figure out how I can do this as-is but would be nice if that field was parsed out with filebeat module.
You should be able to see this with ANY okta log but I have attached 2 screenshots with field values obfuscated (they are all strings).
The text was updated successfully, but these errors were encountered: