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 #11329] API requests from execute-script action are too verbose #4010

Closed
icinga-migration opened this issue Mar 8, 2016 · 9 comments
Labels
area/api REST API bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by tobiasvdk on 2016-03-08 08:48:19 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-12-08 00:05:03 +00:00)
Target Version: 2.6.0
Last Update: 2016-12-08 00:05:03 +00:00 (in Redmine)

Icinga Version: 2.4.10

Using the directors kickstart the following debug message is shown as information

[2016-03-07 17:37:26 +0000] information/Console: Executing expression: var constants = [];
for (k => v in globals) {
   if (typeof(v) in [String, Number, Boolean]) {
      res = { name = k, value = v }
      constants.add({name = k, value = v})
   }
};
constants

Changesets

2016-12-07 23:59:24 +00:00 by mfriedrich b10a6b7

API: Change log level for console endpoint

fixes #11329
@icinga-migration
Copy link
Author

Updated by elippmann on 2016-03-08 09:03:26 +00:00

  • Project changed from Icinga Web 2 to Director

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-03-08 10:10:55 +00:00

  • Project changed from Director to Icinga 2
  • Icinga Version set to 2

It's the Icinga 2 log, writing all console actions at this level is too noisy.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-03-14 07:55:30 +00:00

How about 'notice'?

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-03-14 07:55:43 +00:00

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

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-04-14 09:44:33 +00:00

  • Tracker changed from Bug to Feature
  • Subject changed from Debug message categorized as "information" to Add API endpoint for globals (constants, etc.)
  • Category set to API
  • Status changed from Feedback to New
  • Assigned to deleted tgelf
  • Target Version set to Backlog

We should add a specified API endpoint for that.

Example:

/v1/globals returns a list of global constants and the type
/v1/globals?name=PluginDir&name=MyConstant returns the selected constants, their value and type

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-04-14 09:56:04 +00:00

Such an API endpoint would of course make the shown example easier. But please open a dedicated issue for that one and do not hijack this issue. The original problem reported is that logging is too verbose here. It affects everything you run through console/execute-script if I recall this correctly.

Thanks,
Thomas

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-08-09 12:49:42 +00:00

  • Tracker changed from Feature to Bug
  • Subject changed from Add API endpoint for globals (constants, etc.) to API requests from execute-script action are too verbose
  • Target Version deleted Backlog
  • Icinga Version set to 2

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-08 00:00:17 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Target Version set to 2.6.0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-08 00:05:03 +00:00

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

Applied in changeset b10a6b7.

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

No branches or pull requests

1 participant