> On 08 Jun 2015, at 11:15, Sergey Kirpichev <[email protected]> wrote:
> 
> tags 787400 +moreinfo
> thanks
> 
> Hello,
> 
> On Mon, Jun 1, 2015 at 2:43 PM, Martin Pala <[email protected]> wrote:
>> regarding the hostname … please check your monit configuration - if the
>> “check system <string>” statement is used, then you give the system a custom
>> name which overrides the hostname with a “<string>” => if you have
>> “check system localhost”, you will see “localhost”.
> 
> Sorry, Martin, but right now this looks as a regression.  I assume that
> the current configuration was working on < 5.13.
> 
> Jens, I'm wrong?  Could you provide used monit configuration, related
> to the example ("check system", apache configuration, etc).
> 
> PS: Please CC to the bug thread, unless you intentionaly willing
> to hide some information.


Actually the original behaviour was bug - the name used in the “check system” 
was always intended to be visible in M/Monit, snip from Monit 5.9 manual (see 
the last sentence in the snip):

—8<—
=item 7. CHECK SYSTEM <unique name>

The system name is usually hostname, but any descriptive name can be
used. You can use the variable $HOST as the name, which will expand to
the hostname. This test allows one to check general system resources
such as CPU usage (percent of time spent in user, system and wait),
total memory usage or load average. The unique name is used as the
system hostname in mail alerts and when M/Monit is configured, then
also as initial name of the host entry in M/Monit.
—8<—

Monit 5.13 fixes the problem - the “localhost” name is configuration issue … 
“$HOST” should be used if the real hostname is needed instead of custom name.

I’m sorry about the bug thread … i wanted to post the data to it and used 
“reply-all” to the original message, which automatically includes 
“[email protected]” - i guess the “-quiet” postfix makes the message 
invisible in the thread, changing it to “[email protected]” instead.

Regards,
Martin


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to