pulse_actions should create some files with information on what it has triggered

RESOLVED WONTFIX

Status

Testing
General
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
Today bug 1199226 started making everyone worried that something was over scheduling tasks on Treeherder.

It took a bit of digging to figure out that it was not pulse_actions or trigger_bot (I had access to the Papertrail logs).

I believe we can give some pieces of data in order to help sheriffs or anyone easily check.

I was thinking that every time one of the Heroku workers start will create a data structure of known format (It probably makes more sense to make mozci track it).

We can probably name the file like "worker1_{{unix_timestamp}}.txt"
That way we can easily roll over when Heroku is restarted.

We can probably write the structure to disk every few seconds and overwriting the previous one.

We can probably put a clean up function to clean files older than a year.

{
   {{repo_name}}:
        {{push_id}}: <-- to help with sorting
             "revision": 1234567af,
             "requests": {
                  [
                     {{unix_timestamp}}: <-- to help with sorting
                          "time":  {{human_readable_time_utc}}
                          "builder": {{buildername}}
                          "reason": [1]
                          "who": {{developers_email_address}}
                  ]
             }
        {{push_id-1}} ...
}
                 

[1] "treeherder_action_{backfill,fillme}|automatic_back_filling"
(Reporter)

Comment 1

2 years ago
For now.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.