Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

Anybody noticing dogpush not working as of yesterday? #12

Open
gyoza opened this issue Mar 1, 2017 · 4 comments
Open

Anybody noticing dogpush not working as of yesterday? #12

gyoza opened this issue Mar 1, 2017 · 4 comments

Comments

@gyoza
Copy link

gyoza commented Mar 1, 2017

I think datadog changed their APi and now pushing does nothing as it says that the monitors that were updated in the previous run are still out of date on datadog.

@nandrienko
Copy link
Contributor

If I'm seeing it right, it seems datadog does not give us back same definition of monitors as we've given to them. Due to that, each time dogpush is ran, it tries to update all monitors.

@gyoza
Copy link
Author

gyoza commented Mar 2, 2017

So, i was able to add to the ignore items the (forgive me cause im going from memory at home) overall_state_modified. Once added, and you run a diff DogPush will say there are no changes. This is great!

At this point i went to make minor changes to the monitors and push them out but it seems the push is still failing to send new data through the API as those changes never stick.

@thisRalf
Copy link

thisRalf commented Mar 2, 2017

I'm experiencing this issue as well. Datadog added a field called "overall_state_modified" on Tuesday which coincided with the breaking of the push feature. We were told if we remove that field from our yaml files it would push, but after doing so, its still is not working.

Anybody have any ideas?

@alexef
Copy link
Contributor

alexef commented Mar 3, 2017

This PR is fixing it for me: #11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants