-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Make breaking changes that require a major version update (2.0) #9478
Comments
Looks like We should figure out when we can start removing these plugins. |
Can I nominate plugins to be deprecated as well?
|
I'm not sure if the deprecation of telegraf/plugins/inputs/snmp/snmp.go Line 118 in 4321f8a
|
deprecate inputs.mysql metric version 1 as it is recommended for user to use metric version 2 |
@sjwang90 I believe this should be also the case for the influx inputs, no?
|
Thanks @Hipska - I updated the list. Feel free to make any changes that you see |
Edit: Nevermind, I updated the list. |
I removed all checkmarks as it is confusing given the fact that this is not yet done in master. Let's revisit this topic when we actually merge the PRs. |
One thing which confuses me still is
|
The plugin procstat doesn't have the same result with different mode. |
In v1.30.0 we finally removed some long-deprecated config options and plugins. We do not plan to remove anything else in the short-term. I am going to close this issue as we have no plans for a 2.x. We were keeping this open for a while to ensure we deprecated config options and plugins, but that is in a decent state at this point. |
Just because 2.0 isn’t required to be backward compatible doesn’t mean we can ignore usability for current users. When we remove something people use we should replace it with a clear error so people know a change has been made and they need to adapt.
The errors should recommend a migration path or actively allow users push an update to their config. For example, the udp_listener will be removed. If someone tries to use it there should be an error saying to migrate to socket_listener. It shouldn’t be a warning that the user can ignore, but instead be a fatal error that requires the user to adapt their config before continuing to use telegraf.
Deprecated
Entire Plugins
inputs.kafka_consumer_legacy is the only way to use kafka version <0.8. When remove legacy plugin, note that plugin only supports Kafka v0.8+
Partially resolved in: #9609
Refactor plugins
Input plugin settings
server
andport
enable_ssl
url
datacentre
mountpoints
container_names
perdevice
total
directory
path
address
name
max_line_size
ssl_enabled
andcacerts
metric_buffer
servers
format without schememetric_buffer
name
server
ssl
andssl_ca
address
default value "local" instead of "localhost" #4872name
queues
path
query_version
andazuredb
convert_names
parse_data_dog_tags
udp_packet_size
force_discover_on_init
PreVistaSupport
enable_ssl
Output plugin settings
Resolved in: #11748
database
andretention_policy
precision
url
precision
url
partitionkey
anduse_random_partitionkey
source_tag
string_to_number
subtableProcessor plugin settings
agent
default value #8011Serializers
Common settings
flush_buffer_when_full
utc
enable_tls
ssl_ca
,ssl_cert
andssl_key
Metric formats
uptime_format field
Prometheus input and prometheus_client outputmetric_version = 1
(May be more difficult than we think to remove)metric_version=1
server
result_type
andstring_found
terminated_reason
metric_version = 1
(only existed for backwards compatibility for those on < Telegraf 1.6)Internal APIs
Builds, Packaging
Support only one v1/v2 plugins
Remove version nomenclature from plugin
Note that the two InfluxDB output plugins will remain. They are named influxdb and influxdb_v2, but in this case the version doesn't refer to the plugin but the compatible version of influxdb.
The text was updated successfully, but these errors were encountered: