Remove Prometheus in Cassandra integration

Author: Dlorite

resources/cassandra/INSTALL.md

@@ -1,10 +1,3 @@
-# Prerequisites
-The cassandra exporter generates a high number of metrics. As the Sysdig Agent has a limit of time series that can send to Sysdig Monitor, you have to deploy a Prometheus server and create the recording rules that we provide to filter only the metrics used in dashboards and alerts.
-
-To deploy a Prometheus server you will need:
-* [helm](https://helm.sh/docs/intro/install/)  
-* [helmfile](https://github.com/roboll/helmfile)
-
 # Installing the exporter
 Cassandra expose the metrics with jmx and the exporter gather this metrics and expose them in Prometheus format. Usually jmx is unsecured and it has not user or password. In this case, the best way to deploy it is to add a sidecar with the exporter.
 
@@ -30,23 +23,6 @@ Cassandra expose the metrics with jmx and the exporter gather this metrics and e
         initialDelaySeconds: 180
         timeoutSeconds: 45
 ```
-
-# Installing and configuring Prometheus
-## Installing a new Prometheus with helm
-In this section we will explain how to install and configure a new prometheus server with the recording rules.  
-
-Download the following files: 
-- helmfile.yaml
-- recording_rules.yaml
-- prometheus.yaml
-- prometheus.yml.gotmpl
-
-execute
-
-```
-helmfile sync
-```
-
 # Sysdig Agent configuration
 To use the Sysdig agent, first create the recording rules to scrape only the metrics that will be use in the dashboards.
 

resources/cassandra/README.md

@@ -18,7 +18,7 @@
 * Memory_total
 
 # Number of time series generated
-The metrics filtered are around 600
+The metrics for each instance are around 7k
 
 # Attributions
 Using the [Cassandra exporter](https://github.com/instaclustr/cassandra-exporter) with license Apache 2.0