Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Sep 13, 2021

Datapower syslog - GROK filter for Logstash

Datapower has delimeters in syslog messages, but when certain data is missing from the syslog, delimiters are also missing from the message so it is hard to figure out, what part is missing.


Example:

1. missing: DomainSub, Direction, ClientIP, GlobalTID

- Syslog:

<15>2021-08-20T13:56:31.831414+02:00 \\DP-TES\Domain1 [0x80e003ca][network][debug] xmlmgr(default): trans(4806034): Attempting TCP connect to ClientIP.


- Pattern:

%{TIMESTAMP_ISO8601:Time} \\\\%{GREEDYDATA:Device}\\%{GREEDYDATA:Domain} \[%{GREEDYDATA:MessageCode}\]\[%{GREEDYDATA:Category}\]\[%{GREEDYDATA:Severity}\] %{GREEDYDATA:ObjectType}\(%{GREEDYDATA:ObjectName}\): trans\(%{INT:TransactionID}\): %{GREEDYDATA:Message}

2. missing: Direction

- Syslog:

<14>2021-08-25T15:30:04.617934+02:00 \\\DP-TES\Domain1 [Domain1][0x80e0015b][network][info] mpgw(MPGW-Test): trans(16644771)[112.21.12.122] gtid(8b94ee1a612645dc00fdfaa3): HTTP response code 200 for 'https://CalloutDestination:915/Service1'


- Pattern:

%{TIMESTAMP_ISO8601:Time} \\\\%{GREEDYDATA:Device}\\%{GREEDYDATA:Domain} \[%{GREEDYDATA:DomainSub}\]\[%{GREEDYDATA:MessageCode}\]\[%{GREEDYDATA:Category}\]\[%{GREEDYDATA:Severity}\] %{GREEDYDATA:ObjectType}\(%{GREEDYDATA:ObjectName}\): trans\(%{INT:TransactionID}\)\[%{GREEDYDATA:ClientIP}\] gtid\(%{GREEDYDATA:GlobalTID}\): %{GREEDYDATA:Message}


Idea priority Low
  • Guest
    Nov 29, 2021

    Hello,

    my final filters (I couldn't join these two, so i left them seperate):


    firstFilter ^(<%{INT:PRIORITY}>)?%{TIMESTAMP_ISO8601:Time} \\\\%{GREEDYDATA:Device}\\%{GREEDYDATA:Domain} (\[%{USERNAME:DomainSub}\])?\[(%{BASE16NUM:MessageCode})?\]\[%{USERNAME:Category}\]\[%{LOGLEVEL:Severity}\]( %{DATA:ObjectType}\(%{DATA:ObjectName}\):)? (trans\(%{INT:TransactionID}\))?(\[%{WORD:Direction}\])?(\[%{IP:ClientIP}\])?( gtid\(%{BASE16NUM:GlobalTID}\))?: %{GREEDYDATA:Message}

    secondFilter ^(<%{INT:PRIORITY}>)?%{TIMESTAMP_ISO8601:Time} \\\\%{GREEDYDATA:Device}\\%{GREEDYDATA:Domain} (\[%{USERNAME:DomainSub}\])?\[(%{BASE16NUM:MessageCode})?\]\[%{USERNAME:Category}\]\[%{LOGLEVEL:Severity}\]( %{DATA:ObjectType}\(%{DATA:ObjectName}\):)? (trans\(%{INT:TransactionID}\))?(\[%{WORD:Direction}\])?(\[%{IP:ClientIP}\])?( gtid\(%{BASE16NUM:GlobalTID}\))?%{GREEDYDATA:Message}


    That is all for now, I will focus on other tasks.

  • Guest
    Nov 2, 2021

    Hi,


    It seems this task is doable. I tried merging all the filters into one, so far I have come the pattern below - it still needs a few corrections, but it mostly works fine. "\\Device\Domain" format is needed as Local Identifier in DP Log target for this to work):


    %{TIMESTAMP_ISO8601:Time} \\\\%{GREEDYDATA:Device}\\%{GREEDYDATA:Domain} (\[%{GREEDYDATA:DomainSub}\])?\[%{GREEDYDATA:MessageCode}\]\[%{GREEDYDATA:Category}\]\[%{GREEDYDATA:Severity}\]( %{GREEDYDATA:ObjectType}\(%{GREEDYDATA:ObjectName}\):)? trans\(%{INT:TransactionID}\)(\[%{WORD:Direction}\])?(\[%{GREEDYDATA:ClientIP}\])?( gtid\(%{GREEDYDATA:GlobalTID}\))?: %{GREEDYDATA:Message}


    To be continued...