![](https://secure.gravatar.com/avatar/f8439d15d0ba9653e1d430326958b8d2.jpg?s=120&d=mm&r=g)
Dear All,
could someone give me some advice how to graph F5 LTM's SSL client TPS ? If teher is any way ...
Regards, imedve
![](https://secure.gravatar.com/avatar/0896e673efe2e0118c2617b5af6c817b.jpg?s=120&d=mm&r=g)
Hmm...
Seems we did have it working, up until a couple of weeks ago (see below). It's possible something changed on our observium instance (we almost always run PE+custom patches).
I've also checked our dev instance and it's not reporting back any current values either. We've had numerous changes around that time, including a V-to-P migration of the observium host, so it's possible something got missed.
I'll check it out during the coming week and see if a tickle is required to the code.
Cheers,
Michael
On 28 Jan 2017, at 1:19 am, Medve István medve.istvan@pillerkft.hu wrote:
Dear All,
could someone give me some advice how to graph F5 LTM's SSL client TPS ? If teher is any way ...
Regards, imedve
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
Did we brek, or did you brek? ;)
Adam.
Sent from BlueMail
On 27 Jan 2017, 21:16, at 21:16, Michael obslist@smarsz.com wrote:
Hmm...
Seems we did have it working, up until a couple of weeks ago (see below). It's possible something changed on our observium instance (we almost always run PE+custom patches).
I've also checked our dev instance and it's not reporting back any current values either. We've had numerous changes around that time, including a V-to-P migration of the observium host, so it's possible something got missed.
I'll check it out during the coming week and see if a tickle is required to the code.
Cheers,
Michael
On 28 Jan 2017, at 1:19 am, Medve István medve.istvan@pillerkft.hu
wrote:
Dear All,
could someone give me some advice how to graph F5 LTM's SSL client
TPS ?
If teher is any way ...
Regards, imedve
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/0896e673efe2e0118c2617b5af6c817b.jpg?s=120&d=mm&r=g)
On 28 Jan 2017, at 8:33 am, Adam Armstrong adama@memetic.org wrote:
Did we brek, or did you brek? ;)
Yes. Definitely yes. :p
I'll have to check on that though. We've been doing a bunch of stuff lately, including some extras to the F5 metrics & it's not at all unusual that we push our changes to prod before we submit the patch for consideration to trunk. It's most likely that we broke our own instance.
The screenshot was hopefully for the initial benefit of imedve. Showing where to find the data (Graphs --> F5 SSL).
I'll let you know what I find.
... Actually, I've just checked one other instance that's on r8327 and it is still collecting the data fine. Must be our end.
Michael
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
gubmint IT, eh?
adam. On 28/01/2017 01:27:05, Michael obslist@smarsz.com wrote:
On 28 Jan 2017, at 8:33 am, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
Did we brek, or did you brek? ;)
Yes. Definitely yes. :p
I'll have to check on that though. We've been doing a bunch of stuff lately, including some extras to the F5 metrics & it's not at all unusual that we push our changes to prod before we submit the patch for consideration to trunk. It's most likely that we broke our own instance.
The screenshot was hopefully for the initial benefit of imedve. Showing where to find the data (Graphs --> F5 SSL).
I'll let you know what I find.
... Actually, I've just checked one other instance that's on r8327 and it is still collecting the data fine. Must be our end.
Michael
![](https://secure.gravatar.com/avatar/f8439d15d0ba9653e1d430326958b8d2.jpg?s=120&d=mm&r=g)
Hi,
Thank you works fine!
imedve
On Sat, 2017-01-28 at 08:16 +1100, Michael wrote: Hmm...
Seems we did have it working, up until a couple of weeks ago (see below). It's possible something changed on our observium instance (we almost always run PE+custom patches).
I've also checked our dev instance and it's not reporting back any current values either. We've had numerous changes around that time, including a V-to-P migration of the observium host, so it's possible something got missed.
I'll check it out during the coming week and see if a tickle is required to the code.
Cheers,
Michael
[cid:1485797283.24562.24.camel@pillerkft.hu]
On 28 Jan 2017, at 1:19 am, Medve István <medve.istvan@pillerkft.humailto:medve.istvan@pillerkft.hu> wrote:
Dear All,
could someone give me some advice how to graph F5 LTM's SSL client TPS ? If teher is any way ...
Regards, imedve
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong
-
Medve István
-
Michael