Skip to content
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

Azure TSDB Enablement: storage_account datastream #7215

Closed
6 tasks done
ritalwar opened this issue Aug 2, 2023 · 1 comment · Fixed by #8064
Closed
6 tasks done

Azure TSDB Enablement: storage_account datastream #7215

ritalwar opened this issue Aug 2, 2023 · 1 comment · Fixed by #8064
Assignees

Comments

@ritalwar
Copy link
Contributor

ritalwar commented Aug 2, 2023

Test Environment Setup

  • Creation of Azure Test Environment

Datastream : storage_account

Verification and validation

  • Verification of data in visualisation after enabling TSDB flag in kibana
  • Verification of the count of documents (before & after TSDB enablement) in Discover Interface
  • Verify if dimension field mapping is correct in the data stream template.

Enable TSDB by default - #8064

Screenshots

Screenshot 2023-10-03 at 11 37 10 AM Screenshot 2023-10-03 at 11 37 38 AM Screenshot 2023-10-03 at 11 37 46 AM Screenshot 2023-10-03 at 11 38 19 AM Screenshot 2023-10-03 at 11 38 38 AM Screenshot 2023-10-03 at 11 38 45 AM Screenshot 2023-10-03 at 11 39 00 AM
@ritalwar
Copy link
Contributor Author

ritalwar commented Aug 11, 2023

Azure has additional dimensions for storage accounts, such as GeoType, Authentication, FileShare, BlobType, and tier. However, these dimensions are not currently included in this PR. As in the current Beats implementation, only two dimensions, namely ResponseType and ApiName, are allowed. I've used these two dimensions for enabling TSDB for now.

Although the current set of dimensions doesn't discard any documents, I'm in the process of using Azure Rest APIs to explore the values for the other dimensions defined by Azure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant