Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behavior of HTTP string monitoring settings(hinemos-6.1-manager) #7

Open
inogashiragoro opened this issue Jul 12, 2019 · 0 comments
Open

Comments

@inogashiragoro
Copy link

inogashiragoro commented Jul 12, 2019

Hello,
Our team is monitoring servers running on AWS with hinemos, and I would like to know about the following events that occurred there.

■ Summary
We got some errors saying "critical" although "success" was returned after rebooted himemos manager service.
It does not seem working as intended.

■ Operation and what occurred
#0 The HTTP monitoring kept returning "success" and we got no errors
#1 Stopped himemos manager service and then restarted it (hinemos agent was not restarted)

  • terminal command
    (root) # service hinemos_manager stop
    (root) # service hinemos_manager start

#2 Got "critical" alert even though conditions for HTTP monitoring settings are not met (HTTP monitoring kept returning "success")

#3 Opened the setup screen on web UI, changed nothing and saved it (The last modification date is only changed.)

#4 The "critical" alert was stopped

■ Inquiries
#1 Is this an intended behavior?
#2 Is there anything wrong with setting of HTTP monitor?
#3 If this is not intended, is there any workaround?

■ Info
・manager
OS:CentOS Linux release 7.5.1804 (Core)
kernel:3.10.0-862.3.2.el7.x86_64
manager:hinemos-6.1-manager-6.1.1-1.el7.x86_64
Web:hinemos-6.1-web-6.1.1-1.el7.x86_64

・agent #1
OS:Amazon Linux AMI release 2015.09
kernel:4.1.10-17.31.amzn1.x86_64
agent:hinemos-6.1-agent-6.1.1-1.el.noarch

・agent #2
OS:Amazon Linux release 2 (Karoo)
kernel:4.14.123-111.109.amzn2.x86_64
agent:hinemos-6.1-agent-6.1.1-1.el.noarch

・HTTP monitoring (string) configuration information
Manager:Manager1
Moniter ID:FOO-WEBAP-HTTPSTATUS-RESPONSESTRING-001
Description:FOO-WEBAP-HTTPSTATUS-RESPONSESTRING-001
Owner Role ID:ALL_USERS
Scope:FOO-BAR>FOO-BAR-WEBAP>FOO-BAR-WEBAP-WEB101>

Conditon
 Interval:1 minute
 Calendar ID:CAL-FOO-WEBAP-001(CAL-FOO-WEBAP-001)
 Check Setting
  URL:http://foo.bar.com/AliveChecker/AliveCheckerServlet
  Timeout:30000 msec

Judge
 Order 1
  Description:Success
  Judge
   Pattern matching expression:.Success.
   Do not process if the condition is met
  Process
   Priority:None
   Message:None
  Enable this setting
 Order 2
  Description:Asterisk
  Judge
   Pattern matching expression:.*
   Do not process if the condition is met
  Process
   priority:Critical
   Message:Web Down
  Enable this setting

Notification
Notification ID:
  EVENT-FOO-ADMINS-002
  MAIL-FOO-ADMINS-002
  MAIL-FOO-USERS-001
 Apprication:WEBAP-HTTPSTATUS

Collection
 Collection:No check
 Log Format ID:None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant