- Cyware Intel Exchange [ti_cyware_intel_exchange]

- Qualys Global AssetView [qualys_gav]

- Cyware Intel Exchange [ti_cyware_intel_exchange]

- Qualys Global AssetView [qualys_gav]

Elastic License 2.0

URL: https://www.elastic.co/licensing/elastic-license

## Acceptance

By using the software, you agree to all of the terms and conditions below.

## Copyright License

The licensor grants you a non-exclusive, royalty-free, worldwide,

non-sublicensable, non-transferable license to use, copy, distribute, make

available, and prepare derivative works of the software, in each case subject to

the limitations and conditions below.

## Limitations

You may not provide the software to third parties as a hosted or managed

service, where the service provides users with access to any substantial set of

the features or functionality of the software.

You may not move, change, disable, or circumvent the license key functionality

in the software, and you may not remove or obscure any functionality in the

software that is protected by the license key.

You may not alter, remove, or obscure any licensing, copyright, or other notices

of the licensor in the software. Any use of the licensor’s trademarks is subject

to applicable law.

## Patents

The licensor grants you a license, under any patent claims the licensor can

license, or becomes able to license, to make, have made, use, sell, offer for

sale, import and have imported the software, in each case subject to the

limitations and conditions in this license. This license does not cover any

patent claims that you cause to be infringed by modifications or additions to

the software. If you or your company make any written claim that the software

infringes or contributes to infringement of any patent, your patent license for

the software granted under these terms ends immediately. If your company makes

such a claim, your patent license ends immediately for work on behalf of your

company.

## Notices

You must ensure that anyone who gets a copy of any part of the software from you

also gets a copy of these terms.

If you modify the software, you must include in any modified copies of the

software prominent notices stating that you have modified the software.

## No Other Rights

These terms do not imply any licenses other than those expressly granted in

these terms.

## Termination

If you use the software in violation of these terms, such use is not licensed,

and your licenses will automatically terminate. If the licensor provides you

with a notice of your violation, and you cease all violation of this license no

later than 30 days after you receive that notice, your licenses will be

reinstated retroactively. However, if you violate these terms after such

reinstatement, any additional violation of these terms will cause your licenses

to terminate automatically and permanently.

## No Liability

*As far as the law allows, the software comes as is, without any warranty or

condition, and the licensor will not be liable to you for any damages arising

out of these terms or the use or nature of the software, under any kind of

legal claim.*

## Definitions

The **licensor** is the entity offering these terms, and the **software** is the

software the licensor makes available under these terms, including any portion

of it.

**you** refers to the individual or entity agreeing to these terms.

**your company** is any legal entity, sole proprietorship, or other kind of

organization that you work for, plus all organizations that have control over,

are under the control of, or are under common control with that

organization. **control** means ownership of substantially all the assets of an

entity, or the power to direct its management and policies by vote, contract, or

otherwise. Control can be direct or indirect.

**your licenses** are all the licenses granted to you for the software under

these terms.

**use** means anything you do with the software requiring one of your licenses.

**trademark** means trademarks, service marks, and similar rights.

- version: "0.1.0"

changes:

- description: Initial draft of the Apache OTel content package

type: enhancement

link: https://github.com/elastic/integrations/pull/14838

The Apache OTEL integration fetches metrics from [Apache](https://httpd.apache.org/) servers.

Use the Apache OTEL integration to collect performance metrics from your Apache servers. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference metrics when troubleshooting performance issues. Apache server exposes metrics through its [status module](http://httpd.apache.org/docs/current/mod/mod_status.html), `mod_status`.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

1. Compatibility and supported versions: This integration is compatible with systems running the upstream OpenTelemetry Collector and Apache server with the `mod_status` module enabled. This integration has been tested with OTEL collector version [v0.129.0](https://github.com/open-telemetry/opentelemetry-collector/tree/v0.129.0), and Apache version 2.4.59.

2. Permissions required: The collector requires access to the Apache server-status endpoint (for example, http://localhost:80/server-status). When running the collector, make sure you have the appropriate permissions to access this endpoint. If that link doesn't work, you may need to enable mod_status in your Apache configuration file.

3. Apache configuration: You'll need to update the block (either in your status module's config file or main Apache config file) that starts with `<Location /server-status>` to specify which IP addresses should have access to the status page. In the example below, we are allowing access from localhost, as well as the IP address x.x.x.x.

4. Finding the Apache config: On Debian-based systems, the status module’s configuration file is typically located at `/etc/apache2/mods-enabled/status.conf`. On other UNIX-like platforms (such as Red Hat–based systems or macOS), you’ll usually find the main configuration file at one of the following paths: `/etc/apache2/apache2.conf`, `/etc/httpd/conf/httpd.conf`, or `/etc/apache2/httpd.conf`.

Within the main configuration file, locate the following line and make sure it is uncommented:

1. Make sure the `mod_status` module is enabled and the server-status endpoint is accessible.

2. Install and configure the EDOT Collector or upstream Collector to export metrics to Elasticsearch, as shown in the following example:

Use this configuration to run the collector.

For a complete list of all available metrics and their detailed descriptions, refer to the [Apache Receiver documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/apachereceiver/documentation.md) in the upstream OpenTelemetry Collector repository.