Refine your search:

1
1

I have been tagging hosts to aid in searching by environment, service, sub-service

I would like to make a dashboard widget that lists all the services for a particular environment.

Is there a search query i can use to dynamically list all tags in the system or app?

asked 18 Sep '10, 00:25

gfriedmann's gravatar image

gfriedmann
257119
accept rate: 11%

I think i got a little closer with |metadata type=hosts | fields host| tags| search tag::host=*| fields - host

If that is closer, now i need to figure out how to breakup the multiline, dedupe, and make the drill-down work. I'm hoping there is an easy query i'm missing.

(18 Sep '10, 00:55) gfriedmann

One Answer:

This will do it:

| metadata type=hosts | tags | mvexpand tag::host | dedup tag::host | fields tag::host

If you need to drill down, you should be able to modify the standard dashboard a bit, just to select the right field name(s).

BTW, and maybe this is too late for you to consider, but I would strongly recommend for this purpose that you consider a lookup table (with a lookup on host returning each of your other fields) rather than tags. In some ways, they are much easier to manage, and you will be able to search by, e.g., environment=prod service=webserver rather than tag::host=env-prod tag::host=serv-webserver.

link

answered 18 Sep '10, 02:15

gkanapathy's gravatar image

gkanapathy ♦
32.4k4827
accept rate: 41%

edited 18 Sep '10, 02:30

Are you suggesting the lookup table approach specifically because he's hitting metadata, as opposed to raw results? If searching against actual events, wouldn't there be a (possibly severe) performance penalty?

(18 Sep '10, 03:56) southeringtonp ♦

It would be no worse and probably better to use lookup tables than tags.

(18 Sep '10, 09:09) gkanapathy ♦

Thank you. Tags seemed more natural to me and i understand them already. I'll investigate the lookup table. I suspect lookup tables would be cached in RAM for it to be speedy. I can see how exporting "tag" type info from another system would be easier with a lookup table.

(20 Sep '10, 16:04) gfriedmann
Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×1,651
×99
×76

Asked: 18 Sep '10, 00:25

Seen: 738 times

Last updated: 18 Sep '10, 02:30

Copyright © 2005-2012 Splunk Inc. All rights reserved.