# Kibana Alerts - Action on Recovered contains no context.group
**URL:** https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946
**Category:** Kibana
**Tags:** elastic-stack-alerting
**Created:** [March 31, 2021, 7:18pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946 "2021-03-31T19:18:45Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@JMisset88](https://discuss.elastic.co/u/JMisset88)
#### Post date: [March 31, 2021, 7:18pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946/1 "2021-03-31T19:18:45Z")
Hi,
We recently upgraded from Elastic 7.10.0 to 7.12.0. Mainly because I saw the new Alerting/Action functionality to only send an Alert on a Status Change (instead of on an interval). This is a very nice feature, however, I've noticed that the Recovered Alert does not contain the context.group information.
So whenever I get a slack Alert that tells me about the specific grouping variables (in our case, kubernetes.cluster.name, pod name, container name) I can see this information when the state changes to Alert, but not when the state changes to OK..
I have configured the following Slack Actions within the same Alert;
```auto
Run when: Alert
Message: A container will not start up. Cluster, Namespace, Pod, Container, Status:
{{context.group}}
```
```auto
Run when: Recovered
Message: A container Recovered. Cluster, Namespace, Pod, Container, Status:
{{context.group}}
```
This results in the following Slack messages:
```auto
A container will not start up. Cluster, Namespace, Pod, Container, Status:
testcluster, testnamespace, testservice-855bcd9849-rlvmt, testservice, CrashLoopBackOff
```
```auto
A container Recovered. Cluster, Namespace, Pod, Container, Status:
```
Am I doing something wrong? Is there another way to include the same information in the Recovered Alert?
Thanks in advance!
Jasper
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [April 1, 2021, 3:30pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946/2 "2021-04-01T15:30:03Z")
Hi @JMisset88 Welcome to the community!
No its not you. At this time that data is not available.
You can use the to help with the alignment / correlation at this time.
"alertId" : "{{alertId}}",
"alertInstanceId" : "{{alertInstanceId}}",
I will open an issue, when I do I will notify you perhaps you can add your use case ++ to it.
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [April 1, 2021, 6:33pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946/3 "2021-04-01T18:33:47Z")
Update there is an Issue [Here](https://github.com/elastic/kibana/issues/87048) . It is a bit low level but I I will add this / you discuss context / use case in there for reference.
---
### Author:  [@JMisset88](https://discuss.elastic.co/u/JMisset88)
#### Post date: [April 1, 2021, 7:20pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946/4 "2021-04-01T19:20:19Z")
Hi Stephen,
Thanks for your reply. I will check out the alertId's for correlation and keep an eye on the issue.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 29, 2021, 7:20pm UTC](https://discuss.elastic.co/t/kibana-alerts-action-on-recovered-contains-no-context-group/268946/5 "2021-04-29T19:20:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.