# Heartbeat tag information
**URL:** https://discuss.elastic.co/t/heartbeat-tag-information/229702
**Category:** Beats
**Tags:** elastic-stack-monitoring, heartbeat
**Created:** [April 24, 2020, 5:51pm UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702 "2020-04-24T17:51:12Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@sheldonh](https://discuss.elastic.co/u/sheldonh)
#### Post date: [April 24, 2020, 5:51pm UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/1 "2020-04-24T17:51:13Z")
I don't see any tags for filtering or grouping in heartbeats after configuring 100+ agents. I coded a snippet in the install script that pulls the ec2 tags and appends as yaml values. This is the format I used. Most of the examples online show a single key, but I wanted to provide multiple.
Is this how I'm supposed to provide multiple back? I need to group by the `stage`, `app`, and more, and not sure how to properly pass mutiple tags for classifying and grouping.
```auto
- add_tags:
tags: [prod11]
target: env
- add_tags:
tags: [monitor]
target: scope
```
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [April 27, 2020, 10:15am UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/2 "2020-04-27T10:15:06Z")
Hi @sheldonh examples shows you can add multiple like this , are you adding under processors?
[https://www.elastic.co/guide/en/beats/heartbeat/current/add-tags.html](https://www.elastic.co/guide/en/beats/heartbeat/current/add-tags.html)
```
processors:
- add_tags:
tags: [web, production]
target: "environment"
```
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 28, 2020, 1:07am UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/3 "2020-04-28T01:07:57Z")
You can also add tags on a [per monitor](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html#monitor-tags) basis. The `processors` section will add tags to every monitor.
---
### Author:  [@sheldonh](https://discuss.elastic.co/u/sheldonh)
#### Post date: [April 28, 2020, 7:14pm UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/4 "2020-04-28T19:14:35Z")
I understand the example I believe.
However, my example is that I have multiple tags beyond that such as:
1. Tags environment (solved above)
2. add tag for scope of application
3. add tag for cost center
4. add tag for country
No tags are showing up in my test right now, so I'm not sure if this supposed. I don't just want environment, I might have 6+ tags to help filter down application type, geo location and more.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 28, 2020, 9:19pm UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/5 "2020-04-28T21:19:52Z")
@sheldonh when you say no tags are showing up, do you mean in the uptime UI?
I'm just now noticing that you're using the `target` option for the `add_tags` processor. For the Uptime UI you'll need to omit that option, we only show tags in the `tags` field. Since it looks like you want to namespace tags for various purposes, consider using a prefix for the namespace. So, maybe use tags like `env:prod11` or `scope:monitor`.
That said, we are actively discussing ways to create `groups` or `labels` or some similar notion within the Uptime UI, probably by saving a query.
We have an [old issue](https://github.com/elastic/kibana/issues/37107) tracking this, that will probably be replaced by a new one sometime soon.
It'd be great if we could hear more about your use case.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 26, 2020, 9:19pm UTC](https://discuss.elastic.co/t/heartbeat-tag-information/229702/6 "2020-05-26T21:19:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.