Track users invoking Windchill REST Services

[arajanala]

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Manufacturing

2. What version of Windchill are you currently running?
Windchill 12

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Keep track of users who are Invoking REST API's, who is invoking what and how many times they are triggering the REST API 

4. What is the use case for your organization?
Keep track of users who are Invoking REST API's, who is invoking what and how many times they are triggering the REST API 

5. What business value would your suggestion represent for your organization?
Have a clear track of users consuming REST API's

[olivierlp]

Thank you @arajanala for publishing your idea. However, you gave the very bare minimum. The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration.

Here are some well documented ideas: 

start Save As from Replace - PTC Community

Add Cascading Attribute Functionality/Support to C... - PTC Community

Please let us know within the next two weeks.

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

[arajanala]

Hello, I am not seeing option to edit my original post, 

[olivierlp]

No problem to do this as a comment. 

[arajanala]

4. What is the use case for your organization?
Keep track of users who are Invoking REST API's, who is invoking what and how many times they are triggering the REST API, Having this information will help us to analyze the users consuming this kind of data, and also see if this consumption will lead to any kind of performance issues

5. What business value would your suggestion represent for your organization?
With Introduction of REST API's consumption will only increase as this is OOTB way to retrieve and consume data, if we don't have track of users who are consuming and why they are consuming it might lead to issues of over consumption and we will not have any clue to track and understand why they are doing what they are doing. If few users are using in the wrong way we can go back and correct it

Hope this explanation is sufficient

[olivierlp]

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

[Ruediger_Scholz]

Hi arajanala,

today you could track usage of Windchill REST Services by monitoring WebServer logs, e.g. Apache. All Windchill REST Services use URLs in some form of http(s)://<Windchill server>/Windchill/servlet/odata. So every access to Windchill REST Services will be logged in Apache Access logs:

10.XXX.XXX.XXX - User [21/Nov/2022:17:45:35 +0100] "GET /Windchill/servlet/odata/v5/ProdMgmt/$metadata HTTP/1.1" 200 6907 1518110

You can either manually prepare the data, but there also log analyzer like GoAccess (https://goaccess.io) available that will present the information from Webserver logs nicely.

With the above in mind - I wonder whether Windchill would be the right place to track these things.

Regards,

Ruediger