Skip to content

[Filebeat] Okta module mapping issue for 'okta.target' #24354

@Trogdor-007

Description

@Trogdor-007

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).
okta_2
okta_1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions