-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DBNBK-207, CRP-1288] private slack channels are also supported #27481
Merged
dd-mergequeue
merged 1 commit into
master
from
vickie/CRP-1288-slack-recipient-private-channels
Feb 6, 2025
Merged
[DBNBK-207, CRP-1288] private slack channels are also supported #27481
dd-mergequeue
merged 1 commit into
master
from
vickie/CRP-1288-slack-recipient-private-channels
Feb 6, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vjfridge
changed the title
private slack channels are also supported
[DBNBK-207, CRP-1288] private slack channels are also supported
Feb 6, 2025
Preview links (active after the
|
vjfridge
commented
Feb 6, 2025
To add Slack recipients, select the Slack workspace and channel from the available dropdowns. If you do not see any Slack workspaces available, ensure you have the Datadog [Slack Integration][8] installed. To send a test message to Slack, add a channel recipient and click **Send Test Message**. | ||
To add Slack recipients, select the Slack workspace and channel from the available dropdowns. If you do not see any Slack workspaces available, ensure you have the Datadog [Slack Integration][8] installed. All public channels within the Slack workspace should be listed automatically. To select a private Slack channel, make sure to invite the Datadog Slack bot to the channel in Slack. To send a test message to Slack, add a channel recipient and click **Send Test Message**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jcmaunsell
approved these changes
Feb 6, 2025
drichards-87
approved these changes
Feb 6, 2025
/merge |
Devflow running:
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
Feb 6, 2025
dd-mergequeue
bot
deleted the
vickie/CRP-1288-slack-recipient-private-channels
branch
February 6, 2025 17:10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Updates public docs for Scheduled Reports to reflect you can also send Slack reports to private Slack channels.
QA instructions
BEFORE: https://docs.datadoghq.com/dashboards/sharing/scheduled_reports/
AFTER: https://docs-staging.datadoghq.com/vickie/CRP-1288-slack-recipient-private-channels/dashboards/sharing/scheduled_reports/
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional Notes
Recent similar PRs: