by Contributed | Dec 13, 2020 | Technology
This article is contributed. See the original author and article here.
This installment is part of a broader series to keep you up to date with the latest features in Azure Sentinel. The installments will be bite-sized to enable you to easily digest the new content.
Note: The Log Analytics agent is sometimes referred to as the OMS Agent or the Microsoft Monitoring Agent (MMA).
We’ve made some improvements to the Log Analytics agent that will make it even easier and flexible for you to use across a wider range of platforms.
If you’re unfamiliar with this product, the Azure Log Analytics agent collects telemetry from Windows and Linux virtual machines in any cloud, on-premises machines, and those monitored by System Center Operations Manager and sends it collected data to your Log Analytics workspace. You can read more about it here. You can also read the release notes for the agent here.
In Azure Sentinel, it can be used to facilitate the sending of the following events to your workspace:
- Windows Security events
- Syslog
- Common Event Format (CEF) logs
- Windows Firewall logs
- DNS logs
- IIS logs
- Network connections
Support for new operating systems
The Log Analytics agent can now be installed on an even wider range of Linux distros. We recently added support for:
- CentOS 8
- RedHat 8
- SUSE Linux 15
Click here to see the full list of supported OSs.
Support for Python 3
Probably even more anticipated then our expanded OS support, we are happy to announce that starting from Agent version 1.13.27, the Linux Log Analytics Agent will support both Python 2 and 3. This means that customers now have the option to use whatever Python version they prefer (or whatever comes by default on their machine). This works both for a direct install of the agent and when installing as part of the CEF log forwarder.
Get started today!
Try out the new connector and let us know your feedback using any of the channels listed in the Resources.
You can also contribute new connectors, workbooks, analytics and more in Azure Sentinel. Get started now by joining the Azure Sentinel Threat Hunters GitHub community and follow the guidance.
With thanks to @Jeremy Tan, @Chi_Nguyen and @Ofer_Shezaf for their inputs on this blog post.
by Contributed | Dec 13, 2020 | Technology
This article is contributed. See the original author and article here.
Final Update: Sunday, 13 December 2020 20:02 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 12/13, 19:40 UTC. Our logs show the incident started on 11/20, 02:40 UTC and that during the duration of ~23 days that it took to resolve the issue some customers experienced alerting failures. For new alerts that fired post 12/13 19:40 UTC, these are accurately reflecting the state of the resource health. For alerts in Fired/Resolved status between 11/20 02:40 UTC and 12/13 19:40 UTC, please depend on notifications that are setup through Action groups for accurate status of resource health.
Root Cause: Root cause has been isolated to data from older version of code which was impacting Metric Alerts in Azure Portal.
Incident Timeline: ~23 days – 11/20, 02:40 UTC through 12/13, 19:40 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.
-Anupama
Update: Sunday, 13 December 2020 18:35 UTC
Root cause has been isolated to data from old version of code which was impacting Metric Alerts in Azure Portal. Mitigation is complete on most of the instances and is in progress for last couple of instances.
- Work Around: None
- Next Update: Before 12/13 21:00 UTC
-Anupama
Update: Sunday, 13 December 2020 15:06 UTC
Root cause has been isolated to data from old version of code which was impacting Metric Alerts in Azure Portal. To address this issue we have rolled out a hotfix deployment. Some customers may continue to experience alerting failures.
- Work Around: None
- Next Update: Before 12/13 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sandeep
Initial Update: Sunday, 13 December 2020 11:18 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers may see alerts still active in the Azure Portal even though they receive resolved notification. Our logs show the incident started on 12/07, ~15:00 UTC.
- Work Around: None
- Next Update: Before 12/13 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sandeep
by Contributed | Dec 13, 2020 | Technology
This article is contributed. See the original author and article here.
Update: Sunday, 13 December 2020 18:35 UTC
Root cause has been isolated to data from old version of code which was impacting Metric Alerts in Azure Portal. Mitigation is complete on most of the instances and is in progress for last couple of instances.
- Work Around: None
- Next Update: Before 12/13 21:00 UTC
-Anupama
Update: Sunday, 13 December 2020 15:06 UTC
Root cause has been isolated to data from old version of code which was impacting Metric Alerts in Azure Portal. To address this issue we have rolled out a hotfix deployment. Some customers may continue to experience alerting failures.
- Work Around: None
- Next Update: Before 12/13 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sandeep
Initial Update: Sunday, 13 December 2020 11:18 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers may see alerts still active in the Azure Portal even though they receive resolved notification. Our logs show the incident started on 12/07, ~15:00 UTC.
- Work Around: None
- Next Update: Before 12/13 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sandeep
by Contributed | Dec 13, 2020 | Technology
This article is contributed. See the original author and article here.
Initial Update: Sunday, 13 December 2020 11:18 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers may see alerts still active in the Azure Portal even though they receive resolved notification. Our logs show the incident started on 12/07, ~15:00 UTC.
- Work Around: None
- Next Update: Before 12/13 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sandeep
by Contributed | Dec 13, 2020 | Technology
This article is contributed. See the original author and article here.
What is Agile?
Agile is a term used to describe approaches to software development emphasizing incremental delivery, team collaboration, continual planning, and continual learning. The term “Agile” was coined in 2001 in the Agile Manifesto. The manifesto set out to establish principles to guide a better approach to software development. At its core, the manifesto declares 4 value statements representing the foundation of the agile movement. As written, the manifesto states…
What is Scrum?
Scrum is a framework used by teams to manage their work. Scrum implements the principles of Agile as a concrete set of artifacts, practices, and roles
There are some important milestones as mentioned in the following diagram
How we can Manager Scrum Using Microsoft 365?
There are a lot of tools in Microsoft 365 that allow to run Scrum projects, like the following:
1- Microsoft Teams is the core where we can use to connect other tools, still you can reach to the other tools directly, with Teams you can have daily standup calls, planning and retro meetings, check this TechNet wiki article
2- Microsoft Forms: with forms you can create surveys to get the complexity/T-shirt sizes of User stories during planning check this wiki article
3- Planner: with planner you can create User Stories/Tasks and assign to the team check this TechNet wiki Planner
4- SharePoint: You can share your files and you can use lists to track your bugs and defects.
So Microsoft 365 is very powerful and allow scrum masters and product owners to manage scrum projects.
By John Naguib ( Twitter , TechNet Profile , MVP Profile )
Recent Comments