[AZINTS-3391] add azure storage monitoring setup #28861
Open
Conversation
This file contains hidden or 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
Preview links (active after the
|
ava-silver
force-pushed
the
ava.silver/azints-3391/add-azure-storage-monitoring-setup
branch
from
fc0d40e to
6c767c3
Compare
iadjivon
reviewed
Apr 18, 2025
| private: true | ||
| --- | ||
|
|
||
| <div class="alert alert-info">Storage Monitoring is in Preview.</div> | ||
|
|
||
| ## Overview | ||
|
|
||
| Storage Monitoring for Amazon S3 & Google Cloud Storage provides deep, prefix-level analytics to help you understand exactly how your storage is being used, detect potential issues before they impact operations, and make data-driven decisions about storage optimization. Use these insights to help you track storage growth, investigate access patterns, and optimize costs. | ||
| Storage Monitoring for Amazon S3, Google Cloud Storage, and Azure Blob Storage provides deep, prefix-level analytics to help you understand exactly how your storage is being used, detect potential issues before they impact operations, and make data-driven decisions about storage optimization. Use these insights to help you track storage growth, investigate access patterns, and optimize costs. |
There was a problem hiding this comment.
Suggested change
| Storage Monitoring for Amazon S3, Google Cloud Storage, and Azure Blob Storage provides deep, prefix-level analytics to help you understand exactly how your storage is being used, detect potential issues before they impact operations, and make data-driven decisions about storage optimization. Use these insights to help you track storage growth, investigate access patterns, and optimize costs. | |
| Storage Monitoring for Amazon S3, Google Cloud Storage, and Azure Blob Storage provides deep, prefix-level analytics to help you understand exactly how your storage is being used. It also detect potential issues before they impact operations, and make data-driven decisions about storage optimization. Use these insights to help you track storage growth, investigate access patterns, and optimize costs. |
Splitting the sentence to make it easier to follow
iadjivon
reviewed
Apr 18, 2025
|
|
||
| You can set this up either manually or using the provided CloudFormation templates. Access your Storage Monitoring data by navigating to **Infrastructure -> Storage Monitoring**. | ||
| Access your Storage Monitoring data by navigating to **Infrastructure -> Storage Monitoring**. |
There was a problem hiding this comment.
Suggested change
| Access your Storage Monitoring data by navigating to **Infrastructure -> Storage Monitoring**. | |
| Access your Storage Monitoring data by navigating to **Infrastructure > Storage Monitoring**. |
iadjivon
reviewed
Apr 18, 2025
| | bash -s -- <client_id> <subscription_id> <comma_separated_storage_account_names> | ||
| ``` | ||
|
|
||
| Ensure your [shell environment][302] is set to Bash before running the script. Ensure that the you replace the various placeholder inputs with the correct values: |
There was a problem hiding this comment.
Suggested change
| Ensure your [shell environment][302] is set to Bash before running the script. Ensure that the you replace the various placeholder inputs with the correct values: | |
| Before running the script, set your [shell environment][302] to Bash and replace the various placeholder inputs with the correct values: |
iadjivon
reviewed
Apr 18, 2025
|
|
||
| {{% tab "Azure Portal" %}} | ||
|
|
||
| For Each Storage Account you wish to monitor: |
There was a problem hiding this comment.
Suggested change
| For Each Storage Account you wish to monitor: | |
| For Each Storage Account you wish to monitor, follow all of the steps here: |
iadjivon
reviewed
Apr 18, 2025
|
|
||
| #### Create a blob inventory policy | ||
| 1. In the Azure portal, navigate to your Storage Account. | ||
| 2. Go to **Data management** -> **Blob inventory**. |
There was a problem hiding this comment.
Suggested change
| 2. Go to **Data management** -> **Blob inventory**. | |
| 2. Go to **Data management** > **Blob inventory**. |
iadjivon
reviewed
Apr 18, 2025
|
|
||
| #### Add the role assignment | ||
| 1. In the Azure portal, navigate to your Storage Account. | ||
| 2. Go to **Data storage** -> **Containers**. |
There was a problem hiding this comment.
Suggested change
| 2. Go to **Data storage** -> **Containers**. | |
| 2. Go to **Data storage** > **Containers**. |
iadjivon
reviewed
Apr 18, 2025
| 2. Go to **Data storage** -> **Containers**. | ||
| 3. Click on the **datadog-storage-monitoring** container. | ||
| 4. Click on **Access control (IAM)** in the left-hand menu. | ||
| 5. Click **Add** -> **Add role assignment**. |
There was a problem hiding this comment.
Suggested change
| 5. Click **Add** -> **Add role assignment**. | |
| 5. Click **Add** > **Add role assignment**. |
iadjivon
reviewed
Apr 18, 2025
|
|
||
| ### Post-Installation | ||
|
|
||
| Once you finish with the above steps, fill out the [post-setup form][310]. |
There was a problem hiding this comment.
Suggested change
| Once you finish with the above steps, fill out the [post-setup form][310]. | |
| After you finish with the above steps, fill out the [post-setup form][310]. |
iadjivon
reviewed
Apr 18, 2025
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?
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes