Hello,
In the task list on the WAPT Enterprise 2.6.0 console, we only see what has happened since the PC restarted.
Sometimes we need to go back further to trace the chronology of events.
Is it possible to have more historical data?
Thank you for your help.
How do I access the task history by client?
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Erems,
Indeed, the task tab retrieves the task history directly from the agent, a history that is stored in the agent's memory since its last startup.
It's possible to create an audit package that retrieves information from the agent's logs, performs some parsing, and sends the information to the WAPT server.
If the need is for the installation history, it should be stored locally in the SQLite database, so it should be even easier to retrieve during auditing.
We'll look into how to integrate this to retrieve enough useful information by default, without overloading the server (in fact, the problem isn't reporting too many issues, but finding the right balance to avoid exceeding the necessary storage and CPU/RAM for parsing
).
In your case, the issue was retrieving the history of versions installed on the machine and by whom (self-service, machine package, group package, etc.)?
See you soon,
Denis
Indeed, the task tab retrieves the task history directly from the agent, a history that is stored in the agent's memory since its last startup.
It's possible to create an audit package that retrieves information from the agent's logs, performs some parsing, and sends the information to the WAPT server.
If the need is for the installation history, it should be stored locally in the SQLite database, so it should be even easier to retrieve during auditing.
We'll look into how to integrate this to retrieve enough useful information by default, without overloading the server (in fact, the problem isn't reporting too many issues, but finding the right balance to avoid exceeding the necessary storage and CPU/RAM for parsing
).In your case, the issue was retrieving the history of versions installed on the machine and by whom (self-service, machine package, group package, etc.)?
See you soon,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
yes, it would be helpful to have a history of actions performed by the WAPT agent on a workstation. In our case, the user wanted to know if WAPT had uninstalled any software.
We checked the agent's logs; they're not easy to read, but the information is there.
It would be good to be able to retrieve this information from the console. An auditing package, as you suggested, would probably be sufficient.
Thank you.
yes, it would be helpful to have a history of actions performed by the WAPT agent on a workstation. In our case, the user wanted to know if WAPT had uninstalled any software.
We checked the agent's logs; they're not easy to read, but the information is there.
It would be good to be able to retrieve this information from the console. An auditing package, as you suggested, would probably be sufficient.
Thank you.
