Even before COVID-19 forced nearly everyone to grapple with virtual work, most organizations had mountains of content scattered across numerous teams and dozens, if not hundreds, of apps. But now new research shows the cost of poor employee experiences for organizations: productivity, confidence, and opportunity.

You may have seen the announcement that Splunk and McLaren Racing have expanded their partnership, which sees Splunk as an Official Global Partner of the McLaren Shadow Esports team and the Logitech McLaren G Challenge. As a budding Esports fan and data enthusiast, it’s really exciting to see these two worlds collaborate and accelerate the virtual racing experience.

So you’re using InfluxDB Cloud, and you’re writing millions of metrics to your account. Whether you’re building an IoT application on top of InfluxDB or monitoring your production environment with InfluxDB, your time series operations are finally running smoothly. You want to keep it that way. You might be a Free Plan Cloud user or a Usage-Based Plan user, but either way, you need visibility into your instance size to manage resources and costs.

In InfluxDB 1.x, we provided support for the Prometheus remote write API. The release of InfluxDB 2.0 does not provide support for the same API. However, with the release of Telegraf 1.19, Telegraf now includes a Prometheus remote write parser that can be used to ingest these metrics and output them to either InfluxDB 1.x or InfluxDB 2.0.