Skip to content

Editorial around usage reporting in ServicePulse - #8515

Open
helenktsai wants to merge 2 commits into
masterfrom
usage-config
Open

helenktsai wants to merge 2 commits into
masterfrom
usage-config

Conversation

@helenktsai

Copy link
Copy Markdown
Member

No description provided.

Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Comment thread servicepulse/usage-reporting-setup.md Outdated
Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Comment thread servicepulse/usage-reporting-with-servicepulse.md Outdated
Co-Authored-By: Helen T <35390871+helenktsai@users.noreply.github.com>
Co-Authored-By: Jayanthi <jayanthi.sourirajan@particular.net>

A usage report is a file generated by ServicePulse that shows messaging throughput of a system based on identified NServiceBus endpoints and the throughput of their corresponding queues. To enable this functionality in ServicePulse, [usage reporting setup](/servicepulse/usage-reporting-setup.md) must be completed first. Once configured, no ongoing maintenance is needed, and the Usage page will display throughput for each queue detected.

After at least 24 hours of data is collected, the report can be downloaded from the Usage page. This is needed when licensing the Particular Platform. Particular Software does not automatically have access to this report; it is typically requested at license renewal time and must be downloaded and sent manually. Before submitting the report, [sensitive data can be masked](usage-reporting-setup.md#report-masks) and queues that do not map to NServiceBus endpoints (and therefore, do not count toward licensing) can be marked as such.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Removing some information that is also on the Downloading the report section

Suggested change
After at least 24 hours of data is collected, the report can be downloaded from the Usage page. This is needed when licensing the Particular Platform. Particular Software does not automatically have access to this report; it is typically requested at license renewal time and must be downloaded and sent manually. Before submitting the report, [sensitive data can be masked](usage-reporting-setup.md#report-masks) and queues that do not map to NServiceBus endpoints (and therefore, do not count toward licensing) can be marked as such.
This report is needed when licensing the Particular Platform and must be downloaded and sent manually. Before submitting the report, [sensitive data can be masked](usage-reporting-setup.md#report-masks) and queues that do not map to NServiceBus endpoints (and therefore, do not count toward licensing) can be marked as such.


### Detected endpoint queues

All detected endpoint queues have a clear connection to an NServiceBus endpoint which counts toward licensing. However, these can be marked to indicate if they correspond to a [type of endpoint that should not count toward licensing](#endpoint-type-indicators).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: This feels a bit disjointed

Suggested change
All detected endpoint queues have a clear connection to an NServiceBus endpoint which counts toward licensing. However, these can be marked to indicate if they correspond to a [type of endpoint that should not count toward licensing](#endpoint-type-indicators).
This list correspond to all endpoint queues that have a clear connection to an NServiceBus endpoint which counts toward licensing. However, these can be marked to indicate if they correspond to a [type of endpoint that should not count toward licensing](#endpoint-type-indicators).


## Downloading a usage report

Click `Download Report` from ServicePulse to generate a usage report JSON file with the detected [endpoint queues](#viewing-usage-data-in-servicepulse-detected-endpoint-queues) and [broker queues](#viewing-usage-data-in-servicepulse-detected-broker-queues). The report includes the [endpoint type](#endpoint-type-indicators) selections made on screen, and any specified [words to mask](usage-reporting-setup.md#report-masks) will be obfuscated.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Adding more words

Suggested change
Click `Download Report` from ServicePulse to generate a usage report JSON file with the detected [endpoint queues](#viewing-usage-data-in-servicepulse-detected-endpoint-queues) and [broker queues](#viewing-usage-data-in-servicepulse-detected-broker-queues). The report includes the [endpoint type](#endpoint-type-indicators) selections made on screen, and any specified [words to mask](usage-reporting-setup.md#report-masks) will be obfuscated.
Click `Download Report` to generate a usage report as a JSON file. This report contains the queues from both the [detected endpoint queues](#viewing-usage-data-in-servicepulse-detected-endpoint-queues) and [detected broker queues](#viewing-usage-data-in-servicepulse-detected-broker-queues) tabs. The report also includes the [endpoint type](#endpoint-type-indicators) selections made on screen, and any specified [words to mask](usage-reporting-setup.md#report-masks) will be obfuscated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants