Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync master #791

Merged
merged 21 commits into from
May 12, 2017
Merged

Sync master #791

merged 21 commits into from
May 12, 2017

Conversation

mxinden
Copy link
Member

@mxinden mxinden commented May 12, 2017

No description provided.

prymitive and others added 21 commits April 26, 2017 19:10
When user creates a new silence with regex match it's left to the user to anchor it, which is not consistent with Prometheus regex handling (promql/functions.go#L818).
AlertStatus doesn't have json tag with the field name, so it's serialized into 'Status', and it's the only uppercase field in the alert object. Tag it with 'status' name for consistency
Locking is a bit tricky there since some state-modifying methods will call to other methods that also modify marker state, simple defer won't work.
…t_route

Throw error when continue in route root of Alertmanager config
Use proper locks when modifying alert status
Found that we are only defining MarshalJSON for the Regexp type for
references not for the direct object

Also took the time to simplify the json.Unmarshal usage in cli/config.go
* Added unit test for continue in root route error

* replaced %v with %q
docs: Add note to not load balance Alert trafic
@mxinden mxinden merged commit f298a21 into prometheus:ui-rewrite May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants