vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If the agent cannot resolve an IP address to a structure (for example, Service, Deployment, Daemonset, and so on), the IP address will be flagged as "unresolved" in the [Ingress and Egress views](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-netsec_policyknp_coms). In addition to resolving these IP addresses in the Ingress and Egress views you can add unresolved IP addresses or CIDR blocks in the Unresolved IP Configuration section of the Configuration page.

IP addresses and CIDR blocks can be associated with an alias and, optionally, set to "allowed" which will allow them to be included in a policy without being remediated each time they are encountered.

Grouping IP addresses with a single alias will not reduce entities in the [Topology map.](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-netsec_policyknp_map)





 Configuring cluster CIDR blocks 

Unresolved IP addresses are flagged as Internal if they are inside the cluster or External if they are outside the cluster. Unknown IP addresses are those where subnet information is incomplete.

To resolve these situations one time for your environment, you can specify cluster and CIDR blocks for clusters in the Cluster CIDR configuration.

You can define Default internal CIDR blocks as well as CIDR blocks for individual clusters. Configurations that are no longer needed can be deleted.
Total disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_disk_total_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used CPU for an instance 

How much CPU is used as a percentage of total CPU available. Only for deployments that have dedicated CPU.



Table 14. Used CPU for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_cpu_used_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 Used JVM heap for a database member of the instance in percent 

How much JVM heap is used as a percentage of total JVM heap is available.



Table 15. Used JVM heap for a database member of the instance in percent metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_jvm_heap_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 Used disk space for an instance 

How much disk your deployment is using.



Table 16. Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_disk_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used memory for an instance 

How much memory your deployment is using.



Table 16. Used memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_memory_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 









 Attributes for segmentation 



 Global Attributes 

The following attributes are available for segmenting all of the metrics.



Table 17. Global Attributes

 Attribute Attribute Name Attribute Description 

 Cloud Type ibm_ctype The cloud type is a value of public, dedicated, or local. 
 Location ibm_location The location of the monitored resource - this can be a region, data center, or global. 
 Resource ibm_resource The resource being measured by the service - typically an identifying name or GUID. 
 Resource Type ibm_resource_type The type of the resource being measured by the service.
* INGESTION_KEY contains the ingestion key active for the IBM Log Analysis instance where you are configuring to forward logs.
* ENDPOINT is the authentication endpoint. The logging agent uses this host to authenticate and get the token to forward logs. You can set a public endpoint logs.REGION.logging.cloud.ibm.com or a private endpoint logs.private.REGION.logging.cloud.ibm.com. Replace REGION with the location of the IBM Log Analysis instance where you are configuring to forward logs.
* NAME_OF_SOURCE contains a human-readable name for the source where you are collecting logs, such as the name of a vsi, for example.
* OTHER_LOG_PATHS define more log paths to be monitored, for example, /path/to/log/folders. By default, /var/log is monitored.
* TAGS define a comma-separated list of tags that you want to attach as metadata to each log record.









 Step 3. Start the logging agent 



 Agent V2 

Complete the following steps to start the logging agent:



1. Set the ingestion key.

logdna-agent -k INGESTION_KEY
2. Start the logdna-agent service by running the following command:

sudo service logdna-agent start



Next, verify that the agent is running.

sudo service logdna-agent status





 Agent V3 

Start the logdna-agent service by running the following command:

sudo systemctl start logdna-agent

Next, verify that the agent is running.

systemctl status logdna-agent







 Appendix. Commands to manage the agent 



 Get the agent version 

logdna-agent --version





 Enable the agent on boot 

sudo systemctl enable logdna-agent





 Check the status of the agent 

systemctl status logdna-agent





 Start the agent 

sudo systemctl start logdna-agent





 Stop the agent 

sudo systemctl stop logdna-agent





 Get a log trace from the agent
How much CPU is used as a percentage of total CPU available. Only for deployments that have dedicated CPU.



Table 9. Used CPU for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_redis_cpu_used_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 Used disk space for an instance 

How much disk your deployment is using in bytes.



Table 10. Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_redis_disk_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used disk space as a percentage of total disk available 

How much disk space is used as a percentage of total disk available



Table 10.5: Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_redis_disk_used_percent 
 Metric Type gauge 
 Value Type PERCENT 
 Segment By Service instance 







 Used memory for an instance 

How much memory your deployment is using in bytes.



Table 11. Used memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_redis_memory_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used memory as a percentage of total memory available 

How much memory is used as a percentage of total memory available



Table 11.5: Used memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_redis_memory_used_percent 
 Metric Type gauge 
 Value Type PERCENT 
 Segment By Service instance 









 Attributes for Segmentation 



 Global Attributes 

The following attributes are available for segmenting all of the metrics listed.



Table 12. Global Attributes Metadata

 Attribute Attribute Name Attribute Description 

 Cloud Type ibm_ctype The cloud type is a value of public, dedicated, or local. 
 Location ibm_location The location of the monitored resource - this may be a region, data center, or global. 
 Resource ibm_resource The resource being measured by the service - typically a identifying name or GUID. 
 Resource Type ibm_resource_type The type of the resource being measured by the service.
