A user asked why their output was going to Device Events despite the configuration being set to write to an index. After a troubleshoot, they fixed the issue by using the standard “`Write-Output("### SIP DATA BEGINS ###") $output | ConvertTo-Json Write-Output("### SIP DATA ENDS ###")“` instead of their earlier code.
Read the entire ‘Troubleshooting Data Writes to Device Events in ControlUp’ thread below:
Good day
Hope all are well
Happy Wacky Wednesday
Why would something wright to Device Events if i tell it to write to Data Index "clear_disk_space"
Also have the send events in
Write-Output("### SIP EVENT BEGINS ###")
Write-Output ($output | ConvertTo-Json)
Write-Output("### SIP EVENT ENDS ###")
in device events:
{
"totalclearedspace": "406.56 KB",
"totalsizebeforecleared": "166.58 MB"
}
Not sure if I fully understand your question, but if you use
“`### SIP DATA BEGINS ###
SIP DATA ENDS ###“`
It will write whatever is in between those in an index, using the Data Collection settings in the left pane
If you use
“`### SIP EVENT BEGINS ###
SIP EVENT ENDS ###“`
it will write what’s in between to the Device Events
Are you seeing a different behavior?
Yes
I have my output between the Sips and i have the config set to write the output to a index , but its not , instead its going to device events
Fixed
Write-Output("### SIP DATA BEGINS ###")
Write-Output -InputObject $output | ConvertTo-Json
Write-Output("### SIP DATA ENDS ###")
That seems over-complex. Does the following not work?
“`Write-Output("### SIP DATA BEGINS ###")
$output | ConvertTo-Json
Write-Output("### SIP DATA ENDS ###")“`
(It is the standard I use)
Syntactically Write-Output -InputObject $output should be completely equivalent to $output
Continue reading and comment on the thread ‘Troubleshooting Data Writes to Device Events in ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI