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 #8693] New function: parse_performance_data #2743

Closed
icinga-migration opened this issue Mar 11, 2015 · 5 comments
Closed

[dev.icinga.com #8693] New function: parse_performance_data #2743

icinga-migration opened this issue Mar 11, 2015 · 5 comments
Labels
enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

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

Created by tgelf on 2015-03-11 15:10:41 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-03-19 12:38:42 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-19 12:38:42 +00:00 (in Redmine)

Backport?: Already backported
Include in Changelog: 1

Since 2.3 I'm able to access all kind of object properties at runtime. That way I can access current performance data:

get_service("workshop.example.com", "load").last_check_result.performance_data[0]
"load1=0.080;5.000;10.000;0;"

It would be nice to have those values available for conditional configuration, that would however require a method allowing me to parse such a perfdata string. Given that, configuration could look as follows:

vars.apache_procs_crit = {{
  loadstring = get_service("workshop.example.com", "load").last_check_result.performance_data[0]
  load = parse_performance_data(load).value
  if (load > 5) {
    return 100
  } else {
    return 200
  }
}}

Cheers,
Thomas

Changesets

2015-03-11 15:29:50 +00:00 by (unknown) 228aafc

Implement the parse_performance_data function

fixes #8693

2015-03-19 12:38:24 +00:00 by (unknown) 2826ef7

Implement the parse_performance_data function

fixes #8693
@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-03-11 15:28:02 +00:00

  • Category set to libicinga
  • Status changed from New to Assigned
  • Assigned to set to gbeutner
  • Target Version set to 2.4.0

@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-03-11 15:30:03 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 228aafc.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-03-13 13:04:30 +00:00

  • Estimated Hours set to 1

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-03-19 10:16:03 +00:00

  • Status changed from Resolved to Assigned
  • Target Version changed from 2.4.0 to 2.3.3
  • Backport? changed from TBD to Yes
  • Add Changelog Information

@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-03-19 12:38:42 +00:00

  • Status changed from Assigned to Resolved

Applied in changeset 2826ef7.

@icinga-migration icinga-migration added enhancement New feature or request libicinga labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.3 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant