Best monitoring strategy for production

[vvilaplana]

@Anaisdg

• Check&monitor tasks vs check tasks + monitor task
  Yes you can just do the checking with conditional querying and then write that data to a new bucket with to().

Since monitor.xxxxx() functions are very strict, the only solution seems to go low-level and directly writing/parsing _monitoring bucket. But quite frankly, I don’t think that’s gonna be very performant on large scale platforms. Feel free to correct me if I’m wrong.

Your post (TL;DR InfluxDB Tech Tips — Using Tasks and Checks for Monitoring with InfluxDB | InfluxData) explains the monitoring workflow process and what monitor.check() internally does, but it doesn’t describe how to parse _monitoring.statuses.

Can you provide a working example (influx 2.0.4) of any trivial test check task writing to _monitoring bucket and a monitor alert task that processes _monitoring bucket? I’m sure that’s what’s gonna help a lot of people.

@Anaisdg

• Monitoring previous statuses
  Are you familiar with https://docs.influxdata.com/flux/v0/stdlib/influxdata/influxdb/monitor/statechanges/?
  Last tutorial, I promise but this could be useful: TL;DR InfluxDB Tech Tips – How to Monitor States with InfluxDB | InfluxData
  If these two resources don’t help, please let me know. I appreciate your willingness to take a look in advance.

Again thanks for your detailed question, im sure this will help future users. Please let me know if you have any more questions or points I can clarify.

I’ve been testing StateChangesOnly(), but I couldn’t make it work I haven’t seen a single alert task using it. All the examples I found just show partial lines of StateChangesOnly(). The most “detailed” place I’ve found about that function is here: stateChangesOnly() does not work as expected - #17 by Anaisdg