Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[filebeat] Optional service and containerPorts
See original GitHub issueDescribe the feature:
By default, the current chart would remain as-is.
Optionally, if a user wants to expose arbitrary ports then the user could do this through a extraPorts features that defaults to an empty array.
Describe a specific use case for the feature:
Filebeat supports TCP/UDP/Syslog. https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html#filebeat-input-types
These are not usable by the chart because the ports can’t be exposed.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:18 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
could this issue be re-opened? It seems to be still valid…
This feature also makes sense when deploying metricbeat to collect filebeat stats. The http port is not enabled and metricbeat fails to connect to it. The alternative to collecting filebeat stats is to have metricbeat as a sidecar, which is cumbersome.