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

Make breaking changes that require a major version update (2.0) #9478

Closed
13 of 75 tasks
sjwang90 opened this issue Jul 7, 2021 · 13 comments
Closed
13 of 75 tasks

Make breaking changes that require a major version update (2.0) #9478

sjwang90 opened this issue Jul 7, 2021 · 13 comments
Assignees
Labels
area/agent breaking change Improvement to Telegraf that requires changes to the plugin or agent; for minor/major releases pm/core capability Feature requests that impact and improve core Telegraf rfc Request for comment - larger issues that require clarification

Comments

@sjwang90
Copy link
Contributor

sjwang90 commented Jul 7, 2021

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

Partially resolved in: #9609

Refactor plugins

Input plugin settings

  • Activemq server and port
  • Aerospike enable_ssl
  • Amqp_consumer url
  • Consul datacentre
  • Disk mountpoints
  • Docker container_names
  • Docker perdevice
  • Docker total
  • Filecount directory
  • Http_listener_v2 path
  • Http_response address
  • Httpjson name
  • Influxdb_listener max_line_size
  • Mongodb ssl_enabled and cacerts
  • MQTT Consumer metric_buffer
  • MQTT Consumer servers format without scheme
  • NATS Consumer metric_buffer
  • Nsq name
  • Nsq_consumer server
  • Openldap ssl and ssl_ca
  • PostgreSQL address default value "local" instead of "localhost" #4872
  • Rabbitmq name
  • Rabbitmq queues
  • Smart path
  • Sqlserver query_version and azuredb
  • Statsd convert_names
  • Statsd parse_data_dog_tags
  • Statsd udp_packet_size
  • Vsphere force_discover_on_init
  • Win_perfcounters PreVistaSupport
  • Zookeeper enable_ssl

Output plugin settings

Resolved in: #11748

  • AMQP database and retention_policy
  • AMQP precision
  • AMQP url
  • Influxdb precision
  • Influxdb url
  • Kinesis partitionkey and use_random_partitionkey
  • Librato source_tag
  • Wavefront string_to_number subtable

Processor plugin settings

Serializers

Common settings

  • flush_buffer_when_full
  • utc
  • Kafka enable_tls
  • TLS ssl_ca, ssl_cert and ssl_key

Metric formats

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.

@telegraf-tiger telegraf-tiger bot added the area/execd Issues related to execd or plugins that would be better suited to be used through execd label Jul 7, 2021
@sjwang90 sjwang90 added pm/core capability Feature requests that impact and improve core Telegraf and removed area/execd Issues related to execd or plugins that would be better suited to be used through execd labels Jul 7, 2021
@sjwang90 sjwang90 added this to the 2.0.0 milestone Jul 7, 2021
@sjwang90 sjwang90 added area/agent breaking change Improvement to Telegraf that requires changes to the plugin or agent; for minor/major releases labels Jul 21, 2021
@sspaink
Copy link
Contributor

sspaink commented Aug 2, 2021

Looks like inputs.udp_listener has a flaky test, so will be nice to get that removed.
Example of failed test: https://app.circleci.com/pipelines/github/influxdata/telegraf/5841/workflows/83257327-ac12-47a2-961a-035a253a096c/jobs/104391/parallel-runs/0/steps/0-110

We should figure out when we can start removing these plugins.

@reimda reimda changed the title Remove deprecated plugins Make breaking changes that require a major version update (2.0) Aug 10, 2021
@Hipska
Copy link
Contributor

Hipska commented Oct 11, 2021

Can I nominate plugins to be deprecated as well?

  • inputs.leofs -> inputs.snmp
    Since this one is running the snmpwalk command and then parsing its output.

@Hipska
Copy link
Contributor

Hipska commented Oct 12, 2021

I'm not sure if the deprecation of inputs.snmp.name is a good thing, since the given alternative gives undesired results.

Name string // deprecated in 1.14; use name_override

@MyaLongmire
Copy link
Contributor

deprecate inputs.mysql metric version 1 as it is recommended for user to use metric version 2

@Hipska
Copy link
Contributor

Hipska commented Feb 11, 2022

@sjwang90 I believe this should be also the case for the influx inputs, no?

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.

@Hipska Hipska self-assigned this Feb 18, 2022
@Hipska Hipska added the rfc Request for comment - larger issues that require clarification label Feb 28, 2022
@sjwang90
Copy link
Contributor Author

sjwang90 commented Mar 1, 2022

Thanks @Hipska - I updated the list. Feel free to make any changes that you see

@Hipska
Copy link
Contributor

Hipska commented Sep 6, 2022

@sspaink You ticked off all deprecated plugins as being removed by #9609, but that isn't correct. The first one I checked isn't removed by that PR. Can you revisit that PR or the checkboxes in that list so there is none forgotten?

@Hipska
Copy link
Contributor

Hipska commented Sep 23, 2022

@sspaink?

Edit: Nevermind, I updated the list.

@sspaink sspaink self-assigned this Sep 28, 2022
@sspaink sspaink removed their assignment Nov 17, 2022
@srebhan
Copy link
Member

srebhan commented Jan 26, 2023

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.

@srebhan srebhan self-assigned this Jan 26, 2023
@powersj powersj removed this from the 2.0.0 milestone Feb 2, 2023
@redbaron
Copy link
Contributor

redbaron commented May 29, 2023

One thing which confuses me still is fieldpass/fielddrop. Rest of "*pass/*drop" parameters accept/reject measurement without modifying metric as a whole, so they trully filter which measurements go through. fieldpass/fielddrop on the other had modify measurement fields, they do not filter them even though they are listed all together as filters and named similarly.

fieldinclude/fieldexclude would be a better names for them given their behaviour.

@Hipska
Copy link
Contributor

Hipska commented May 29, 2023

@redbaron correct! See #12675. PR are appreciated!

@tguenneguez
Copy link
Contributor

The plugin procstat doesn't have the same result with different mode.
The native mode with "exec" shoud filter on /proc/(pid)/comm and not on /proc/(pid)/exe.

#6174 (comment)

@powersj
Copy link
Contributor

powersj commented Mar 20, 2024

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.

@powersj powersj closed this as completed Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/agent breaking change Improvement to Telegraf that requires changes to the plugin or agent; for minor/major releases pm/core capability Feature requests that impact and improve core Telegraf rfc Request for comment - larger issues that require clarification
Projects
None yet
Development

No branches or pull requests

8 participants