If your refresh rate is causing issues for the system, try pre-calculating
the values using a continuous query, and then have Grafana display the
stored calculated values rather than recalculating the full query every
time.

Also, for real-time alerting, check out the Kapacitor
<https://docs.influxdata.com/kapacitor/v0.13/> project, which works
natively with InfluxDB.

On Wed, Aug 10, 2016 at 12:16 PM, <[email protected]> wrote:

> Hi Sean,
>
> Thanks for replying.
>
> Yep, monitoring the machine sounds definitely good.
>
> So, in order to visualize data in as close to real-time as possible
> changing the refresh-rate in Grafana is the proposed way? Anything else to
> be aware of? (first time for me using the InfluxDB / Grafana toolset).
>
> Thank you.
>
> On Tuesday, August 9, 2016 at 10:43:59 AM UTC-7, Sean Beckett wrote:
> > You can monitor the CPU and RAM needs of the machine for stress from the
> queries. Without knowing the shape of your data and the actual queries,
> it's hard to predict what load the hardware could sustain.
> >
> >
> > On Wed, Aug 3, 2016 at 1:09 PM,  <[email protected]> wrote:
> > Hello!
> >
> >
> >
> > I am new to InfluxDB/Grafana and have a question regarding best
> practices to visualize time series data stored in InfluxDB in (as near as
> possible -) real-time in Grafana.
> >
> >
> >
> > I have been playing with setting the "Refreshing every" time range in
> Grafana to 1s. I have also figured out that I can even go below 1s and set
> this refresh rate to 0.5 sec or even less.
> >
> >
> >
> > This works relatively well, but I am not sure if this
> >
> > a) is really the best practice to see data in real-time
> >
> > b) could cause too much stress on my InfluxDB instance. especially once
> the number of Grafana dashboard users grows (let's say up to 5 or 10) we
> would increase the load to Influx even more.
> >
> >
> >
> > Thankful to any feedback on this.
> >
> >
> >
> > Thank you.
> >
> > Robert
> >
> >
> >
> > --
> >
> > Remember to include the InfluxDB version number with all issue reports
> >
> > ---
> >
> > You received this message because you are subscribed to the Google
> Groups "InfluxDB" group.
> >
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> >
> > To post to this group, send email to [email protected].
> >
> > Visit this group at https://groups.google.com/group/influxdb.
> >
> > To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/6c4f862a-7735-4e14-bc79-6f18cb15652a%40googlegroups.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> >
> >
> > --
> >
> >
> > Sean Beckett
> > Director of Support and Professional Services
> > InfluxDB
>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/a3080dfe-fae5-4b3f-95f6-41d914aa4cc3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CALGqCvM84SNEMomhOLOisxsO1xkhW4X0gTS6S94_5ss_n1%3DK_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to