Repository navigation
[ManyVarious]: Expose Http-json input settings to integrations that depend on it. #12182
Description
Integration Name
ForgeRock [forgerock]
Dataset Name
No response
Integration Version
1.20.0
Agent Version
8.15.3
OS Version and Architecture
Ubuntu 20.04
User Goal
This issue is opened under ForgeRock integration but can be extended to any integrations that depend on filebeat http-json input.
Settings like: https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-httpjson.html#_configuration_options_11 should be exposed somehow to the integration.
Sometimes, users (usually in enterprise networks) need to only fetch data from an API via proxy, but Fleet and Elastic do not need proxy. In these cases, usually, users rely on a stand alone Elastic Agent or pure Filebeat.
Exposing these settings will give the integrations a lot more config flexibility.
Existing Features
Users cannot pass input settings via agent configuration.
What did you see?
Users cannot pass input settings via agent configuration.
Anything else?
No response
Activity
elasticmachine commentedon Dec 23, 2024
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
botelastic commentedon Dec 23, 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
Staleto 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!