Heartbeat Events

[Scott Hunter]

With the update to OneFS 8.2 we get dozens of heartbeat event email messages every night.  

The posted support solution appears doesn't look optimal to me:

https://emcservice.force.com/CustomersPartners/kA2j0000000RHEHCA4

a) disable all heartbeat event notification

b) lower the frequency of the tests from daily to weekly or monthly.

It seems like there should be an option to only receive "real events".  I do want to know if there is a connectivity problem.  

Am I reading this wrong?  

Thanks

Scott 

[Peter Serocka]

Don’t know about “8.2”…

but back in 6.5/7.1/7.2 we found the event notification
system really deserved permanent (read: daily) connectivity testing,
so we had set up a cron job to send a test mail at noon.

Kind of glad to find this being built-in with 8.0…

(Did you mean you "do want" or you "do not want…” ?)

— Peter

> --
> You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Erik Weiman]

As of now there is no 8.2 ... maybe you meant 8.1.0.2?

> To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-group+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-group+unsubscribe@googlegroups.com.

[Karim Youssri Mahmoud]

The Heartbeat event belongs to Software events category (category 400000000). When you configure alerting that uses SMTP channel for Software Events, the SMTP recipients would receive daily email notification for heartbeat event (event ID 400050004)

You can list all the event type in the Software category using the following command:

# isi event types list --category=400000000

Now, if you want to exclude the HeartBeat event (400050004) from Alerting, you will have to remove the entire Software category, and explicitly specify the other events you want to receive.

# isi event alerts modify <alertname> --add-eventgroup= "400020001,400020002,400030001,400030002,400040012,400040020,400040021,400050001,400050002,400050003,400060004,400070004,400070005,400070006,400070007,400080001,400090001,400090002,400090003,400090004,400100001,400100002,400100003,400100004,400100005,400100011,400110001,400120001,400130001,400130002,400140001,400140002,400150001,400150002,400150003,400150004,400150005,400160001,400210001,400210002"

I hope this helps.

Karim.

[Scott Hunter]

>  As of now there is no 8.2 ... maybe you meant 8.1.0.2?

Yes.   8.1.0.2.    Doh!

[Scott Hunter]

(Did you mean you "do want" or you "do not want…” ?)

 

Each cluster is sending dozens of pointless messages.  This is in the "do not want" category. 

At the moment, the Dell fix is to disable all alerts on heartbeats, or to dramatically lower the frequency of system tests of heartbeat connectivity.   Neither option really makes sense.