It makes sense to separate the dashboards on a per-project/cluster basis.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
make logstash messages separable by cluster | operations/puppet | production | +1 -1 |
Related Objects
- Mentioned In
- T128787: Reduce Cassandra logstash output
- Mentioned Here
- T128787: Reduce Cassandra logstash output
Event Timeline
Change 278330 had a related patch set uploaded (by Eevans):
make logstash messages separable by cluster
I've queued up https://gerrit.wikimedia.org/r/278330 for next Tuesdays Puppet SWAT (16:00 UTC).
Mentioned in SAL [2016-03-22T16:21:05Z] <urandom> Restarting Cassandra on restbase1007.eqiad.wmnet (canary) : T130393, T128787
Mentioned in SAL [2016-03-22T16:54:55Z] <urandom> Performing rolling restart of AQS Cassandra cluster : T130393, T128787
Mentioned in SAL [2016-03-22T17:03:18Z] <urandom> Rolling restart of AQS Cassandra cluster complete : : T130393, T128787
Mentioned in SAL [2016-03-22T18:39:39Z] <urandom> Rolling restart of Cassandra on maps cluster : T130393, T128787
Mentioned in SAL [2016-03-22T18:41:11Z] <urandom> Aborting restart of Cassandra on maps cluster : T130393, T128787
Mentioned in SAL [2016-03-22T19:53:30Z] <urandom> Rolling restart of RESTBase Cassandra cluster : T130393, T128787
Mentioned in SAL [2016-03-22T20:45:38Z] <urandom> Rolling restart of RESTBase Cassandra cluster complete : T130393, T128787
Separate dashboards for Maps and AQS have been created using the new cluster log attribute:
https://logstash.wikimedia.org/#/dashboard/elasticsearch/analytics-cassandra
https://logstash.wikimedia.org/#/dashboard/elasticsearch/maps-cassandra