2.5.00 enhancements

For more information, see the following links:

• Changing data retention for multiple data collectors
• Creating data collectors (from here, navigate to the desired data collector type.)

ENTERPRISE READY  

Back to top

INTEGRATION ENTERPRISE READY AUTOMATION

Back to top

INTEGRATION DATA COLLECTION  

Back to top

To be able to collect JSON data, while creating the data collector, you need to manually select one of the preceding data patterns.

By using these data patterns, you can extract key-value pairs and nested objects available in the data as fields (name=value pairs). These fields can enhance your search capabilities.

This feature is available with Collection Agent versions 2.5 and later.

For more information, see Assigning the data pattern and date format.

DATA COLLECTION INTEGRATION

Back to top

You can also protect the indexed data from potential data loss by enabling index replication. Index replication involves storing multiple copies of the data indexed. This means if an Indexer goes down, possibilities of losing the indexed data is minimized. For more information, see Indexer redundancy.

ENTERPRISE READY

Back to top

This capability helps you specify multiple directories as input to the data collector instead of listing each file separately. The same feature is also available while adding data collector templates in a collection profile.

The following wildcards are supported:

• The ? wildcard matches a single character
• The * wildcard matches zero or more characters
• The ** wildcard sequence matches a partial path or includes subdirectories depending on where you place the wildcard in the path.

For more information, see Using wildcards in the directory path.

Note that with this enhancement, the Include subdirectories check box is no longer available while you are creating the following data collectors. Instead, you can specify the ** wildcard sequence at the end of the directory path to collect data from subdirectories.

• Monitor file on Collection Agent
• Monitor file over Windows share
• Monitor file over SSH
  (With this release, you can add a data collector template of this type. This feature was not available in previous releases.
  For more information, see Setting up bulk data collectors.)

This capability of using wildcards in the directory path is only available with Collection Agent versions 2.5 and later. However, the capability of collecting data from subdirectories by specifying a ** wildcard sequence is available even with Collection Agent versions earlier than 2.5.

DATA COLLECTION  EASE OF USE   

Back to top

At a high level, this version provides a list of new commands that help you achieve tasks related to enabling Indexer redundancy and administering indexers in the cluster.

The following table describes the new commands :

EASE OF USE ENTERPRISE READY AUTOMATION

Back to top

The following data collector template types are supported:

• Monitor file over SSH
• Monitor local Windows events
• Monitor remote Windows events
• Monitor script output on Collection Agent
• Monitor script output over SSH
• Receive over HTTP/HTTPS

For more information, see Creating a collection profile.

 ENTERPRISE READY DATA COLLECTION

Back to top

ENTERPRISE READY

Back to top

The changes and improvements are summarized as follows:

• Improved usability for components imported via a content pack, these are summarized as follows:
  
  • Make copies of components included in content packs.
  • Use saved searches imported via a content pack in notifications and dashboards.
  • Easily identify components imported via a content pack.
• Support for versioning content packs.
• Components imported via a content pack cannot be modified.
• Content packs that are imported cannot be renamed.

For more information, see Managing content packs.

ENTERPRISE READY  EASE OF USE  

Back to top

The enhancements are listed as follows:

• You can add dashboards and notifications based on saved searches that are public (shared by other users) and imported via content packs.
• You can clone dashboards and collection profiles.
• You can view details of dashlets and saved searches.
• You can sort and search by the source details on the Saved Searches page, Data Patterns page, and Collection Profiles page.
• As compared to earlier versions, creation (or export) of content packs is simplified.
• You can identify the source of the saved search by looking at the source details on the Saved Searches page.
  This enhancement can be useful in the scenario of duplicate saved searches. Duplicate saved searches can occur when saved searches created by you, public saved searches (shared by other users), and saved searches imported via a content pack share the same name.
• During dashlet or notification creation, while selecting a saved search, you can find saved searches by specifying any portion of the saved search name (including the source details displayed in the name). Similarly, while adding a data collector or collection profile, while selecting a data pattern, you can find data patterns by specifying any portion of the data pattern name (including the content pack name).
• You can clone collection profiles and dashboards imported via a content pack.
  (Capability for cloning data patterns and saved searches is already available.)
• Earlier components imported via a content pack were prefixed by the content pack name. With this release, the components are instead suffixed with the content pack name in square brackets.
• Data collectors created by using collection profiles use the following naming convention. This naming convention provides information about the collection profile name and the content pack name.
  
  • If the collection profile is created by a user: <collectionProfileName>_<dataCollectorTemplateName>_<hostName>.
    Example: A data collector created by using the collection profile, "CollP1", associated with the host, "HostA" and using the data collector template, "DCT1" is named as "CollP1_DCT1_HostA".
  • If the collection profile is imported via a content pack: <collectionProfileName> [contentPackName]_<dataCollectorTemplateName>_<hostName>.
    Example: A data collector created by using the collection profile, "CollP1", imported via a content pack, "CP1", associated with the host, "HostA" and using the data collector template, "DCT1" is named as "CollP1 [CP1]_DCT1_HostA".

 EASE OF USE  

Back to top