-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add data collection page #4846
base: main
Are you sure you want to change the base?
Add data collection page #4846
Conversation
👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉 You can read more about the versioning within our docs in our documentation guidelines. |
versioned_docs/version-8.3/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.3/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.4/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.4/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.5/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.5/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.6/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-8.6/reference/data-collection/data-collection.md
Outdated
Show resolved
Hide resolved
Re: the build errors you're seeing, it looks like the links are incorrect in two ways:
I'm also going to assign tech writers for review, as they should be the reviewers for content changes like this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated a few of the links that were throwing errors, but not entirely, as a few are within versions that do not have a matching page to link to - largely the SM Console telemetry links prior to 8.5, but also the "AI-powered features" section was introduced in 8.5 as well.
The remainder of the content looks good to me, but for versions 8.3 and 8.4, I am unsure if you'd like to remove the versioned references, or leave them and always point the reader to /next, where the page exists.
|
||
- Feature Usage: | ||
- SaaS System Actions: All SaaS organizations submit basic information about which features are being used. When certain features are used, Camunda logs which feature is used and basic information about how it has been used. This information is tied to an pseudonymized organization. | ||
- SaaS User Actions: Users that opt-in to analytics cookies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@conceptualshark can you please include screenshots of these 2 parts of the UI to explain how to opt-out of analytics cookies?
Hi @conceptualshark or @pepopowitz , I'm strapped for time and I'd like to release these docs ideally by EOW. Can one of you support merging in the post-legal review changes here and push the docs live? |
@HanselIdes I can get this updated for you! To confirm from the conversation on Slack, I will also remove the backported versions of these updates? Should these changes be available in 8.6, 8.7, and 8.8? Thank you! |
Thanks @conceptualshark! That's a good call. These changes should be available in 8.6, 8.7, and 8.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HanselIdes I still need to pull in the screenshots, but this should be updated with the new content, including removing the content from versions prior to 8.6, and introducing it for 8.7. I've flagged two specific changes here for you to look at as well.
- Camunda [Docs AI](/components/modeler/web-modeler/advanced-modeling/camunda-docs-ai.md) records the entire conversation to provide ongoing support. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the 8.6 version of this doc, I removed the section on Camunda Copilots, as those docs are only available in 8.7 and 8.8. If this is available in 8.6, I can either:
- Backport the Copilot docs to 8.6, and add it back in here
- Link to the 8.7 or /next version of the Copilot docs here instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Camunda Copilots are just now available on SaaS 8.6, which is currently rolled out to everyone. I'd keep 8.6
Hi @conceptualshark the docs were basically completely re-written as part of the legal review. Can you use the link I shared above as the source of truth and copy over that content? |
This should include all the changes from the linked docs: f51aa19 Can you let me know if this is correct? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@conceptualshark I reviewed the document closely for readability. I don't have any further changes requested from here
|
||
### Contractual metrics telemetry | ||
|
||
Telemetry Data includes a limited set of contractually agreed [usage metrics](/reference/data-collection/usage-metrics.md) to evaluate usage metric use and bill for overages. For example, how many process instance usage metrics are used compared to the number of process instance usage metrics purchased by customers. These are summary usage metrics that contain no sensitive information and that are collected automatically for SaaS customers and sent in a report generated by Self-Managed customers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Telemetry Data includes a limited set of contractually agreed [usage metrics](/reference/data-collection/usage-metrics.md) to evaluate usage metric use and bill for overages. For example, how many process instance usage metrics are used compared to the number of process instance usage metrics purchased by customers. These are summary usage metrics that contain no sensitive information and that are collected automatically for SaaS customers and sent in a report generated by Self-Managed customers. | |
Contractual metrics telemetry data includes a limited set of contractually agreed [usage metrics](/reference/data-collection/usage-metrics.md) to evaluate usage metric use and bill for overages. One example is how many process instance usage metrics are used compared to the number of process instance usage metrics purchased by customers. These are summary usage metrics that contain no sensitive information and that are collected automatically for SaaS customers and sent in a report generated by Self-Managed customers. |
|
||
Telemetry data includes contractual metrics, environment, and usage data. Contractual metrics, environment, and usage telemetry data are collected automatically in SaaS (except for personalized telemetry data which is only used via user discretionary opt-in) or collected via admin discretionary opt-in for Self-Managed platforms. Each of these categories of telemetry data are described below. | ||
|
||
### Contractual metrics telemetry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Contractual metrics telemetry | |
### Contractual metrics telemetry data |
|
||
### Environment telemetry Data (Self-Managed only) | ||
|
||
Environment telemetry data includes information about your Self-managed installations to enable better support and product improvement decisions. Self-Managed customers may choose to send a very limited set of environment information through the Console component's telemetry mechanism. View the [telemetry](/self-managed/console-deployment/telemetry.md) page for a description of this data. Environment telemetry data is not relevant to SaaS installations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Environment telemetry data includes information about your Self-managed installations to enable better support and product improvement decisions. Self-Managed customers may choose to send a very limited set of environment information through the Console component's telemetry mechanism. View the [telemetry](/self-managed/console-deployment/telemetry.md) page for a description of this data. Environment telemetry data is not relevant to SaaS installations. | |
Environment telemetry data includes information about your Self-Managed installations to enable better support and product improvement decisions. Self-Managed customers may choose to send a very limited set of environment information through the Console component's telemetry mechanism. View the [telemetry](/self-managed/console-deployment/telemetry.md) page for a description of this data. Environment telemetry data is not relevant to SaaS installations. |
|
||
## Telemetry data collection | ||
|
||
Telemetry data includes contractual metrics, environment, and usage data. Contractual metrics, environment, and usage telemetry data are collected automatically in SaaS (except for personalized telemetry data which is only used via user discretionary opt-in) or collected via admin discretionary opt-in for Self-Managed platforms. Each of these categories of telemetry data are described below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Telemetry data includes contractual metrics, environment, and usage data. Contractual metrics, environment, and usage telemetry data are collected automatically in SaaS (except for personalized telemetry data which is only used via user discretionary opt-in) or collected via admin discretionary opt-in for Self-Managed platforms. Each of these categories of telemetry data are described below. | |
Telemetry data includes contractual metrics, environment, and usage data. Telemetry data is collected automatically in SaaS (except for personalized telemetry data which is only used via user discretionary opt-in) and collected via admin discretionary opt-in for Self-Managed platforms. Each category of telemetry data is described below. |
- Feature Usage: | ||
|
||
- SaaS System Actions: All SaaS organizations submit basic information about which features are being used as part of telemetry data collection. When certain features are used, Camunda logs which feature is used and basic information about how it has been used. This information is tied to a pseudonymized organization. | ||
- SaaS User Actions: Users that opt-in to analytics cookies gain access to in-app tutorials and automatically submit information about which features they interact with in Camunda’s UI as part of telemetry data. In addition to the data collected from system actions described above, Camunda collects cursor activity, geographical area, browser information, and basic biographical information limited tolike email, and name, and city/region/country for user actions. If a user interacts through API, then personal information is not collected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- SaaS User Actions: Users that opt-in to analytics cookies gain access to in-app tutorials and automatically submit information about which features they interact with in Camunda’s UI as part of telemetry data. In addition to the data collected from system actions described above, Camunda collects cursor activity, geographical area, browser information, and basic biographical information limited tolike email, and name, and city/region/country for user actions. If a user interacts through API, then personal information is not collected. | |
- SaaS User Actions: Users that opt-in to analytics cookies gain access to in-app tutorials and automatically submit information about which features they interact with in Camunda’s UI as part of telemetry data. In addition to the data collected from system actions described above, Camunda collects cursor activity, geographical area, browser information, and basic biographical information limited to email, name, and city/region/country for user actions. If a user interacts through API, then personal information is not collected. |
|
||
- AI Usage: Camunda's AI features, currently available in SaaS only, are clearly labeled as AI features. For Enterprise organizations, these features must be enabled by the customer via opt-in in the [Console](/components/console/manage-organization/enable-alpha-features.md#enable-ai-powered-features). Depending on the feature, they may collect different information. | ||
- Camunda [Docs AI](/components/modeler/web-modeler/advanced-modeling/camunda-docs-ai.md) records the entire conversation to provide ongoing support. | ||
- Camunda [Copilots](/components/early-access/alpha/bpmn-copilot/bpmn-copilot.md) only gather usage telemetry data. For free users only, Copilots may collect all information sent to and from our AI models for product and model improvement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Camunda [Copilots](/components/early-access/alpha/bpmn-copilot/bpmn-copilot.md) only gather usage telemetry data. For free users only, Copilots may collect all information sent to and from our AI models for product and model improvement. | |
- Camunda [Copilots](/components/early-access/alpha/bpmn-copilot/bpmn-copilot.md) only gather usage telemetry data. Camunda automatically log all information sent to and from our AI models for system monitoring by a limited set of operators. Camunda will only use the data from free users for product and model improvement. |
|
||
Camunda follows certain principles in its collection and use of telemetry data to ensure the privacy of its customers and the success of its product development efforts: | ||
|
||
- Camunda will use telemetry data subject to applicable law (including, where necessary, opt-in and opt-out functionalities for personal data). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Camunda will use telemetry data subject to applicable law (including, where necessary, opt-in and opt-out functionalities for personal data). | |
- Camunda will use telemetry data subject to applicable law (including opt-in and opt-out functionalities for personal data where necessary). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HanselIdes This should contain all of your edits, and the screenshots - if it feels complete to you, I think it could be pulled out of draft and another technical writer could give a final review. 😄
|
||
- AI Usage: Camunda's AI features, currently available in SaaS only, are clearly labeled as AI features. For Enterprise organizations, these features must be enabled by the customer via opt-in in the [Console](/components/console/manage-organization/enable-alpha-features.md#enable-ai-powered-features). Depending on the feature, they may collect different information. | ||
- Camunda [Docs AI](/components/modeler/web-modeler/advanced-modeling/camunda-docs-ai.md) records the entire conversation to provide ongoing support. | ||
- Camunda [Copilots](/docs/components/early-access/alpha/bpmn-copilot/bpmn-copilot.md) only gather usage telemetry data. Camunda automatically logs all information sent to and from our AI models for system monitoring by a limited set of operators. Camunda will only use the data from free users for product and model improvement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HanselIdes @akeller We have no concept of alpha features in the 8.6 documentation, so to add this back in, I've linked to the /next version of the docs here.
@conceptualshark this looks good to me 👍🏼 |
@HanselIdes I've approved, but put a Hold label on it so it isn't merged too early. @camunda/tech-writers I've tagged you all for a quick check here! This document is approved by legal and so the wording can not be adjusted much, but as I did a lot of moving of content, a second set of eyes for spelling/grammar/etc would be great. I will also be out on Monday/Tuesday, so if this isn't merged today, any assistance there would be appreciated! 👍 |
The preview environment relating to the commit 058c1e1 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4846/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm - I've reviewed it for spelling etc as you requested, and although I would like to change a lot of the wording, I understand it is legal so can't be touched, some formatting I might change, but nothing blocking so certainly good to go as a first iteration 👍 🚀
Description
Resolves #4038
Blocked by
Provides an overview into the data collected by Camunda's products.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).