Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2704] Allow to create filters for the "output" column #815

Closed
icinga-migration opened this issue Jun 22, 2012 · 4 comments

Comments

@icinga-migration
Copy link

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

Created by tgelf on 2012-06-22 08:36:15 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:34 +00:00 (in Redmine)


At least for host/servicestatus grids it would be great if you could use the output columns for your custom filters.

Cheers,
Thomas


Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-09-24 15:01:54 +00:00

would those queries even scale? afaik the output would need a proper index, being text only now (at leat on mysql). or am i wrong with that assumption?

@icinga-migration
Copy link
Author

Updated by tgelf on 2012-09-24 16:29:30 +00:00

Index -> it depends. I wouldn't add an index, as most such queries WILL be slow if used on very large history tables - but you shouldn't note them on state tables. An index could help sometimes. On MySQL searching "www." would be fast, ".domain.tld" would probably still do a full table scan.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-04-08 20:41:05 +00:00

this will need a re-evalution once #3268 is released.

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:17:34 +00:00

  • Target Version set to Backlog

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@dnsmichi dnsmichi removed this from the Backlog milestone Dec 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants