Nov 09 2020 07:57 AM - edited Nov 10 2020 04:26 AM
I get blocked access to Sandbox resources in following learning example:
"Monitor the health of your Azure virtual machine by using Azure Metrics Explorer and metric alerts",
direct link:
https://docs.microsoft.com/en-us/learn/modules/monitor-azure-vm-using-diagnostic-data/
I can believe that command sequence in unit 8 which should stress VM CPU, cause issue:
sudo stress --cpu 16 -v -t 10m
Directly after execution of the sequence my access to Sandbox resources was blocked, I sent appeal as requested. As well I sent feedback - content of the online course must be reviewed, and instructions
to stop the CPU stress sequence added, before user leave Azure CLI session or move to next example.
Nov 11 2020 07:59 AM
Solution@Dimitri-K Thanks for noting that, I'll let the content team responsible for that module know. They will certainly trip up the fraud detection with that statement!
Nov 12 2020 12:05 AM - edited Nov 12 2020 03:51 AM
Hello, Mark
Thank you for your reply and support actions.
I would like to add more technical details - I receive 2 alert Emails from this
learning example, so advised VM CPU stress sequence did right job.
However, requested by command sequence 16 workers and timeout 10 minutes
was enough to trigger alarm of Sandbox misuse.
Moreover, in next example, unit 4, similar sequence "- sudo stress --cpu 1" in use,
without timeout, direct link:
https://docs.microsoft.com/en-us/learn/modules/incident-response-with-alerting-on-azure/4-exercise-m...
That exact entry point of the Sandbox request where I face block message
after execution of the previous example.
Will wait until my appeal is reviewed by appropriate support team and
continue my journey.
Regards,
Dimitri
Nov 12 2020 06:56 AM
Nov 13 2020 12:51 AM - edited Nov 13 2020 12:51 AM
Hi,
Would like to finalize this post with positive feedback - my appeal was reviewed and
access to Sandbox resources restored. I was able to complete my module without
technical issues or errors.
Thanks.
Regards,
Dimitri
Nov 11 2020 07:59 AM
Solution@Dimitri-K Thanks for noting that, I'll let the content team responsible for that module know. They will certainly trip up the fraud detection with that statement!