-
Notifications
You must be signed in to change notification settings - Fork 69
/
onboarding_lite_labs_log_store.prolific
103 lines (52 loc) · 3.12 KB
/
onboarding_lite_labs_log_store.prolific
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
Lab: Log Store is unavailable, logs will not display
### Bug description
App Metrics UI display's in "Error: Log Store is unavailable, logs will not display"
### Slack thread
This issue seems to have originated as a JIRA ticket, not a Slack thread, but there was this follow-up thread on November 11th:
https://vmware.slack.com/archives/CH1RH9KH7/p1605103633211500
### JIRA ticket
https://pivotal-io.atlassian.net/browse/APPMETRICS-67
### Link to branch with code at time of bug
https://github.com/pivotal/log-store-release/tree/lts-lab/APPMETRICS-67-logs-will-not-display
### Acceptance criteria / desired outcome
Logs display in App Metrics as a result of fixing Log Store within it
### Can I push changes somewhere safe to see the fix without pushing to prod?
Create a Toolsmiths environment or ask your facilitator to create one for you!
L: onboarding-lite, log-store-lab
---
Lab: AppMetric 2.0.5 Missing Logs
### Bug description
Customer does not see any logs older than 1 day
### JIRA ticket
https://pivotal-io.atlassian.net/browse/APPMETRICS-73
### Acceptance criteria / desired outcome
Simply think about and answer the following questions. Be ready for a conversation with your facilitator.
How would you respond to this ticket, without looking at the answers already there? Would you attempt to fix this? Is there a problem here to fix?
### Hint
Try to answer the question on your own, and once you do you may want to visit this previous Slack conversation:
https://vmware.slack.com/archives/CH1RH9KH7/p1605042790205700
This thread isn't the thread that corresponds directly to the issue, but the explanation should support the answer you just came up with.
L: onboarding-lite, log-store-lab
---
Lab: Log Store unavailable for some apps
### Bug description
Log Store unavailable for some apps
### JIRA ticket
https://pivotal-io.atlassian.net/browse/APPMETRICS-70
### Acceptance criteria / desired outcome
Simply think about and answer the following questions. Be ready for a conversation with your facilitator.
How would you respond to this ticket, without looking at the answers already there? Is the data corrupted? How can you tell? What should they do?
L: onboarding-lite, log-store-lab
---
Lab: Log Store has been breached
### Bug description
A malicious hacker has cracked into an unsecured bot account with read / write privileges and arbitrarily removed / altered bits of code in the Log Store project in an attempt to have us send broken code through the pipeline and into production! Yikes! Jokes on him or her, though, because we have tests in place that stop code like this from being released :D However, somehow they have locked us out of our commit history so you'll have to use the tests to identify the issues and fix them. Good thing we wrote these tests!
**Note:** the hacker and the damage done is fictitious; we have not actually been hacked.
### Link to branch with code at time of bug
https://github.com/pivotal/log-store-release/tree/broken
### Acceptance criteria / desired outcome
All the tests now pass.
L: onboarding-lite, log-store-lab
---
[RELEASE] Log Store Labs ⇧
L: onboarding-lite, log-store-lab