Individually tag instance in Azure VMSS












0















Is it possible to individually tag a specific vm instance in a scale set?



Something like this command:



az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"


SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:



curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"


However the response I get is:



az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>


Tried using:



 az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}


But no luck either, response is:



The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.









share|improve this question



























    0















    Is it possible to individually tag a specific vm instance in a scale set?



    Something like this command:



    az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"


    SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:



    curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"


    However the response I get is:



    az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>


    Tried using:



     az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}


    But no luck either, response is:



    The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.









    share|improve this question

























      0












      0








      0








      Is it possible to individually tag a specific vm instance in a scale set?



      Something like this command:



      az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"


      SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:



      curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"


      However the response I get is:



      az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>


      Tried using:



       az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}


      But no luck either, response is:



      The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.









      share|improve this question














      Is it possible to individually tag a specific vm instance in a scale set?



      Something like this command:



      az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"


      SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:



      curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"


      However the response I get is:



      az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>


      Tried using:



       az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}


      But no luck either, response is:



      The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.






      azure-vm-scale-set






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 8:31









      J00MZJ00MZ

      357312




      357312
























          1 Answer
          1






          active

          oldest

          votes


















          1














          It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.



          enter image description here



          About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.



          Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.






          share|improve this answer


























          • Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

            – J00MZ
            Nov 21 '18 at 4:22








          • 1





            Welcome to vote it, I have posted this feature request here.

            – Nancy Xiong
            Nov 21 '18 at 5:26











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370880%2findividually-tag-instance-in-azure-vmss%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.



          enter image description here



          About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.



          Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.






          share|improve this answer


























          • Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

            – J00MZ
            Nov 21 '18 at 4:22








          • 1





            Welcome to vote it, I have posted this feature request here.

            – Nancy Xiong
            Nov 21 '18 at 5:26
















          1














          It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.



          enter image description here



          About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.



          Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.






          share|improve this answer


























          • Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

            – J00MZ
            Nov 21 '18 at 4:22








          • 1





            Welcome to vote it, I have posted this feature request here.

            – Nancy Xiong
            Nov 21 '18 at 5:26














          1












          1








          1







          It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.



          enter image description here



          About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.



          Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.






          share|improve this answer















          It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.



          enter image description here



          About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.



          Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 20 '18 at 5:08

























          answered Nov 20 '18 at 3:18









          Nancy XiongNancy Xiong

          3,003118




          3,003118













          • Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

            – J00MZ
            Nov 21 '18 at 4:22








          • 1





            Welcome to vote it, I have posted this feature request here.

            – Nancy Xiong
            Nov 21 '18 at 5:26



















          • Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

            – J00MZ
            Nov 21 '18 at 4:22








          • 1





            Welcome to vote it, I have posted this feature request here.

            – Nancy Xiong
            Nov 21 '18 at 5:26

















          Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

          – J00MZ
          Nov 21 '18 at 4:22







          Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?

          – J00MZ
          Nov 21 '18 at 4:22






          1




          1





          Welcome to vote it, I have posted this feature request here.

          – Nancy Xiong
          Nov 21 '18 at 5:26





          Welcome to vote it, I have posted this feature request here.

          – Nancy Xiong
          Nov 21 '18 at 5:26


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370880%2findividually-tag-instance-in-azure-vmss%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          鏡平學校

          ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

          Why https connections are so slow when debugging (stepping over) in Java?