You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/cassandra/_dev/build/docs/README.md
+64-1Lines changed: 64 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,70 @@ This integration periodically fetches metrics from [Cassandra](https://cassandra
6
6
7
7
This integration has been tested against `Cassandra version 3.11.11`.
8
8
9
-
### Troubleshooting
9
+
## Steps to Setup Jolokia
10
+
11
+
### Prerequisites
12
+
13
+
- Java Development Kit (JDK) 1.8 or later
14
+
- Apache Cassandra 3.x or 4.x (depending on user's version)
15
+
- Jolokia agent JAR file
16
+
17
+
### Jolokia Setup
18
+
19
+
Follow these steps to set up Jolokia for monitoring Apache Cassandra:
20
+
21
+
1. Download the Jolokia JVM Agent:
22
+
23
+
Visit the [Jolokia official download page](https://repo1.maven.org/maven2/org/jolokia/jolokia-jvm/) to obtain the latest version of the Jolokia JVM agent JAR file. Download the `jolokia-jvm-<jolokia_version>-agent.jar` file.
24
+
25
+
2. Copy the Jolokia Agent to Cassandra's Library Directory:
26
+
27
+
Copy the downloaded `jolokia-jvm-<jolokia_version>-agent.jar` file to the Cassandra library directory on the server where Cassandra is installed.
Replace `/path/to/cassandra/lib/` with the actual path to Cassandra's library directory.
36
+
37
+
3. Configure Cassandra to use the Jolokia Agent:
38
+
39
+
Open the `cassandra-env.sh` file, located in the Cassandra configuration directory, using a text editor, and add the following line at the bottom of the file:
Replace `/path/to/jolokia-jvm-<version>-agent.jar` with the actual path to the Jolokia agent JAR file copied in Step 2. Save the changes and close the `cassandra-env.sh` file.
46
+
47
+
4. Restart Cassandra:
48
+
49
+
Restart the Apache Cassandra service to apply the changes made to the configuration.
50
+
51
+
> Note:
52
+
- Restarting the Apache Cassandra service will temporarily disrupt database connectivity. Ensure that dependent services are designed to handle such interruptions gracefully.
53
+
- Immediately after a restart, Cassandra's performance may be impacted due to cold caches and commit log replay. Allow some time for the system to stabilize.
54
+
- Before restarting Cassandra, ensure that no cluster maintenance tasks are in progress to prevent any unintended consequences.
55
+
- The exact steps will vary based on the installation type, the setup process might differ based on the specific deployment method or environment.
56
+
- Procedures for restarting Cassandra may vary based on user's specific setup and configuration.
57
+
58
+
## Verifying the setup
59
+
60
+
After restarting Cassandra, user can verify that Jolokia is properly set up by accessing the Jolokia endpoint:
61
+
62
+
```
63
+
http://<cassandra-host>:<jolokia_port>/jolokia
64
+
```
65
+
66
+
Replace with the hostname or IP address of user's Cassandra server.
67
+
68
+
If the setup is successful, user should see a JSON response containing information about the available Jolokia operations and the Cassandra instance.
69
+
70
+
User can now use Jolokia to monitor and manage Apache Cassandra cluster.
71
+
72
+
## Troubleshooting
10
73
11
74
- If `log.flags` appears conflicted under the ``logs-*`` data view, this issue can be resolved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``Logs`` data stream.
Copy file name to clipboardExpand all lines: packages/cassandra/docs/README.md
+64-1Lines changed: 64 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,70 @@ This integration periodically fetches metrics from [Cassandra](https://cassandra
6
6
7
7
This integration has been tested against `Cassandra version 3.11.11`.
8
8
9
-
### Troubleshooting
9
+
## Steps to Setup Jolokia
10
+
11
+
### Prerequisites
12
+
13
+
- Java Development Kit (JDK) 1.8 or later
14
+
- Apache Cassandra 3.x or 4.x (depending on user's version)
15
+
- Jolokia agent JAR file
16
+
17
+
### Jolokia Setup
18
+
19
+
Follow these steps to set up Jolokia for monitoring Apache Cassandra:
20
+
21
+
1. Download the Jolokia JVM Agent:
22
+
23
+
Visit the [Jolokia official download page](https://repo1.maven.org/maven2/org/jolokia/jolokia-jvm/) to obtain the latest version of the Jolokia JVM agent JAR file. Download the `jolokia-jvm-<jolokia_version>-agent.jar` file.
24
+
25
+
2. Copy the Jolokia Agent to Cassandra's Library Directory:
26
+
27
+
Copy the downloaded `jolokia-jvm-<jolokia_version>-agent.jar` file to the Cassandra library directory on the server where Cassandra is installed.
Replace `/path/to/cassandra/lib/` with the actual path to Cassandra's library directory.
36
+
37
+
3. Configure Cassandra to use the Jolokia Agent:
38
+
39
+
Open the `cassandra-env.sh` file, located in the Cassandra configuration directory, using a text editor, and add the following line at the bottom of the file:
Replace `/path/to/jolokia-jvm-<version>-agent.jar` with the actual path to the Jolokia agent JAR file copied in Step 2. Save the changes and close the `cassandra-env.sh` file.
46
+
47
+
4. Restart Cassandra:
48
+
49
+
Restart the Apache Cassandra service to apply the changes made to the configuration.
50
+
51
+
> Note:
52
+
- Restarting the Apache Cassandra service will temporarily disrupt database connectivity. Ensure that dependent services are designed to handle such interruptions gracefully.
53
+
- Immediately after a restart, Cassandra's performance may be impacted due to cold caches and commit log replay. Allow some time for the system to stabilize.
54
+
- Before restarting Cassandra, ensure that no cluster maintenance tasks are in progress to prevent any unintended consequences.
55
+
- The exact steps will vary based on the installation type, the setup process might differ based on the specific deployment method or environment.
56
+
- Procedures for restarting Cassandra may vary based on user's specific setup and configuration.
57
+
58
+
## Verifying the setup
59
+
60
+
After restarting Cassandra, user can verify that Jolokia is properly set up by accessing the Jolokia endpoint:
61
+
62
+
```
63
+
http://<cassandra-host>:<jolokia_port>/jolokia
64
+
```
65
+
66
+
Replace with the hostname or IP address of user's Cassandra server.
67
+
68
+
If the setup is successful, user should see a JSON response containing information about the available Jolokia operations and the Cassandra instance.
69
+
70
+
User can now use Jolokia to monitor and manage Apache Cassandra cluster.
71
+
72
+
## Troubleshooting
10
73
11
74
- If `log.flags` appears conflicted under the ``logs-*`` data view, this issue can be resolved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``Logs`` data stream.
0 commit comments