[Bug]: Cannot select a specific time for Stats Report

akama-aka commented 8 months ago

Bug description

Hello, every time I want to select a specific timeframe on the Netdata website, e.g. from [...] 19:40 to [...] 19:50 and then I try to save or click on something else, the "to" display goes straight back to the current time and date. And if I click directly on "Apply" then a timeframe from December 30 1996, 10:19 to December 30 1996, 10:20 is selected

Expected behavior

Das man den eingegebenen Timestamp speichert und dann auch angezeigt bekommt.

Steps to reproduce

1.Just normally download and setup Netdata on Device 2.Go to app.netdata.cloud/... 3.Click on Bar for changing the Timeframe and select a custom one

Installation method

kickstart.sh

System info

/etc/almalinux-release:AlmaLinux release 9.3 (Shamrock Pampas Cat)
/etc/os-release:NAME="AlmaLinux"
/etc/os-release:VERSION="9.3 (Shamrock Pampas Cat)"
/etc/os-release:ID="almalinux"
/etc/os-release:ID_LIKE="rhel centos fedora"
/etc/os-release:VERSION_ID="9.3"
/etc/os-release:PLATFORM_ID="platform:el9"
/etc/os-release:PRETTY_NAME="AlmaLinux 9.3 (Shamrock Pampas Cat)"
/etc/os-release:ANSI_COLOR="0;34"
/etc/os-release:LOGO="fedora-logo-icon"
/etc/os-release:CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
/etc/os-release:
/etc/os-release:ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
/etc/os-release:ALMALINUX_MANTISBT_PROJECT_VERSION="9.3"
/etc/os-release:REDHAT_SUPPORT_PRODUCT="AlmaLinux"
/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
/etc/redhat-release:AlmaLinux release 9.3 (Shamrock Pampas Cat)
/etc/system-release:AlmaLinux release 9.3 (Shamrock Pampas Cat)

Netdata build info

time=2023-12-29T20:18:46.440+01:00 comm=netdata source=daemon level=error errno="13, Permission denied" tid=1931462 thread=netdata msg="System info script /usr/libexec/netdata/plugins.d/system-info.sh not found."
Packaging:
    Netdata Version ____________________________________________ : v1.44.0-108-nightly
    Installation Type __________________________________________ : binpkg-rpm
    Package Architecture _______________________________________ : x86_64
    Package Distro _____________________________________________ :  
    Configure Options __________________________________________ : dummy-configure-command
Default Directories:
    User Configurations ________________________________________ : /etc/netdata
    Stock Configurations _______________________________________ : /usr/lib/netdata/conf.d
    Ephemeral Databases (metrics data, metadata) _______________ : /var/cache/netdata
    Permanent Databases ________________________________________ : /var/lib/netdata
    Plugins ____________________________________________________ : /usr/libexec/netdata/plugins.d
    Static Web Files ___________________________________________ : /usr/share/netdata/web
    Log Files __________________________________________________ : /var/log/netdata
    Lock Files _________________________________________________ : /var/lib/netdata/lock
    Home _______________________________________________________ : /var/lib/netdata
Operating System:
    Kernel _____________________________________________________ : 
    Kernel Version _____________________________________________ : 
    Operating System ___________________________________________ : 
    Operating System ID ________________________________________ : 
    Operating System ID Like ___________________________________ : 
    Operating System Version ___________________________________ : 
    Operating System Version ID ________________________________ : 
    Detection __________________________________________________ : 
Hardware:
    CPU Cores __________________________________________________ : 
    CPU Frequency ______________________________________________ : 
    RAM Bytes __________________________________________________ : 
    Disk Capacity ______________________________________________ : 
    CPU Architecture ___________________________________________ : 
    Virtualization Technology __________________________________ : 
    Virtualization Detection ___________________________________ : 
Container:
    Container __________________________________________________ : 
    Container Detection ________________________________________ : 
    Container Orchestrator _____________________________________ : none
    Container Operating System _________________________________ : 
    Container Operating System ID ______________________________ : 
    Container Operating System ID Like _________________________ : 
    Container Operating System Version _________________________ : 
    Container Operating System Version ID ______________________ : 
    Container Operating System Detection _______________________ : 
Features:
    Built For __________________________________________________ : Linux
    Netdata Cloud ______________________________________________ : YES
    Health (trigger alerts and send notifications) _____________ : YES
    Streaming (stream metrics to parent Netdata servers) _______ : YES
    Back-filling (of higher database tiers) ____________________ : YES
    Replication (fill the gaps of parent Netdata servers) ______ : YES
    Streaming and Replication Compression ______________________ : YES (zstd lz4 gzip)
    Contexts (index all active and archived metrics) ___________ : YES
    Tiering (multiple dbs with different metrics resolution) ___ : YES (5)
    Machine Learning ___________________________________________ : YES
Database Engines:
    dbengine ___________________________________________________ : YES
    alloc ______________________________________________________ : YES
    ram ________________________________________________________ : YES
    map ________________________________________________________ : YES
    save _______________________________________________________ : YES
    none _______________________________________________________ : YES
Connectivity Capabilities:
    ACLK (Agent-Cloud Link: MQTT over WebSockets over TLS) _____ : YES
    static (Netdata internal web server) _______________________ : YES
    h2o (web server) ___________________________________________ : YES
    WebRTC (experimental) ______________________________________ : NO
    Native HTTPS (TLS Support) _________________________________ : YES
    TLS Host Verification ______________________________________ : YES
Libraries:
    LZ4 (extremely fast lossless compression algorithm) ________ : YES
    ZSTD (fast, lossless compression algorithm) ________________ : YES
    zlib (lossless data-compression library) ___________________ : YES
    protobuf (platform-neutral data serialization protocol) ____ : YES (system)
    OpenSSL (cryptography) _____________________________________ : YES
    libdatachannel (stand-alone WebRTC data channels) __________ : NO
    JSON-C (lightweight JSON manipulation) _____________________ : YES
    libcap (Linux capabilities system operations) ______________ : NO
    libcrypto (cryptographic functions) ________________________ : YES
Plugins:
    apps (monitor processes) ___________________________________ : YES
    cgroups (monitor containers and VMs) _______________________ : YES
    cgroup-network (associate interfaces to CGROUPS) ___________ : YES
    proc (monitor Linux systems) _______________________________ : YES
    tc (monitor Linux network QoS) _____________________________ : YES
    diskspace (monitor Linux mount points) _____________________ : YES
    freebsd (monitor FreeBSD systems) __________________________ : NO
    macos (monitor MacOS systems) ______________________________ : NO
    statsd (collect custom application metrics) ________________ : YES
    timex (check system clock synchronization) _________________ : YES
    idlejitter (check system latency and jitter) _______________ : YES
    bash (support shell data collection jobs - charts.d) _______ : YES
    debugfs (kernel debugging metrics) _________________________ : YES
    cups (monitor printers and print jobs) _____________________ : YES
    ebpf (monitor system calls) ________________________________ : YES
    freeipmi (monitor enterprise server H/W) ___________________ : YES
    nfacct (gather netfilter accounting) _______________________ : NO
    perf (collect kernel performance events) ___________________ : YES
    slabinfo (monitor kernel object caching) ___________________ : YES
    Xen ________________________________________________________ : NO
    Xen VBD Error Tracking _____________________________________ : NO
    Logs Management ____________________________________________ : YES
