Blog Feed Post

Manage planned downtimes with maintenance windows

The latest release of Dynatrace enables you to define maintenance windows using either the Dynatrace API or the Dynatrace web interface.

Even if your organization runs a ‘100% availability’ production environment, there are times when your DevOps team must roll out new software updates. Various release-deployment strategies are available for this, including performing rolling updates and iteratively updating parts of instances. No matter which release-rollout strategy your DevOps team uses, it’s good practice to keep your performance monitoring system informed of these activities to ensure accurate monitoring data.

Maintenance window overview

Dynatrace distinguishes between two types of maintenance windows: planned maintenance windows and unplanned maintenance windows. Planned maintenance windows are configured in advance while unplanned windows are added retroactively to notify Dynatrace of unexpected downtimes that’s shouldn’t be factored into overall performance and availability metrics. Dynatrace adapts its baselining, alerting, and problem detection behavior based the type of the configured maintenance window.

Each maintenance window you configure has a name and description that you can use to provide contextual information about the purpose of the maintenance window.

Once a maintenance window is defined, Dynatrace automatically excludes the configured time period from its baseline calculations. With this approach, any response time anomalies that occur during the corresponding rolling update won’t negatively influence your overall service and application baselines.

With respect to baselining, it’s a good idea to define your maintenance windows before performing any load testing. Using maintenance windows during load testing ensures that any load spikes, longer-than-usual response times, or increased error rates won’t negatively influence your overall baselining.

To define a maintenance window via the Dynatrace UI

  1. Go to Settings > Maintenance > Maintenance windows.
  2. Define a Name for the maintenance window.
  3. Provide a Description of the purpose of the maintenance window.
  4. From the Maintenance type drop list, select Planned or Unplanned.
  5. If the maintenance window is to recur on a regular schedule, use the drop lists to define a daily, weekly, or monthly recurring schedule.
  6. From the Problem detection and alerting drop list, specify the action that Dynatrace should take if a monitored component experiences a problem during a scheduled maintenance window:
    • Detect problems and alert: Dynatrace will automatically detect and report all problems as usual and display a maintenance window icon (wrench and bolt icon, see below) on each problem that is detected during a maintenance window.
    • Detect problems but don’t alert: Problems will be detected but Dynatrace won’t send out alerts for the problems. Each problem will be listed on the Problems page with a maintenance window icon.
    • Disable problem detection: Detection and alerting of problems is disabled. Problems that occur during scheduled maintenance windows will not be included on the Problems page and no alerts will be sent out.
  7. The Scope of maintenance section of the page enables you to further reduce the set of monitored components that are included in the configured maintenance window. You can include entity tags for specific ApplicationsServices, or Hosts (see host tag example in the image below) or for tagged groups of components (for example, all hosts that have the tag PROD. If no scope filter is defined, the maintenance window affects your entire environment.

Define maintenance windows using REST API

Most users find it easy to define maintenance windows and downtimes using the settings page detailed above. Your DevOps team will however likely prefer to use our automation REST API to define maintenance windows. With our REST API, you get all the functionality you need to read, create, and update maintenance window configurations.

To read all defined maintenance windows, execute an HTTP GET call to /api/v1/maintenance/. The result is shown below:

		"id":"New application deployment",
		"We will deploy a new easyTravel application version",
			"maintenanceStart":"2017-08-29 14:43",
			"maintenanceEnd":"2017-08-29 15:43",

An HTTP POST request to /api/v1/maintenance/ with the payload below creates a new maintenance window:

	"id" : "theWindowId",
	"type": "Planned",
	"description" : "Again another release",
	"suppressAlerts" : true,
	"suppressProblems" : false,
	"scope" : {
		"entities" : [
			"HOST-0B3371A5AC53FF12", "SERVICE-13FA1F30530CDEE1"
		"matches" : [
				"type" : "HOST",
				"tags" : [ 
						"context" : "AWS",
						"key" : "myTag1", 
						"value" : "myValue1"
					{	"key" : "myTag2" }
	"schedule" : {
		"type" : "Month",
		"timezoneId" : "Universal",
		"maintenanceStart" : "2017-01-01 00:00",
		"maintenanceEnd" : "2017-10-01 00:00",
		"recurrence" : {
			"dayOfMonth" : 4,
			"start" : "11:00",
			"duration" : 30

Refer to Dynatrace Help for more details about our maintenance window API.

Once you’ve defined your maintenance windows, Dynatrace flags all problems that occur during maintenance windows with a special maintenance (wrench and bolt) icon (see examples below). If you chose to completely disable problem detection during maintenance windows, no detected problems will be displayed here.

The Problems page filters now include an Under maintenance filter that enables you to view a list of problems that occurred during maintenance windows (see below).

If you open a problem that occurred during a maintenance window, Dynatrace shows a header on the Problem page, as shown below.

Even if you aren’t within a problem context and you select a global timeframe in which a selected host was under maintenance, Dynatrace shows you the details on the Maintenance tile. If the host is included in multiple, maintenance periods, Dynatrace shows you the most recent window and a count of how many maintenance windows the host experienced during the selected timeframe.

The newly introduced maintenance window feature enables Dynatrace you identify periods of possibly abnormal operation, such as downtimes, reduced performance periods, and high traffic events during load tests. Defining maintenance windows during abnormal operation times helps you reduce alert spam and keep your baseline clean for accurate monitoring and alerting. By providing a convenient and powerful automation API your DevOps teams can automatically create or modify maintenance windows in sync with your release pipeline.

One additional aspect that will be part of an upcoming release is the exclusion of planned maintenance window from your SLA reports. So stay tuned.

The post Manage planned downtimes with maintenance windows appeared first on Dynatrace blog – monitoring redefined.

Read the original blog entry...

More Stories By Dynatrace Blog

Building a revolutionary approach to software performance monitoring takes an extraordinary team. With decades of combined experience and an impressive history of disruptive innovation, that’s exactly what we ruxit has.

Get to know ruxit, and get to know the future of data analytics.

Latest Stories
Daniel Jones is CTO of EngineerBetter, helping enterprises deliver value faster. Previously he was an IT consultant, indie video games developer, head of web development in the finance sector, and an award-winning martial artist. Continuous Delivery makes it possible to exploit findings of cognitive psychology and neuroscience to increase the productivity and happiness of our teams.
The standardization of container runtimes and images has sparked the creation of an almost overwhelming number of new open source projects that build on and otherwise work with these specifications. Of course, there's Kubernetes, which orchestrates and manages collections of containers. It was one of the first and best-known examples of projects that make containers truly useful for production use. However, more recently, the container ecosystem has truly exploded. A service mesh like Istio addr...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Business professionals no longer wonder if they'll migrate to the cloud; it's now a matter of when. The cloud environment has proved to be a major force in transitioning to an agile business model that enables quick decisions and fast implementation that solidify customer relationships. And when the cloud is combined with the power of cognitive computing, it drives innovation and transformation that achieves astounding competitive advantage.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...
"NetApp is known as a data management leader but we do a lot more than just data management on-prem with the data centers of our customers. We're also big in the hybrid cloud," explained Wes Talbert, Principal Architect at NetApp, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Evan Kirstel is an internationally recognized thought leader and social media influencer in IoT (#1 in 2017), Cloud, Data Security (2016), Health Tech (#9 in 2017), Digital Health (#6 in 2016), B2B Marketing (#5 in 2015), AI, Smart Home, Digital (2017), IIoT (#1 in 2017) and Telecom/Wireless/5G. His connections are a "Who's Who" in these technologies, He is in the top 10 most mentioned/re-tweeted by CMOs and CIOs (2016) and have been recently named 5th most influential B2B marketeer in the US. H...
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of bus...
With 10 simultaneous tracks, keynotes, general sessions and targeted breakout classes, @CloudEXPO and DXWorldEXPO are two of the most important technology events of the year. Since its launch over eight years ago, @CloudEXPO and DXWorldEXPO have presented a rock star faculty as well as showcased hundreds of sponsors and exhibitors! In this blog post, we provide 7 tips on how, as part of our world-class faculty, you can deliver one of the most popular sessions at our events. But before reading...
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.