Skip to content

[Azure Logs] Clarify the Storage Account container role in the integration #5604

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.

Sign up for GitHub

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

Merged
merged 8 commits into from
Mar 24, 2023
Merged

[Azure Logs] Clarify the Storage Account container role in the integration #5604

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
f8bab44
Clarify that the SA container is required
zmoog Mar 21, 2023
e9d575c
Add more details
zmoog Mar 21, 2023
cd6536b
Add a link requirements and setup instructions
zmoog Mar 22, 2023
e166ea9
Update changelog
zmoog Mar 22, 2023
bcbf721
Apply suggestions from code review
zmoog Mar 23, 2023
631e99f
Revise and clean up data streams docs
zmoog Mar 23, 2023
3e47d20
Update packages/azure/_dev/build/docs/README.md
zmoog Mar 23, 2023
ee7789d
Fix typo
zmoog Mar 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix typo
  • Loading branch information
@zmoog
zmoog committed Mar 24, 2023
commit ee7789d5800ab1c2d559c0c7ba09d172c900da2a
2 changes: 1 addition & 1 deletion packages/azure/_dev/build/docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ To learn more about Event Hubs, refer to [Features and terminology in Azure Even

The [Storage account](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview) is a versatile Azure service that allows you to store data in various storage types, including blobs, file shares, queues, tables, and disks.

The Azure Logs integration requieres a Storage account container to work. The integration uses the Storage account container for checkpointing; it stores data about the Consumer Group (state, position, or offset) and shares it among the Elastic Agents. Sharing such information allows multiple Elastic Agents assigned to the same agent policy to work together; this enables horizontal scaling of the logs processing when required.
The Azure Logs integration requires a Storage account container to work. The integration uses the Storage account container for checkpointing; it stores data about the Consumer Group (state, position, or offset) and shares it among the Elastic Agents. Sharing such information allows multiple Elastic Agents assigned to the same agent policy to work together; this enables horizontal scaling of the logs processing when required.

```text
┌────────────────┐ ┌────────────┐
Expand Down
2 changes: 1 addition & 1 deletion packages/azure/docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ To learn more about Event Hubs, refer to [Features and terminology in Azure Even

The [Storage account](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview) is a versatile Azure service that allows you to store data in various storage types, including blobs, file shares, queues, tables, and disks.

The Azure Logs integration requries a Storage account container to work. The integration uses the Storage account container for checkpointing; it stores data about the Consumer Group (state, position, or offset) and share it among the Elastic Agents. Sharing such information allows multiple Elastic Agents assigned to the same agent policy to work together; this enables horizontal scaling of the logs processing when required.
The Azure Logs integration requires a Storage account container to work. The integration uses the Storage account container for checkpointing; it stores data about the Consumer Group (state, position, or offset) and shares it among the Elastic Agents. Sharing such information allows multiple Elastic Agents assigned to the same agent policy to work together; this enables horizontal scaling of the logs processing when required.

```text
┌────────────────┐ ┌────────────┐
Expand Down