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.

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

Improve HTTPJSON implicit array split documentation #29810

Open
marc-gr opened this issue Jan 12, 2022 · 8 comments
Open

Improve HTTPJSON implicit array split documentation #29810

marc-gr opened this issue Jan 12, 2022 · 8 comments
Labels

Comments

@marc-gr
Copy link
Contributor

marc-gr commented Jan 12, 2022

HTTPJSON does an implicit split when an it gets and array response.

This might lead to confusion and needs to be properly documented.

@elasticmachine
Copy link
Collaborator

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

@marc-gr marc-gr changed the title Improve HTTPJSON documentation Improve HTTPJSON implicit array split documentation Jan 12, 2022
@Tigger2014
Copy link

Should it not also actually be possible to disable this behaviour as some things output as an array but need to be processed as a single event.

@marc-gr
Copy link
Contributor Author

marc-gr commented Jan 19, 2022

Should it not also actually be possible to disable this behaviour as some things output as an array but need to be processed as a single event.

That would be ideal as far as we can default to the current behavior to avoid introducing a breaking change

@botelastic
Copy link

botelastic bot commented Jan 19, 2023

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 19, 2023
@thopico
Copy link

thopico commented Jan 19, 2023

I find it still relevant, especially giving the ability to process the output as one single event.

@botelastic botelastic bot removed the Stalled label Jan 19, 2023
@botelastic
Copy link

botelastic bot commented Jan 19, 2024

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@elasticmachine
Copy link
Collaborator

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

@botelastic botelastic bot removed the Stalled label Jan 31, 2024
@botelastic
Copy link

botelastic bot commented Jan 30, 2025

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants