Skip to content

Conversation

@marvin659
Copy link

The part about testing Fn Server with syslog is outdated. Papertrail does not work the same way anymore. Updated the step to use a local syslog container, which is easier to setup.

@marvin659
Copy link
Author

@dependabot rebase

@marvin659
Copy link
Author

check is stuck

@marvin659 marvin659 closed this Jan 23, 2026
@marvin659 marvin659 reopened this Jan 23, 2026
@marvin659
Copy link
Author

reopen

@marvin659 marvin659 closed this Jan 23, 2026
@marvin659 marvin659 reopened this Jan 23, 2026
**Note:** As of the time of writing, Podman Desktop does not support syslog log driver. The syslog option is only supported when you are running Fn Server in Docker Desktop and Rancher Desktop.
Since we've already created the 'tutorial' app, we'll have to update it using
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: If you have already created an app*

application:
`fn update app`. But before we do that we'll need a syslog server ready to receive log data.
There are multiple options to setup a syslog server for testing. You could look up free online
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we suggest using free syslog servers? this can lead to user data leak.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I think we can remove it. I will fix it.

syslog server, or you could start up a local syslog server. We will show how to run a local syslog
container for our test.
### Run local syslog docker container
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Can we point to official syslog documentation instead of maintaining steps here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Their doc is quite complex and too much details beyond what we need to do: https://www.rsyslog.com/doc/getting_started/index.html so I would like to keep our steps here. It is easier for our users to follow.

But I will add a link to the rsyslog doc if our users want to checkout more details.

`syslog_url` looks to be pointing to Papertrail so let's rerun our failing
function:
`syslog_url` looks to be pointing to our syslog container so let's rerun our failing function:
Copy link

@theatul theatul Jan 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: syslog_url` is now pointing*

@marvin659 marvin659 force-pushed the marleung/update-syslog-doc branch from 3e1a7bf to 3b4dcd4 Compare January 27, 2026 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants