Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide events.json #20

Closed
jchesterpivotal opened this issue Sep 1, 2018 · 5 comments
Closed

Provide events.json #20

jchesterpivotal opened this issue Sep 1, 2018 · 5 comments
Assignees
@jchesterpivotal
Labels
size/L
Milestone
v0.11.0

Comments

@jchesterpivotal
Copy link
Owner

jchesterpivotal commented Sep 1, 2018 •
edited
Loading

Description

Currently, the resource renders events out to events.log. This is useful for folks wanting raw loglines.

It would be nice to have access to the original JSON form (say events.json), however. This would allow analysis of timestamps and grouping into the various steps.
@jchesterpivotal jchesterpivotal added this to the v0.8.0 milestone Sep 1, 2018
@jchesterpivotal jchesterpivotal self-assigned this Sep 1, 2018
@jchesterpivotal jchesterpivotal modified the milestones: v0.8.0, v0.9.0 Sep 6, 2018
@jchesterpivotal
Copy link
Owner Author

There's not much inbuilt support for this in go-concourse, which is a bit of a hassle.

@jchesterpivotal jchesterpivotal modified the milestones: v0.9.0, v0.10.0 Sep 9, 2018
@jchesterpivotal jchesterpivotal modified the milestones: v0.10.0, v0.11.0 Sep 9, 2018
@jchesterpivotal jchesterpivotal modified the milestones: v0.11.0, v0.12.0 Sep 22, 2018
@jchesterpivotal
Copy link
Owner Author

So a few notes.

  1. This really would be super helpful to perform more detailed analyses of build behaviour.
  2. Concourse 4.2.1 and 3.14.x (the versions I've been referring to in the wild) have very different levels of detail. In a 4.2.1 instance I can see actual markers that tell me when a get, put or task ends. It also looks as though they provide more detailed metadata about the tasks etc.
  3. Authentication (Support authentication #9) rears its head again. This won't be very useful for lots of folks if it requires them to have public job logs.

@jchesterpivotal
Copy link
Owner Author

Marking blocked on the authentication story.

@jchesterpivotal
Copy link
Owner Author

Unblocking. This is possible without authentication, just not as useful in cases of private jobs.

@jchesterpivotal
Copy link
Owner Author

Also, I was wrong in saying that 3.x and 4.x have different levels of detail about the stuff I am interested in. Mea culpa.

jchesterpivotal added a commit that referenced this issue Oct 6, 2018
@jchesterpivotal @jchester
Add events.json support
3534d29 
- Backfill missing test for events.log

[#20]

Signed-off-by: Jacques Chester <[email protected]>
jchesterpivotal added a commit that referenced this issue Oct 6, 2018
@jchesterpivotal @jchester
Inject metadata into events.json
d013b6b 
- Extract JSON fetching into a separate method, so it can
  follow the same logic as other endpoints.

[#20]

Signed-off-by: Jacques Chester <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jchesterpivotal jchesterpivotal

Labels
size/L
Projects
None yet
Milestone
v0.11.0
Development

No branches or pull requests
1 participant
@jchesterpivotal