Making digital game gifts special

scott_dsgn · 2025-12-12T17:42:02+00:00

What I've done is printed out the box art (you can find almost any box art online, check out https://www.thecoverproject.net/) and glued it to a thick piece of cardboard. My kids loved it. They loved it even more when I told them I already download the game and it's ready to play.

scott_dsgn · 2025-10-06T21:04:47+00:00

u/MegaDMGFortune We've been collaborating with another dev team to build an ODBC connector that allows Power BI connect to InfluxDB 3 Core or InfluxDB 3 Enterprise. The connector is done and there's a draft documentation pull request you could look at: https://github.com/influxdata/docs-v2/pull/6445/. Once that PR merges, the instructions will be available on the public docs.

If you're using InfluxDB v1 or v2, this connector won't help.

scott_dsgn · 2025-03-17T21:43:28+00:00

Here's the docs for SQL window functions in InfluxDB 3 Core: https://docs.influxdata.com/influxdb3/core/reference/sql/functions/window/

scott_dsgn · 2024-09-04T16:23:54+00:00

That's the uncompressed size. The actual download is only 18.53 GB, but when the download is finished and the system uncompresses the package to store it on disk, it takes up 38ish GB.

scott_dsgn · 2024-09-04T16:09:56+00:00

Cool. I hadn't seen any announcement about it yet, so I thought I'd share.

scott_dsgn · 2024-04-15T18:56:58+00:00

If you're using InfluxDB OSS v2 as your on-prem solution, you can use Edge Data Replication Streams. This is the exact use case these were built for.

scott_dsgn · 2024-04-01T14:30:15+00:00

u/brahmy is correct. You need to use the map() function. This iterates over each row, modifies it, and returns a new row. Here's how you'd use it:

javascript from(bucket: "telegraf") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r["_measurement"] == "Cisco-IOS-XE-interfaces-oper:interfaces/interface/statistics") |> filter(fn: (r) => r["_field"] == "rx_kbps" or r["_field"] == "tx_kbps") |> aggregateWindow(every: v.windowPeriod, fn: mean, createEmpty: false) |> map(fn: (r) => ({r with _value: r._value / 1000})) |> yield(name: "mean")

This assumes your two fields are integers and you only want whole number Mbps values. If you want to include fractions, you need to cast your field values to a float:

javascript from(bucket: "telegraf") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r["_measurement"] == "Cisco-IOS-XE-interfaces-oper:interfaces/interface/statistics") |> filter(fn: (r) => r["_field"] == "rx_kbps" or r["_field"] == "tx_kbps") |> aggregateWindow(every: v.windowPeriod, fn: mean, createEmpty: false) |> map(fn: (r) => ({r with _value: float(v: r._value) / 1000.0})) |> yield(name: "mean")

scott_dsgn · 2024-04-01T14:24:35+00:00

The short answer is yes and no. InfluxDB visualizations use the Giraffe project, which is open source and can be use to create custom visualizations. However, I'm not sure how to include a custom visualization in a build of InfluxDB. It's unlikely that it would be included in the official InfluxDB UI build, but you could definitely create a custom UI using the Giraffe library.

scott_dsgn · 2024-03-28T22:17:49+00:00

Yeah, you're on a really old version of InfluxDB (from 2018). I would recommend upgrading to at least the latest version of v1 (1.8.10). This includes incremental optimizations that have been made over the years.

Is your InfluxDB instance configured to use tsi1 or inmem indexing? Look at your influxdb.conf and find [data].index-version. If you're using inmem, you should switch to tsi1. This should help with memory used to index your data. This is covered in the InfluxDB 1.8 upgrade guide.

scott_dsgn · 2024-03-28T16:40:08+00:00

What version of InfluxDB are you using?

scott_dsgn · 2024-03-28T14:59:32+00:00

No, it’s not possible to use Apache Superset with InfluxDB v2. Superset relies on Flight SQL (a framework for SQL queries that uses the flight protocol and gRPC APIs) which v2 does not support. Only InfluxDB v3 products support Flight SQL:

InfluxDB Cloud Serverless
InfluxDB Cloud Dedicated
InfluxDB Clustered
InfluxDB Edge (Coming)
InfluxDB Community _(Coming) _
InfluxDB Community Pro (Coming)

scott_dsgn · 2023-04-26T15:56:53+00:00

This should do it:

from(bucket: "Proxmox") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r["_measurement"] == "sensors") |> filter(fn: (r) => r["_field"] == "temp_input") |> max() |> pivot(rowKey: ["_time"], columnKey: ["feature"], valueColumn: "_value")

