The document provides information about InfluxDB 2.0 going to general availability (GA) and the migration path for existing users. It discusses that the next release will be the first release candidate with bug fixes and no new features. It also outlines reasons users may want to hold off upgrading, including continuous queries and authorization changes. The document asks existing users to help with testing the upcoming release candidate.

1. Community Office Hours
September 2020
Russ Savage - Director, Product
Management
Samantha Wang - Product Manager

2. © 2020 InfluxData. All rights reserved.2
InfluxDB 2.0 is
going GA!

3. © 2020 InfluxData. All rights reserved.3
The Road to GA
• The next release of InfluxDB OSS 2.0 will be the first release
candidate
• We will continue to address bugs/defects while limiting new
features
• We will have upgrade tooling for existing InfluxDB users
• InfluxDB Alpha/Beta users can migrate their resources and
data. Steps are documented. No tooling.
• Once we GA, maintenance releases will be monthly, feature
releases quarterly

4. © 2020 InfluxData. All rights reserved.4
Recent Major (breaking) Changes
• Underlying storage engine updated to be compatible with
existing InfluxDB 1.x format
– No conversion of time series data needed for the upgrade
• Default port has changed from 9999 to 8086
– You can use --http-bind-address :9999 to keep using the old
port
• Read/Delete/Drop InfluxQL support added to the API
– Existing integrations using InfluxQL will still work
• Flux is being upgraded to the latest version

5. © 2020 InfluxData. All rights reserved.5
Reasons you might want to hold off upgrading
• You are a heavy user of continuous queries
– They will need to be manually converted to Flux Tasks
• You have many users with detailed authorization and
permissions
– You will need to re-configure users and permissions when you
upgrade. Tooling to make that easier will come post-GA
• You are writing data into InfluxDB via some other format
(UDP, Graphite, etc.)
– You will need to leverage Telegraf in conjunction with InfluxDB to
get the same capability.
• You run on a non-Linux OS
• You use InfluxDB as a Prometheus Remote Endpoint

6. © 2020 InfluxData. All rights reserved.6
Migration path for existing alpha/beta users
• Existing users will need to reconfigure their 3rd party
integrations
• Existing users will need to export and import their InfluxDB
resources using the CLI
– influx export all -c influx_old | influx apply -c default
– Now would be a great time to checkout InfluxDB Templates and
Stacks!
• Existing users will need to migrate their data from the current
storage format to the new one
– Leverage the CLI to stream from one to another
• Full instructions available soon

7. © 2020 InfluxData. All rights reserved.7
We need your help!!!
• The first RC will be released in the coming weeks
• Please grab the latest bits and help shape the future of
InfluxDB
• Join us in our Community Slack channel (#influxdb-v2) or on
Github (influxdata/influxdb)
– Tag @russ (Slack) or @russorat (Github) and I’ll see it

8. © 2020 InfluxData. All rights reserved.8
IoT Monitoring w/
Telegraf

9. © 2020 InfluxData. All rights reserved.9
Industrial IoT (IIoT) Market

10. © 2020 InfluxData. All rights reserved.10
OPC UA Input Plugin
• Polls OPC UA metrics on a timed interval basis
• Not subscription based
[[inputs.opcua_client]]
name = "opcua"
endpoint = "opc.tcp://localhost/OPCUA/SimulationServer"
security_policy = "Basic256"
security_mode = "Sign"
nodes = [
{name="Random", namespace="3", identifier_type="i", identifier="1002", data_type="double", description="Prosys OPC UA Simulation Server"},
{name="Triangle", namespace="3", identifier_type="i", identifier="1006", data_type="double", description="Prosys OPC UA Simulation Server"},
]
opcua,host=MBP15-SWANG.local,name=Random,type=double Random=1.746295 1599604830000000000
opcua,host=MBP15-SWANG.local,name=Triangle,type=double Triangle=0 1599604830000000000
Sample Input:
Sample Output:

11. © 2020 InfluxData. All rights reserved.11
OPC UA Node Configuration
nodes = [
{name="Random", namespace="3", identifier_type="i", identifier="1002", data_type="double",
description="Prosys OPC UA Simulation Server"},
]

12. © 2020 InfluxData. All rights reserved.12

13. © 2020 InfluxData. All rights reserved.13
Community
Questions

14. © 2020 InfluxData. All rights reserved.14
I’m currently researching collecting streaming telemetry from
Cisco network devices and came across the Telegraf inputs.gnmi
input plugin. The way it appears to work is by Telegraf reaching
out to the switches themselves to collect the data, sort of like a
poller.
What is the suggested way to use the Telegraf input plugin
inputs.gnmi to achieve redundancy? With the data being sent in I
can simply put the Telegraf containers behind a load balancer,
but with data being collected the other way around by Telegraf
that doesn't work as multiple containers collecting duplicate data
and sending that data to the TSDB is not ideal. Suggestions?

15. © 2020 InfluxData. All rights reserved.15
Is there any control over JSON response format for the query
endpoint? I have values that are serialized as exponential
notation for some values (> ~1.0E21) and all digits for others
(greater than ~1.0E17 but less than 1.0E21). All values are just
32-bit floating point precision but serializing them using 20
digits with a bunch of trailing zeros (as InfluxDB does) causes
a deserialization problem.

16. © 2020 InfluxData. All rights reserved.16
I’d like to see is an example of a Prometheus
summary within a InfluxDB 2.0 dashboard
showing P50 and P95 quantiles using the Flux
prometheus.histogramQuantile() function.

17. © 2020 InfluxData. All rights reserved.17
Communication &
Engagement

18. © 2020 InfluxData. All rights reserved.18
Community Forum
This is our community forum, a place
for people & users to come to for
support, share ideas, and ask
questions.
community.influxdata.com

19. © 2020 InfluxData. All rights reserved.19
InfluxDB Slack
We have a Slack Workspace for our
community.
Influxers and community members
talk about all things InfluxDB (TICK
stack, 2.0, Cloud, meetups, etc).
It’s a great place for us to get to
know and work with our users.
influxdata.com/slack

20. © 2020 InfluxData. All rights reserved.20
InfluxDB Subreddit
This is least active channel but we’re
here for those who are on Reddit.
reddit.com/r/influxdb

21. © 2020 InfluxData. All rights reserved.21
Announcements &
Resources

22. © 2020 InfluxData. All rights reserved.22
Time Series Meetup
Time series meetups are events for
everyone who is passionate or
curious about time series data and
how it can be used.
influxdata.com/time-series-
meetup/virtual-2020/

23. © 2020 InfluxData. All rights reserved.23
Community Office Hours
We host a monthly live webinar
where users can ask a panel of
Influxers questions and talk in real
time. We record these and post
them on YouTube.
influxdata.com/community-
showcase/community-office-
hours-registration/

24. © 2020 InfluxData. All rights reserved.24
Community Showcase
A central hub for all things
community. We have upcoming
events, where Influxers are going to
be, webinars, featured articles from
the community, and links to all of our
community initiatives.
influxdata.com/community-
showcase

25. © 2020 InfluxData. All rights reserved.25
We look forward to bringing together our
community of developers to learn, interact and
share tips and use cases.
October 27 – 28, 2020
Hands-On Flux Training
www.influxdays.com/virtual-experience-2020/
November 10 – 11, 2020
Virtual Experience

26. Thank You