-
Notifications
You must be signed in to change notification settings - Fork 31
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
Downloading logged packets from a script #1711
Comments
#937 is how you do it. You can use the |
@jmthomas are there any plans to create a method that would work for pulling large amounts of telemetry items? I am looking for some scripting functionality that would do the equivalent of pressing the "Process" button in the Data Extractor (which downloads large amounts of telemetry instantly). I need to be able to process and download telemetry items from a packet that collects every tenth of a second and runs for 3 hours. The process above of putting all items into memory and adding each entry to a .csv takes forever. If there is not an option to perform the "Process" functionality of the Data Extractor within a script, I will resort to doing it manually, but am wondering if I am missing something here |
I would recommend using the StreamingAPI with your test's start and end time like so (works in the COSMOS Demo):
|
@jmthomas when I execute this against the COSMOS Demo, the put_target_file line runs but does not populate the "INST/test.txt" with anything. But what is odd is that when I download that file after, the downloaded file is populated. This is still an issue, however, as I need to later be able to pull from that file for further manipulation of the data. I am working in 5.19.0. Why is the file not populating in targets_modified for INST?
|
Before calling
|
@jmthomas that worked, thanks! |
@jmthomas Thanks for your guidance with this. I actually have a few follow up questions:
|
Note I put the looping inside of
|
I found a work around that can work until we fix our implementation (should work for both items and packets):
|
@jmthomas thanks for the input on work arounds. I was unable to get the most recent method provided working for more than 8 item inputs and for the packet. It would run to completion but not populate the file (code below)
The previous work around that you gave for the batch size limitation worked great. No need to dig further into this though - I have opted to split items from the desired packet into two separate files - works for what I need at the moment. |
@jmthomas I have another telemetry logging question as well. Is there any way to mass download raw & decom logs from the bucket explorer (either from a script or another function)? Or is the best way to do this by manually downloading each log |
We don't provide an interface to mass download files from MINIO. That said this is open source software and MINIO is pretty well documented so it would awesome if you could create something and share it with the community! :-) |
@jmthomas thanks for the recommendation, I will look into it! |
Hello
I am looking to automate processing and downloading packets from the Data Extractor so it can be performed within scripts that are being ran, based off of variables defined within that script (ie. start and end time). I am using the method described in Issue 937 (#937) and adding the items to a .csv, but it takes a while to add all rows of telemetry. One of the lines in that script references not using this method for large queries. Is there a better way to do this, for large queries? I am unable to locate any code that details how the Data Extractor performs on the backend. I tried using batch/parallel processing methods to speed up this process, but COSMOS does not seem to recognize the 'concurrent' library. Here is what I am currently working with:
The text was updated successfully, but these errors were encountered: