You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the discussion under StackStorm/st2#5974 opening this issue for requesting a feature.
Would want to see a feature in the UI where we can have the option to download the logs related to the actions/workflows executed by Stackstorm at a specific date and time . Facilitating it with an example: Like the way we have a full fledged option to download the logs of pagerduty / nagios , in the similar fashion , it would be beneficial for an organization that is leveraging stackstorm extensively for automating the environment to review these logs periodically.
Would like the UI to support the downloading of the CSV report of these logs for past 2-3 months or atleast weeks. This will actively help to analyze the actions that stackstorm took in form of workflows/actions.
Because i have been working on pagerduty as well . I could see the logs coming in from nagios and then Pager reaching out to us. What all it paged can be viewed for any past date/time as well (a month/week older).
Below is the link that explains it well : https://support.pagerduty.com/docs/analytics#section-incidents-report
Let me know the views on it. Will be happy to provide any other information if required.
The text was updated successfully, but these errors were encountered:
Sounds like a helpful feature overall, not sure though how many people would really need it as it might be specific to your environment.
A few ideas:
create a custom st2 action + cron task that goes through the st2 executions based on your filter criteria like daterange, fetches the results and stores them in a format you need like CSV, or uploads to S3/etc. More automatic way compared to manual export.
implement the feature in the ST2 Web UI and contribute back to st2web (if you'd like) or cooperate with a partner to implement it for you.
Thinking about the corner cases, one of the difficulties could be trying to export in one go a lot of data from every execution in a long daterange (might need ST2 api changes). From that standpoint custom st2 action + cron task might be more reliable.
Thanks for looking into it. This feature will be useful by the people/organisations who are extensively using Stackstorm in their environment. Vision is to make stackstorm more efficient by introducing the things/features that will definitely be required by an organization who has a lot of reliability on Stackstorm as we have.
We already have custom cron running in our environment. The sample is as below. But think about having this feature in stackstorm GUI serving this purpose helping in directly downloading the required csv report for analysing the actions that stackstorm is taking. I would say good to have feature kind of thing.
As per the discussion under StackStorm/st2#5974 opening this issue for requesting a feature.
Would want to see a feature in the UI where we can have the option to download the logs related to the actions/workflows executed by Stackstorm at a specific date and time . Facilitating it with an example: Like the way we have a full fledged option to download the logs of pagerduty / nagios , in the similar fashion , it would be beneficial for an organization that is leveraging stackstorm extensively for automating the environment to review these logs periodically.
Would like the UI to support the downloading of the CSV report of these logs for past 2-3 months or atleast weeks. This will actively help to analyze the actions that stackstorm took in form of workflows/actions.
Because i have been working on pagerduty as well . I could see the logs coming in from nagios and then Pager reaching out to us. What all it paged can be viewed for any past date/time as well (a month/week older).
Below is the link that explains it well :
https://support.pagerduty.com/docs/analytics#section-incidents-report
Let me know the views on it. Will be happy to provide any other information if required.
The text was updated successfully, but these errors were encountered: