1312839 - Improve pulse data ingestion experience

Status: RESOLVED FIXED

(Tree Management :: Treeherder: Data Ingestion, defect)

Description

[Gregory Szorc [:gps]]

As a new contributor, I got hung up with Pulse ingestion. Commits to improve the docs and experience coming shortly...

Comment 1

[GitHub Autolander Bot]

Attachment: [treeherder] indygreg:pulse-ingestion-improvements > mozilla:master

Comment 2

[Cameron Dawson [:camd]]

Comment on attachment 8804408 [details] [review]
[treeherder] indygreg:pulse-ingestion-improvements > mozilla:master

Thanks for doing this!

Comment 3

[Treeherder GitHub Bugbot]

Commits pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/fb7a630f3d8fcb5fec3378eec6a415b3c18e1392
Bug 1312839 - Properly document pulse data ingestion config

The previous docs incorrectly said to use a settings_local.py file.
The correct way to define the Pulse URL is via an environment
variable.

https://github.com/mozilla/treeherder/commit/305257bddb99573cf7f04121e04c7f1b42f4d475
Bug 1312839 - Log when a pulse message is received

Previously, `manage.py read_pulse_jobs` would print initial connection
info then sit around quietly. You had no idea if it was actually
doing anything.

With this commit, the pulse consumer logs that it has received a
message. Now we have feedback that the process is actually doing
something.