Showing results for 
Show  only  | Search instead for 
Did you mean: 

Filtering by timeframe doesn't work for openpurepathlist



I want to open a list of purepaths using simple form as:

<form id="dynatracePost" action="http://localhost:8030/rest/integration/openpurepathlist" method="POST">
<input type="hidden" name="purepathid" value="PT=56865;PA=-2099996968;SP=Monitoring;PS=2141417844">
<input type="hidden" name="purepathid" value="PT=56870;PA=-2099996968;SP=Monitoring;PS=2141417844">
<input type="hidden" name="purepathid" value="PT=56875;PA=-2099996968;SP=Monitoring;PS=2141417844">
<input type="hidden" name="filter" value="tf:Last1h">
<input type="hidden" name="context" value="Example">

In the client I'm getting purepaths opened, but neither filtering nor context are not applied. If I make the context param as query (like http://localhost:8030/rest/integration/openpurepat...) it sets the context, but this doesn't work similar for the filtering. It works perfectly if I change method to GET (using openpurepath instead of openpurepathlist), but that is not what I need. So, how can I set the timeframe filter for the POST request?


Dynatrace Guru
Dynatrace Guru


Sorry for the very late reply on this. I think the intention of OpenPurePath list is to simply open PurePaths. The same should be true for openpurepath (via GET). In both cases I would have not assumed that you can add additional filters as you already clearly specify which PurePaths you want to see.

The bug here seems to be the inconsistency between both REST Endpoints. I suggest to open a support ticket so that our engineering team can look into this.

What would be interesting to understand is WHY you would like to have an additional Time Frame Filter set? If you already specify the PurePaths then adding an additional filter might even be contracting in case the PurePaths you selected are not in that timeframe