Failing to update with MonitorUpdateRequest

Open

#2,043 opened on Jul 12, 2024 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: python
Domain: api

Research direction

Start by reproducing the update monitor call with the exported JSON and the datadog-api-client-2.26.0 environment, then inspect MonitorUpdateRequest and the calling update monitor method. Done means the exported monitor data can be parsed and monitors update without the restriction_policy attribute error.

Written by the indexing model from the issue text.

Description

kind/bug stale

Describe the bug
A clear and concise description of what the bug is.

When my team updates monitoring via the datadog api client using the calling update monitor method the MonitorUpdateRequest returns an attribute error.

datadog_api_client.exceptions.ApiAttributeError: MonitorUpdateRequest has no attribute 'restriction_policy' at ['restriction_policy']

To Reproduce
Steps to reproduce the behavior:

Export monitor as a JSON
Add to code base
Use the datadog api to update monitoring
See error

Expected behavior
A clear and concise description of what you expected to happen.

Our monitors should update and not return an error when parsing the JSON.

Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 2024-07-12 at 12 17 13 PM

Environment and Versions (please complete the following information):
A clear and precise description of your setup:

Latest version of datadog api client, datadog-api-client-2.26.0

Dominant language: Python
Stars: 166
Forks: 55
Avg merge: 2d 17h
Merged PRs (30d): 73

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[essnmx] Fix typo in NXLauetof application definition Open

essnmx good first issue

Difficulty 1/5 Under an hour Newbie friendliness 95/100

scipp/ess#760 · Opened Sep 23, 2026
[Feature] 奇物选择添加优先级 Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

syfoud/Simulated_Scepter#174 · Opened Sep 23, 2026
garak adapter grades a NaN detector score as PASS Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Giskard-AI/giskard-oss#2840 · 1 comment · Opened Sep 23, 2026
A claim comment carrying the issue number is silently declined while the workflow reports success Open

area: repo bug perceived difficulty: 2

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Nitjsefnie-Harness-Commons/daedalus#926 · Opened Sep 23, 2026
`IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

yeti-platform/yeti#1380 · Opened Sep 23, 2026

More Python issues