From 8eb84d1d1575af08f59fd831062b14289842710f Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Wed, 23 Aug 2023 18:30:24 +0530 Subject: [PATCH 1/6] Resolve the confrict in host.ip field --- .../_dev/build/docs/README.md | 97 +++++++++++++++++ .../changelog.yml | 5 + .../data_stream/jdbc/fields/ecs.yml | 2 + .../data_stream/servlet/fields/ecs.yml | 2 + .../session_manager/fields/ecs.yml | 2 + .../data_stream/threadpool/fields/ecs.yml | 2 + .../docs/README.md | 101 ++++++++++++++++++ .../websphere_application_server/manifest.yml | 2 +- 8 files changed, 212 insertions(+), 1 deletion(-) diff --git a/packages/websphere_application_server/_dev/build/docs/README.md b/packages/websphere_application_server/_dev/build/docs/README.md index 44d2c8c29bb..b6759fd619e 100644 --- a/packages/websphere_application_server/_dev/build/docs/README.md +++ b/packages/websphere_application_server/_dev/build/docs/README.md @@ -11,6 +11,103 @@ This integration uses Prometheus to collect above metrics. To open Prometheus endpoint read following [instructions](https://www.ibm.com/docs/en/was/9.0.5?topic=mosh-displaying-pmi-metrics-in-prometheus-format-metrics-app). +### Troubleshooting + +Conflicts in any field in any data stream can be solved by reindexing the data. +If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. + +To reindex the data for a particular data stream, the following steps must be performed. + +1. Stop the data stream by going to `Integrations -> WebSphere Application Server -> Integration policies` open the configuration of WebSphere Application Server and disable the `Collect WebSphere Application Server metrics` toggle to reindex metrics data stream and save the integration. + +2. Copy data into the temporary index and delete the existing data stream and index template by performing the following steps in the Dev tools. + +``` +POST _reindex +{ + "source": { + "index": "" + }, + "dest": { + "index": "temp_index" + } +} +``` +Example: +``` +POST _reindex +{ + "source": { + "index": "metrics-websphere_application_server.jdbc-default" + }, + "dest": { + "index": "temp_index" + } +} +``` + +``` +DELETE /_data_stream/ +``` + +Example: +``` +DELETE /_data_stream/metrics-websphere_application_server.jdbc-default +``` + +``` +DELETE _index_template/ +``` + +Example: +``` +DELETE _index_template/metrics-websphere_application_server.jdbc +``` + +3. Go to `Integrations -> WebSphere Application Server -> Settings` and click on `Reinstall WebSphere Application Server`. + +4. Copy data from temporary index to new index by performing the following steps in the Dev tools. + +``` +POST _reindex +{ + "conflicts": "proceed", + "source": { + "index": "temp_index" + }, + "dest": { + "index": "", + "op_type": "create" + } +} +``` +Example: +``` +POST _reindex +{ + "conflicts": "proceed", + "source": { + "index": "temp_index" + }, + "dest": { + "index": "metrics-websphere_application_server.jdbc-default", + "op_type": "create" + } +} +``` + +5. Verify data is reindexed completely. + +6. Start the data stream by going to the `Integrations -> WebSphere Application Server -> Integration policies`, open configuration of integration, enable the `Collect WebSphere Application Server metrics` toggle and save the integration. + +7. Delete temporary index by performing the following step in the Dev tools. + +``` +DELETE temp_index +``` + +More details about reindexing can be found [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html). + ## JDBC This data stream collects JDBC (Java Database Connectivity) related metrics. diff --git a/packages/websphere_application_server/changelog.yml b/packages/websphere_application_server/changelog.yml index 448acfa518b..809e286859a 100644 --- a/packages/websphere_application_server/changelog.yml +++ b/packages/websphere_application_server/changelog.yml @@ -1,4 +1,9 @@ # newer versions go on top +- version: "0.7.1" + changes: + - description: Resolve the conflict in host.ip field. + type: bugfix + link: https://github.com/elastic/integrations/pull/1 #FIX ME - version: "0.7.0" changes: - description: Rename ownership from obs-service-integrations to obs-infraobs-integrations diff --git a/packages/websphere_application_server/data_stream/jdbc/fields/ecs.yml b/packages/websphere_application_server/data_stream/jdbc/fields/ecs.yml index 392e2eb7c5a..7bf8e76ce5b 100644 --- a/packages/websphere_application_server/data_stream/jdbc/fields/ecs.yml +++ b/packages/websphere_application_server/data_stream/jdbc/fields/ecs.yml @@ -1,5 +1,7 @@ - external: ecs name: ecs.version +- external: ecs + name: host.ip - external: ecs name: server.address - external: ecs diff --git a/packages/websphere_application_server/data_stream/servlet/fields/ecs.yml b/packages/websphere_application_server/data_stream/servlet/fields/ecs.yml index 95994b26bcb..ffd8ccfb54d 100644 --- a/packages/websphere_application_server/data_stream/servlet/fields/ecs.yml +++ b/packages/websphere_application_server/data_stream/servlet/fields/ecs.yml @@ -1,5 +1,7 @@ - external: ecs name: ecs.version +- external: ecs + name: host.ip - external: ecs name: server.address - external: ecs diff --git a/packages/websphere_application_server/data_stream/session_manager/fields/ecs.yml b/packages/websphere_application_server/data_stream/session_manager/fields/ecs.yml index 392e2eb7c5a..7bf8e76ce5b 100644 --- a/packages/websphere_application_server/data_stream/session_manager/fields/ecs.yml +++ b/packages/websphere_application_server/data_stream/session_manager/fields/ecs.yml @@ -1,5 +1,7 @@ - external: ecs name: ecs.version +- external: ecs + name: host.ip - external: ecs name: server.address - external: ecs diff --git a/packages/websphere_application_server/data_stream/threadpool/fields/ecs.yml b/packages/websphere_application_server/data_stream/threadpool/fields/ecs.yml index 392e2eb7c5a..7bf8e76ce5b 100644 --- a/packages/websphere_application_server/data_stream/threadpool/fields/ecs.yml +++ b/packages/websphere_application_server/data_stream/threadpool/fields/ecs.yml @@ -1,5 +1,7 @@ - external: ecs name: ecs.version +- external: ecs + name: host.ip - external: ecs name: server.address - external: ecs diff --git a/packages/websphere_application_server/docs/README.md b/packages/websphere_application_server/docs/README.md index f18e4b652a3..af5cd85330c 100644 --- a/packages/websphere_application_server/docs/README.md +++ b/packages/websphere_application_server/docs/README.md @@ -11,6 +11,103 @@ This integration uses Prometheus to collect above metrics. To open Prometheus endpoint read following [instructions](https://www.ibm.com/docs/en/was/9.0.5?topic=mosh-displaying-pmi-metrics-in-prometheus-format-metrics-app). +### Troubleshooting + +Conflicts in any field in any data stream can be solved by reindexing the data. +If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. + +To reindex the data for a particular data stream, the following steps must be performed. + +1. Stop the data stream by going to `Integrations -> WebSphere Application Server -> Integration policies` open the configuration of WebSphere Application Server and disable the `Collect WebSphere Application Server metrics` toggle to reindex metrics data stream and save the integration. + +2. Copy data into the temporary index and delete the existing data stream and index template by performing the following steps in the Dev tools. + +``` +POST _reindex +{ + "source": { + "index": "" + }, + "dest": { + "index": "temp_index" + } +} +``` +Example: +``` +POST _reindex +{ + "source": { + "index": "metrics-websphere_application_server.jdbc-default" + }, + "dest": { + "index": "temp_index" + } +} +``` + +``` +DELETE /_data_stream/ +``` + +Example: +``` +DELETE /_data_stream/metrics-websphere_application_server.jdbc-default +``` + +``` +DELETE _index_template/ +``` + +Example: +``` +DELETE _index_template/metrics-websphere_application_server.jdbc +``` + +3. Go to `Integrations -> WebSphere Application Server -> Settings` and click on `Reinstall WebSphere Application Server`. + +4. Copy data from temporary index to new index by performing the following steps in the Dev tools. + +``` +POST _reindex +{ + "conflicts": "proceed", + "source": { + "index": "temp_index" + }, + "dest": { + "index": "", + "op_type": "create" + } +} +``` +Example: +``` +POST _reindex +{ + "conflicts": "proceed", + "source": { + "index": "temp_index" + }, + "dest": { + "index": "metrics-websphere_application_server.jdbc-default", + "op_type": "create" + } +} +``` + +5. Verify data is reindexed completely. + +6. Start the data stream by going to the `Integrations -> WebSphere Application Server -> Integration policies`, open configuration of integration, enable the `Collect WebSphere Application Server metrics` toggle and save the integration. + +7. Delete temporary index by performing the following step in the Dev tools. + +``` +DELETE temp_index +``` + +More details about reindexing can be found [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html). + ## JDBC This data stream collects JDBC (Java Database Connectivity) related metrics. @@ -128,6 +225,7 @@ An example event for `jdbc` looks as following: | event.kind | Event kind | constant_keyword | | event.module | Event module | constant_keyword | | event.type | Event type | constant_keyword | +| host.ip | Host ip addresses. | ip | | server.address | Some event server addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. | keyword | | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword | | service.type | The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`. | keyword | @@ -253,6 +351,7 @@ An example event for `servlet` looks as following: | event.kind | Event kind | constant_keyword | | event.module | Event module | constant_keyword | | event.type | Event type | constant_keyword | +| host.ip | Host ip addresses. | ip | | server.address | Some event server addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. | keyword | | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword | | service.type | The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`. | keyword | @@ -403,6 +502,7 @@ An example event for `session_manager` looks as following: | event.kind | Event kind | constant_keyword | | event.module | Event module | constant_keyword | | event.type | Event type | constant_keyword | +| host.ip | Host ip addresses. | ip | | server.address | Some event server addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. | keyword | | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword | | service.type | The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`. | keyword | @@ -540,6 +640,7 @@ An example event for `threadpool` looks as following: | event.kind | Event kind | constant_keyword | | event.module | Event module | constant_keyword | | event.type | Event type | constant_keyword | +| host.ip | Host ip addresses. | ip | | server.address | Some event server addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. | keyword | | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword | | service.type | The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`. | keyword | diff --git a/packages/websphere_application_server/manifest.yml b/packages/websphere_application_server/manifest.yml index 5a3e807e7f8..f4307b18f39 100644 --- a/packages/websphere_application_server/manifest.yml +++ b/packages/websphere_application_server/manifest.yml @@ -1,7 +1,7 @@ format_version: 1.0.0 name: websphere_application_server title: WebSphere Application Server -version: "0.7.0" +version: "0.7.1" license: basic description: Collects metrics from IBM WebSphere Application Server with Elastic Agent. type: integration From eac6a6363e340f83a44763744a21ec5823535dfa Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Wed, 23 Aug 2023 18:36:20 +0530 Subject: [PATCH 2/6] update changelog --- packages/websphere_application_server/changelog.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/websphere_application_server/changelog.yml b/packages/websphere_application_server/changelog.yml index 809e286859a..36c9b66517d 100644 --- a/packages/websphere_application_server/changelog.yml +++ b/packages/websphere_application_server/changelog.yml @@ -3,7 +3,7 @@ changes: - description: Resolve the conflict in host.ip field. type: bugfix - link: https://github.com/elastic/integrations/pull/1 #FIX ME + link: https://github.com/elastic/integrations/pull/7507 - version: "0.7.0" changes: - description: Rename ownership from obs-service-integrations to obs-infraobs-integrations From 0952cc7f99c5839c0875179c759a9fe50d4a7950 Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Tue, 29 Aug 2023 10:34:35 +0530 Subject: [PATCH 3/6] update README --- packages/websphere_application_server/_dev/build/docs/README.md | 1 - packages/websphere_application_server/docs/README.md | 1 - 2 files changed, 2 deletions(-) diff --git a/packages/websphere_application_server/_dev/build/docs/README.md b/packages/websphere_application_server/_dev/build/docs/README.md index b6759fd619e..19cbfde2d9b 100644 --- a/packages/websphere_application_server/_dev/build/docs/README.md +++ b/packages/websphere_application_server/_dev/build/docs/README.md @@ -13,7 +13,6 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do ### Troubleshooting -Conflicts in any field in any data stream can be solved by reindexing the data. If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. To reindex the data for a particular data stream, the following steps must be performed. diff --git a/packages/websphere_application_server/docs/README.md b/packages/websphere_application_server/docs/README.md index af5cd85330c..091afefa1fd 100644 --- a/packages/websphere_application_server/docs/README.md +++ b/packages/websphere_application_server/docs/README.md @@ -13,7 +13,6 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do ### Troubleshooting -Conflicts in any field in any data stream can be solved by reindexing the data. If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. To reindex the data for a particular data stream, the following steps must be performed. From 85d5f75b2e3c78ea868ecf97ccb68efd82549a80 Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Fri, 1 Sep 2023 18:09:45 +0530 Subject: [PATCH 4/6] remove reindexing steps --- .../_dev/build/docs/README.md | 93 +------------------ .../docs/README.md | 93 +------------------ 2 files changed, 4 insertions(+), 182 deletions(-) diff --git a/packages/websphere_application_server/_dev/build/docs/README.md b/packages/websphere_application_server/_dev/build/docs/README.md index 19cbfde2d9b..9e098133725 100644 --- a/packages/websphere_application_server/_dev/build/docs/README.md +++ b/packages/websphere_application_server/_dev/build/docs/README.md @@ -15,97 +15,8 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. -To reindex the data for a particular data stream, the following steps must be performed. - -1. Stop the data stream by going to `Integrations -> WebSphere Application Server -> Integration policies` open the configuration of WebSphere Application Server and disable the `Collect WebSphere Application Server metrics` toggle to reindex metrics data stream and save the integration. - -2. Copy data into the temporary index and delete the existing data stream and index template by performing the following steps in the Dev tools. - -``` -POST _reindex -{ - "source": { - "index": "" - }, - "dest": { - "index": "temp_index" - } -} -``` -Example: -``` -POST _reindex -{ - "source": { - "index": "metrics-websphere_application_server.jdbc-default" - }, - "dest": { - "index": "temp_index" - } -} -``` - -``` -DELETE /_data_stream/ -``` - -Example: -``` -DELETE /_data_stream/metrics-websphere_application_server.jdbc-default -``` - -``` -DELETE _index_template/ -``` - -Example: -``` -DELETE _index_template/metrics-websphere_application_server.jdbc -``` - -3. Go to `Integrations -> WebSphere Application Server -> Settings` and click on `Reinstall WebSphere Application Server`. - -4. Copy data from temporary index to new index by performing the following steps in the Dev tools. - -``` -POST _reindex -{ - "conflicts": "proceed", - "source": { - "index": "temp_index" - }, - "dest": { - "index": "", - "op_type": "create" - } -} -``` -Example: -``` -POST _reindex -{ - "conflicts": "proceed", - "source": { - "index": "temp_index" - }, - "dest": { - "index": "metrics-websphere_application_server.jdbc-default", - "op_type": "create" - } -} -``` - -5. Verify data is reindexed completely. - -6. Start the data stream by going to the `Integrations -> WebSphere Application Server -> Integration policies`, open configuration of integration, enable the `Collect WebSphere Application Server metrics` toggle and save the integration. - -7. Delete temporary index by performing the following step in the Dev tools. - -``` -DELETE temp_index -``` - -More details about reindexing can be found [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html). +Note: +- This [document](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) provides details about reindexing. ## JDBC diff --git a/packages/websphere_application_server/docs/README.md b/packages/websphere_application_server/docs/README.md index 091afefa1fd..5b9b484d9c6 100644 --- a/packages/websphere_application_server/docs/README.md +++ b/packages/websphere_application_server/docs/README.md @@ -15,97 +15,8 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. -To reindex the data for a particular data stream, the following steps must be performed. - -1. Stop the data stream by going to `Integrations -> WebSphere Application Server -> Integration policies` open the configuration of WebSphere Application Server and disable the `Collect WebSphere Application Server metrics` toggle to reindex metrics data stream and save the integration. - -2. Copy data into the temporary index and delete the existing data stream and index template by performing the following steps in the Dev tools. - -``` -POST _reindex -{ - "source": { - "index": "" - }, - "dest": { - "index": "temp_index" - } -} -``` -Example: -``` -POST _reindex -{ - "source": { - "index": "metrics-websphere_application_server.jdbc-default" - }, - "dest": { - "index": "temp_index" - } -} -``` - -``` -DELETE /_data_stream/ -``` - -Example: -``` -DELETE /_data_stream/metrics-websphere_application_server.jdbc-default -``` - -``` -DELETE _index_template/ -``` - -Example: -``` -DELETE _index_template/metrics-websphere_application_server.jdbc -``` - -3. Go to `Integrations -> WebSphere Application Server -> Settings` and click on `Reinstall WebSphere Application Server`. - -4. Copy data from temporary index to new index by performing the following steps in the Dev tools. - -``` -POST _reindex -{ - "conflicts": "proceed", - "source": { - "index": "temp_index" - }, - "dest": { - "index": "", - "op_type": "create" - } -} -``` -Example: -``` -POST _reindex -{ - "conflicts": "proceed", - "source": { - "index": "temp_index" - }, - "dest": { - "index": "metrics-websphere_application_server.jdbc-default", - "op_type": "create" - } -} -``` - -5. Verify data is reindexed completely. - -6. Start the data stream by going to the `Integrations -> WebSphere Application Server -> Integration policies`, open configuration of integration, enable the `Collect WebSphere Application Server metrics` toggle and save the integration. - -7. Delete temporary index by performing the following step in the Dev tools. - -``` -DELETE temp_index -``` - -More details about reindexing can be found [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html). +Note: +- This [document](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) provides details about reindexing. ## JDBC From 10dbe434c1cea9fb20cfb1246212a5697384ea0e Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Mon, 4 Sep 2023 18:07:11 +0530 Subject: [PATCH 5/6] update README --- .../websphere_application_server/_dev/build/docs/README.md | 5 +---- packages/websphere_application_server/docs/README.md | 5 +---- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/packages/websphere_application_server/_dev/build/docs/README.md b/packages/websphere_application_server/_dev/build/docs/README.md index 9e098133725..00eb765dbfc 100644 --- a/packages/websphere_application_server/_dev/build/docs/README.md +++ b/packages/websphere_application_server/_dev/build/docs/README.md @@ -13,10 +13,7 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do ### Troubleshooting -If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. - -Note: -- This [document](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) provides details about reindexing. +If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. ## JDBC diff --git a/packages/websphere_application_server/docs/README.md b/packages/websphere_application_server/docs/README.md index 5b9b484d9c6..4ff1b7431e5 100644 --- a/packages/websphere_application_server/docs/README.md +++ b/packages/websphere_application_server/docs/README.md @@ -13,10 +13,7 @@ To open Prometheus endpoint read following [instructions](https://www.ibm.com/do ### Troubleshooting -If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. - -Note: -- This [document](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) provides details about reindexing. +If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. ## JDBC From 503db5d1faf8b3c55ab04d38577b3f0450f08f77 Mon Sep 17 00:00:00 2001 From: aliabbas-elastic Date: Mon, 4 Sep 2023 18:27:13 +0530 Subject: [PATCH 6/6] revert changes --- .../websphere_application_server/_dev/build/docs/README.md | 4 ++++ packages/websphere_application_server/docs/README.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/packages/websphere_application_server/_dev/build/docs/README.md b/packages/websphere_application_server/_dev/build/docs/README.md index 00eb765dbfc..671b27aaba0 100644 --- a/packages/websphere_application_server/_dev/build/docs/README.md +++ b/packages/websphere_application_server/_dev/build/docs/README.md @@ -11,6 +11,10 @@ This integration uses Prometheus to collect above metrics. To open Prometheus endpoint read following [instructions](https://www.ibm.com/docs/en/was/9.0.5?topic=mosh-displaying-pmi-metrics-in-prometheus-format-metrics-app). +## Compatibility + +This integration has been tested against WebSphere Application Server traditional version `9.0.5.11`. + ### Troubleshooting If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices. diff --git a/packages/websphere_application_server/docs/README.md b/packages/websphere_application_server/docs/README.md index 4ff1b7431e5..64f4be2b0fd 100644 --- a/packages/websphere_application_server/docs/README.md +++ b/packages/websphere_application_server/docs/README.md @@ -11,6 +11,10 @@ This integration uses Prometheus to collect above metrics. To open Prometheus endpoint read following [instructions](https://www.ibm.com/docs/en/was/9.0.5?topic=mosh-displaying-pmi-metrics-in-prometheus-format-metrics-app). +## Compatibility + +This integration has been tested against WebSphere Application Server traditional version `9.0.5.11`. + ### Troubleshooting If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/use-a-data-stream.html#reindex-with-a-data-stream) the ``JDBC``, ``Servlet``, ``Session Manager`` and ``ThreadPool`` data stream's indices.