[jira] [Commented] (CASSANDRA-12747) Fix monitoring documentation about DroppedMessage metric

["Stefan Podkowinski (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945758#comment-15945758 ] 

Stefan Podkowinski commented on CASSANDRA-12747:
------------------------------------------------

bq. Any guidelines on the contribution process would allow me to directly propose PR for next small errors I might find while doing my current work.

[~arodrime], thanks for looking to help out with our documentation. Would you be interested to give our new contribution process a try?
https://github.com/apache/cassandra/blob/trunk/doc/source/development/documentation.rst


> Fix monitoring documentation about DroppedMessage metric
> --------------------------------------------------------
>
>                 Key: CASSANDRA-12747
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12747
>             Project: Cassandra
>          Issue Type: Task
>          Components: Documentation and Website
>            Reporter: Alain RODRIGUEZ
>            Priority: Minor
>
> I am currently using the new documentation about monitoring (thanks [~tjake], it is very useful), I noticed that there is an error about DroppedMessage metric: http://cassandra.apache.org/doc/latest/operating/metrics.html?highlight=metrics#droppedmessage-metrics
> {noformat}
> Metric Name: org.apache.cassandra.metrics.DroppedMessages.<MetricName>.<Type>
> JMX MBean: org.apache.cassandra.metrics:type=DroppedMetrics scope=<Type> name=<MetricName>
> {noformat}
> I believe it should be as follow instead:
> {noformat}
> Metric Name: org.apache.cassandra.metrics.DroppedMessage.<MetricName>.<Type>
> JMX MBean: org.apache.cassandra.metrics:type=DroppedMessage scope=<Type> name=<MetricName>
> {noformat}
> So DroppedMessage without the 's' in the first line and 'DroppedMessage' instead of 'DroppedMetrics' in the second one.
> I am not sure on how to fix it by myself. Also since the documentation is living alongside the Cassandra code, what versions should I apply this fix to? 
> Any guidelines on the contribution process would allow me to directly propose PR for next small errors I might find while doing my current work.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)