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 #11460] How to use predefined check variables in director hosts / services / templates? #164

Closed
icinga-migration opened this issue Mar 28, 2016 · 5 comments
Milestone

Comments

@icinga-migration
Copy link

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

Created by geotek on 2016-03-28 10:21:16 +00:00

Assignee: (none)
Status: Closed (closed on 2016-10-24 21:31:23 +00:00)
Target Version: 1.2.0
Last Update: 2016-10-24 21:31:23 +00:00 (in Redmine)


There are several predefined variables such as vars.snmp_v2 or vars.dns_lookup that we need to set or override at different levels of the object hierarchy, but I can't find a way to set them in director. I would expect these variables to show up in the commands => fields => field dropdown list, but I can't find a way to set them anywere. As some of these variables are essential, how should we use them in director?

By the way, big congratulations to the people behind icinga - I have evaluated numerous NMS and this is by far the most elegant, attractive and promising open source NMS that I have ever seen. Heads Up!!


Relations:

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-07-20 09:45:15 +00:00

  • Status changed from New to Feedback
  • Assigned to set to geotek

Is this still an issue, have you been able to figure out how it works, anything you are still missing?

@icinga-migration
Copy link
Author

Updated by geotek on 2016-07-20 11:26:44 +00:00

At the moment this is not an issue for us any more as we have found ways to work around it.

However, I think it would be helpful to at least document the relationship between Director variables and static or live variables, which can be accessed and which not. I can think of several use cases where one would want to access externally defined variables (set_if, or assignment rules).

Thanks for coming back to this issue.

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-24 03:59:09 +00:00

  • Status changed from Feedback to New
  • Assigned to deleted geotek
  • Target Version set to 1.2.0

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-24 21:30:07 +00:00

  • Relates set to 12972

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-24 21:31:23 +00:00

  • Status changed from New to Closed

Created a related feature request that should make tasks like this more obvious. Not much text over there, but I hope I can remember what it was all about ;-)

Cheers,
Thomas

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

No branches or pull requests

1 participant