The IBM Maximo Application Suite SaaS SRE team performs proactive management and deployment of patches, updates and fixes to the Application, Middleware, Database and O/S layers via a planned Maintenance & Outage Calendar

IBM Cloud Delivery Services employs a defense in depth strategy (DiD) for boundary protection that includes firewalls and encrypted communications for remote connectivity to access the environment. All communications that cross this boundary are controlled and monitored.

The IBM Cloud network ports are protected with firewalls, which serve as intrusion detection (IDS) and intrusion prevention (IPS) agents. Details regarding on IBM Cloud intrusion detection management is IBM Confidential information and covered under IBM Cloud SOC2 compliance (see compliance section below).

All IBM Maximo and TRIRIGA SaaS environments are configured for Anti-Malware (Anti-Virus) protection and Endpoint Detection and Response (EDR) technology with associated telemetry. Status and alerts are monitored continuously.

IBM Trust Center - Enterprise IT Security and Trust: [https://www.ibm.com/trust/security](https://www.ibm.com/trust/security)

Physical Security for AWS Cloud: [https://aws.amazon.com/compliance/data-center/controls/](https://aws.amazon.com/compliance/data-center/controls/)





 Customer Access 

IBM Maximo Application Suite as a Service is a public internet based offering. Customers connect to AWS using HTTPS encryption over the internet

There is no direct link, peering or private cloud option available for the IBM Maximo Application Suite SaaS offering

Every IBM Maximo Application Suite SaaS customer environment is delivered in a single tenant instance of the application, running on the Openshift platform.

All IBM Maximo Application Suite SaaS customers use HTTPS (SSL) encryption (256 bit) at the browser level to access IBM hosted applications. Connections are SHA-2 and TLS v1.2 compatible

IBM obtains and implements externally facing SSL certificates from a trusted Certificate Authority (CA)

All databases use native AES-256 encryption (data is encrypted at rest)

Customers will not have direct access to the operating system, file system or web application server.
new ClientQuotaAlteration.Op("producer_byte_rate", null)));

        admin.alterClientQuotas(Arrays.asList(alteration)).all().get();

    }

}
Show more









 IBM Cloud Activity Tracker events 

Whenever throughput quotas are updated, an Event Streams configuration event is generated, which can be monitored in IBM Cloud® Activity Tracker.

For more information about configuring Activity Tracker events for Event Streams, see the [Activity tracker documentation](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-at_events).
(https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-facet-add-options.png)

Figure 17. Facet options
5. Choose enriched_text.keywords.mentions.text, change the label to Keywords, and then click Apply.

Zoom

![Shows the facet panel where a keyword facet is being added.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-keyword-facet-add.png)

Figure 18. Creating a Keywords-based facet

Remember the JSON representation of the document that you looked at earlier? Now that the Keywords enrichment is applied to the text field, and the documents are reprocessed, any keyword mentions found in the text field are included in the JSON representation of the document.

The field you picked to use for the facet (enriched_text.keywords.mentions.text) reflects where the keyword text is stored in JSON.

"enriched_{field_name}": [
"keywords" :
"mentions" :
"text": "Cloud Pak"
]
]
]
6. The new facet is displayed. You can click a keyword to filter the documents to include only those results that mention the keyword.

Zoom

![Shows how the keyword facet looks.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-keyword-facet-added.png)

Figure 19. Keywords facet
Likewise, if the protocol is HTTPS, then httpsPort must be set, and httpPort must not be set. If the protocol is HTTP_AND_HTTPS, then bothhttpPort and httpsPortmust be set. Akamai has certain limitations on port numbers. See the [FAQs](https://cloud.ibm.com/docs/CDN?topic=CDN-faqsare-there-any-restrictions-on-what-port-numbers-are-allowed) for allowed port numbers.
* uniqueId- (Required) the unique ID of the mapping to which this origin belongs.
* bucketName- (Required for Object Storage only) Bucket name for your S3 Object Storage.
* fileExtension- (Required for Object Storage only) File extensions that are allowed to be cached.



* cacheKeyQueryRule- (Required if being updated) Cache key behavior rules can be updated only for origin paths created after 11/16/17. The following options are available to configure Cache Key behavior:
* include-all - Includes all query arguments default.
* ignore-all - Ignores all query arguments.
* ignore: space separated query-args - Ignores those specific query arguments (for example, ignore: query1 query2).
* include: space separated query-args - Includes those specific query arguments (for example, include: query1 query2).



* dynamicContentAcceleration- (Required for Dynamic Content Acceleration only) Provide the DCA parameters. [DCA container](https://cloud.ibm.com/docs/CDN?topic=CDN-dynamic-content-acceleration-container)



* Return - A collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping_Path.

[Origin path container](https://cloud.ibm.com/docs/CDN?topic=CDN-path-origin-container)



--------------------





 deleteOriginPath 

Deletes and existing origin path for an existing CDN, and for a particular customer.
The default value is 5.
11. Select the Number of retries to attempt. Decide how many times the health check is tried before declaring that the origin health check has failed. Retries are attempted immediately. The default value is 1. TCP monitor type options end with this step. Click Create to save your changes and create the health check. HTTP and HTTPS monitor types have additional options, which follow.
12. Enter the Expected response codes, which are the HTTP response codes or code range of the health check. This value must be between 200-299 with wildcards denoted by an x.
13. Optionally, enter a Response body which is a case-insensitive substring to match against in the response body. If this string is not found, the origin is marked as unhealthy.
14. In the optional Request headers section, you can add and configure HTTP request headers to send in the health check. Enter a header name and value in the fields provided. Click Add request header to configure additional headers.
15. Click Create to save your changes and create the health check.







 Adding an origin pool 

Origin pools group your origins for the load balancer to use. An origin can be either an IP or a hostname. Decide whether you want to create a monitored or unmonitored origin pool. For monitored pools, you must specify the health check to use, and from which subnet the health is monitored. Origin pools exist at the instance level, and can be used by any global load balancer in any DNS zone that is configured in the instance.

Before you begin, keep the following considerations in mind when working with origin pools:



* At least one origin pool is required for each load balancer.
* Origin health monitoring continues even when an origin pool is disabled. To disable health monitoring on an origin, you can disable the origin.
* When creating an origin pool, it can take 1 - 10 minutes for the health check to get initiated, during which time the pool appears in a Critical state.
Use New Relic to monitor Liberty in IBM Cloud 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

New Relic is a third-party service that provides monitoring metrics for your app. For more information on what the New Relic service provides, see [New Relic](http://newrelic.com/java).

According to the [Java agent manual installation documentation](https://docs.newrelic.com/docs/agents/java-agent/installation/install-java-agent), Java apps that are to be monitored by using the New Relic service are typically required to be bundled and configured with a New Relic agent and an account license key. In the IBM Cloud® environment, a New Relic license agreement and account can be obtained by creating a service instance in IBM Cloud. Java apps can then be bound to the New Relic service instance and the Liberty buildpack auto configures the app that is ready to be monitored by the New Relic service. Specifically, the buildpack:



* provides the app with a New Relic agent.
* obtains the app name and license key from the VCAP_APPLICATION and VCAP_SERVICES app environment variables.
* configures the properties and configuration template that is required by the New Relic agent.



See the sample configuration that is generated by the Liberty buildpack for the app:

-javaagent:/home/vcap/app/.new_relic_agent/new_relic_agent-3.12.0.jar
-Dnewrelic.home=/home/vcap/app/.new_relic_agent
-Dnewrelic.config.license_key=123456
-Dnewrelic.config.app_name=myapp
-Dnewrelic.config.log_file_path=../../../../../logs



 Add a user-provided New Relic service
Controlling data usage 

In IBM Log Analysis, you can control the data that is collected and available for analysis through a logging instance. You can define exclusion rules in the UI that apply to data collected in that instance. You can also configure logging agents and customize them to collect and forward specific log data. In addition, you can define an alert that is triggered when the data usage threshold that you define for that logging instance is reached.



 Controlling data by excluding log files through the logging agent 

You can stop logs from being forwarded to your logging instance by customizing the logging agent to exclude any files that you do not want the logging agent to monitor.



* By default, the agent monitors all files with extension .log, and extensionless files under /var/log/.
* You must configure the EXCLUDE parameter in the logging agent configuration file to exclude files that are located in any of the paths that are defined through the logdir parameter.
* To define the files that you want to exclude, you can separate multiple files by using commas. You can use glob patterns. You can also configure specific files.



[Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-exclude_logs_from_agent).





 Controlling data by using exclusion rules 

You can configure exclusion rules through the logging web UI to stop logs from counting against your data usage quota and from being stored for search. For example, you might want to collect and forward all logs from a source to a logging instance. However, you might be interested in a subset of those logs such as error logs.

Logs that are excluded do not count towards your data usage quota. Also, logs that match the exclusion rule are not archived.

When you exclude logs through an exclusion rule, you can choose to Preserve these lines for live-tail and alerting. When you check this option, log lines that match the exclusion rule are shown through the live tail and you can set up an alert for that data.

[Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-exclusion_rules).





 Configuring the usage alert
Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information might include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information, which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
Kubernetes cluster [Adding tags to logs from a Kubernetes cluster](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adding_tagsadding_tags_kube) 
 Linux Ubuntu or Debian [Adding tags to logs from Linux Ubuntu or Debian](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adding_tagsadding_tags_linux) 







 Exclude log files that are monitored by the agent 

You can configure a logging agent to exclude logs that you do not want to monitor through the logging UI.



* You can exclude files that are located in any of the paths that are defined through the logdir parameter in a Linux system or the LOGDNA_EXCLUDE variable in a Kubernetes cluster.
* You can configure multiple files. You separate multiple files by using commas.
* You can use glob patterns to define what you want to exclude.
* You can configure specific files.



For more information, see [Excluding log files through the logging agent](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-exclude_logs_from_agent).