Skip to content

okta: fill okta.request.ip_chain.* as a flattened object#3326

Merged
efd6 merged 2 commits intoelastic:mainfrom
efd6:3292-okta
May 16, 2022
Merged

okta: fill okta.request.ip_chain.* as a flattened object#3326
efd6 merged 2 commits intoelastic:mainfrom
efd6:3292-okta

Conversation

@efd6
Copy link
Contributor

@efd6 efd6 commented May 11, 2022

What does this PR do?

This change fills the already mapped okta.request.ip-chain array, but redefines the mapping as a flattened object array.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

  • The names that are used here match the names that existed in the fields file, but could be changed to better match the ECS without any possibility of breaking users since these fields were not previously filled. Thought about whether this change should be made and whether it constitutes a breaking change welcomed.

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 requested a review from a team as a code owner May 11, 2022 10:21
@efd6 efd6 self-assigned this May 11, 2022
@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@efd6 efd6 added bug Something isn't working, use only for issues and removed enhancement New feature or request labels May 11, 2022
@elasticmachine
Copy link

elasticmachine commented May 11, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-05-12T07:54:52.603+0000

  • Duration: 16 min 34 sec

Test stats 🧪

Test Results
Failed 0
Passed 12
Skipped 0
Total 12

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented May 11, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (1/1) 💚 3.597
Classes 100.0% (1/1) 💚 3.597
Methods 100.0% (15/15) 💚 11.753
Lines 84.704% (443/523) 👎 -4.409
Conditionals 100.0% (0/0) 💚

Comment on lines +341 to +342
field: _ingest._value.geographicalContext
target_field: _ingest._value.geographical_context
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are renaming fields breaking changes ? Could it break custom dashboards / searches ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be if the data had got into documents previously, but because of the old parsing these have not previously been available.

@efd6 efd6 merged commit 188b5fb into elastic:main May 16, 2022
efd6 added a commit to efd6/beats that referenced this pull request Feb 21, 2023
efd6 added a commit to elastic/beats that referenced this pull request Feb 22, 2023
mergify bot pushed a commit to elastic/beats that referenced this pull request Feb 23, 2023
…ned object (#34621)

Added to reflect addition in okta integration: elastic/integrations#3326

(cherry picked from commit 1f1868d)

# Conflicts:
#	x-pack/filebeat/module/okta/fields.go
#	x-pack/filebeat/module/okta/system/test/okta-system-test.json.log-expected.json
efd6 added a commit to elastic/beats that referenced this pull request Feb 23, 2023
….ip_chain.* as a flattened object (#34657)

* x-pack/filebeat/module/okta: fill okta.request.ip_chain.* as a flattened object (#34621)

Added to reflect addition in okta integration: elastic/integrations#3326

(cherry picked from commit 1f1868d)

# Conflicts:
#	x-pack/filebeat/module/okta/fields.go
#	x-pack/filebeat/module/okta/system/test/okta-system-test.json.log-expected.json

* resolve conflicts

---------

Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
chrisberkhout pushed a commit to elastic/beats that referenced this pull request Jun 1, 2023
@efd6 efd6 deleted the 3292-okta branch February 5, 2025 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working, use only for issues Integration:okta Okta

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Okta] Exported fields not being parsed

4 participants