Update experimental notices for 5.3 #3525
Conversation
tsg
force-pushed
the
remove_experimentals
branch
3 times, most recently
from
2843b10 to
dab0dcf
Compare
| @@ -44,7 +44,7 @@ func (c *Crawler) Start(r *registrar.Registrar, reloaderConfig *common.Config) e | |||
| } | |||
|
|
|||
| if reloaderConfig.Enabled() { | |||
| logp.Warn("EXPERIMENTAL feature dynamic configuration reloading is enabled.") | |||
| logp.Warn("BETA feature dynamic configuration reloading is enabled.") | |||
There was a problem hiding this comment.
Me and Steffen discovered kind of a bug in the filebea reloading last Friday which will need some refactoring / cleanup to resolved. I'm not sure if we get this in until the release as it could touch quite a few parts. Do we have a place to mention such issues / known bugs? Just thinking if we perhaps should keep it experimental but support would probably be similar ...
There was a problem hiding this comment.
I think it still fits the Beta description. We did have Known issues in the release notes in the past, for example: https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-5.0.0-alpha1.html#_known_issues
There was a problem hiding this comment.
I will open a PR to the changelog to add this as known issue in case we can't fix it today.
Configuration reloading -> beta[] Filebeat symlinks -> GA Filebeat harvester_limit -> GA Filebeat publish_async -> experimental & deprecated Using environment variables in the Configuration -> GA Metricbeat ceph -> beta[] Metricbeat couchbase -> beta[] Metricbeat docker -> beta[] Metricbeat haproxy -> GA Metricbeat kafka -> beta[] Metricbeat php_fpm -> beta[] Metricbeat prometheus -> beta[] This also cleans up the CHANGELOG.
tsg
force-pushed
the
remove_experimentals
branch
from
dab0dcf to
9154cb0
Compare
Changes: