mingzeh opened a new issue, #4124:
URL: https://github.com/apache/hertzbeat/issues/4124

   ### Is there an existing issue for this?
   
   - [x] I have searched the existing issues
   
   ### Current Behavior
   
   When using GreptimeDB as the time-series database in HertzBeat 1.8.0, the 
metrics labels of monitoring tasks are not written into the database.
   However, when switching to VictoriaMetrics, the labels are written correctly.
   
   <img width="3002" height="1632" alt="Image" 
src="https://github.com/user-attachments/assets/289019a8-e9a5-428d-b267-4ffbfe60a1ca";
 />
   
   **VictoriaMetrics (labels are present)** 
   <img width="3024" height="1650" alt="Image" 
src="https://github.com/user-attachments/assets/e8b3a17a-0c3c-4203-b4b3-fa4a9b11020b";
 />
   
   → Custom labels are correctly stored and can be queried.
   
   ---
   
   **GreptimeDB (labels are missing)** 
   <img width="3024" height="1654" alt="Image" 
src="https://github.com/user-attachments/assets/40c84387-ab4a-4f93-9f49-5b982c6cbc25";
 />
   → Custom labels are NOT written into the database.
   
   ### Expected Behavior
   
   Metrics labels should be written consistently regardless of the selected 
time-series database backend.
   
   ### Steps To Reproduce
   
   1. Deploy HertzBeat 1.8.0
   
   2. Configure GreptimeDB as the storage backend
   
   3. Create a monitoring task with labels
   
   4. Check stored metrics in GreptimeDB → labels missing
   
   5. Switch to VictoriaMetrics
   
   6. Check metrics again → labels exist
   
   ### Environment
   
   ```markdown
   HertzBeat version(s): v1.8.0
   
   Time-series DB:
     GreptimeDB (issue occurs)
     VictoriaMetrics (works as expected)
   ```
   
   ### Debug logs
   
   _No response_
   
   ### Anything else?
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to