# Ability to selectively log specific information in app logs rather than a general "catch it all"

**URL:** <https://community.tulip.co/t/ability-to-selectively-log-specific-information-in-app-logs-rather-than-a-general-catch-it-all/8102>\
**Category:** Product Suggestions\
**Created:** [April 18, 2023, 7:06am UTC](https://community.tulip.co/t/ability-to-selectively-log-specific-information-in-app-logs-rather-than-a-general-catch-it-all/8102 "2023-04-18T07:06:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [April 18, 2023, 7:06am UTC](https://community.tulip.co/t/ability-to-selectively-log-specific-information-in-app-logs-rather-than-a-general-catch-it-all/8102/1 "2023-04-18T07:06:25Z")

</div>

Currently - unless I am missing something - Tulip does not allow a developer to selectively log specific variables/data in the immutable app completion records.

Instead there is only the choice to either log a variable “all the time” “for analysis” or not at all.

I would like to be able to explicitly state which kind of information I would like to log when I instruct the app to do so as part of its “completion records”. This way, it would be clear what is logged when and it would also ensure that no misleading information is potentially destroying selective analytics performed on the collected output.

Due to the fact that everything is logged all the time or nothing, handling this requires defining difficult to maintain filter logic to really narrow in on the information and the data points that are of interest.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/4/4d3b701a56fb4e49d2843eb69dae16214cfdb8bd.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/f/fe3ef875f0433d369c8cf9623aff3a932d221431.png)

---

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [April 18, 2023, 11:13am UTC](https://community.tulip.co/t/ability-to-selectively-log-specific-information-in-app-logs-rather-than-a-general-catch-it-all/8102/2 "2023-04-18T11:13:52Z")

</div>

To illustrate this a little more… one of our apps has a whopping 298 variables… happy clicking if you want to go through that all manually.

Luckily, I was able to get a helping hand from RPA. But I would consider this a rather lucky situation.