You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which means the field google_workspace.drive.visibility has been automatically mapped and is correct.
4. Abandon the create detector flow
5. Edit the detection rule from step 2 above and change it to
We see that now we have google_workspace.drive-visibility under unmapped_field_aliases but the log index field google_workspace.drive.visibility is not present under the unmapped_index_fields array.
i'm also having the same issue with log index fields missing under unmapped_field_aliases and obsolete/non-used entries also under unmapped_field_aliases after misconfiguring some custom detection rules.
i'm lucky that im able to drop the datastream, but even after this the missing and obselete fields under unmapped_field_aliases from the Mappings view API still persist(!)
What is the bug?
Log index field not returned as part of the
unmapped_index_fields
array in the response for get mappings view API.How can one reproduce the bug?
Steps to reproduce the behavior:
gworkspace
:gworkspace
and log typegworkspace
. The response from the view mappings API iswhich means the field
google_workspace.drive.visibility
has been automatically mapped and is correct.4. Abandon the create detector flow
5. Edit the detection rule from step 2 above and change it to
We see that now we have
google_workspace.drive-visibility
underunmapped_field_aliases
but the log index fieldgoogle_workspace.drive.visibility
is not present under theunmapped_index_fields
array.The expected response is
What is your host/environment?
Do you have any screenshots?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: