January 22, 20215 yr Author I just wanted to thank The Average Guy Network for discussing the UUD and their kind words on their latest live podcast (Home Gadget Geeks 476). You can watch that segment starting at 50:55 through 53:18 right below. Here is their website: https://theaverageguy.tv/ Looks like I might be joining the show right after I finish and release UUD 1.6, in the first week in February! If that happens, maybe we can get the UUD community to submit questions for the live stream and I can talk in more detail about anything you guys want to know. Edited January 22, 20215 yr by falconexe
January 22, 20215 yr 5 hours ago, hermy65 said: @GilbN which command am i supposed to be running? Didnt see it mentioned unless i missed something. The query from Falconexe post a couple of posts above this.
January 22, 20215 yr Author 4 minutes ago, GilbN said: The query from Falconexe post a couple of posts above this. New Query: SELECT DISTINCT("ID_SERIAL") FROM (SELECT * FROM "diskio" WHERE $timeFilter)
January 22, 20215 yr 8 hours ago, falconexe said: New Query: SELECT DISTINCT("ID_SERIAL") FROM (SELECT * FROM "diskio" WHERE $timeFilter) @falconexe @GilbN Well, maybe we found an issue? There is data under diskio but im not seeing any serials Edited January 22, 20215 yr by hermy65
January 22, 20215 yr 2 hours ago, hermy65 said: @falconexe @GilbN Well, maybe we found an issue? There is data under diskio but im not seeing any serials Run it using http://influxui.s3-website-us-east-1.amazonaws.com/
January 22, 20215 yr 3 hours ago, hermy65 said: @falconexe @GilbN Well, maybe we found an issue? There is data under diskio but im not seeing any serials use command SELECT DISTINCT "ID_SERIAL" FROM (SELECT * FROM "diskio" WHERE time >= now() - 10s)
January 22, 20215 yr 5 minutes ago, GilbN said: use command SELECT DISTINCT "ID_SERIAL" FROM (SELECT * FROM "diskio" WHERE time >= now() - 10s) @GilbN Would rather not expose my db to the internet but if i need to i can to use your link above. I did run the command via console and got the result below which makes me assume its not pulling serial data but that wouldnt explain why the drives arent visible in the top bar of the dashboard (i assume): Edited January 22, 20215 yr by hermy65
January 22, 20215 yr 28 minutes ago, hermy65 said: @GilbN Would rather not expose my db to the internet but if i need to i can to use your link above. I did run the command via console and got the result below which makes me assume its not pulling serial data but that wouldnt explain why the drives arent visible in the top bar of the dashboard (i assume): As I said, it works locally. Through the browser as your computer is on your LAN. So through the browser on the computer it has access. Edited January 22, 20215 yr by GilbN
January 22, 20215 yr 24 minutes ago, hermy65 said: @GilbN Would rather not expose my db to the internet but if i need to i can to use your link above. I did run the command via console and got the result below which makes me assume its not pulling serial data but that wouldnt explain why the drives arent visible in the top bar of the dashboard (i assume): Try SELECT DISTINCT "ID_SERIAL" FROM (SELECT * FROM "diskio" WHERE time >= now() - 1d) If that doesnt work, try SHOW TAG VALUES FROM "diskio" WITH KEY = "ID_SERIAL" If that doesn't work, your telegraf config is wrong. Edited January 22, 20215 yr by GilbN
January 22, 20215 yr 1 hour ago, GilbN said: Try SELECT DISTINCT "ID_SERIAL" FROM (SELECT * FROM "diskio" WHERE time >= now() - 1d) If that doesnt work, try SHOW TAG VALUES FROM "diskio" WITH KEY = "ID_SERIAL" If that doesn't work, your telegraf config is wrong. Interesting, never saw mention of it working locally. I ran all the commands you gave but never got a result from any of them. Here is what my telegraf config looks like in the [[inputs.diskio]] section # Read metrics about disk IO by device [[inputs.diskio]] ## By default, telegraf will gather stats for all devices including ## disk partitions. ## Setting devices will restrict the stats to the specified devices. # devices = ["sda", "sdb"] ## Uncomment the following line if you need disk serial numbers. # skip_serial_number = false # ## On systems which support it, device metadata can be added in the form of ## tags. ## Currently only Linux is supported via udev properties. You can view ## available properties for a device by running: ## 'udevadm info -q property -n /dev/sda' device_tags = ["ID_SERIAL"] # ## Using the same metadata source as device_tags, you can also customize the ## name of the device via templates. ## The 'name_templates' parameter is a list of templates to try and apply to ## the device. The template may contain variables in the form of '$PROPERTY' or ## '${PROPERTY}'. The first template which does not contain any variables not ## present for the device is used as the device name tag. ## The typical use case is for LVM volumes, to get the VG/LV name instead of ## the near-meaningless DM-0 name. # name_templates = ["$ID_FS_LABEL","$DM_VG_NAME/$DM_LV_NAME"]
January 22, 20215 yr Just now, hermy65 said: Interesting, never saw mention of it working locally. I ran all the commands you gave but never got a result from any of them. Here is what my telegraf config looks like in the [[inputs.diskio]] section # Read metrics about disk IO by device [[inputs.diskio]] ## By default, telegraf will gather stats for all devices including ## disk partitions. ## Setting devices will restrict the stats to the specified devices. # devices = ["sda", "sdb"] ## Uncomment the following line if you need disk serial numbers. # skip_serial_number = false # ## On systems which support it, device metadata can be added in the form of ## tags. ## Currently only Linux is supported via udev properties. You can view ## available properties for a device by running: ## 'udevadm info -q property -n /dev/sda' device_tags = ["ID_SERIAL"] # ## Using the same metadata source as device_tags, you can also customize the ## name of the device via templates. ## The 'name_templates' parameter is a list of templates to try and apply to ## the device. The template may contain variables in the form of '$PROPERTY' or ## '${PROPERTY}'. The first template which does not contain any variables not ## present for the device is used as the device name tag. ## The typical use case is for LVM volumes, to get the VG/LV name instead of ## the near-meaningless DM-0 name. # name_templates = ["$ID_FS_LABEL","$DM_VG_NAME/$DM_LV_NAME"] What do you have in the post arguments for telegraf?
January 22, 20215 yr 2 minutes ago, GilbN said: What do you have in the post arguments for telegraf? /bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf' Edited January 22, 20215 yr by hermy65
January 22, 20215 yr 24 minutes ago, hermy65 said: /bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf' Share your complete telegraf container config, paths and variables ect
January 22, 20215 yr 2 hours ago, GilbN said: Share your complete telegraf container config, paths and variables ect
January 22, 20215 yr Just now, GilbN said: And in the 'show more settings'? Nothing under Show More Settings
January 22, 20215 yr 1 minute ago, hermy65 said: Nothing under Show More Settings Add this to your config.
January 22, 20215 yr Author 11 minutes ago, GilbN said: Add this to your config. This is found in the instructions on POST# 1. Edited January 22, 20215 yr by falconexe
January 22, 20215 yr 46 minutes ago, GilbN said: Add this to your config. Boom - good to go now. Did i miss something that said that needed to be there? Appreciate the help
January 22, 20215 yr 2 minutes ago, hermy65 said: Boom - good to go now. Did i miss something that said that needed to be there? Appreciate the help Yeah you missed the instructions
January 22, 20215 yr Just now, GilbN said: Yeah you missed the instructions dammit...i read those like 11 times before i made any posts because i didnt want to be that guy. My apologies
January 22, 20215 yr Author 3 minutes ago, GilbN said: Yeah you missed the instructions @hermy65 Look up 4 posts LOL. No worries man!😉 Edited January 22, 20215 yr by falconexe
January 24, 20215 yr I'm sure I've simply screwed something up in the config file - can't seem to figure it out: E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: plugin inputs.cpu: line 2324: configuration specified the fields [\"attributes\"], but they weren't used\n There is no "attributes" field there - I put one in with no difference - help?
January 25, 20215 yr Author 1 hour ago, Lucky Jay said: I'm sure I've simply screwed something up in the config file - can't seem to figure it out: E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: plugin inputs.cpu: line 2324: configuration specified the fields [\"attributes\"], but they weren't used\n There is no "attributes" field there - I put one in with no difference - help? See page 21 for mine. Try that.
January 26, 20215 yr Author Hi everyone. Due to an unforeseen circumstances, I will need to postpose the UUD 1.6 release until late February. I'll be away from the forums until I get back from my trip. Sorry about the delay. The next release will be worth the wait.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.