Hi Janos,

What filter are you referring to? Can you share some screenshot? 

Or are you referring to customizing the Octane connector in order to only retrieve features/stories/epics that match a specific criteria to synchronize with PPM Request? In that case, it requires a customization of the Octane connector code, and even though it's possible (and supported), I'm not aware of customer or partner having done it yet in production.

To get source code of Octane connector, it's this way: https://github.com/MicroFocus/ppm-octane-connector/

To learn more about the connector code structure, it's here: https://github.com/MicroFocus/ppm-agileSDK-home/wiki/Intro_Overview

Hello Etienne,

yes, we just want to filter on a specific criteria. We plan to add an attribute in Octane (i.e. Sync to PPM Y/N) and filter on that.

I've already downloaded the sources from github, I was a bit worried because the compatibility to 10.0.2 (we running 23.4). 

I'll extend the connector and add a filter.

Thank you!

Greetings

János

Hello Etienne,

my filtering is ready, but I needed to add System.outs because the logger activation does not work (com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL = com.ppm.integration.agilesdk.connector.octane, DEBUG).

Do you know if the logger can be activated even when it's processed by the ppmLightService?

Greetings

Jánostail 

Hi,

How exactly are you logging your statements in the octane connector code? How did you create the logger object? 

And do your logs appear in PPM logs if you create them with ERROR or STATUS logging level?

Hi Etienne,

logger.error is also not printed - weird.

I use:

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
...

private Logger logger = LogManager.getLogger(this.getClass().getName())

...
someMethod() {
...
// I used a logString and System.out as workaround...
String logstring = " log text";
logger.info(logstring);

Greetings

János

Hi Janos,

1) Make sure that you have com.kintana.core.logging.SYSTEM_THRESHOLD = DEBUG in logging.conf, by default it's set to ERROR and will discard every log under the system threshold.

2) Instead of using package org.apache.logging.log4 for your Logger and LogManager classes, use com.kintana.core.logging instead (same class names).

I get connector debug logs to appear just fine in PPM Logs with these changes, let me know if it's the same for you.

Hello Etienne,

it works with knta logging - thanks!

Greetings

János