New Log Analytics Sku - PerGB2018 #1513
Closed
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
|
Can one of the admins verify this patch? |
|
|
MattMencel
force-pushed
the
dev
branch
2 times, most recently
from
11753d4 to
d6a2956
Compare
MattMencel
changed the title
|
I was informed I should have updated the |
|
Closing as this should be fixed in the specs repo. Once the change has been merged into the specs repo we'll get it into the SDK. |
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.
devbranch, or I'm fixing a bug that warrants its own release and I'm targeting themasterbranch.On April 3rd, 2018 Microsoft changed the pricing tiers for Log Analytics.
https://azure.microsoft.com/en-us/blog/introducing-a-new-way-to-purchase-azure-monitoring-services/
I did some research and was able to find the new Sku name,
PerGB2018. This is not officially documented anywhere yet that I can find. I successfully tested a deployment with the Azure RM Terraform provider using the new Sku with my forked code.I believe the old Skus will still work if you have an older Azure subscription and have deployed Log Analytics services prior to April 3, 2018. I am unable to test this in my subscription.