Get output of vagrant process when using Measure-Command
I want to collect some metrics when provisioning my Vagrant dev machines and found Measure-Command. But I don't get any output when running Vagrant commands:
PS VagrantTest> Measure-Command {vagrant up}
Days : 0
Hours : 0
Minutes : 0
Seconds : 14
Milliseconds : 183
Ticks : 141838408
TotalDays : 0,000164164824074074
TotalHours : 0,00393995577777778
TotalMinutes : 0,236397346666667
TotalSeconds : 14,1838408
TotalMilliseconds : 14183,8408
When running Vagrant standalone I got more information about the progress like here:
PS VagrantTest> vagrant up
Bringing machine 'rancher-base-box' up with 'virtualbox' provider...
==> rancher-base-box: Checking if box 'ubuntu/xenial64' is up to date...
==> rancher-base-box: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> rancher-base-box: available! You currently have version '20181113.0.0'. The latest is version
==> rancher-base-box: '20181114.0.0'. Run `vagrant box update` to update.
[...]
My goal is to see the regular output of vagrant and display the metrics of its execution time after the command has finished. Does this work using Measure-Command or is it required to collect execution time on my own using (Get-Date).Milliseconds or StopWatch?
Following the KISS principle, I would like to use existing commands instead of writing my own metrics.
powershell vagrant output stdout metrics
asked Nov 19 '18 at 12:45
DanielDaniel
97110
add a comment |
I want to collect some metrics when provisioning my Vagrant dev machines and found Measure-Command. But I don't get any output when running Vagrant commands:
PS VagrantTest> Measure-Command {vagrant up}
Days : 0
Hours : 0
Minutes : 0
Seconds : 14
Milliseconds : 183
Ticks : 141838408
TotalDays : 0,000164164824074074
TotalHours : 0,00393995577777778
TotalMinutes : 0,236397346666667
TotalSeconds : 14,1838408
TotalMilliseconds : 14183,8408
When running Vagrant standalone I got more information about the progress like here:
PS VagrantTest> vagrant up
Bringing machine 'rancher-base-box' up with 'virtualbox' provider...
==> rancher-base-box: Checking if box 'ubuntu/xenial64' is up to date...
==> rancher-base-box: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> rancher-base-box: available! You currently have version '20181113.0.0'. The latest is version
==> rancher-base-box: '20181114.0.0'. Run `vagrant box update` to update.
[...]
My goal is to see the regular output of vagrant and display the metrics of its execution time after the command has finished. Does this work using Measure-Command or is it required to collect execution time on my own using (Get-Date).Milliseconds or StopWatch?
Following the KISS principle, I would like to use existing commands instead of writing my own metrics.
powershell vagrant output stdout metrics
asked Nov 19 '18 at 12:45
DanielDaniel
97110
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04
add a comment |
I want to collect some metrics when provisioning my Vagrant dev machines and found Measure-Command. But I don't get any output when running Vagrant commands:
PS VagrantTest> Measure-Command {vagrant up}
Days : 0
Hours : 0
Minutes : 0
Seconds : 14
Milliseconds : 183
Ticks : 141838408
TotalDays : 0,000164164824074074
TotalHours : 0,00393995577777778
TotalMinutes : 0,236397346666667
TotalSeconds : 14,1838408
TotalMilliseconds : 14183,8408
When running Vagrant standalone I got more information about the progress like here:
PS VagrantTest> vagrant up
Bringing machine 'rancher-base-box' up with 'virtualbox' provider...
==> rancher-base-box: Checking if box 'ubuntu/xenial64' is up to date...
==> rancher-base-box: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> rancher-base-box: available! You currently have version '20181113.0.0'. The latest is version
==> rancher-base-box: '20181114.0.0'. Run `vagrant box update` to update.
[...]
My goal is to see the regular output of vagrant and display the metrics of its execution time after the command has finished. Does this work using Measure-Command or is it required to collect execution time on my own using (Get-Date).Milliseconds or StopWatch?
Following the KISS principle, I would like to use existing commands instead of writing my own metrics.
powershell vagrant output stdout metrics
asked Nov 19 '18 at 12:45
DanielDaniel
97110
I want to collect some metrics when provisioning my Vagrant dev machines and found Measure-Command. But I don't get any output when running Vagrant commands:
PS VagrantTest> Measure-Command {vagrant up}
Days : 0
Hours : 0
Minutes : 0
Seconds : 14
Milliseconds : 183
Ticks : 141838408
TotalDays : 0,000164164824074074
TotalHours : 0,00393995577777778
TotalMinutes : 0,236397346666667
TotalSeconds : 14,1838408
TotalMilliseconds : 14183,8408
When running Vagrant standalone I got more information about the progress like here:
PS VagrantTest> vagrant up
Bringing machine 'rancher-base-box' up with 'virtualbox' provider...
==> rancher-base-box: Checking if box 'ubuntu/xenial64' is up to date...
==> rancher-base-box: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> rancher-base-box: available! You currently have version '20181113.0.0'. The latest is version
==> rancher-base-box: '20181114.0.0'. Run `vagrant box update` to update.
[...]
My goal is to see the regular output of vagrant and display the metrics of its execution time after the command has finished. Does this work using Measure-Command or is it required to collect execution time on my own using (Get-Date).Milliseconds or StopWatch?
Following the KISS principle, I would like to use existing commands instead of writing my own metrics.
powershell vagrant output stdout metrics
powershell vagrant output stdout metrics
asked Nov 19 '18 at 12:45
DanielDaniel
97110
asked Nov 19 '18 at 12:45
DanielDaniel
97110
asked Nov 19 '18 at 12:45
DanielDaniel
97110
asked Nov 19 '18 at 12:45
DanielDaniel
97110
asked Nov 19 '18 at 12:45
DanielDaniel
97110
97110
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04
add a comment |
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04
add a comment |
1 Answer
1
active
oldest
votes
Try Start-process -RedirectStandardOutput ?
It will output to file
doc
Or :
-NoNewWindow -PassThru could do the trick
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374949%2fget-output-of-vagrant-process-when-using-measure-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try Start-process -RedirectStandardOutput ?
It will output to file
doc
Or :
-NoNewWindow -PassThru could do the trick
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
add a comment |
Try Start-process -RedirectStandardOutput ?
It will output to file
doc
Or :
-NoNewWindow -PassThru could do the trick
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
add a comment |
Try Start-process -RedirectStandardOutput ?
It will output to file
doc
Or :
-NoNewWindow -PassThru could do the trick
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
Try Start-process -RedirectStandardOutput ?
It will output to file
doc
Or :
-NoNewWindow -PassThru could do the trick
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
answered Nov 19 '18 at 13:59
Lukasz GoozLukasz Gooz
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374949%2fget-output-of-vagrant-process-when-using-measure-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Start-/Stop-Transcript will include start and end times but only with a resolution of whole seconds. So your StopWatch link may be the better option.
– LotPings
Nov 19 '18 at 13:04