Post B6iKggTgXKnIVoSJQ8 by acf@masto.alancfrancis.com
 (DIR) More posts by acf@masto.alancfrancis.com
 (DIR) Post #B6iKggTgXKnIVoSJQ8 by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       TelemetryDeck question I can't seem to find an easy answer for. Am getting Error.occurred events (because I am recording errors that occurred). In my app I am adding additional parameters to those signals. I'd like to be able to just get a table/list of all those Error.occurred signals and their parameters (so I can see more about why the error occurred) but I only seem to be able to display aggregate information. There are 21.  That's great, but I'd like to see each of those 21 in more detail.
       
 (DIR) Post #B6iKggjzYhq1KO5Kq0 by omich@mastodon.social
       0 likes, 0 repeats
       
       @acf cc @daniel
       
 (DIR) Post #B6iKggucvALRrN3pPk by daniel@social.telemetrydeck.com
       0 likes, 0 repeats
       
       @omich @acf you could build a scan query for these: https://telemetrydeck.com/docs/tql/scan/
       
 (DIR) Post #B6iKghLDKJc1BpV3r6 by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       Suggestions welcome :-)
       
 (DIR) Post #B6iSCAiQrWhIwvJbBA by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       @daniel @omich Hah I keep forgetting that Daniel who I follow on mastodon is also Daniel from telemetry deck 😂
       
 (DIR) Post #B6iTYNWE2c9yyyl4Vc by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       @daniel @omich That seems to be working, except the timestamp column just shows "all time" instead of the actual timestamp.  I assume I'm doing something wrong somewhere 🙂 {  "appID": "xxxxx",  "baseFilters": "thisApp",  "queryType": "scan",  "limit": 200,  "columns": [    "__time",    "user",    "data"  ],  "granularity": "all",  "filter": {    "type": "selector",    "dimension": "type",    "value": "TelemetryDeck.Error.occurred"  }}
       
 (DIR) Post #B6iTcWbQD41OJWALmy by daniel@social.telemetrydeck.com
       0 likes, 0 repeats
       
       @acf drop the granularity property, otherwise you should be good :)
       
 (DIR) Post #B6iUKNy7fglKHIhNAG by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       @daniel yay!  Thank you.  Last question.  The data column seems mostly blank, but some of my errorOccurred() calls do indeed have blank data passed as a parameter ( parameters:["data":"", "user":foo]). EITHER: My scan is properly configured to access those user and data parameters and 'data' is really empty OR 'user' is somehow special and is working by a different means and I'm not correctly accessing the 'data' parameter.  Just want to check its the former :-)
       
 (DIR) Post #B6ia2r9h17MlJM8Qs4 by daniel@social.telemetrydeck.com
       0 likes, 0 repeats
       
       @acf hmm no "user" should not be changed or edited in any way
       
 (DIR) Post #B6idWKgCco3T8j5Wjo by acf@masto.alancfrancis.com
       0 likes, 0 repeats
       
       @daniel I'll have a play with different parameters in test mode and see how the scan responds.