Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Off Topic
  4. Grafana/Flux: Timestamp in 2 Queries nicht identisch

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    9
    1
    84

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.4k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.3k

Grafana/Flux: Timestamp in 2 Queries nicht identisch

Scheduled Pinned Locked Moved Off Topic
2 Posts 1 Posters 238 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    ExMatador
    wrote on last edited by
    #1

    Ich habe 2 Flux-Queries (Energie & Kosten) in einem Grafana-Panel. Sieht so aus:
    cf874095-0f4f-46eb-8092-edff790edbc0-image.png
    Am 29.10. liegen beide Werte nicht nebeneinander, weil die DB-Timestamps nicht identisch sind (eine Tausendstel Sek unterschiedlich):
    5ffa0e87-d5d5-48b5-bc47-096ffedf2b85-image.png

    Wie kann ich in der Query die vergleichenden TS kürzen, damit sie identisch sind?

    FinalOutput = ["_field", "_time", "_value"]
    
    RawSeries = from(bucket: "iobroker")
        |> range(start: -14d)
        |> filter(fn: (r) => r._measurement == "0_userdata.0.Stromverbrauch.stromTagEnergie" and r._field == "value")
    
    NamedSeries = RawSeries
        |> map(fn: (r) => ({_value:r._value, _time:r._time, _field:"stromEnergie"}))
        |> keep(columns:FinalOutput)
        
    NamedSeries |> yield()
    

    Vielen Dank
    ExMatador

    Intel(R) Core(TM) i7 | 32GB | 1TB SSD
    Virtualization: wsl2 | Ubuntu 22.04 | Docker
    ESPeasy | ESP8266 | ESP32 | ESP32CAM
    Zigbee | Coral | Lupus XT2 | Ender 3 S1 Pro
    Frigate | Influx | Grafana | GPX-Tracking | usw.

    1 Reply Last reply
    0
    • E Offline
      E Offline
      ExMatador
      wrote on last edited by
      #2

      Hab es gefunden
      Werden die Sekunden & Millisek entfernt, stimmt es wieder.

      |> truncateTimeColumn(unit: 1m)
      

      ExMatador

      Intel(R) Core(TM) i7 | 32GB | 1TB SSD
      Virtualization: wsl2 | Ubuntu 22.04 | Docker
      ESPeasy | ESP8266 | ESP32 | ESP32CAM
      Zigbee | Coral | Lupus XT2 | Ender 3 S1 Pro
      Frigate | Influx | Grafana | GPX-Tracking | usw.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      Support us

      ioBroker
      Community Adapters
      Donate

      802

      Online

      32.5k

      Users

      81.7k

      Topics

      1.3m

      Posts
      Community
      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
      ioBroker Community 2014-2025
      logo
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Home
      • Recent
      • Tags
      • Unread 0
      • Categories
      • Unreplied
      • Popular
      • GitHub
      • Docu
      • Hilfe