question

Upvote
Accepted
jeff.waterman avatar image
16 ●2 ●4 ●8

Dacs API not logging usage

First i would like to point out we have tried the suggestions recommended in the POST

How to enable logging usage data in open Dacs API, but with no joy

so any pointers would be appreciated, so code snippet below:

public void ProcessEventStatus(AuthorizationAgentEventStatus eventStatus)

{

bool isRepermissioning = eventStatus.StatusCode == AuthorizationAgentEventStatus.StatusCodeEnum.DoRepermission;

if (isRepermissioning)

{

Logger.Info($"Repermissioning requested for user '{Identity}'.");

}

[...]

CheckSubscription([...], isRepermissioning)

}

private bool CheckSubscription(string service, string ric, long userHandle, byte[] authorizationLock, bool isRepermissioning)

{

AuthorizationRequest.PerformUsageEnum usage = isRepermissioning

? AuthorizationRequest.PerformUsageEnum.OnlyDenialPerformUsageLogging

: _configuration.DefaultUsageLogging; // This is AuthorizationRequest.PerformUsageEnum.AlwaysPerformUsageLogging

AuthorizationAgent.AuthorizationCheckResultEnum authorizationCheckResult = _authorizationAgent.CheckSubscription(

userHandle,

usage,

_authorizationCheckStatus,

new RFA_String(service),

new RFA_String(ric),

authorizationLock.Length,

authorizationLock);

bool result = authorizationCheckResult == AuthorizationAgent.AuthorizationCheckResultEnum.AccessAllowed;

return result;

}

elektronrefinitiv-realtimetrepDACS
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

zoya faberov avatar image   zoya faberov

Hello @jeff.waterman,

I'd like to be sure we are on the same page.

You mention you have read and implemented the multi-step suggestions in "how-to-enable-logging-usage-data-in-open-dacs-api" .

To confirm, you have started with DACS administrator console (you either have access as dacs admin, or you have contacted your organization's marked data group to do so on your behalf) , and have used it enable dacs usage generation on the dacs side and having done so, you have tested the second part, the code side?

And you do not see usage file stored on the dacs side, or does your market data group let you know it does not get created?

The code invocation can only be effective if dacs setup is fully complete and the running dacs process has the permissions to create the usage file according to dacs config, this is what the post you refer to was aiming to describe in detail, this is not just DACS API, so is good to confirm being on the same page?

veerapath.rungruengrayubkul avatar image   veerapath.rungruengrayubkul

@jeff.waterman,

Hi,

Thank you for your participation in the forum. Is the reply below satisfactory in answering your question? If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.

Thanks,

AHS

pimchaya.wongrukun01 avatar image   pimchaya.wongrukun01

Hello @jeff.waterman

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,

AHS

1 Answer

· Write an Answer
Upvote
Accepted
Jirapongse avatar image
79.1k ●250 ●52 ●74

@jeff.waterman

As I know, the configurations in DACS Sink Daemon can also override the settings in Open DACS API.

  • For local DACS Sink Daemon, DACS API controls the size and location of the usage file. However, DACS Daemon can override it by configuring (DACS_SNKD_P2P_USAGE, DACS_SNKD_P2P_USAGE_SIZE)
  • For remote DACS Sink Daemon, DACS API doesn’t create the usage file. DACS Daemon will create dacs.usage when using DACS_SNKD_P2P_USAGE, DACS_SNKD_P2P_USAGE_SIZE

DACS_SNKD_P2P_USAGE

This configuration parameter is used by the DACS Sink Daemon to control the connecting DACS APIs. When this parameter is enabled, the DACS Sink Daemon sends a message to the DACS API which interprets the command to mean that all usage data should be sent to the DACS Sink Daemon, even if the DACS API is configured for usage path / usage size. Set this parameter with the path to where usage data (i.e. dacs.usage / dacs.usage.BAK) should be saved.

DACS_SNKD_P2P_USAGE_SIZE

This configuration parameter is used by the DACS Sink Daemon to control the maximum size in K bytes to which the usage data file can grow. Once this maximum is reached the DACS Sink Daemon sends a message to the DACS Station in order for the DACS Station to collect the usage data. If this parameter is not set but this feature is enabled, then the default value is 512.

You may need to verify the location of DACS Sink Daemon and the DACS configurations (dacs.env) used by DACS Sink Daemon.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.