Forum Discussion

billbianco's avatar
billbianco
Icon for Neophyte rankNeophyte
5 days ago

Dashboard Graph Use Case: Tracking Incoming and Accumulated Data

I’m working on a dashboard graph that not only displays the measured incoming data for each time slot but also tracks the cumulative total over time. The goal is to provide both a real-time view of data flow and a broader perspective on total data volume.

For example, consider the following data points:

  • At 12:01, 100 bytes are received
  • At 12:02, 150 bytes are received
  • At 12:03, 200 bytes are received

The graph would include two lines:

  1. Incoming Data – showing the raw data received at each time point: 100, 150, 200
  2. Accumulated Data – showing the running total from the start of the graph (e.g., starting at 12:00 with 0): 0, 100, 250, 450

Initially, I didn’t think this would be a big deal to implement — just some basic math and data transformation. But once I started building the appropriate complex data points and logic to make this happen, I realized it was more involved than expected. The core challenge seems to stem from the inability to set initial variable conditions or reference data from previous time slots within the tooling I’m using.

I have worked with LM support to no avail.  This surprises me as I would have thought this would be a common use-case.

Has anyone else encountered this kind of use case and found a clean solution? I’d love to hear how others have approached this — especially if you’ve managed to do it without relying on GROOVY scripting, which I’m not familiar with and would prefer to avoid.

I apologize in advance if this has been covered before, but haven't seen any reference to this.

Thanks to all!

1 Reply

  • jnahm's avatar
    jnahm
    Icon for Product Manager rankProduct Manager

    Hi billbianco​ ,

    I would be interested in learning more about this use case. If I understood the request correctly, you would like to plot.

    • The raw metrics as is
    • Sum of raw metrics, per each time interval the metrics is collected over a period of time.

    Seems like you were not able to use the custom graph widget to do so, and now are considering complex datapoints in a datasource, potentially using Groovy. 

    If you're willing, it would be great to go into more details around the areas you feel challenged.