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.

Sign up for GitHub

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

Jump to bottom

[dev.icinga.com #8876] Allow module developers to implement new/custom command transports #1508

Closed
icinga-migration opened this issue Mar 27, 2015 · 4 comments
Closed

[dev.icinga.com #8876] Allow module developers to implement new/custom command transports #1508

icinga-migration opened this issue Mar 27, 2015 · 4 comments
Labels
area/monitoring Affects the monitoring module enhancement New feature or improvement wontfix Deprecated, not supported or not worth any effort

Comments

@icinga-migration
Copy link

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

Created by elippmann on 2015-03-27 08:17:54 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-06-11 07:40:42 +00:00 (in Redmine)

As a module developer, I want to implement custom command transports because the monitoring module does not provide the command transport I need.

Relations:
@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-27 08:21:43 +00:00

  • Relates set to 6593

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-27 08:22:56 +00:00

  • Relates set to 8877

@icinga-migration
Copy link
Author

Updated by jmeyer on 2015-06-11 07:40:42 +00:00

  • Target Version changed from 2.0.0-rc1 to Backlog

@icinga-migration icinga-migration added enhancement New feature or improvement area/monitoring Affects the monitoring module labels Jan 17, 2017
@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@lippserd lippserd removed this from the Backlog milestone Apr 11, 2018
@lippserd
Copy link
Member

No progress has been made here. I'll close this issue because it's very old and we have no plans to work on it in the near future. If you're interested in this topic, please open a new issue.

@lippserd lippserd added the wontfix Deprecated, not supported or not worth any effort label Apr 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/monitoring Affects the monitoring module enhancement New feature or improvement wontfix Deprecated, not supported or not worth any effort
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lippserd @icinga-migration