0

I run a couple of nodejs APPS in cloud foundry on IBM cloud. I wanted to integrate all this in logDNA so I setup a logDNA instance.

1 - I did NOT configure any source as is described in the help (adding agents etc). Still logs started to appear from my cloudant services and my nodejs Apps. System logs apparently. Wondering why... Is the agent by default in the buildpack or something like this?

2 - Now I also wanted to add nodejs APP logs. So I followed: https://github.com/logdna/nodejs and added the following code in my app: 

var Logger = require('logdna');
var options = {
    //hostname: ,
    //logdna_url: "https://logs.eu-de.logging.cloud.ibm.com",
    //mac: macAddress,
    //env: "Development"

};
const apikey = "MY KEY"; //my REAL key ;-)
var logger = Logger.createLogger(apikey, options);
logger.log('Starting APP');

But I never got any APP logs in the logdna instance. Only the platform logs. I tried many different options, never got it to work.

Any idea anyone?

BobDenis
  • 33
  • 6
  • There is Activity Tracker with LogDNA (audit) and Log Analysis with LogDNA (diagnostics). Are you sure you checked the right one? – data_henrik Jun 08 '20 at 16:47
  • I enabled both of these. In Activity Tracker I see the IAM authentications, and in Log Analysis I see the log entries. But I see my APP level logs in none... To start I am wondering why they don't specify to enter any kind of enpoint. The logdna_url above is smtg I saw in an example somewhere but it is not even in the basic usage example. In other words: I don't even understand how it could work, but I don't see a guide... ;-) – BobDenis Jun 08 '20 at 16:53
  • just to be sure, i see the logdna_url in options is commented; it should look something like logdna_url : 'https://logs.us-south.logging.cloud.ibm.com/logs/ingest' – Milan Jun 12 '20 at 15:54

2 Answers2

0

My understanding is that you don't need any LogDNA-specific in your code. You use the regular Cloud Foundry app logging. With the app in place, you would configure "syslog drain". Follow the instructions how to configure Log Analysis with LogDNA for Cloud Foundry apps. There are roughly 3 steps involved, including setting up a user-provided service, binding it to the app and restaging the app:

 ibmcloud cf cups SVC_INSTANCE_NAME -l syslog-tls://SYSLOG_ENDPOINT_URL:PORT_NUMBER

 ibmcloud cf bind-service CF_APP_NAME SVC_INSTANCE_NAME

 ibmcloud cf restage CF_APP_NAME
data_henrik
  • 16,724
  • 2
  • 28
  • 49
  • So far I didn't do any of these steps and I get the logs. I believe CUPS is for user provided instances and in my case I am using logDNA with cloud Foundry infra so not sure I need cups. In the IBM cloud logDNA service GUI I selected the service platform that should send logs, so behind the scene it is probably already connecting the instance. – BobDenis Jun 09 '20 at 08:42
  • @BobDenis you wrote: ...and I get the logs. It sounds like your problem has been resolved? Can you describe the steps taken? – Powell Quiring Jun 13 '20 at 15:53
0

So this is how it works now: - I only configured the "configure platform logs" in the GUI. - I did not add a CUPS instance. I tried it (as described in the docs by provisionning a syslog port) but it did not bring anything new, I actually started to get a log of rubbish logs.... SO I removed that CUPS instance. Not too sure what this is for.

--> I am getting the platform logs, and I also see any console.log entries.

I then also finally got logDNA nodejs package to work. The culprit was the lodDNA URL as @Milan pointed out. I had tried several, but the one that worked in the end was: logdna_url: "https://logs.eu-de.logging.cloud.ibm.com/logs/ingest"

BobDenis
  • 33
  • 6