-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
[Metricbeats] Migrate uwsgi/status to ReporterV2 #11153
[Metricbeats] Migrate uwsgi/status to ReporterV2 #11153
Conversation
@fearful-symmetry I definitively would recommend to update the |
totals := findItems(events, "total") | ||
assert.Equal(t, 1, len(totals)) | ||
} | ||
|
||
func TestData(t *testing.T) { | ||
compose.EnsureUp(t, "uwsgi_http") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We started to skip the EnsureUp
in the TestData
runs as it would boot up the environment but then on CI it skips the generation anyway. And when generating it locally, I personally always boot up the env manually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM. One minor comment for the skip and it would be great to have the data.json
update. It will validate mostly that the change is as expected, but don't be surprised if the values change, this is ok.
Updated to fix a test and the compose line that @ruflin mentioned |
new data.json at @ruflin 's request. |
"read_errors": 0, | ||
"pid": 1 | ||
}, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seeing that empty line in here it definitively indicates this was generated manually. I'm glad we have a new one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jenkins failure seems unrelated. |
jenkins, test this |
See #10774
This one was a bit of a pain, as it has a lot more tests and varies from the normal module setup in a number of ways. I ended up having to change a bit (and was tempted to clean some things up, but that's probably a job for a separate PR) so if anything seems unnecessary or weird just tell me.
I also didn't commit the updated data.json, as this PR is large enough and @sayden advised me against it.