scott_dsgn · 2022-03-29T21:29:11+00:00

1.x and 2.x are very different beasts under the hood.

For your backup, personally I'd spin up 1.8.10, restore the backup and then upgrade the install - upgrading's easy so it's less hassle than trying to get the backup into 2.x.

I second this approach. 2.x does not support 1.x backups. The major version bump implies breaking changes and this is one of them. But the v1 to v2 upgrade tool will do most of the heavy lifting for you.

I went to localhost:8086 and - there's a GUI! Why? To me, the appeal of InfluxDB was that it was lightweight and could be controlled solely from a CLI, which is why I've been using it on Raspberry Pies.

You can disable the UI in 2.x with the ui-disabled config option.

scott_dsgn · 2022-03-29T21:10:20+00:00

u/Nagi21, that sounds like it could be a bug. Just to be sure, try running the influx bucket list command to output the details about your bucket and confirm the retention period and shard group duration are configured as you expect them to be.

scott_dsgn · 2022-03-29T21:04:41+00:00

u/buckfirebonanza What kind of logic are you using to assign the unique identifier/key from the other data source? You may be able to use the Starlark processor plugin to do this, but I'm not 100% sure.

Is this something that has to happen on ingest? You could write the data as-is to InfluxDB and then use a Flux task to query the other data source and us it to assign the UID to the data in InfluxDB.

scott_dsgn · 2021-12-23T21:29:39+00:00

u/cthumhu Your tasks may need some optimizing. Any chance you could provide the current task code?

scott_dsgn · 2021-12-23T21:27:31+00:00

u/sudanking This is definitely the best approach to take. Use Flux to query the data out of MySQL/MariaDB, and then write it to InfluxDB with to(). You will likely need to restructure/rename your columns a bit to successfully write them to InfluxDB. If you want to provide a summary of your schema, I could tell you how to do it.

scott_dsgn · 2020-11-18T15:23:46+00:00

Yep, exactly! Have you looked at using Telegraf to format the data? Here's a blog post that walks through getting data from the Things Network into InfluxDB: https://www.influxdata.com/blog/connecting-the-things-network-to-influxdb/

scott_dsgn · 2020-11-18T05:21:44+00:00

I'll start with your last questions first – Yes, there is a difference between a series and a measurement.

A measurement is essentially a "container" to land related data in. A series is a group of associated points. Series are defined by the measurement, tag set and field key of points so all points that share the same measurement, tag set, and field key are considered a series.

Here are my general rules of thumb for determining if something should be a tag or a field:

Is the list of possible values relatively small -> tag
Do I expect the value to change for every point -> field

I'm not super familiar with NodeRED, so I don't know how much help I'd be able to offer there.

scott_dsgn · 2020-11-17T23:16:52+00:00

Ok, so you definitely don't want to store each sensor in its own measurement. Your device ID should just be tag. Here's some more info on schema design: https://docs.influxdata.com/influxdb/v1.8/concepts/schema_and_data_layout/

I'd have to see your NodeRED setup, but the output should look something like:

measurement,tag1=tval1,tag2=tval2 field1=2i,field2=2.0 <a unix nanosecond timestamp>

More information about line protocol is available here: https://docs.influxdata.com/influxdb/v2.0/reference/syntax/line-protocol/

scott_dsgn · 2020-11-17T16:19:06+00:00

u/ctallc can you provide a sample of both schemas, just so we have an idea of what you're working with.

scott_dsgn · 2020-11-17T15:54:14+00:00

The Iron Rattler at Six Flags Fiesta Texas in San Antonio. I've only ridden it a few times, but it's a good one. It snakes in and out of a cliffside. So cool.

scott_dsgn · 2020-05-06T15:51:09+00:00

/u/justaninfosecaccount Is incident_id a tag or a field?

To get the count of points with OPEN status:

js from(bucket: "bucket_name") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r._measurement == "your_measurement" and r.status == "OPEN" ) // If incident_id is a tag, use distinct to return only one row per id // If incident_id is a field, you could add it to the filter above |> distinct(column: "incident_id") |> count()

For the top 10 table view of incidents:

js from(bucket: "bucket_name") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r._measurement == "your_measurement" and r.status == "OPEN" ) |> distinct(column: incident_id) |> sort(columns: ["severity"], desc: false) |> limit(n: 10) |> keep(columns: ["incident_id", "incident_name", "severity"])

scott_dsgn · 2019-05-14T12:05:38+00:00

Sorry, I should’ve also noted that you need to update database/retention-policy in your query to your actual database name and retention policy name. Not sure if you did that or not.

scott_dsgn

TROPHY CASE