Exporters:
    AWS Kinesis ________________________________________________ : NO
    GCP PubSub _________________________________________________ : NO
    MongoDB ____________________________________________________ : YES
    Prometheus (OpenMetrics) Exporter __________________________ : YES
    Prometheus Remote Write ____________________________________ : YES
    Graphite ___________________________________________________ : YES
    Graphite HTTP / HTTPS ______________________________________ : YES
    JSON _______________________________________________________ : YES
    JSON HTTP / HTTPS __________________________________________ : YES
    OpenTSDB ___________________________________________________ : YES
    OpenTSDB HTTP / HTTPS ______________________________________ : YES
    All Metrics API ____________________________________________ : YES
    Shell (use metrics in shell scripts) _______________________ : YES
Debug/Developer Features:
    Trace All Netdata Allocations (with charts) ________________ : NO
    Developer Mode (more runtime checks, slower) _______________ : NO

Additional info

THe same thing happens at all hosts.

hugovalente-pm commented 7 months ago

@akama-aka could you perhaps add a video of the issue? I wasn't able to reproduce it, I'm not running the exact same setup but an Alma 9.0 running on Windows WSL2

https://github.com/netdata/netdata-cloud/assets/82235632/df72e779-1a74-4b59-9edf-8a0ae6a11867

Linux hugo-pc 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
/etc/almalinux-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/os-release:NAME="AlmaLinux"
/etc/os-release:VERSION="9.0 (Emerald Puma)"
/etc/os-release:ID="almalinux"
/etc/os-release:ID_LIKE="rhel centos fedora"
/etc/os-release:VERSION_ID="9.0"
/etc/os-release:PLATFORM_ID="platform:el9"
/etc/os-release:PRETTY_NAME="AlmaLinux 9.0 (Emerald Puma)"
/etc/os-release:ANSI_COLOR="0;34"
/etc/os-release:LOGO="fedora-logo-icon"
/etc/os-release:CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
/etc/os-release:
/etc/os-release:ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
/etc/os-release:ALMALINUX_MANTISBT_PROJECT_VERSION="9.0"
/etc/os-release:REDHAT_SUPPORT_PRODUCT="AlmaLinux"
/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="9.0"
/etc/redhat-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/system-release:AlmaLinux release 9.0 (Emerald Puma)

akama-aka commented 7 months ago

@akama-aka could you perhaps add a video of the issue? I wasn't able to reproduce it, I'm not running the exact same setup but an Alma 9.0 running on Windows WSL2 chrome_v7VReIsfAc.mp4

Linux hugo-pc 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
/etc/almalinux-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/os-release:NAME="AlmaLinux"
/etc/os-release:VERSION="9.0 (Emerald Puma)"
/etc/os-release:ID="almalinux"
/etc/os-release:ID_LIKE="rhel centos fedora"
/etc/os-release:VERSION_ID="9.0"
/etc/os-release:PLATFORM_ID="platform:el9"
/etc/os-release:PRETTY_NAME="AlmaLinux 9.0 (Emerald Puma)"
/etc/os-release:ANSI_COLOR="0;34"
/etc/os-release:LOGO="fedora-logo-icon"
/etc/os-release:CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
/etc/os-release:
/etc/os-release:ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
/etc/os-release:ALMALINUX_MANTISBT_PROJECT_VERSION="9.0"
/etc/os-release:REDHAT_SUPPORT_PRODUCT="AlmaLinux"
/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="9.0"
/etc/redhat-release:AlmaLinux release 9.0 (Emerald Puma)
/etc/system-release:AlmaLinux release 9.0 (Emerald Puma)

Somehow it works right now again.

hugovalente-pm commented 7 months ago

ok, closing as some potential temporary glitch let us know if you spot it again

akama-aka commented 4 months ago

I've this issue again :/

Tried to change the time frame from 05:00 to 06:30 (Its currently 09:25 CEST) and it directly changed it again to the current time in my location.

hugovalente-pm commented 4 months ago

re-opening the issue with a recording to showcase it, this happens when users enter a specific timeframe and don't use the relative ones

https://github.com/netdata/netdata-cloud/assets/82235632/02990bea-e251-4bcf-ac64-60b32ae12a80

novykh commented 4 months ago

Should be fixed in latest release.

netdata / netdata-cloud