On 18.3.43 field %status show "Down ended" instead "Up" ???

Hi there,

What version where you using prior the upgrade so we can reproduce this on our side. The reason I am asking is that I can't find any hint for this change in the recent notes and our internal development database.

Best regards.

Hi,

we are using standard Stable release channel for updates.

Here is history of updates:
August 22 - installed Version 18.3.43.2323
July 24 - installed Version 18.3.42.1748
June 13 - installed Version 18.2.41.1652

status text for Up in email notifications was changed to Down ended (now: Up) right after update on August 22.

Best regards.

Hi there,

I was able to reproduce this behavior. As far as I know this was added with the overall Notification Improvement in the latest release, even though we don't specify it in the notes:

• Release Notes For The "Stable" Release Channel Before we will open an internal development ticket to change that back, we will see if other customers see this improvement as bad. But please note that your feedback will be used in further discussions about this change.
  
  Best regards.

Hi,

believe me, that was not improvement, it's very, very, very bad change !

Up and Down are statuses, but Down ended is not status, it's just information.

return it back, please!

Best regards,

I have to agree, I miss having [Up] at the start of the notification email. It was simple, clear, concise.

Now it's a bloated and complicated [Down ended (now: Up)] - of course the Down will end when something goes back Up.

It's following the previous formatting as when something is paused [Down ended (now: Paused)]. I wish it would just say the actual status Paused

Hi there,

We just want to offer more information within the notification so you can see what the status was before the change. Before this improvement you had to lookup the status log in the mail to check what the old status was, now you can see it at the first glance. This also works for other states, such as "Unknown", "Warning", "Unusual", "Partial Down" and "Up". All these states can be selected now to create a Notification Trigger and in order to avoid confusion when the notification says Up ended (now: Down) we have implemented this.

Best regards.

Wow, wow, wow ... guys your intentions was good, but implementation is (epic!) example of fail.

First %status% for me (and I think most of other people which depends on PRTG) means what is current status of my sensor.

Sometimes it is nice to know previous status, but you put as first word something what is sometimes nice to know, and most important information at the end. Also you put several information into simple field which just need to tell you just one information!

So your information is totally unpractical and hard to process for humans and machines. (Think when you have big list of messages, and every begins with word Down !)

It will be much better if you return this field to old and introduce new filed %oldstatus%, or something like that, which will contain previous status, so user can combine it int form which best suites him.

Please don't change concept of existing fields, people relays on that (mail filtering for example!), instead introduce new fields with new forms of information, specially when we are talking about elementary fields like %status%.

If you decide to keep this change, at least please create new field with old form of correct status information!

Best regards,

So, if the "new and improved" status' can't be modified (or even included in the Release Notes explaining the change) - how can I downgrade my version back to get the old status messages again?

Hi there,

You can always find the version your had installed pre-update on the Core Server under:

You can install this on top and you should be back to the old version.

Best regards.

For anyone who has stumbled upon this post and also affected by this new and improved "complicated status", there is now a Feature Request to re-add a "simplified status" to restore the option of having the good old simple Up, Down single word status'.

https://kb.paessler.com/en/topic/81708-open-simplified-status-placeholder

Hi, just for record, it's not quite true that this change is "not mentioned" in change log.

If you look at 18.3.43 version history under Notifications section, you will find "Notification Triggers" " You can now use Up and Unknown states with the State Trigger."

This version introduced ability to specify on what state notification trigger is triggered. But under the hood they also change the logic of %status placeholder to show notification instead of sensor status.

Yes you are probably right, users requested this change, but I'm not sure that they also requested change of logic in %status placeholder :-).

But if you stay with this change, you need to update description of %status placeholder under What placeholders can I use with PRTG?

Hi there,

@siers, thanks for linking the feature request. If this gets enough votes, then we can take this change into consideration and may reevaluate it.

@turki, updated the placeholder page, thanks for that. :)

Best regards.

PRTG Network Monitor 23.2.83.1760 x64

Is it possible to make only two statuses? UP DOWN