New issue
Advanced search Search tips

Issue 642134 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Document full JSON format for alerts

Project Member Reported by zhangtiff@chromium.org, Aug 29 2016

Issue description

Maybe in the README? 

I've been testing SoM locally by just directly sending JSON for alerts to the client.So far alerts-data.js in the test directory has been a useful reference for formatting the JSON, but it's missing some stuff like FindIt results. 

I feel like it would be a good idea to note the exact JSON format used for the frontend and maybe edit this each time we need to edit the alert JSON format. 
 
Status: Available (was: Untriaged)
This sounds like a great thing to document in the README! There's the original json format proposal: https://docs.google.com/document/d/10MESGzRy9uAy3Y3-PxUcjiuF3BD3FGGmCNvCjqm3WQQ/edit but reality has drifted a bit since then.


Should we put it in the README, or in the go source? It (should) be decently documented there; see https://cs.chromium.org/chromium/infra/go/src/infra/monitoring/messages/alerts.go?q=alerts.go&sq=package:chromium&l=82

We can improve it there, and then we don't have two sources of truth :)
It could potentially get quite lengthy (with example json blobs etc), so a separate README might be better. But having it close to alerts.go would be good, especially once the gae app starts using alerts.go to parse the json.


Labels: Type-Bug
Labels: -Milestone-SoMNGFollowUp Milestone-Reliability
Status: Archived (was: Available)
I think this is probably not really necessary because yeah, it'd just be another thing to update. 

Sign in to add a comment