Details
- Other Assignee
- jbond
- Reference
- fl4
Reference | Source Branch | Dest Branch | Author | Title | |
---|---|---|---|---|---|
repos/releng/release!10 | tarball-echo-plus | master | jforrester | Add Echo, LoginNotfiy, and Thanks to the default MediaWiki bundle |
Revisions and Commits
Unknown Object (Diffusion Commit) |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Feature | None | T63779 Add system logs to logstash (tracking) | ||
Resolved | • bd808 | T1 Get puppet runs into logstash |
Event Timeline
We have the technology to implement this, but WMF TechOps has valid concerns about sensitive data that may be contained in the puppet reports themselves. As one example, file diffs can show passwords that are generally protected via file permissions from reading by all users with shell access to the host.
Change 274054 had a related patch set uploaded (by Xqt):
Remove imagetransfer.py from T001/T003 testing (print function)
Change 291859 had a related patch set uploaded (by Xqt):
Remove casechecker .py from "T001/T003" testing (print function)
Change 274054 abandoned by Xqt:
Remove casechecker .py from T001/T003 testing (print function)
Change 303408 had a related patch set uploaded (by Xqt):
Remove casechecker.py from T001/T003 testing (print function)
Change 291859 abandoned by Xqt:
Remove casechecker .py from "T001/T003" testing (print function)
Reason:
duplicate of I1d23ab55e
Change 303408 merged by jenkins-bot:
Remove casechecker.py from ignoring T001/T003 (print function)
Change 274054 restored by Xqt:
Remove casechecker .py from T001/T003 testing (print function)
Change 308753 had a related patch set (by Paladox) published:
Add support for searching gerrit using bug:T1
Change 407865 had a related patch set uploaded (by Paladox; owner: Paladox):
[All-Projects@refs/meta/config] Modify access rules+test+test
Change 434719 had a related patch set uploaded (by Herron; owner: Herron):
[operations/puppet@production] puppet-agent: remove --show_diff from scheduled puppet-run script
This is strange. Even the first task is still unresolved. Can someone please guide me how we go about in the phabricator about backlog clearing?
@Capankajsmilyo: Please move off-topic general questions to mw:Talk:Phabricator/Help and read mw:Bug management/Development prioritization
Five years later, is that still the take / situation? (If it is, feel free to update the task status again.)
Change 734961 had a related patch set uploaded (by Jbond; author: John Bond):
[operations/puppet@production] puppetmaster: enable logstash reports
Change 734961 merged by Jbond:
[operations/puppet@production] puppetmaster: enable logstash reports
Change 736233 had a related patch set uploaded (by Jbond; author: jbond):
[operations/puppet@production] P:rsyslog: ship puppetmaster logs to kafka
Change 736233 merged by Jbond:
[operations/puppet@production] P:rsyslog: ship puppetmaster logs to kafka
after the last change above, we now have puppet report data going into logstash. I haven't played with it much and im a elastic noob but the following is an example showing when a hosts where running a specific puppet git sha1 https://logstash.wikimedia.org/goto/473ad9da22eb1255d4168658f42a7ed5
As said i have not played with the data much but here is an example of what data gets sent on each run.
i think this comment referees to puppet diff's however the implementation doesn't add the diffs and im not sure if we would want them. As such i think we can finally close this task down and will boldly do so
Change 875401 had a related patch set uploaded (by Jbond; author: John Bond):
[operations/puppet@production] phabricator: update pattern to support old tickets like T1
Change 875401 merged by Jbond:
[operations/puppet@production] phabricator: update pattern to support old tickets like T1