We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9185
Created by mfriedrich on 2015-04-27 09:25:20 +00:00
Assignee: mfriedrich Status: Resolved (closed on 2015-04-27 13:09:25 +00:00) Target Version: 2.3.5 Last Update: 2015-04-27 13:09:25 +00:00 (in Redmine)
Backport?: Already backported Include in Changelog: 1
Similar to #8374 but only changing the default TIMET::$timet$ format template to TIMET::${host,service}.last_check$ by default.
Changesets
2015-04-27 13:06:48 +00:00 by (unknown) dcc8704
Add timestamp support for PerfdataWriter Change the default from $timet$ to ${host,service}.last_check$ fixes #9185
2015-04-27 13:09:05 +00:00 by (unknown) beead48
Relations:
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2015-04-27 09:25:31 +00:00
Sorry, something went wrong.
Updated by mfriedrich on 2015-04-27 12:17:37 +00:00
Updated by mfriedrich on 2015-04-27 13:08:50 +00:00
Updated by Anonymous on 2015-04-27 13:09:25 +00:00
Applied in changeset dcc8704.
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9185
Created by mfriedrich on 2015-04-27 09:25:20 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-04-27 13:09:25 +00:00)
Target Version: 2.3.5
Last Update: 2015-04-27 13:09:25 +00:00 (in Redmine)
Similar to #8374 but only changing the default TIMET::$timet$ format template to TIMET::${host,service}.last_check$ by default.
Changesets
2015-04-27 13:06:48 +00:00 by (unknown) dcc8704
2015-04-27 13:09:05 +00:00 by (unknown) beead48
Relations:
The text was updated successfully, but these errors were encountered: