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

[dev.icinga.com #11035] acknowledgement sticky wont work #3876

Closed
icinga-migration opened this issue Jan 26, 2016 · 6 comments
Closed

[dev.icinga.com #11035] acknowledgement sticky wont work #3876

icinga-migration opened this issue Jan 26, 2016 · 6 comments
Labels
bug Something isn't working

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11035

Created by GreenRover on 2016-01-26 09:22:20 +00:00

Assignee: (none)
Status: Rejected (closed on 2016-06-07 19:07:07 +00:00)
Target Version: (none)
Last Update: 2016-06-07 19:07:21 +00:00 (in Redmine)

Icinga Version: r2.4.1-1
Backport?: Not yet backported
Include in Changelog: 1

If i mark an acknowledgement as sticky it will be removed if service returns OK.
Shoulnd the acknowledgement persist ut to the end date or manual deletion?

Here an demo video:

https://www.youtube.com/watch?v=YE5dvwimQK0

My test config:

object Host "bug_demo_host" {
    check_command = "dummy"

    address = "127.0.0.1"
}

apply Service "bug_demo_service" {
    check_command = "check_bug_demo"

    max_check_attempts = 3
    check_interval = 10s
    retry_interval = 5s

    assign where host.name == "bug_demo_host"
} 

object CheckCommand "check_bug_demo" {
    import "plugin-check-command"
    import "ipv4-or-ipv6"

    command = [ PluginDir + "/check_tcp" ]

    arguments = {
        "-H" = "$check_address$"
        "-p" = "1337"
        "-w" = "2"
        "-c" = "3"
    }
}

Test Service

while true; do nc -n -l 1337; done

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-01-26 18:02:53 +00:00

  • Category set to libicinga
  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

I'll look into that.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-01-28 13:32:46 +00:00

  • Relates set to 9619

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-03-04 16:51:17 +00:00

  • Parent Id set to 11311

@icinga-migration
Copy link
Author

Updated by GreenRover on 2016-04-01 10:18:12 +00:00

For the acutal case:

as the servers got an error i did:

/v1/actions/acknowledge-problem
            'author' => $author,
            'comment' => $comment,
            'expiry' => 1459634400, 
            'sticky' => true,
            'notify' => true,

The services retuns OK and afterwords:

/v1/objects/comments?1?joins=service
     results: [ ]

The comment list is empty, but:

/v1/objects/downtimes?filter[]=downtime.host_name=="DIV-023"
     gives 2 entrys.

So the alarms no notifications will send, but i have no cloue why. Becasue the comment is missing.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-07 19:07:08 +00:00

  • Status changed from Assigned to Rejected
  • Assigned to deleted mfriedrich

Apparently this was a misunderstanding how acknowledgements work, no matter if they are sticky or not. Icinga is not designed to keep acknowledgements after a service returned into an OK state, waiting for the next NOT-OK state. Downtimes suppressing notifications is the way to go. This has been discussed offline with both sides agreeing on the matter.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-07 19:07:22 +00:00

  • Parent Id deleted 11311

@icinga-migration icinga-migration added bug Something isn't working libicinga labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant