最近搜索
没有最近搜索

Ryan Winkler
已加入2021年4月14日
·
最后活动2025年2月03日
关注
0
关注者
4
活动总数
229
投票
89
订阅
92
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Ryan Winkler
Ryan Winkler 进行了评论,
February Update:
Hey Everyone,
For anyone tuning in, since the launch of the UI, we've been busy optimising how best to provide this experience, as well as support more fields. Your feedback is KEY to prioritisation, so please don't hold back
Here are some of the key updates we have added since December
[Dec 14th release] Access Log UI: We launched the UI in Admin Center to rapidly expand the use of this feature. No longer will you need to use an API or third party connection for simply viewing.
Since the original release, notable Updates include:
- Sort by time (in the API as well!) -- ability to retrieve and view logs by latest first
-
Agent filter by name or email -- Simplify Actor look ups by a name or email!
Coming soon:
- Column manager -- show or hide certain fields in the UI!
- URL pathway filter -- Just like our API, filter activity down by URL pathway, instead of Actor, allowing you to check who viewed what specific ticket, attachment, etc.
-
Log Details panel -- A side panel to display further information, such as User Identity, and the groups they belong to.
-
Authorization Type and client (user_agent) fields: We’ve added authorization type and client details in the access logs. This enables you and your admins to see very explicitly if activity is coming from an API call, browser or otherwise. So far, we've seen this used to identify API activity and errors which may occur, as well as easier identification of usage of Tokens or non browser use. We're still looking to mature this offering so please let us know if you have any feedback related to this
GraphQL fields -- we will add columns to handle GraphQL fields in the UI!
We Need your Help!
We want to continue to build out an actionable and comprehensive feature, so we're looking for the following direct validation on the following:
-
How important is Description for you?
- We're planning to add Description and product area fields to each log event and are looking for any feedback or comments on how important this is to you
-
We have some mock ups that we would love to talk with you about (so please reach out to your Account manager to get in touch!)
-
WEBHOOKS/ Pushing data
- We've heard your need for a better way to get filtered data. We're considering adding webhooks to accommodate this. We're looking for any and all feedback relating to how this could help you with Audit Logs OR Access logs, so please send them in (as a comment or in a ticket!)
-
How important is Description for you?
Please let us know if you have any questions or concerns. Your feedback to us will help prioritise and is vital to building out the best solution, so please don't hesitate to reach out!
查看评论 · 已于 2025年2月03日 编辑 · Ryan Winkler
0
关注者
1
投票
0
评论
Ryan Winkler 进行了评论,
Hey Tim Fischer !
Thanks for reaching out and providing context here. GDPR and regulatory needs are something we are sensitive to ourselves, so the need is not lost on us!
Deletion of old Audits is something we've done some basic discovery into but have not been prioritised anytime in the near future unfortunately.
Are you just worried about the logs which could have PII within it, or would you like the need to delete settings and configuration changes (Admin center) as well?
If we were to just target a specific category of logs, which log would we want that to be in?
Would love any additional context or feedback you can provide!
Thanks again for the details and feedback!
查看评论 · 已于 2024年12月18日 发布 · Ryan Winkler
0
关注者
1
投票
0
评论
Ryan Winkler 进行了评论,
Hey Jill, Rudolph and Karl.
Firstly, Apologies for a lack of response, but secondly, we really appreciate the feedback.
Access logs being part of our Advanced data Privacy and protection add-on was an intentional choice due to the very large volume of logs (and data) that are produced. They are unsampled network logs of all agent activity within your account, which equates to millions of records (on average), which brings some large storage considerations.
We've attempted to price and provide the offiering competitively in line with similar offerings in the market, while coupling it with some key functionality to help build value even further, with more and more to come in the future.
However, I understand that cost being a huge blocker is frustrating. While I don't have any changes on pricing to provide, I can say that we are actively listening and here for you with any feedback or concerns.
Keep us honest and continue to provide us this crucial feedback. I can't promise that I will be able to resolve every concern, but I can promise to actively cheerlead for anything need cheering for!
查看评论 · 已于 2024年12月12日 编辑 · Ryan Winkler
0
关注者
0
投票
0
评论
Ryan Winkler 创建了一篇文章,
宣布日期 | 推行日期 |
2024 年 12 月 12 日 | 2024 年 12 月 12 日 |
我们很高兴宣布在管理中心推出访问日志 UI。访问日志旨在增强 Zendesk 帐户的数据安全和管理控制。该功能随高级数据隐私和保护 (ADPP) 附加功能提供。
此前,访问日志功能只能作为 API 使用。现在,随着访问日志 UI 推出,您可以直接在管理中心根据访问过的 URL 了解已访问的内容。
此公告包括以下主题:
有什么变化?
此版本推出之前,只能通过 API 调用获取访问日志数据。但是,随着此版本推出,现在可以在管理中心访问该数据。
在接下来的几个季度,访问日志 UI 将不断改进,添加更多功能。此版本推出后,您将可以直接在管理中心监测专员活动,了解其在 Zendesk 帐户中查看的内容,而无需专业技术知识或时间来使用 API 进行检索。
Zendesk 为何作出这项更改?
Zendesk 致力于让用户控制自己的数据。访问日志 UI 推出后,您将可以直接在管理中心详细记录专员对帐户的数据访问情况,从而加强客户隐私保护。您将能够了解哪些专员何时从哪个 IP 地址查看了哪些数据,以便问责。您还可以识别并预防不当数据访问的风险,并证明数据隐私法规的合规性。
我需要做些什么?
如果您已安装高级数据隐私和保护附加功能,并已开启访问日志,则无需进一步操作即可使用该 UI。如果您尚未开启访问日志,可以开启该功能,开始捕获活动日志以在 UI 中显示。
请参阅使用访问日志监测专员活动了解更多信息,包括使用访问日志帮助保护 Zendesk 帐户的示例场景。
如果您不是高级数据隐私和保护附加功能的订阅者,并希望获得访问日志 UI 的访问权限,请参阅 关于高级数据隐私和保护附加功能。
如果您对此公告有任何反馈或疑问,请访问我们的社区论坛,我们将在这里收集和管理客户对产品的反馈。如需获取关于 Zendesk 产品的常规帮助,请联系 Zendesk 客户支持。
已于 2024年12月17日 编辑 · Ryan Winkler
0
关注者
1
投票
0
评论
Ryan Winkler 创建了一个帖子,
Access Log UI release
Calling ALL ADDP subscribers (or anyone thinking of subscribing for Access Logs)!
We've just released our UI for our Advanced Data Privacy and Protection Add-on feature, access logs (Announcement here).
What we're looking for
We are interested in hearing about your experience when using the Access Log UI. We're releasing today to get you access to your events in Admin Center, as we have heard that this has been a major frustration and blocker in regularly using Access logs.
While we plan to continue to make improvements over the next few quarters to this feature, we would love to hear from you on what is important, missing or needs improvement from a functionality or information basis.
You can also check back here to know any known limitations or planned fixes as well (this post will be monitored!)
How can you help
Upvote, comment, provide feedback as thoroughly as possible. We're looking for usecases and help find what is best to prioritise and when!
已于 2024年12月12日 编辑 · Ryan Winkler
3
关注者
5
投票
1
Comment
Ryan Winkler 进行了评论,
Hey Friends,
Audit Log Product guy here – I didn't realize we didn't have these changes. Let me talk to the team taking care of the dynamic content side of things and see if we can get something going.
No ETA or commitments here, but definitely glad to cheerlead.
and thank you all for the input! It's extremely helpful in terms of uncovering “misses” and prioritizing things… Keep them coming!
查看评论 · 已于 2024年7月22日 发布 · Ryan Winkler
0
关注者
0
投票
0
评论
Ryan Winkler 进行了评论,
Is there a way to schedule the audit log to send to email via CSV/EXL? We'd like to be able to schedule the audit log to send a log of the past x day/weeks/months.
Scheduling with filtering so it alerts based on concering changes would be beneficial.
At the moment we do not have any sort of scheduling or alerting of any kind in product for Audit logs. We generally advise to export to your data warehouse or tooling which can alert and action from the API itself
However, that doesn't really help in terms of ease of use or general needs when you don't have that, or need a user friendly option, and I can definitely see how both of those could be useful.
Hannah Lucid – For the export for the csv/file, what do you use to review that from there? Do you upload the file to your analytics tool or some application to read that or are you just reviewing the file directly? Is the CSV/XML export out of convienance or is that the ideal output?
I'm curious on the full journey here, for sure
@monica — For alerting – What is your ideal outcome? Email? Webhook (3rd party integration alert) or something else? Curious to know your thoughts here — Is there anything specific or higher priority to alert on than anything else? What would you denote as a concerning change?
Thanks, both of you, for the feedback and thoughts!
查看评论 · 已于 2024年7月11日 编辑 · Ryan Winkler
0
关注者
0
投票
0
评论
Ryan Winkler 进行了评论,
Is there a way to exclude specific actors from the log? I'd like to remove an API actor, as well as an admin from the audit log so that I can identify users who may mistakenly make changes and look at education them.
Thank you as always :)
Hey Matt! No exclusions possible at the moment, but I have that logged as a proper feature request, and definitely see the need.
No ETA or priority on that at the moment, but I can say that explicit feedback like yours helps a lot with prioritization, so keep them coming! We're listenting :)
查看评论 · 已于 2024年7月11日 发布 · Ryan Winkler
0
关注者
0
投票
0
评论
Ryan Winkler 进行了评论,
Hey Sydney and Hannah,
Thanks so much for the in depth feedback.
My team (the Audit log and Access Log team) does not presently have these events slated to add, but I will explicitly reach out to the people who own skills and skill based routing to see if we can at least get this in the back log.
It is my intention to have a fully comprehensive (and complete) audit log service, so every event is very important.
If you have any feedback or additional thoughts on this, or more context in terms of urgency, or impact that NOT having this or anything within Audit logs or Access logs is taking, I'd love to hear it!
查看评论 · 已于 2024年7月10日 发布 · Ryan Winkler
0
关注者
0
投票
0
评论
Ryan Winkler 进行了评论,
Hey Michelle, to confirm, are we talking about SSL certificates on brands & CNAME for host mapping or the SPF/DKIM/DMARC/CNAME verification for support addresses?
Just want to verify before I go into solutions or recording the right feedback.
查看评论 · 已于 2024年7月10日 发布 · Ryan Winkler
0
关注者
0
投票
0
评论