Skip to content
This repository was archived by the owner on May 8, 2026. It is now read-only.

Commit b17e9aa

Browse files
authored
Merge pull request #95 from department-of-veterans-affairs/Get-support-update
Update get-support.md
2 parents b2979fa + f716ba5 commit b17e9aa

1 file changed

Lines changed: 46 additions & 18 deletions

File tree

docs/get-support.md

Lines changed: 46 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,66 @@
11
---
2-
title: Get Support
2+
title: Event Bus Contact and Support
33
---
44

5-
# **Get Support**
5+
# **Event Bus Contact and Support**
66

7-
## **Report an incident**
7+
## **Learn More About Enterprise Event Bus**
88

9-
To report a security or privacy incident, or an urgent critical operational incident requiring immediate support, check the [#event-bus-support Slack channel][slack-#event-bus-support] Topic for our PagerDuty email address. Sending an email to this PagerDuty address will generate a notification to the on-call engineer's mobile device 24/7 as long as the email was sent from a @va.gov email address. You can expect a response within 30 minutes in the [#event-bus-support Slack channel][slack-#event-bus-support] in the Office of CTO @VA workspace.
9+
Interested in learning how Enterprise Event Bus (EEB) can benefit you? Our team is ready to help you understand the capabilities, architecture, and best practices for EEB implementation.
1010

11-
If you prefer to use a non @va.gov email address to trigger notifications to the on-call engineer's mobile device, you can request a specific email address, or workplace email domain, be added to an "allowed list". To initiate this request, send a message explaining your need to the [#event-bus-support Slack channel][slack-#event-bus-support] and the appropriate personnel will reach out to you.
11+
## **Quick Reference**
1212

13-
Please include the following information in your email:
13+
| Support Type | Contact Method | Response Time |
14+
| :---: | :---: | :---: |
15+
| General Contact | OCTO Slack: #event-bus-support |1 hour (during support hours)|
16+
| General Contact | Email: OITEnterpriseEventBus@va.gov | Varies |
17+
| Urgent/Critical Incidents and Security/Privacy Incidents |OCTO Slack: #event-bus-support |1 hour (during support hours) |
18+
| Urgent/Critical Incidents and Security/Privacy Incidents | Email: found on OCTO Slack [#event-bus-support][slack-#event-bus-support] | 30 minutes |
1419

15-
* Is this a security or privacy incident? Yes/No
16-
* Which environment is impacted? Sandbox/Production
17-
* Briefly, what is the impact of the incident?
20+
## **General Contact and Support**
1821

19-
## **General support requests**
22+
To learn more or for non-urgent questions and support:
23+
- **OCTO Slack:** [#event-bus-support][slack-#event-bus-support]in the Office of CTO @VA workspace
24+
- **Email:** OITEnterpriseEventBus@va.gov
2025

21-
For non-urgent support requests, the best way to request support from the Event Bus Team is to reach out to us via the [#event-bus-support Slack channel][slack-#event-bus-support] in the Office of CTO @VA workspace.
26+
**Best Practice:** Please use the public channel rather than direct messaging team members. This helps others learn from shared questions and answers.
2227

23-
Please avoid direct messaging an Event Bus team member in Slack. Chatting openly in the channel allows others to learn from the questions and answers discussed.
28+
## **Support Hours**
2429

25-
Event Bus Slack channel support hours are from 12pm - 5pm ET, Monday through Friday, with the exception of federal holidays. Often, an engineer will respond by 9am ET if they live in the Eastern or Central timezones. You can expect a response within 1 hour during the support hours.
30+
- **Slack Support Hours:** Monday - Friday, 12pm - 5pm ET (excluding federal holidays)
31+
- **Note:** Engineers often respond by 9am ET if they're in Eastern or Central timezones
32+
- **24/7 Support:** Available for urgent incidents via PagerDuty email which can be found on OCTO Slack [#event-bus-support][slack-#event-bus-support] (Must email from a @va.gov address. If you do not have a @va.gov email address, see below.)
2633

34+
## **Reporting Urgent Incidents**
2735

28-
## **Slack service notifications**
36+
When you need immediate assistance with a critical operational, security, or privacy incident:
2937

30-
Alerts and warnings from Event Bus monitoring can be found in the following Slack channels:
38+
1. Check the [#event-bus-support][slack-#event-bus-support] OCTO Slack channel first
39+
2. Email the PagerDuty email **from a @va.gov email address**
40+
- This will alert the on-call engineer's mobile device 24/7
41+
- Response expected within 30 minutes in the [#event-bus-support][slack-#event-bus-support] OCTO Slack Channel
3142

43+
**Include in your email:**
3244

33-
* [#ves-event-bus-sandbox-alerts (must be in the Office of CTO @VA workspace)][slack-#ves-event-bus-sandbox-alerts]
34-
* [#ves-event-bus-prod-alerts (must be in the Office of CTO @VA workspace)][slack-#ves-event-bus-prod-alerts]
35-
* [#vaapi-lhdi-customer-env-alerts (must be in the Lighthouse workspace)][slack-#vaapi-lhdi-customer-env-alerts] (includes alerts for the wider LHDI environment)
45+
- Is this a security or privacy incident? (Yes/No)
46+
- Which environment is impacted? (Sandbox/Production)
47+
- Brief description of the incident's impact
48+
49+
## **Using Non-VA Email Addresses**
50+
51+
If you need to use a non @va.gov email address to contact the on-call engineer:
52+
53+
1. Send a message to the [#event-bus-support][slack-#event-bus-support] OCTO Slack channel
54+
2. Request your email address or domain be added to the "allowed list"
55+
3. Explain your specific need for using a non-VA email address
56+
57+
## **Monitoring and Alerts**
58+
59+
Stay informed about Event Bus status through these Slack channels:
60+
61+
- **Sandbox Environment:** [#ves-event-bus-sandbox-alerts (must be in the Office of CTO @VA workspace)][slack-#ves-event-bus-sandbox-alerts]
62+
- **Production Environment:** [#ves-event-bus-prod-alerts (must be in the Office of CTO @VA workspace)][slack-#ves-event-bus-prod-alerts]
63+
- **LHDI Environment:** [#vaapi-lhdi-customer-env-alerts (must be in the Lighthouse workspace)][slack-#vaapi-lhdi-customer-env-alerts]
3664

3765
<!-- links -->
3866
[slack-#event-bus-support]: https://dsva.slack.com/archives/C074VK55M9P

0 commit comments

Comments
 (0)